If you are a driver/system developer and need the entire set of symbols for Windows Server 2003, Windows XP, or Windows 2000, then you can download a symbol package and install it on your computer. The symbol download packages are listed by CPU type (x86 and Itanium) and build type.
Could this used to more accuratly reverse engineer the Windows APIs/ABIs?
You get global function and variable names for each Windows DLL, EXE, driver and others. I’d be surprised if no WINE developers had picked up on this before, since these symbols have been available since Windows NT came out.
Instead of downloading the symbols package, use the symbols server with KD/WinDbg to download the symbols as needed. It will also automatically match the binaries to the correct symbols so that you don’t have to search for it manually.
Yes, we are aware of them. However, they are not integrated with our debugging tools.
I would guess that their usefulness is somewhat limited though. Most of the time with Wine you have to treat binary only code as an opaque black box. While you can disassemble parts of it if worst comes to worst, generally that’s frustrating and difficult, as well as often unproductive.
Usually it’s possible to fix bugs (which is all it would be useful for) without knowing too much about the native code at all.
Bear in mind that the APIs/ABIs that applications use are already documented and viewable in the exports table. Still, I think I will ask on the list whether anybody has any plans to integrate them with winedbg, every bit of info might help.
all it does is allow you to clarify what you’ve found on your own while using the kernel debugger etc.
I mena, you do read books like “Inside Windows NT”, do you? I
ve found them to be of great assistance.
Cracking just got a whole lot more fun.
Each x86 symbol package may require 750 megabytes (MB) or more of hard disk space, and each Itanium symbol package may require 560 MB or more.
Call me a moron, but why the 200 MB difference between Itanium symbols and x86 symbols? The Itanium versions support fewer syscalls or what?
Me confused
The symbols have always been available for download, what’s new here?
Windows 2003 symbols
Does this make the BSOD more informative when a third party driver decides to crash?
No, but if you set up Windows to make crash dump files and open such a file in Windbg, it will give you full context information (especially useful for the call stack at the time of the crash).
It’s a tool.
You have to know how to use it.
All the wines really don’t understand wnt,
because than they would not try to clone win32.
And that’s okay.
Never tried Windows XP and never will. If I have to upgrade to a proprietary OS from Linux again it will probably be the outsourced OS/2 variant eCom Station. In fact I would even pay SCO for a “Linux License” if they won their case before using the WICKED Windows XP operating system. Doesn’t the very idea behind WinXP ‘product activation’ that you have to accept a NUMBER from a would be ONE WORLD MONOPOLY to use your operating system raise at least a tiny sense of FAMILIARITY with other Bible reading Christians out there besides myself.
Especially Revelation 13 ;-).
WinXP is just plain wicked. It is the beginning of the “Wide Road” leading to THE MARK OF THE BEAST!!! Furthermore here is a another little tidbit of information Microsoft would rather you not hear. “Palladium” the original name for another Microsoft control everything technology is actually the name of a LUCIFERIAN Secret Society founded by the late Confedeate General Albert Pike who was a Satan worshipper and the South’s version of William T. Sherman!!! Microsoft indeed has a LOT more than just crapware and stock “watering” fraud to cover up, and alot to answer for in this world AND THE NEXT!!!
What a load of crap.
Euginia: your moderation policy is utterly random. “Revelation 13?” Come on. Coral Snake’s post is probably the most bizzare flame I’ve seen on this site, yet I expect that post to stay and for this one to be moderated.
Under normal circumstances I would agree with you and the moderator than OS News is not the proper place for Biblical are other Religiously based posts but we aren’t living in normal circumstances. Rather these are the circumstances that computing is being forced to live under.
1. Micro$oft is funding the lawsuit of a near bankrupt company (SCO group) covering it up as a “licensing deal” in order to Kill GNU/Linux the only thing standing between them and total monopoly on non Apple desktop and server computing. (Sorry BSD, you will not be able to develop the mindshare and hardware drivers needed to stand in the way of the Micro$oft monopoly in the timely manner needed to do so if Linux should be banned or legally gutted by the SCO suit.)
2. Palladium or whatever official Micro$oft confusion name it bears today has long been exposed as not only DRM but a way to virtually give Micro$oft control over whatever anyone does with a personal or server computer. Such computers are so prevalant not only on our desktops (or laptops if we use notebooks) but also in banks, retail stores, military and the police that such a control system would give Micro$oft not only money but far more importantly
POWER over all of our lives weather we use such computers or not.
I therefore believe that Micro$oft crossed a line of no return with “product activation” and Palladium. This is the line between a corperation simply interested in making money for its board of directors and stockholders as all businesses should to a criminal organization seeking fascist GOVERNMENT LIKE POWER over us. Under the circumstances I have outlined all of us including OS News should be concerned with the spiritual condition of this company and those running it. The good news in all of this is that if you don’t like George W. Bush you soon won’t have to worry about him. The way things are going Washington DC may soon be replaced with Redmond Washington
and Bush and Cheny replaced with GATES AND BALLMER ;-).