From: Tom Tromey <tromey@redhat.com>
To: Doug Evans <dje@google.com>
Cc: "Frank Ch. Eigler" <fche@redhat.com>,
Yao Qi <yao@codesourcery.com>,
"gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: duplicated code in gdb and gdbserver
Date: Wed, 12 Jan 2011 15:47:00 -0000 [thread overview]
Message-ID: <m3k4iagnf9.fsf@fleche.redhat.com> (raw)
In-Reply-To: <AANLkTi=WSW8snse3PaNZTYnax6Mo6+F=Pah6JKo8=B2R@mail.gmail.com> (Doug Evans's message of "Mon, 10 Jan 2011 08:34:53 -0800")
>>>>> "Doug" == Doug Evans <dje@google.com> writes:
Doug> It would give us the impetus to get multiprocess debugging across fork
Doug> working well (which Tom wants for gcc). 1/2 :-)
For the record, it already works pretty great, thanks to Pedro.
My current branch doesn't really have much code -- a few new Python
events (based on the work of Oguz and Sami) and a new Python command to
make a kind of cross-inferior pending breakpoint.
Tom
next prev parent reply other threads:[~2011-01-12 15:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 15:23 Yao Qi
2011-01-07 16:37 ` Doug Evans
2011-01-08 3:34 ` Yao Qi
2011-01-08 5:17 ` Joel Brobecker
2011-01-10 13:39 ` Frank Ch. Eigler
2011-01-10 14:09 ` Joel Brobecker
2011-01-10 15:10 ` Frank Ch. Eigler
2011-01-10 15:50 ` Paul Koning
2011-01-10 15:51 ` Doug Evans
2011-01-10 15:54 ` Frank Ch. Eigler
2011-01-10 16:35 ` Doug Evans
2011-01-10 19:02 ` Frank Ch. Eigler
2011-01-11 23:35 ` Joel Brobecker
2011-01-11 23:38 ` Joel Brobecker
2011-01-12 0:30 ` Frank Ch. Eigler
2011-01-12 17:54 ` Doug Evans
2011-01-12 18:06 ` Doug Evans
2011-01-12 18:43 ` Paul Koning
2011-01-12 19:04 ` Doug Evans
2011-01-12 20:09 ` Joel Brobecker
2011-01-12 20:48 ` Frank Ch. Eigler
2011-01-14 17:04 ` Doug Evans
2011-01-12 15:47 ` Tom Tromey [this message]
2011-01-07 17:17 ` Stan Shebs
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=m3k4iagnf9.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=dje@google.com \
--cc=fche@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=yao@codesourcery.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