From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: gingold@adacore.com
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA Darwin]: handle simultaneous signal posting and single-stepping
Date: Tue, 07 Jul 2009 09:45:00 -0000 [thread overview]
Message-ID: <200907070943.n679hRt8029389@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <D9A39507-6303-477F-8F9E-60DB79A919F3@adacore.com> (message from Tristan Gingold on Tue, 7 Jul 2009 10:52:15 +0200)
> From: Tristan Gingold <gingold@adacore.com>
> Date: Tue, 7 Jul 2009 10:52:15 +0200
>
> Hi,
>
> in some cases (when a signal was received when the execution was
> stopped on a breakpoint), gdb resumes the
> inferior with both step=1 and signal != 0. This case wasn't handled
> correctly by darwin-nat (as the native
> API isn't able to do that).
>
> This patch fixes the issue by first single-stepping and keeping in
> mind that a signal has to be posted.
I'm not sure that single-stepping before sending the signal is right.
This means we'll execute an instruction (which potentially affects the
way signals are handled) before the program actually sees the signal.
I think a better way to do this is to continue with a signal while
keeping the breakpoints inserted, and deal with hitting the breakpoint
again in the appropriate way.
Also, I think this needs to be handled in the generic code. I'm
facing the same problem on OpenBSD.
> 2009-07-07 Tristan Gingold <gingold@adacore.com>
>
> * darwin-nat.c (darwin_resume_thread): Handle simultaneous single-step
> and signal.
> * darwin-nat.h (struct private_thread_info): Add signal_to_send field.
> Improve comment.
>
>
> Index: darwin-nat.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/darwin-nat.c,v
> retrieving revision 1.13
> diff -u -p -r1.13 darwin-nat.c
> --- darwin-nat.c 22 Jun 2009 08:24:29 -0000 1.13
> +++ darwin-nat.c 7 Jul 2009 08:50:45 -0000
> @@ -640,6 +640,19 @@ darwin_resume_thread (struct inferior *i
> (3, _("darwin_resume_thread: state=%d, thread=0x%x, step=%d
> nsignal=%d\n"),
> thread->msg_state, thread->gdb_port, step, nsignal);
>
> + if (step && nsignal)
> + {
> + /* We can't handle this in one step. The expected behaviour is
> single
> + step first and then post the signal. */
> + thread->signal_to_send = nsignal;
> + nsignal = 0;
> + }
> + else if (thread->signal_to_send && !step)
> + {
> + nsignal = thread->signal_to_send;
> + thread->signal_to_send = 0;
> + }
> +
> switch (thread->msg_state)
> {
> case DARWIN_MESSAGE:
> Index: darwin-nat.h
> ===================================================================
> RCS file: /cvs/src/src/gdb/darwin-nat.h,v
> retrieving revision 1.3
> diff -u -p -r1.3 darwin-nat.h
> --- darwin-nat.h 19 Jun 2009 14:30:30 -0000 1.3
> +++ darwin-nat.h 7 Jul 2009 08:50:45 -0000
> @@ -80,9 +80,13 @@ struct private_thread_info
> /* True if this thread is single-stepped. */
> unsigned char single_step;
>
> - /* True if a signal was manually sent to the thread. */
> + /* True if a signal was manually sent to the thread. In this case,
> we don't
> + report that a signal was posted. */
> unsigned char signaled;
>
> + /* Signal to be sent. Used to handle simultaneous step and
> signal. */
> + unsigned char signal_to_send;
> +
> /* The last exception received. */
> struct darwin_exception_msg event;
> };
>
>
next prev parent reply other threads:[~2009-07-07 9:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-07 8:52 Tristan Gingold
2009-07-07 9:45 ` Mark Kettenis [this message]
2009-07-07 10:42 ` Tristan Gingold
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=200907070943.n679hRt8029389@brahms.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb-patches@sourceware.org \
--cc=gingold@adacore.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