Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@delorie.com>
To: gdb@sources.redhat.com
Cc: Charles Sandmann <sandmann@clio.rice.edu>, djgpp-workers@delorie.com
Subject: Adding support for core files to DJGPP
Date: Fri, 30 Mar 2001 01:10:00 -0000	[thread overview]
Message-ID: <200103300906.EAA18026@indy.delorie.com> (raw)

We are trying to add support for core files to the DJGPP port of GDB.
However, the available documentation which describes what needs to be
done is, at best, scanty ;-)  So I wonder if someone here can help.

Producing a core file in a format already supported by BFD is not
easy, because under the default algorithm used by DJGPP's sbrk the
program's address space may be non-contiguous.  This is due to
peculiarities of various DPMI hosts used on specific platforms,
most notably Windows, and the fact that the DPMI spec doesn't provide
any way for the program to specify where in memory will the program's
code and data be put; you just request a chunk of memory of the size
you need and get a buffer wherever the DPMI host wants it to be.  The
same problem also makes it next to impossible to reproduce the exact
way the program's address space was layed out after reading the core
file.

(If this is not clear enough, and if someone is interested, I can tell
more details.)

We already have a prototype version of code which writes to a disk
file the program's memory image and some additional information, such
as the general-purpose registers, segment selectors, etc.  But the
format of the core file is not something BFD can understand.

For these reasons, we would try first to explore the possibility of
using a custom core file format, instead of going through BFD.
However, I cannot find any real documentation of the API used by GDB
for accessing core files.  I'd expect GDB to need a few functions to
read the core file (or, perhaps, its specific portions), find out the
values in registers at the point of crash, what was the signal that
aborted the program, etc.  Where can I look for some info about this?

If someone has experience in providing such kind of core file support,
could they please post any advice that could be useful, and/or point
to any docs and code that could be of use to us?

Thanks in advance for any help.


             reply	other threads:[~2001-03-30  1:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-30  1:10 Eli Zaretskii [this message]
2001-03-30  2:32 ` egor duda
2001-03-30  3:28   ` Eli Zaretskii
2001-04-02  1:19   ` Eli Zaretskii
2001-04-02  3:20     ` egor duda
2001-03-30  6:44 David Taylor
2001-03-30  7:49 ` Eli Zaretskii
2001-03-30 11:44   ` J.T. Conklin
2001-03-31  1:43     ` Eli Zaretskii
2001-03-30  9:34 David Taylor
2001-03-30 11:14 ` H . J . Lu

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=200103300906.EAA18026@indy.delorie.com \
    --to=eliz@delorie.com \
    --cc=djgpp-workers@delorie.com \
    --cc=gdb@sources.redhat.com \
    --cc=sandmann@clio.rice.edu \
    /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