From: Michael Snyder <msnyder@vmware.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
"teawater@gmail.com" <teawater@gmail.com>
Subject: Re: [RFA, 3 of 3] save/restore process record, part 3 (save/restore)
Date: Sun, 18 Oct 2009 04:10:00 -0000 [thread overview]
Message-ID: <4ADA93C9.5040601@vmware.com> (raw)
In-Reply-To: <83k4ytgxh5.fsf@gnu.org>
Eli Zaretskii wrote:
>> Date: Sat, 17 Oct 2009 15:13:37 -0700
>> From: Michael Snyder <msnyder@vmware.com>
>> CC: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
>> "teawater@gmail.com" <teawater@gmail.com>
>>
>>>> This is the same approach that is used by the "gcore" command.
>>>> How does "gcore" work with go32, if at all?
>>> It doesn't. DJGPP cannot generate core files.
>> Well, save/restore depends on core files, so I guess
>> it won't work in go32.
>
> DJGPP does not support core files created from a memory image of a
> running process, but I don't see any reason why bfdcore_write won't
> work for it.
We don't just do bfdcore_write -- we actually create a core file
from the memory image, and then add an extra segment to it for
bfdcore_write to write into. The core file is an integral part
of the execution log file.
I forgot to post the accompanying changes to gcore.c with this
patch. I'm just about to put them up now that Hui reminded me.
next prev parent reply other threads:[~2009-10-18 4:10 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-17 1:32 Michael Snyder
2009-10-17 8:31 ` Eli Zaretskii
2009-10-17 18:42 ` Michael Snyder
2009-10-17 20:11 ` Eli Zaretskii
2009-10-17 22:19 ` Michael Snyder
2009-10-18 2:23 ` Hui Zhu
2009-10-18 3:59 ` Michael Snyder
2009-10-18 4:06 ` Eli Zaretskii
2009-10-18 4:10 ` Michael Snyder [this message]
2009-10-19 4:34 ` Hui Zhu
2009-10-19 18:00 ` Michael Snyder
2009-10-20 2:47 ` Hui Zhu
2009-10-20 20:03 ` Michael Snyder
2009-10-20 20:05 ` Michael Snyder
2009-10-21 2:36 ` Hui Zhu
2009-10-22 19:42 ` Michael Snyder
2009-10-22 20:40 ` Paul Pluzhnikov
2009-10-22 21:00 ` Michael Snyder
2009-10-22 21:25 ` Paul Pluzhnikov
2009-10-23 0:45 ` Paul Pluzhnikov
2009-10-23 1:05 ` Paul Pluzhnikov
2009-10-23 5:35 ` Hui Zhu
2009-10-23 8:52 ` Pierre Muller
2009-10-23 10:08 ` Eli Zaretskii
2009-10-23 14:42 ` Hui Zhu
2009-10-23 14:54 ` Pedro Alves
2009-10-31 14:57 ` Pedro Alves
2009-11-01 9:54 ` Hui Zhu
2009-10-23 14:58 ` Pedro Alves
2009-10-23 14:46 ` Andreas Schwab
2009-10-23 14:55 ` Eli Zaretskii
2009-10-23 15:35 ` Andreas Schwab
2009-10-23 15:48 ` Eli Zaretskii
2009-10-23 16:31 ` Andreas Schwab
2009-10-23 15:09 ` Pierre Muller
2009-10-23 5:35 ` Hui Zhu
2009-10-23 15:56 ` Michael Snyder
2009-10-23 16:01 ` 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=4ADA93C9.5040601@vmware.com \
--to=msnyder@vmware.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=teawater@gmail.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