From: John Mead <jmead@luxsonor.com>
To: insight@sourceware.cygnus.com
Subject: Insight on MIPS
Date: Thu, 27 Jan 2000 11:27:00 -0000 [thread overview]
Message-ID: <38902BAD.7D7AA0DD@luxsonor.com> (raw)
I just finished building Insight/GDB as a cross-debugger , hosted on
win32/NT, targeted for a MIPS R3000. I'm amazed at how capable GDB and
Insight are together,
and I think Cygnus and the Insight developers/maintainers have done a
fantastic job.
I do have one question, more related to GDB and GCC. When I compile my
code , I've tried using -g , -gstabs+, -gelf. In all cases, it appears
that source line
number information is not being generated for all functions in the file.
As an example,
I compile 'main.c' (using a GCC cross-compiler for MIPS/ELF) :
void main( void )
{
...
foo( );
foo2( );
...
}
void foo(void)
{
...
}
void foo2(void)
{
...
}
Then I do 'objdumpmips -j .text -d -l -S main.o'. What I see is that
line numbers
decorate main( ) and foo( ), but not foo2( ). Trying to single step
into foo2( ) works,
but Insight says that the source line I'm stopped at corresponds to the
closing '}' of
'main( )'.
Any ideas about what's going on here?
--thanks
John Mead
reply other threads:[~2000-01-27 11:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=38902BAD.7D7AA0DD@luxsonor.com \
--to=jmead@luxsonor.com \
--cc=insight@sourceware.cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).