From: Kris Warkentin <kewarken@qnx.com>
To: Hinko Kocevar <hinko.kocevar@iskramedical.si>
Cc: gdb@sources.redhat.com
Subject: Re: remote debugging and source files
Date: Tue, 24 Aug 2004 16:35:00 -0000 [thread overview]
Message-ID: <412B6ABC.9060804@qnx.com> (raw)
In-Reply-To: <412B6515.2030501@iskramedical.si>
auto-solib-add will only work properly if gdb successfully sets the
solib event breakpoint in the loader. Try 'maint info breakpoints' and
see if it's being set. You could also try setting stop-on-solib-events
to see if it's actually stopping. Sometimes you have problems if there
is a different version of the loader on host and target.
cheers,
Kris
Hinko Kocevar wrote:
> Hinko Kocevar wrote:
> ...
>
>>
>> IMHO libraries are found and loaded, but sysbols are not read... Why?
>>
>> regards,
>> h
>>
>
> Ok, I got it to load the symbols manualy with
> sharedlibrary
> /opt/arm-linux/gcc-3.3.3-glibc-2.3.2/arm-softfloat-linux-gnu/usr/local/lib/libnano-X.so
>
>
> I wonder if this could be automated. As I stated earlier on host,
> debugging program compiled for host, it loads symbols automaticaly. If
> debugging program for ARM target I have to manualy load the symbols ?!
>
> 'Autoloading of shared library symbols' is set to true in ddd/gdb so
> this should do it, right?
>
> regards,
> h
>
next prev parent reply other threads:[~2004-08-24 16:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-24 14:05 Hinko Kocevar
2004-08-24 15:34 ` Hinko Kocevar
2004-08-24 15:56 ` Hinko Kocevar
2004-08-24 16:35 ` Kris Warkentin [this message]
2004-08-24 17:42 ` Hinko Kocevar
2004-08-24 17:53 ` Daniel Jacobowitz
2004-08-24 18:05 ` Kris Warkentin
2004-08-25 13:58 ` Hinko Kocevar
2004-08-25 14:16 ` Daniel Jacobowitz
2004-08-25 14:30 ` Hinko Kocevar
2004-08-26 19:38 ` remote debugging and source files - SOLVED Hinko Kocevar
2004-08-25 14:33 ` remote debugging and source files Kris Warkentin
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=412B6ABC.9060804@qnx.com \
--to=kewarken@qnx.com \
--cc=gdb@sources.redhat.com \
--cc=hinko.kocevar@iskramedical.si \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).