This is the mail archive of the mailing list for the GDB 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: arm gdbserver and shared object function resolution

my symbols are loading correctly.

What I need to do: Break into the debugger inside a shared object either
remotely or locally - platform is arm.

using 5.2 (the current snapshot was a little flaky..) I am seeing the
following behavior
(Note: arm target)

native arm gdb:
run gdb targeted at app, set break at main - run - set break at function
inside shared object - run
RESULT: gdb dies (out of memory)

run app - run gdb targeted at app - attach to pid - set break at function
inside shared object
RESULT: gdb dies (out of memory)

run target - run cross (read in symbol file) - set break - continue - i get
the error below.

Tho i am sure i am doing something incorrectly it appears:
1) Arm Cross target remote debugging does not support breaks in shared
libraries as of the current snapshot

2) there is a bug in the current native arm gdb that prevents setting a
breakpoint in a shared library and tripping the breakpoint (without running
out of memory)

Any help is greatly appreciated.

-----Original Message-----
From: Kevin Buettner []
Sent: Monday, April 29, 2002 5:14 PM
To: Kevin "Squail" Endres;
Subject: Re: arm gdbserver and shared object function resolution

On Apr 29,  4:34pm, Kevin \Squail\ Endres wrote:

> note: I can now load the symbols from the file on the host (and thus
> the function to an address and set a breakpoint). However - if i target
> remote target after setting the breakpoint i get the following error:
> warning: shared library handler failed to enable breakpoint. is the issue
> with the current cross target gdb or is it with gdbserver?

It is critical that GDB be able to find your target's dynamic linker
and load its symbols.  To do this, you normally use
``set solib-absolute-prefix'' to tell gdb where to find the sys-root
for the target's libraries.  If you're not doing this, then perhaps
that's your problem?

It is also important for the libraries in the sys-root location on
the host to be exactly the same as those found on the target.  All
kinds of strange things can happen if this is not the case.


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