From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>
Subject: Re: [patch 2/4]#3 Fix lost siginfo_t for inferior calls
Date: Sat, 25 Sep 2010 18:16:00 -0000 [thread overview]
Message-ID: <201009241740.10169.pedro@codesourcery.com> (raw)
In-Reply-To: <20100921224935.GC20130@host1.dyn.jankratochvil.net>
On Tuesday 21 September 2010 23:49:35, Jan Kratochvil wrote:
> gdb/
> 2010-09-20 Jan Kratochvil <jan.kratochvil@redhat.com>
>
> Fix lost siginfo_t for inferior calls
> * infrun.c
> (struct inferior_thread_state) <siginfo_gdbarch, siginfo_data>: New.
> (save_inferior_thread_state): New variables regcache, gdbarch and
> siginfo_data. Initialize SIGINFO_DATA if gdbarch_get_siginfo_type_p.
> Move INF_STATE allocation later, pre-clear it. Initialize REGISTERS
> using REGCACHE.
> (restore_inferior_thread_state): New variables regcache and gdbarch.
> Restore SIGINFO_DATA for matching GDBARCH. Restore REGISTERS using
> REGCACHE. Free also SIGINFO_DATA.
Okay, thanks.
--
Pedro Alves
next prev parent reply other threads:[~2010-09-24 16:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 7:03 Jan Kratochvil
2010-09-25 18:16 ` Pedro Alves [this message]
2010-09-27 7:47 ` Jan Kratochvil
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=201009241740.10169.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.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