Mail Archives: cygwin/1998/03/02/02:58:02
When trying to trace calls into cygwinb19.dll via the assembly stepi command
you get the following error as soon as you execute one of the 'jmp *xxxxxxxx'
instructions which jump to the actual routine in cygwinb19.dll:
0x2000000: Cannot access memory at address 0x2000000.
Does this have anything to do with that cygwinb19.dll now locates at a much
higher address (0x10000000) as did cygwin.dll in b18 ?
When trying to step into e.g. Kernel32.dll code gdb jumps over it,
but that code is loaded at even higher addresses.
Same behaviour occurs when using the b18 gdb to debug a b19 application.
Under b18 I could step into cygwin.dll code.
Does anybody know what is going on here ?
Ton van Overbeek, tvoverbe AT wk DOT estec DOT esa DOT nl
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".
- Raw text -