Re: [rvm-research] Debugging with gdb

On 4/29/2013 5:00 PM, Chapple, Julia D wrote:
> Hello,
>
> I’m trying understand Jikes by tracing execution with gdb. However, I haven’t been able to  set any
> breakpoints that would enable me to observe the functions I’m interested in. When I run it initially
> I hit a breakpoint in sys.C. I can then set breakpoints in sys.C and in files in the same folder but
> I can’t set breakpoints in other files. gdb always says there is no source file with that name and
> the break point is set to pending. The pending break points are never hit, even though the code is
> being executed. I’ve tried specifying the files in different ways (including the absolute file path)
> but none of them work.
>
> I’ve also tried using the memory address found in RVM.map. When I do this gdb states: “Error
> accessing memory address 0x5805b7bc: Input/output error.”

You may need to wait on setting breakpoints until the
bootImageReader has read the image in.  I find it convenient
to set a breakpoint where that happens, run to the breakpoint,
and then set additional breakpoints.

People have developed (slightly) more sophisticated methods,
and gdb macros, that help.  Maybe someone else can respond
about that.

Eliot Moss

------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr