Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: David Griffiths <dgriffiths@undo.io>
To: John Baldwin <jhb@freebsd.org>
Cc: Pedro Alves <palves@redhat.com>, gdb@sourceware.org
Subject: Re: "finish" command leads to SIGTRAP
Date: Fri, 22 Feb 2019 17:38:00 -0000	[thread overview]
Message-ID: <CA++j6c4Yur+FHqbGQFSPtThikhf=S90Gi3e4Y8=URSpCirHnNg@mail.gmail.com> (raw)
In-Reply-To: <8ad15d6e-07be-d175-6345-dddfb46f1b58@FreeBSD.org>

 By the way, just testing my workaround for this (setting a breakpoint and
continuing rather than single step) and it appears to effect both pushfq
and popfq. Even after I fixed the pushfq case the problem still occurred
because it set the TF on the popfq despite the fact the stack value didn't
contain TF.

Cheers,

David
-- 

David Griffiths, Senior Software Engineer

Undo <https://undo.io> | Resolve even the most challenging software defects
with software flight recorder technology

Software reliability report: optimizing the software supplier and customer
relationship
<https://info.undo.io/software-reliability-report-optimizing-supplier-and-customer-relationship>


      reply	other threads:[~2019-02-22 17:38 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
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 [this message]

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='CA++j6c4Yur+FHqbGQFSPtThikhf=S90Gi3e4Y8=URSpCirHnNg@mail.gmail.com' \
    --to=dgriffiths@undo.io \
    --cc=gdb@sourceware.org \
    --cc=jhb@freebsd.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