From: Squal <pmarty@enssat.fr>
To: gdb@sources.redhat.com
Cc: pmarty@enssat.fr, froure@enssat.fr
Subject: displaying source files during debugging.
Date: Thu, 26 Sep 2002 08:27:00 -0000 [thread overview]
Message-ID: <3D932899.F708BD5F@enssat.fr> (raw)
Hi,
We are trying to debug program with gdb for a
m68k target. We are compiling the source files
in two executable:
- the first in aout format.
- the second in srecord format (with objcopy).
The second is download on the target and the first
is giving to gdb in order to reach the symbol table.
Our problem is that this configuration don't allow
us to display source files during debugging.
We tried to specifie the source files directorie
with the dir command but with no success.
This problem occurs only during cross debugging (when
we try to debug a program localy with gdb, there is no
problems to reach source files).
Does any gdb option exist to reach source files during
cross debugging?
Maybe the aout format given to gdb don't include enough
information about source files (it maybe should be better
with the coff or elf format)?
Thanks and regards
Pascal & FX
ENSSAT students
next reply other threads:[~2002-09-26 15:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-26 8:27 Squal [this message]
2002-09-26 10:04 ` Andrew Cagney
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=3D932899.F708BD5F@enssat.fr \
--to=pmarty@enssat.fr \
--cc=froure@enssat.fr \
--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