Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Fernando Nasser <fnasser@redhat.com>
To: Eric Marsden <emarsden@mail.dotcom.fr>
Cc: gdb@sources.redhat.com
Subject: Re: conditional traps on powerpc
Date: Mon, 19 Feb 2001 14:33:00 -0000	[thread overview]
Message-ID: <3A919E78.A2BE2D83@redhat.com> (raw)
In-Reply-To: <wziy9v2z65l.fsf@mail.dotcom.fr>

Eric Marsden wrote:
> 
> I have a problem debugging a program which uses conditional traps on
> powerpc (TWxxx instructions). Upon encountering these the linuxppc
> kernel raises a SIGTRAP, which is grabbed by gdb. When running such a
> program under gdb I can't distinguish between normal breakpoints and
> these conditional trap instructions; debugging becomes impossible.
> 
> Is there some way to handle this situation, or is it necessary to
> modify gdb so that it looks at the faulting instruction to determine
> whether it was a conditional trap?
> 


Gdb considers that the SIGTRAP is a breakpoint if it has inserted a
breakpoint at that address; otherwise it is a signal like any other. So,
your breakpoints should work.

W.r.t the signal processing, gdb has commands that let you decide what
to do with signals received by the program being debugged.  You may
choose to "pass" them.  If I am not mistaken, this would only apply to
the SIGTRAPs that have been already determined not to be caused by a
breakpoint.








-- 
Fernando Nasser
Red Hat Canada Ltd.                     E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9


  reply	other threads:[~2001-02-19 14:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-19 13:59 Eric Marsden
2001-02-19 14:33 ` Fernando Nasser [this message]
2001-02-19 15:02   ` Andrew Cagney

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=3A919E78.A2BE2D83@redhat.com \
    --to=fnasser@redhat.com \
    --cc=emarsden@mail.dotcom.fr \
    --cc=gdb@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