Now that I have IDA nearly sorted, I was wondering.. who maintains the imagehlp dll? It seems kinda empty, and I'm sure it was at one point more complete (I looked into wine some time ago).
I ask this because about a year or so ago I got about 3/4 of the way through reverse engineering the Windows PDB formats (up to those supported by VS.NET). If I had an actual implementation goal in mind and feedback from people using it, I might actually be bothered to finish it off....
Incidentally, I have years of reverse engineering experience.. if anyone wants me to look at anything, feel free to drop me a line (for an example, see the recently released reverse engineered opensource nforce ethernet driver, forcedeth).
Andrew de Quincey adq_dvb@lidskialf.net writes:
Now that I have IDA nearly sorted, I was wondering.. who maintains the imagehlp dll? It seems kinda empty, and I'm sure it was at one point more complete (I looked into wine some time ago).
No, it has always been fairly empty, and nobody has been working on it recently. It's all yours...
Incidentally, I have years of reverse engineering experience.. if anyone wants me to look at anything, feel free to drop me a line (for an example, see the recently released reverse engineered opensource nforce ethernet driver, forcedeth).
Please don't write any code for Wine that would be based on disassembling Windows code.
-----Original Message----- From: wine-devel-admin@winehq.org [mailto:wine-devel-admin@winehq.org]On Behalf Of Alexandre Julliard Sent: 05 December 2003 03:41 To: Andrew de Quincey Cc: 'wine-devel' Subject: Re: Who maintains the imagehlp dll?
Andrew de Quincey adq_dvb@lidskialf.net writes:
Now that I have IDA nearly sorted, I was wondering.. who maintains the imagehlp dll? It seems kinda empty, and I'm sure it was at one
point more
complete (I looked into wine some time ago).
No, it has always been fairly empty, and nobody has been working on it recently. It's all yours...
However, most of it is implemented already in winedbg. It has been a long-term plan to gradually move code from winedbg to imagehlp (or the new and similar debugging DLL, dbghelp). PDB files are also supported in winedbg (so no investigation of the format should be needed). However, I'm not sure whether .dbg files are supported. They could be quite useful when a crash occurs in a native DLL (that doesn't have an associated PDB file) and Wine is the cause.
Rob
--- Robert Shearman R.J.Shearman@warwick.ac.uk wrote:
However, most of it is implemented already in winedbg. It has been a long-term plan to gradually move code from winedbg to imagehlp (or the new and similar debugging DLL, dbghelp). PDB files are also supported in winedbg (so no investigation of the format should be needed). However, I'm not sure whether .dbg files are supported. They could be quite useful when a crash occurs in a native DLL (that doesn't have an associated PDB file) and Wine is the cause.
It would be nice if we could move this code to imagehlp and debughlp so ReactOS can make use of the work.
Thanks Steven
__________________________________ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/
Robert Shearman wrote:
-----Original Message----- From: wine-devel-admin@winehq.org [mailto:wine-devel-admin@winehq.org]On Behalf Of Alexandre Julliard Sent: 05 December 2003 03:41 To: Andrew de Quincey Cc: 'wine-devel' Subject: Re: Who maintains the imagehlp dll?
Andrew de Quincey adq_dvb@lidskialf.net writes:
Now that I have IDA nearly sorted, I was wondering.. who maintains the imagehlp dll? It seems kinda empty, and I'm sure it was at one
point more
complete (I looked into wine some time ago).
No, it has always been fairly empty, and nobody has been working on it recently. It's all yours...
However, most of it is implemented already in winedbg. It has been a long-term plan to gradually move code from winedbg to imagehlp (or the new and similar debugging DLL, dbghelp). PDB files are also supported in winedbg (so no investigation of the format should be needed). However, I'm not sure whether .dbg files are supported.
They are... but it also depends on the MS debugging format used. Ulrich Weigand wrote some support for some formats (NB09, NB10 and N11), but latest formats are not supported.
They could be quite useful when a crash occurs in a native DLL (that doesn't have an associated PDB file) and Wine is the cause.
I started some time ago porting the winedbg stuff inside dbghelp (I have a skeletton from this later DLL). If someone is interested to spend some time on this, I can provide what I have. A+