From: Chris Plummer <darwin.plummer@sun.com>
To: gdb@sources.redhat.com
Subject: problems with GDB on Debian 3.0 for mips
Date: Fri, 28 Mar 2003 18:21:00 -0000 [thread overview]
Message-ID: <3E84922E.96F7B801@sun.com> (raw)
I have an application I build that I can't debug with gdb on Debain 3.0
for mips (on both an SGI Indy and a Cobalt Qube 2). I've sucessfully run
gdb on other large applications like xemacs. Also, if use -static when
linking my app, there is no problem. This same problem can be reproduced
debugging "ls". The log output is below.
indy-04$ gdb ls
GNU gdb 2002-04-01-cvs
[snip]
(gdb) run
Starting program: /bin/ls
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...[New Thread 1024 (LWP 23611)]
(no debugging symbols found)...
Program received signal SIGTRAP, Trace/breakpoint trap.
[Switching to Thread 1024 (LWP 23611)]
warning: Warning: GDB can't find the start of the function at 0xffffffff.
[snip]
0xffffffff in ?? ()
(gdb) bt
#0 0xffffffff in ?? ()
#1 0x2aacf3c8 in _dl_init () from /lib/ld.so.1
Cannot access memory at address 0x38
Any idea what the problem is? I don't subscribe to this mailing list, so
please CC: me.
Thanks,
Chris Plummer
next reply other threads:[~2003-03-28 18:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-28 18:21 Chris Plummer [this message]
2003-03-28 18:25 ` Daniel Jacobowitz
2003-03-28 22:19 ` 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=3E84922E.96F7B801@sun.com \
--to=darwin.plummer@sun.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).