From: Daniel Jacobowitz <drow@mvista.com>
To: Kevin Hilman <khilman@equator.com>
Cc: gdb@sources.redhat.com
Subject: Re: multi-thread gdbserver and static libthread_db
Date: Mon, 21 Apr 2003 17:48:00 -0000 [thread overview]
Message-ID: <20030421174811.GA2099@nevyn.them.org> (raw)
In-Reply-To: <r2wuhnpwvr.fsf@equator.com>
On Mon, Apr 21, 2003 at 10:45:44AM -0700, Kevin Hilman wrote:
> Daniel Jacobowitz <drow@mvista.com> writes:
>
> > On Mon, Apr 21, 2003 at 10:19:17AM -0700, Kevin Hilman wrote:
> > > Also, does this require a specific kernel feature/version? It appears
> > > to use some /proc magic. Is the /proc support available in the 2.2.20
> > > kernel?
> >
> > 2.2.20 is probably fine. I haven't tried it on something that old in a
> > very long time though.
> >
> > There's really no /proc magic involved...
>
> Are there are any docs on the guts of how this is implemented?
Not especially :(
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2003-04-21 17:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-21 16:03 Kevin Hilman
2003-04-21 16:10 ` Daniel Jacobowitz
2003-04-21 17:19 ` Kevin Hilman
2003-04-21 17:26 ` Daniel Jacobowitz
2003-04-21 17:45 ` Kevin Hilman
2003-04-21 17:48 ` Daniel Jacobowitz [this message]
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=20030421174811.GA2099@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=khilman@equator.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).