From: "Kevin \"Squail\" Endres" <kevine@wildseed.com>
To: 'Daniel Jacobowitz' <drow@mvista.com>, gdb@sources.redhat.com
Subject: RE: arm gdbserver and shared object function resolution
Date: Mon, 29 Apr 2002 16:34:00 -0000 [thread overview]
Message-ID: <43CB1396676FD4119F03001083FD2994F5F17C@neptune.kirkland.local> (raw)
note: I can now load the symbols from the file on the host (and thus resolve
the function to an address and set a breakpoint). However - if i target the
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?
:]k
-----Original Message-----
From: Kevin "Squail" Endres [mailto:kevine@wildseed.com]
Sent: Monday, April 29, 2002 4:12 PM
To: 'Daniel Jacobowitz'; gdb@sources.redhat.com
Subject: RE: arm gdbserver and shared object function resolution
seems that it doesnt work in the current snapshot...
:]k
-----Original Message-----
From: Daniel Jacobowitz [mailto:drow@mvista.com]
Sent: Monday, April 29, 2002 3:19 PM
To: gdb@sources.redhat.com
Subject: Re: arm gdbserver and shared object function resolution
On Mon, Apr 29, 2002 at 03:08:08PM -0700, Kevin Squail Endres wrote:
>
> I am using gdbserver from current cvs hosted and targeted for arm along
with
> gdb-5.1.1 hosted on i386 and target for arm.
>
> I am trying to set a breakpoint on a function inside a .so - i am doing
the
> following
>
> assume exec foo with function in shared object test
>
> target: running foo under gdbserver
>
> host:
> 1) open foo under cross gdb
> 2) target remote
> 3) set break point at main
> 4) continue
> 5) attempt to set breakpoint in function in .so
>
> cant resolve symbols!! (NOTE: host .so has symbols)
>
> Further: if i use targer native gdb - set a breakpoint at main - run -
then
> set a break at function everything works as expected.
>
> Any info on why the above scenario is failing would be much appreciated!
Because GDB 5.1.1 doesn't support remote debugging of shared libraries
on ARM. Please try a current snapshot instead.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next reply other threads:[~2002-04-29 23:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-29 16:34 Kevin "Squail" Endres [this message]
2002-04-29 17:14 ` Kevin Buettner
-- strict thread matches above, loose matches on Subject: below --
2002-05-06 9:33 Kevin "Squail" Endres
2002-04-30 16:31 Kevin "Squail" Endres
2002-04-29 17:59 Kevin "Squail" Endres
2002-04-30 8:01 ` Daniel Jacobowitz
2002-04-29 16:11 Kevin "Squail" Endres
2002-04-29 15:20 Kevin "Squail" Endres
2002-04-29 15:08 Kevin "Squail" Endres
2002-04-29 15:19 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43CB1396676FD4119F03001083FD2994F5F17C@neptune.kirkland.local \
--to=kevine@wildseed.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox