From: Michael Snyder <msnyder@vmware.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: "msnyder@sonic.net" <msnyder@sonic.net>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Can we make a gdb snapshot that includes process record?
Date: Fri, 08 May 2009 17:32:00 -0000 [thread overview]
Message-ID: <4A046A78.7040607@vmware.com> (raw)
In-Reply-To: <20090508155922.GI675@adacore.com>
Joel Brobecker wrote:
>> And by the way -- any idea why the last two gdb snapshots (both made
>> in May 2009) don't seem to include process record?
>
> I see a snapshot that was made on May 8: gdb-6.8.50.20090508.tar.bz2.
> Doesn't it include process record?
No, it doesn't. I'm kind of mystified as to why.
The changelog only goes up to 04/22.
> Perhaps we could isolate a snapshot of your choice and add a news entry
> on the website?
Anything current (this week) should do nicely, I would think...
next prev parent reply other threads:[~2009-05-08 17:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-08 15:53 msnyder
2009-05-08 15:59 ` Joel Brobecker
2009-05-08 17:32 ` Michael Snyder [this message]
2009-05-08 21:35 ` Joel Brobecker
2009-05-08 22:09 ` Michael Snyder
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=4A046A78.7040607@vmware.com \
--to=msnyder@vmware.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=msnyder@sonic.net \
/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