From: Daniel Jacobowitz <drow@mvista.com>
To: Chris Plummer <darwin.plummer@sun.com>
Cc: gdb@sources.redhat.com
Subject: Re: problems with GDB on Debian 3.0 for mips
Date: Fri, 28 Mar 2003 18:25:00 -0000 [thread overview]
Message-ID: <20030328182530.GA20454@nevyn.them.org> (raw)
In-Reply-To: <3E84922E.96F7B801@sun.com>
On Fri, Mar 28, 2003 at 10:19:27AM -0800, Chris Plummer wrote:
> 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.
This is a bug in the glibc headers used to build GDB. It should be
fixed in glibc CVS and in Debian unstable.
If you want, you can fix your headers and rebuild gdb. If I remember
correctly you need to change two lines in sys/procfs.h to say:
typedef elf_gregset_t prgregset_t;
typedef elf_fpregset_t prfpregset_t;
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-03-28 18:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-28 18:21 Chris Plummer
2003-03-28 18:25 ` Daniel Jacobowitz [this message]
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=20030328182530.GA20454@nevyn.them.org \
--to=drow@mvista.com \
--cc=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).