Re: debugger fix

[gerard patel]

At 06:24 PM 3/2/01 +0000, you wrote:
<snip>
> however, it would be great if someone else could try Ulrich's patch to see
> if I'm the only one with BAAAAAAAAD results...

I tested Ulrich's patch on current Cvs on a vanilla Suse 7.0 (gcc 2.95.2, binutils 2.9.5)
The patch applied all right, built fine (I had to chmod +x strip_import though).
I can run ForteFreeAgent with the patched Wine; the debugger starts all
right and I can go to a breakpoint using the <dll name in uppercase>.<api>
trick.

Gerard

debugger fix

[Jon Griffiths]

Hi,
> debugger starts all right and I can go to a breakpoint using the <dll name
> in uppercase>.<api> trick.

On a somewhat related note, I'm trying to get the debuggers from lcc and 
visual studio to work. VC is my preference since it will let you bring up a 
release build executable (i.e. any old program), and then set advanced 
breakpoints on dll calls that it makes. It also handles threaded programs 
with ease.

VC currently runs and lets you step through assembly. Both environments need 
some Virtual* calls implemented before they will run properly.

So, does anyone have a hint on how to go about supporting 
VirualProtectEx/VirtualQueryEx on other provesses?

Cheers,
Jon