From: Michael Snyder <msnyder@vmware.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: Gcore doesn't work on i386 without SSE
Date: Thu, 08 Apr 2010 23:37:00 -0000 [thread overview]
Message-ID: <4BBE68C8.6030909@vmware.com> (raw)
In-Reply-To: <i2x6dc9ffc81004081607m116b41e7oa7cc1fc936cc36d2@mail.gmail.com>
H.J. Lu wrote:
> The fundamental question is if coredump generated by
> gcore should be as close to the one generated by OS
> as possible.
I don't think that really matters, since gdb is the only known consumer.
Just as long as gdb can read them is the important thing.
prev parent reply other threads:[~2010-04-08 23:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 23:07 H.J. Lu
2010-04-08 23:37 ` Michael Snyder [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=4BBE68C8.6030909@vmware.com \
--to=msnyder@vmware.com \
--cc=gdb-patches@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=mark.kettenis@xs4all.nl \
/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