Linux - GDB to debug JNI with Tomcat
To debug native code in JNI with GDB, you can do the following
1. Get process ID - first you must know the Java process id for your application
ps -ef | grep java
2. Connect GDB to Java
gdb -p
or
(gdb) attach prog_port
3. If your .so is built with debug information, you should see the following when gdb load the process. To get debug information into your .so, you can use gcc or g++ with -g
Reading symbols from your_debug.so...done.
Loaded symbols for your_debug.so
4. Add your source directory for debugging
(gdb) dir /your/src/path
Below are some abstract from GNU
directory dirname ... dir dirname ...
Add directory dirname to the front of the source path. Several directory names may be given to this command, separated by `:' (`;' on MS-DOS and MS-Windows, where `:' usually appears as part of absolute file names) or whitespace. You may specify a directory that is already in the source path; this moves it forward, so GDB searches it sooner. You can use the string `$cdir' to refer to the compilation directory (if one is recorded), and `$cwd' to refer to the current working directory. `$cwd' is not the same as `.'---the former tracks the current working directory as it changes during your GDB session, while the latter is immediately expanded to the current directory at the time you add an entry to the source path. directory
Reset the source path to empty again. This requires confirmation. show directories
Print the source path: show which directories it contains.
5. Set breakpoint to gdb - the easiest way is to set break point directly to the class::method (eg, YourClass::YourMethod). gdb will locate the corresponding file and set break point to that method
(gdb) break YourClass::YourMethod
You can use the following to list the breakpoints that are set
(gdb) info breakpoints Num Type Disp Enb Address What 2 breakpoint keep y 0x080483c3 in func2 at test.c:5 3 breakpoint keep y 0x080483da in func1 at test.c:10
Info provide you a number. You can use that breakpoint number to ignore/disable/ddelete the breakpoint
(gdb) disable 3
(gdb) ignore 2
(gdb) delete 2
More information on break points http://ftp.gnu.org/old-gnu/Manuals/gdb-5.1.1/html_node/gdb_28.html#SEC29
6. When you attach gdb to tomcat, you may realise that the web application may hang. That is because gdb has taken over the control. To continue the application, type continue at the GDB interface
7. To check a value in your breakpoint, do the following
(gdb) p your_variable
8. - if you see this message, it means that your program is compile with gcc -03 where gcc optimizer think that the variable is redundant and had optimized away
9. Step, Continue, Next - You can use these commands to
s - step to next line
c - continue to run the program
n - to next innermost stack
More information http://www.chemie.fu-berlin.de/chemnet/use/info/gdb/gdb_6.html
Information comes from http://ftp.gnu.org/old-gnu/Manuals/gdb-5.1.1/html_node/gdb_toc.html
1. Get process ID - first you must know the Java process id for your application
ps -ef | grep java
2. Connect GDB to Java
gdb -p
or
(gdb) attach prog_port
3. If your .so is built with debug information, you should see the following when gdb load the process. To get debug information into your .so, you can use gcc or g++ with -g
Reading symbols from your_debug.so...done.
Loaded symbols for your_debug.so
4. Add your source directory for debugging
(gdb) dir /your/src/path
Below are some abstract from GNU
directory dirname ... dir dirname ...
Add directory dirname to the front of the source path. Several directory names may be given to this command, separated by `:' (`;' on MS-DOS and MS-Windows, where `:' usually appears as part of absolute file names) or whitespace. You may specify a directory that is already in the source path; this moves it forward, so GDB searches it sooner. You can use the string `$cdir' to refer to the compilation directory (if one is recorded), and `$cwd' to refer to the current working directory. `$cwd' is not the same as `.'---the former tracks the current working directory as it changes during your GDB session, while the latter is immediately expanded to the current directory at the time you add an entry to the source path. directory
Reset the source path to empty again. This requires confirmation. show directories
Print the source path: show which directories it contains.
5. Set breakpoint to gdb - the easiest way is to set break point directly to the class::method (eg, YourClass::YourMethod). gdb will locate the corresponding file and set break point to that method
(gdb) break YourClass::YourMethod
You can use the following to list the breakpoints that are set
(gdb) info breakpoints Num Type Disp Enb Address What 2 breakpoint keep y 0x080483c3 in func2 at test.c:5 3 breakpoint keep y 0x080483da in func1 at test.c:10
Info provide you a number. You can use that breakpoint number to ignore/disable/ddelete the breakpoint
(gdb) disable 3
(gdb) ignore 2
(gdb) delete 2
More information on break points http://ftp.gnu.org/old-gnu/Manuals/gdb-5.1.1/html_node/gdb_28.html#SEC29
6. When you attach gdb to tomcat, you may realise that the web application may hang. That is because gdb has taken over the control. To continue the application, type continue at the GDB interface
7. To check a value in your breakpoint, do the following
(gdb) p your_variable
8. - if you see this message, it means that your program is compile with gcc -03 where gcc optimizer think that the variable is redundant and had optimized away
9. Step, Continue, Next - You can use these commands to
s - step to next line
c - continue to run the program
n - to next innermost stack
More information http://www.chemie.fu-berlin.de/chemnet/use/info/gdb/gdb_6.html
Information comes from http://ftp.gnu.org/old-gnu/Manuals/gdb-5.1.1/html_node/gdb_toc.html
Comments
Post a Comment