public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "dje at google dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/18060] New: eflags.TF left set after exiting from record mode
Date: Sat, 28 Feb 2015 00:14:00 -0000 [thread overview]
Message-ID: <bug-18060-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=18060
Bug ID: 18060
Summary: eflags.TF left set after exiting from record mode
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: dje at google dot com
Not sure how I did this, I can't recreate it with toy programs.
I was playing with recording gdb, and after doing "record stop"
I did "continue" and got a SIGTRAP.
It didn't appear to be a case of an int3 left in the instruction stream.
It turned out to be due to eflags.TF being set.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2015-02-27 23:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-28 0:14 dje at google dot com [this message]
2015-02-28 0:14 ` [Bug record/18060] " dje at google dot com
2015-02-28 0:26 ` palves at redhat dot com
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=bug-18060-4717@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).