From: Tristan Gingold <gingold@adacore.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb@sourceware.org, Mark Kettenis <mark.kettenis@xs4all.nl>,
drow@false.org
Subject: Re: Regression
Date: Tue, 10 Feb 2009 16:18:00 -0000 [thread overview]
Message-ID: <2730E79B-A022-43ED-86B9-BED442D2A733@adacore.com> (raw)
In-Reply-To: <200902101606.23591.pedro@codesourcery.com>
On Feb 10, 2009, at 5:06 PM, Pedro Alves wrote:
> (gdb) set debug infrun 1
> (gdb) signal SIGUSR1
> Continuing with signal SIGUSR1.
> infrun: clear_proceed_status_thread (process 27276)
> infrun: proceed (addr=0xffffffff, signal=30, step=0)
> infrun: resume (step=1, signal=30), trap_expected=1
> infrun: wait_for_inferior (treat_exec_as_sigtrap=0)
> infrun: target_wait (-1, status) = 27276, status->kind = stopped,
> signal = SIGTRAP
> infrun: infwait_normal_state
> infrun: TARGET_WAITKIND_STOPPED
> infrun: stop_pc = 0xeff4636
>
> Here, it seems like telling BSD to single-step, and, to deliver
> a signal at the same time, just single-steps, resulting in a SIGTRAP.
Fun: at the same time I was trying to fix the regression for darwin/x86.
I don't really understand the semantic of resume(step=1, signal=30).
Does it mean first step and then
send a signal ? If so wouldn't be simpler for targets if infrun ran
two separate operations ?
Tristan.
next prev parent reply other threads:[~2009-02-10 16:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 15:17 Regression Mark Kettenis
2009-02-10 15:27 ` Regression Daniel Jacobowitz
2009-02-10 15:47 ` Regression Mark Kettenis
2009-02-10 16:06 ` Regression Pedro Alves
2009-02-10 16:18 ` Tristan Gingold [this message]
2009-02-10 18:00 ` Regression Pedro Alves
2009-02-10 18:40 ` Regression Mark Kettenis
2009-02-10 19:05 ` Regression Pedro Alves
2009-02-10 19:18 ` Regression Pedro Alves
2009-02-10 19:27 ` Regression Pedro Alves
2009-02-11 15:50 ` Regression Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2009-02-10 15:14 Regression Mark Kettenis
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=2730E79B-A022-43ED-86B9-BED442D2A733@adacore.com \
--to=gingold@adacore.com \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--cc=pedro@codesourcery.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