public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@airs.com>
To: deo@logos-m.ru
Cc: binutils@sourceware.cygnus.com
Subject: Re: elf "note" section for win32-style thread context
Date: Thu, 01 Jul 1999 00:00:00 -0000	[thread overview]
Message-ID: <19990510150327.20323.qmail@daffy.airs.com> (raw)
In-Reply-To: <3778.990510@logos-m.ru>

   Date: Mon, 10 May 1999 18:41:16 +0400
   From: Egor Duda <deo@logos-m.ru>

   I've got an intention to add core dumping functionality to cygwin
   library, so that cygwin application would write elf core file. As a
   part of it, there should be "note" sections to store contexts of all
   running threads. I see two possible ways to do it. I can either
   emulate through one of existing structures (prstatus_t, lwpstatus_t,
   etc.) or add new special note type for cygwin to bfd. Which way should
   i choose?

The real point of storing thread information in a core file is so that
you can examine the thread state using gdb.  So you should probably
make your decision based on what fits more naturally into the gdb
code.

The prstatus_t stuff is all ELF specific, so you would have to copy it
anyhow for the PE-based cygwin code.  The current implementation is
actually not quite right in that it relies on host header files, and
even if the right header files are available can not be built
correctly for a cross toolchain.

Ian

  reply	other threads:[~1999-07-01  0:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-01  0:00 Egor Duda
1999-07-01  0:00 ` Ian Lance Taylor [this message]
1999-07-01  0:00   ` Re[2]: " Egor Duda
1999-07-01  0:00     ` Ian Lance Taylor

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=19990510150327.20323.qmail@daffy.airs.com \
    --to=ian@airs.com \
    --cc=binutils@sourceware.cygnus.com \
    --cc=deo@logos-m.ru \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).