From: Daniel Jacobowitz <drow@mvista.com>
To: Roland McGrath <roland@redhat.com>
Cc: Mark Kettenis <kettenis@chello.nl>, gdb@sources.redhat.com
Subject: Re: gdb/dwarf-frame.c
Date: Fri, 09 May 2003 21:58:00 -0000 [thread overview]
Message-ID: <20030509215850.GA29659@nevyn.them.org> (raw)
In-Reply-To: <200305092119.h49LJVi27336@magilla.sf.frob.com>
On Fri, May 09, 2003 at 02:19:31PM -0700, Roland McGrath wrote:
> [I trimmed the CC because I think everyone else is on the mailing list.]
>
> > Yes indeed. I mostly use FreeBSD instead of Linux nowadays, so I
> > haven't tracked what's been happening on the Linux thread front too
> > closely. I get the feeling though that trying to support both the old
> > and the new threading model in the same code isn't a good idea :-(.
>
> Can you be specific in your criticism? The rigamarole to get sibling
> threads stopped and started is a bit unsightly, but not too horrible I
> didn't think. I think trying to have separate backend implementations for
> linuxthreads and nptl and switching among them (whether two target modules
> or one with internal state flags) would be worse than any moderate amount
> of kludgery in the one backend.
>
> The situation in lin-lwp.c can be much cleaner if Dan and I ever implement
> the enhancements to ptrace in Linux 2.5 that we have discussed in detail
> privately in the past. That would let thread tracing at the kernel level
> work in a sane fashion with either kind of threads on a new kernel, and
> make it easy to detect an old kernel lacking the new ptrace features and
> fall back to the existing code that only supports linuxthreads. We can
> probably be spurred to do this, though it has heretofore fallen off the end
> of our queues of wonderful things that ought to be done real soon now.
Coincidentally, I'm working on this this weekend. Or I was going to.
The NPTL gdb patches do _not_ work on 2.5.69. The message about this
is stuck in my outbox; I'm trying to get GDB to give me a backtrace but
it's been chugging for an hour now with no luck (160K frames and
counting!)
> That doesn't help debugging NPTL on extant 2.5 kernels or on modified 2.4
> kernels that support NPTL like those in RHL9. But personally I am ok with
> such support not going into mainline gdb if cleaner support for newer
> kernels is there. (However I don't speak for my RH colleagues who will
> have to maintain private patches as necessary.)
I'd rather support it. I think we can, too.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-05-09 21:58 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-09 9:45 gdb/dwarf-frame.c Roland McGrath
2003-05-09 13:41 ` gdb/dwarf-frame.c Daniel Jacobowitz
2003-05-09 14:10 ` gdb/dwarf-frame.c Elena Zannoni
2003-05-09 14:56 ` NPTL thread support H. J. Lu
2003-05-09 15:44 ` Elena Zannoni
[not found] ` <20030509091522.A2960@lucon.org>
[not found] ` <16059.55278.841645.134311@localhost.redhat.com>
2003-05-11 20:46 ` H. J. Lu
2003-05-12 19:24 ` J. Johnston
2003-05-12 20:08 ` H. J. Lu
2003-05-12 20:15 ` David Carlton
2003-05-12 21:09 ` Andrew Cagney
2003-05-12 21:18 ` David Carlton
2003-05-12 21:23 ` Daniel Jacobowitz
2003-05-12 20:17 ` Elena Zannoni
2003-05-09 17:01 ` gdb/dwarf-frame.c Andrew Cagney
2003-05-09 17:08 ` gdb/dwarf-frame.c Elena Zannoni
2003-05-09 19:43 ` gdb/dwarf-frame.c Mark Kettenis
2003-05-09 21:19 ` gdb/dwarf-frame.c Roland McGrath
2003-05-09 21:48 ` gdb/dwarf-frame.c Elena Zannoni
2003-05-09 22:17 ` gdb/dwarf-frame.c Roland McGrath
2003-05-09 21:54 ` gdb/dwarf-frame.c Andrew Cagney
2003-05-09 21:58 ` Daniel Jacobowitz [this message]
2003-05-09 22:18 ` gdb/dwarf-frame.c Roland McGrath
2003-05-09 22:28 ` gdb/dwarf-frame.c Andrew Cagney
2003-05-09 22:33 ` gdb/dwarf-frame.c Roland McGrath
2003-05-09 20:32 ` gdb/dwarf-frame.c Roland McGrath
2003-05-09 19:36 ` gdb/dwarf-frame.c Mark Kettenis
2003-05-09 21:34 ` gdb/dwarf-frame.c Roland McGrath
2003-05-09 21:46 ` gdb/dwarf-frame.c Elena Zannoni
2003-05-10 7:07 ` gdb support for Linux vsyscall DSO Roland McGrath
2003-05-10 17:24 ` Andrew Cagney
2003-05-10 18:13 ` Daniel Jacobowitz
2003-05-10 19:42 ` Roland McGrath
2003-05-10 21:49 ` Andrew Cagney
2003-05-12 19:23 ` Andrew Cagney
2003-05-13 2:29 ` Roland McGrath
2003-05-13 16:03 ` Andrew Cagney
2003-05-10 21:28 ` Roland McGrath
2003-05-10 17:55 ` Mark Kettenis
2003-05-10 20:27 ` Roland McGrath
2003-05-11 23:14 ` Mark Kettenis
2003-05-13 1:53 ` Roland McGrath
2003-05-15 21:26 ` Mark Kettenis
2003-05-16 2:25 ` Roland McGrath
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=20030509215850.GA29659@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=kettenis@chello.nl \
--cc=roland@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).