From: Andrew Cagney <ac131313@cygnus.com>
To: David Relson <relson@osagesoftware.com>
Cc: gdb@sources.redhat.com
Subject: Re: Problem with threaded program
Date: Sun, 02 Dec 2001 21:28:00 -0000 [thread overview]
Message-ID: <3C0B0D62.3040708@cygnus.com> (raw)
In-Reply-To: <4.3.2.7.2.20011202201853.00bfba30@mail.osagesoftware.com>
> Daniel,
>
> I don't know what the division of labor is between gdb and the kernel for situations like this, so I can't comment on that. I can report, however, that the problem doesn't occur with gdb-4.18. I had previously tested with an old copy of gdb-4.18. To remove one possible difference, I have tested for the problem using copies of both gdb-4.18 and gdb-5.1 built today under the 2.4.16 kernel. gdb-4.18 works properly and gdb-5.1 shows the problem. If the problem is in the kernel, then 4.18 and 5.1 must be using different capabilities ...
>
Yes, very, very different:
>> The apparent 4.18 -> 5.0 ``breakage'' would have occured because GDB
>> switched to using the thread-db/kernel interface.
best way to describe this is, unfortunatly, is ``radical surgery''.
While the new implementation is significantly better and definitly worth
the effort. however, it is showing up a few teathing problems. Just
make certain that your kernel/glibc are recent.
sigh,
Andrew
next prev parent reply other threads:[~2001-12-03 5:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <David Relson <relson@osagesoftware.com>
2001-12-02 8:44 ` David Relson
2001-12-02 10:41 ` Andrew Cagney
2001-12-02 15:48 ` Daniel Jacobowitz
2001-12-02 17:24 ` David Relson
2001-12-02 21:28 ` Andrew Cagney [this message]
2001-12-03 4:14 ` David Relson
2001-12-03 7:49 ` Trond Eivind Glomsrød
2001-12-06 16:04 ` Kevin Buettner
2001-12-06 16:37 ` David Relson
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=3C0B0D62.3040708@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb@sources.redhat.com \
--cc=relson@osagesoftware.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