From: David Griffiths <dgriffiths@undo.io>
To: Pedro Alves <palves@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: "finish" command leads to SIGTRAP
Date: Thu, 21 Feb 2019 18:22:00 -0000 [thread overview]
Message-ID: <CA++j6c6Hgrb0CiWmC6Cq8TK=68+wak+KNz3vSXaqrs_81BpxFw@mail.gmail.com> (raw)
In-Reply-To: <743edbbc-9812-c8e7-0f47-7b4842199b48@redhat.com>
On Thu, 21 Feb 2019 at 17:50, Pedro Alves <palves@redhat.com> wrote:
>
> Same as <https://sourceware.org/bugzilla/show_bug.cgi?id=13508> ?
>
>
Yes, that's exactly it! I'd just written a simple test also to reproduce:
#include <stdio.h>
int main()
{
asm("pushf\n\t"
"popf\n\t");
printf("after popfq\n");
}
(please avoid top posting)
>
>
Sorry, gmail default!
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>
next prev parent reply other threads:[~2019-02-21 18:22 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 [this message]
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='CA++j6c6Hgrb0CiWmC6Cq8TK=68+wak+KNz3vSXaqrs_81BpxFw@mail.gmail.com' \
--to=dgriffiths@undo.io \
--cc=gdb@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