Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: Yao Qi <qiyaoltc@gmail.com>,  gdb-patches@sourceware.org
Subject: Re: exceptions.KeyboardInterrupt is thrown in gdb.base/random-signal.exp
Date: Wed, 25 Nov 2015 17:16:00 -0000	[thread overview]
Message-ID: <86h9kaxamv.fsf@gmail.com> (raw)
In-Reply-To: <5655E141.7030503@redhat.com> (Pedro Alves's message of "Wed, 25	Nov 2015 16:26:41 +0000")

Pedro Alves <palves@redhat.com> writes:

> Seems like a hack -- I don't see how that can make a difference.  In both
> cases, we send \003 after 500ms.

The only difference is that {send_gdb "\003"} will be executed in an
event handler later while tcl has already been in gdb_test.

>
> The test sets a software watchpoint, and resumes the target.  That means
> the program will be constantly single-stepping, and gdb will be evaluating
> the watched expression at each single-step.  I'd suspect that the problem
> is likely that while the program is stopped to evaluate the watched
> expression, something is calling target_terminal_ours, which restores
> handle_sigint as SIGINT handler.  Then somehow you're unlucky to manage to
> ctrl-c at that exact time.  The fix in that case is likely to be to call
> target_terminal_ours_for_output instead, which doesn't touch the SIGINT
> handler.

That was one of my clues...  I set breakpoint on target_terminal_ours,
but it isn't hit.  Anyway, I'll look into it further.

-- 
Yao (齐尧)


  reply	other threads:[~2015-11-25 17:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-25 16:07 Yao Qi
2015-11-25 16:26 ` Pedro Alves
2015-11-25 17:16   ` Yao Qi [this message]
2015-12-01 17:15   ` Yao Qi
2015-12-03 12:47     ` Pedro Alves
2015-12-03 17:09       ` Yao Qi
2015-12-03 17:19         ` Pedro Alves

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=86h9kaxamv.fsf@gmail.com \
    --to=qiyaoltc@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@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