Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: David Griffiths <dgriffiths@undo.io>
Cc: gdb@sourceware.org
Subject: Re: "finish" command leads to SIGTRAP
Date: Thu, 21 Feb 2019 13:12:00 -0000	[thread overview]
Message-ID: <78e1f522-f6f5-d38d-0644-d083c1e4ab5d@redhat.com> (raw)
In-Reply-To: <CA++j6c6A0DMRwOGBJ4XGGWnC49D1Wi9J9kz6kzSmaj+kiJXo-w@mail.gmail.com>

Might be unrelated, but ISTR that there used to be a kernel bug
that would lead to the cpu's trace flag getting stuck set
when you step in a signal handler.  That would result in
SIGTRAP happening at every step from that point on.  Could
that be the case here?

I'd look at "set debug displaced on" too.  Otherwise, it's a matter
at staring at the logs, and trying to understand what is happening.
Basically, "finish" sets a breakpoint at the caller and runs to it.
But all sorts of other things can happen behind the scenes.

Thanks,
Pedro Alves


  reply	other threads:[~2019-02-21 13:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-21 11:21 David Griffiths
2019-02-21 11:24 ` Pedro Alves
2019-02-21 12:13   ` David Griffiths
2019-02-21 12:17     ` David Griffiths
2019-02-21 13:12       ` Pedro Alves [this message]
2019-02-21 15:55         ` David Griffiths
2019-02-21 17:50           ` Pedro Alves
2019-02-21 18:03             ` Pedro Alves
2019-02-21 18:22             ` David Griffiths
2019-02-21 18:50             ` John Baldwin
2019-02-21 19:34               ` Pedro Alves
2019-02-21 20:50                 ` John Baldwin
2019-02-22 15:09                   ` Pedro Alves
2019-02-22 16:42                     ` John Baldwin
2019-02-22 17:38                       ` David Griffiths

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=78e1f522-f6f5-d38d-0644-d083c1e4ab5d@redhat.com \
    --to=palves@redhat.com \
    --cc=dgriffiths@undo.io \
    --cc=gdb@sourceware.org \
    /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