This is the mail archive of the frysk@sourceware.org mailing list for the frysk project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Debugging a NullPointerException in fstack

Interesting.

I was able to successfully step through the code in gdb but not to print out object contents. I saw things like the following:

(gdb) p pid
$12 = Expected a negative vbase offset (old compiler?)

Also, gdb displayed many warnings along the following lines:

warning: Missing the separate debug info file: /usr/lib/debug/.build- id/fa/841219472d35412ad631ad0f0fabb78e5c1957.debug

warning: Missing the separate debug info file: /usr/lib/debug/.build- id/64/ce37a1b7ee7ce1c23dcfe9344cbb361c321b8f.debug

warning: Missing the separate debug info file: /usr/lib/debug/.build- id/aa/af5e0dff4a6114026fc027a15c895e93e11733.debug

warning: Missing the separate debug info file: /usr/lib/debug/.build- id/91/f8d452c6cc80573296b2bbb28a1dd076b0507f.debug

Ray

On 10-Jun-08, at 10:17 PM, Tom Tromey wrote:

"Ray" == Ray Ruvinskiy <rruvinsk@sybase.com> writes: 

Ray> Is it possible to make it so that when a program compiled with
Ray> gcj throws an exception, the stack trace is displayed, like it
Ray> would be if a jar file is run with Sun's jre?

This should work in general.  I think in some places frysk swallows
exceptions or does not print traces.

Ray> Is there any hope in getting gdb to meaningfully debug
Ray> gcj-compiled binaries?

This should pretty much work.

Tom


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]