From: Andrew Cagney <ac131313@redhat.com>
To: Squal <pmarty@enssat.fr>
Cc: gdb@sources.redhat.com, froure@enssat.fr
Subject: Re: displaying source files during debugging.
Date: Thu, 26 Sep 2002 10:04:00 -0000 [thread overview]
Message-ID: <3D933E25.1080508@redhat.com> (raw)
In-Reply-To: <3D932899.F708BD5F@enssat.fr>
> 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.
Off the top of my head:
Is the original code compiled with -g?
Which C compiler? The problem may be that GDB doesn't recognize the
debug info being generated by the compiler.
Is gdb reporting ``no symbol information found''.
Andrew
prev parent reply other threads:[~2002-09-26 17:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-26 8:27 Squal
2002-09-26 10:04 ` Andrew Cagney [this message]
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=3D933E25.1080508@redhat.com \
--to=ac131313@redhat.com \
--cc=froure@enssat.fr \
--cc=gdb@sources.redhat.com \
--cc=pmarty@enssat.fr \
/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