From: Daniel Jacobowitz <drow@false.org>
To: jbbachky@aim.com
Cc: gdb@sources.redhat.com
Subject: Re: gdbserver/gdb-6/4 and lots of pthreads
Date: Thu, 16 Nov 2006 22:04:00 -0000 [thread overview]
Message-ID: <20061116220412.GA28527@nevyn.them.org> (raw)
In-Reply-To: <8C8D7E0B004BE30-C20-26F0@mblk-d23.sysops.aol.com>
On Thu, Nov 16, 2006 at 04:52:47PM -0500, jbbachky@aim.com wrote:
> After working through a couple of configure bugs (configure #defines
> HAVE_TD_THR_TLS_GET_ADDR to 1 even when the test properly fails), I
> still seem to have the same symptoms.
Oops. I see what's wrong with the check, I'll fix it now. Thanks.
> I have noticed that I now hit the default clause in the ptrace system
> call handler a few times - because there is not a case for
> PTRACE_GETSIGINFO in linux 2.6.10). Is this a/the problem? In the mean
> time, I'll trying to locate a definition for that case and make it work
> on my architectures.
PTRACE_GETSIGINFO is much older than that, so I'm not sure why, but
it should not be relevant to this feature.
> Daniel, is any settings and/or initialization things that I need to do
> in order to make use of your patch?
No. Could you capture a log using "set debug remote 1" of a session
which shows the problem?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-11-16 22:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-15 16:12 jbbachky
2006-11-15 16:50 ` Daniel Jacobowitz
2006-11-15 17:08 ` jbbachky
2006-11-16 15:15 ` Daniel Jacobowitz
2006-11-16 21:53 ` jbbachky
2006-11-16 22:04 ` Daniel Jacobowitz [this message]
2006-11-17 18:47 ` jbbachky
2006-11-17 19:08 ` Daniel Jacobowitz
2006-11-17 20:01 ` jbbachky
2006-11-17 20:14 ` Daniel Jacobowitz
2006-11-29 15:23 ` jbbachky
2006-11-29 15:26 ` 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=20061116220412.GA28527@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=jbbachky@aim.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