When debugging a dll via Attach to local process a breakpoint ist ignored. Console messages are:
attach 3508
[Switching to thread 3508.0xe84]
[Switching to thread 3508.0x5e0]
Cannot access memory at address 0xb5bbd8
Cannot access memory at address 0xb5bbd8
Cannot access memory at address 0xb5bbd8
Cannot access memory at address 0xb5bbd8
Cannot access memory at address 0xb5bbd8
Cannot access memory at address 0xb5bbd8
With Java JRE 1.6.0_06-b02 and wascana-mingw-0.9.3
When debugging with gdb from the command line it works:
C:\Dokumente und Einstellungen\SED>gdb
GNU gdb 5.2.1
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i686-pc-mingw32".
(gdb) attach 3988
Attaching to process 3988
[Switching to thread 3988.0xbc4]
(gdb) break foo.c:15
Breakpoint 1 at 0x1000119c: file ../foo.c, line 15.
(gdb) continue
Continuing.
[Switching to thread 3988.0xb50]
Breakpoint 1, Java_JNIFoo_nativeFoo (env=0x2a54f4, obj=0x90fca4) at ../foo.c:15
15 if(newstring == NULL)
(gdb) continue
Continuing.
Sample Java Code
Logged In: YES
user_id=2125948
Originator: YES
File Added: foo.c
Sample C Code
Sample C Include
Logged In: YES
user_id=2125948
Originator: YES
File Added: JNIFoo.h
Logged In: YES
user_id=2125948
Originator: YES
If JRE 1.5.0_13-b05 is used it works within Wascana, too.