From: Daniel Jacobowitz <dan@debian.org>
To: Scott A McConnell <samcconn@cotw.com>
Cc: "MIPS/Linux List (SGI)" <linux-mips@oss.sgi.com>
Subject: Re: gdb, pthreads and MIPS
Date: Thu, 24 Jan 2002 12:15:44 -0500 [thread overview]
Message-ID: <20020124121544.A26522@nevyn.them.org> (raw)
In-Reply-To: <3C502108.B4024075@cotw.com>
On Thu, Jan 24, 2002 at 08:58:16AM -0600, Scott A McConnell wrote:
> I am targeting a NEC VR5432
>
> I am able to debug/set break points on executables that are not linked
> with -lpthreads. However, whenever I try an executable that was linked
> with pthreads gdb can never find the stack (PC).
>
> Once a SIGTRAP occurs gdb has lost track of the stack. Up until that
> point it seems to be keeping track of the PC.
>
> I have tried gdb from the SGI site (H J Lu) I also have built 5.1.0.1
> native. Both fail.
>
> Are other people having trouble debugging pthreads?
> Are there any patches available?
> Can anyone even help me classify this problem? (gcc, glibc, gdb all
> three)
Primarily glibc. I've spent a long long time trying to get this fixed
and Ulrich categorically refused the patch. The size of prgregset in
the headers is wrong.
Edit /usr/include/sys/procfs.h, change the typedef of pr*regset from
*regset_t to elf_*regset_t, rebuild GDB, see if it works.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-01-24 18:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-24 14:58 gdb, pthreads and MIPS Scott A McConnell
2002-01-24 17:15 ` Daniel Jacobowitz [this message]
2002-01-24 20:42 ` Scott A McConnell
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=20020124121544.A26522@nevyn.them.org \
--to=dan@debian.org \
--cc=linux-mips@oss.sgi.com \
--cc=samcconn@cotw.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.