From: Leon Pollak <leonp@plris.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: Restarting gdbserver
Date: Thu, 20 Jan 2011 14:55:00 -0000 [thread overview]
Message-ID: <201101201700.08641.leonp@plris.com> (raw)
In-Reply-To: <20110120141124.GA19527@host1.dyn.jankratochvil.net>
> Have you tried to play with `set debug-file-directory'?
> Which way is the debug info provided for /opt/FS?
Sorry, I probably do not know how to answer...:-)
I read the docs about `set debug-file-directory' - it says that this is
applicable in the case of the SEPARATE debug info, but I suppose that in my
case it is inside the ELF module, no?
Regarding the second question - I feel that the problem is here, but where
exactly?
I have the target's root FS on my PC in /opt/FS directory mounted via NFS.
The development is done in another separate place - /Projects/CSU/...
The compiled&linked executable module is hard-linked to the file in the
/opt/FS/common/csu and I start the gdb saying:
set sysroot /opt/FS/
set remote exec-file /common/csu
Is this insufficient?
I can put break points and step through the code. The problem seems to be just
with frame/backtrace only.
Thank you very much for your help.
--
Leon
next prev parent reply other threads:[~2011-01-20 14:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 9:25 Leon Pollak
2011-01-20 9:36 ` Jan Kratochvil
2011-01-20 14:07 ` Leon Pollak
2011-01-20 14:11 ` Jan Kratochvil
2011-01-20 14:55 ` Leon Pollak [this message]
2011-01-20 17:29 ` Jan Kratochvil
2011-01-21 22:48 ` Leon Pollak
2011-01-23 13:28 ` Jan Kratochvil
2011-01-23 16:39 ` Leon Pollak
2011-01-23 16:48 ` Jan Kratochvil
2011-01-23 18:01 ` Leon Pollak
2011-01-23 18:20 ` Jan Kratochvil
2011-01-23 18:25 ` Andreas Schwab
2011-01-20 14:10 Leon Pollak
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=201101201700.08641.leonp@plris.com \
--to=leonp@plris.com \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@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