From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Elena Zannoni <ezannoni@redhat.com>, gdb@sources.redhat.com
Subject: Re: RFC: A mode in which gdb avoids libthread_db
Date: Fri, 08 Aug 2003 02:21:00 -0000 [thread overview]
Message-ID: <3F330908.8010803@redhat.com> (raw)
In-Reply-To: <20030726233201.GA13936@nevyn.them.org>
> On Sat, Jul 26, 2003 at 07:37:12PM -0400, Elena Zannoni wrote:
>> I know first hand of the pains of mismatched glibcs, binutils,
>> kernels, gdbs. I wouldn't mind having this coexist with the use of
>> glibc, is that possible?
>
>
> Sure. It could just be a switch or a "set" flag - easy enough.
Yes. In this mode, just restrict libthread_db to, er, visualizing
thread data structures such as the thread ID and, hopefully, eventually,
semaphore state et.al.
>> What ptrace changes did you do? (Elena needs to start reading
>> linux-kernel)
>
>
> Take a look at the support for "set follow-fork-mode", which I've
> posted a few times. I added:
Andrew
next prev parent reply other threads:[~2003-08-08 2:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-26 15:58 Daniel Jacobowitz
2003-07-26 23:29 ` Elena Zannoni
2003-07-26 23:32 ` Daniel Jacobowitz
2003-08-08 2:21 ` Andrew Cagney [this message]
2003-07-28 20:53 ` Kevin Buettner
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=3F330908.8010803@redhat.com \
--to=ac131313@redhat.com \
--cc=drow@mvista.com \
--cc=ezannoni@redhat.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).