Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Orjan Friberg <orjan.friberg@axis.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: schedlock.exp questions
Date: Wed, 25 Aug 2004 15:11:00 -0000	[thread overview]
Message-ID: <412CABED.10108@axis.com> (raw)
In-Reply-To: <20040824145502.GA26280@nevyn.them.org>

Daniel Jacobowitz wrote:
> 
> No.  The request was "single-step this thread, but allow other threads
> to run while you do it".  Other threads might report a breakpoint (not
> possible in this testcase), but they shouldn't report a single-step
> trap - they shouldn't singlestep.

Thanks for clarifying.  Would you mind explaining the "not possible in 
this testcase" part?  I do get spurious SIGTRAPs for the other threads 
from the "break 41 if arg != 5" breakpoint, reported as SIGTRAP (instead 
of as breakpoint hits).

Strangely enough, for the CRIS target (the above refers to CRISv32) I
*also* get breakpoint hits from "break 41 if arg != 5" for the other 
threads also (noticed by inspecting the remote communication), but these 
are ignored by GDB (neither displayed as breakpoint hits, nor as SIGTRAPs).

This is all when stepping without a lock, BTW.

Any insight as to what's going on is greatly appreciated.

-- 
Orjan Friberg
Axis Communications


  reply	other threads:[~2004-08-25 15:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-24 14:51 Orjan Friberg
2004-08-24 14:55 ` Daniel Jacobowitz
2004-08-25 15:11   ` Orjan Friberg [this message]
2004-08-25 16:03     ` Daniel Jacobowitz
2004-08-27 13:59       ` Orjan Friberg
2004-08-31 14:41         ` Orjan Friberg
2004-09-07 12:48       ` Orjan Friberg

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=412CABED.10108@axis.com \
    --to=orjan.friberg@axis.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sources.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