From: Mark Kettenis <kettenis@science.uva.nl>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb@sources.redhat.com
Subject: Re: [RFHelp] Linux, threads, and regsets in thread_db
Date: Tue, 25 Sep 2001 03:09:00 -0000 [thread overview]
Message-ID: <s3ig09b37mi.fsf@debye.wins.uva.nl> (raw)
In-Reply-To: <20010924212808.A20851@nevyn.them.org>
Daniel Jacobowitz <drow@mvista.com> writes:
> I spent a while this summer making thread debugging work on some more
> non-x86 targets, with great frustration. Eventually I reached the
> decision that my problem was in fact a glibc bug; the attached messages
> explain it. Ulrich has categorically (and without explanation, when
> asked. sigh.) refused the patch.
Seems that Ulrich is still confused about the regset issues. I asked
the port maintainers to clean this up when I fixed it for i386. Jakub
Jellinek cleaned up sparc, but nothing else happened.
> Could someone on this list at least sanity check my patch? I have a
> (disgusting) workaround for GDB if the header is not changed, but I'd
> much rather someone convince Ulrich that I'm not crazy. Especially
> since I can not get the workaround to compile without warnings. C
> behaves badly in the presence of casts to/from array types.
In principle, your patch is the right thing. There may be
interactions with <sys/user.h> and <sys/elf.h> though. Look at the
i386 port to see how things should be done.
Mark
next prev parent reply other threads:[~2001-09-25 3:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-24 18:27 Daniel Jacobowitz
2001-09-25 3:09 ` Mark Kettenis [this message]
[not found] ` <20011003170848.A30843@lucon.org>
[not found] ` <20011003211007.A12210@nevyn.them.org>
2001-11-03 12:32 ` PATCH: " H . J . Lu
2001-11-03 14:25 ` Daniel Jacobowitz
2001-11-03 16:54 ` H . J . Lu
2001-11-06 14:28 ` Daniel Jacobowitz
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=s3ig09b37mi.fsf@debye.wins.uva.nl \
--to=kettenis@science.uva.nl \
--cc=drow@mvista.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