This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: gdb with gcj
- From: Andrew Haley <aph at redhat dot com>
- To: Vladimir Leven <vladimirl at wrx-ca dot com>
- Cc: Bryce McKinlay <mckinlay at redhat dot com>, java at gcc dot gnu dot org
- Date: Tue, 4 May 2004 11:36:48 +0100
- Subject: Re: gdb with gcj
- References: <40633001.3090605@wrx-ca.com><408935D7.2060600@wrx-ca.com><4092BD19.8060703@wrx-ca.com><4092C034.4080804@redhat.com><16531.43263.820716.740348@cuddles.cambridge.redhat.com><4096937D.7070009@wrx-ca.com>
Vladimir Leven writes:
> (gdb) run
> Starting program: /home/levinv/dev/GcjDebugTest/a.out
> [New Thread 16384 (LWP 2154)]
> [New Thread 32769 (LWP 2155)]
> [New Thread 16386 (LWP 2156)]
> [Switching to Thread 16384 (LWP 2154)]
>
> Breakpoint 1, test.main(java.lang.String[]) (args=@1003bfe8) at test.java:3
> 3 test runme = new test();
> Current language: auto; currently java
> (gdb) step
> 0x30024f60 in __cache_line_size () from /lib/ld.so.1
> [As you can see, I cannot even step through the program without it
> leaving Java mode. On Friday I was able to do that (not sure why), but
> no luck today. ]
You're stepping into the shared library loader to fixup a PLT entry
There's nothing weird or unexpected about this.
When you leave the shared library loader, you should get back to the
main context.
Andrew.