public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug gdb/18060] New: eflags.TF left set after exiting from record mode
@ 2015-02-28  0:14 dje at google dot com
  2015-02-28  0:14 ` [Bug record/18060] " dje at google dot com
  2015-02-28  0:26 ` palves at redhat dot com
  0 siblings, 2 replies; 3+ messages in thread
From: dje at google dot com @ 2015-02-28  0:14 UTC (permalink / raw)
  To: gdb-prs

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.


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug record/18060] eflags.TF left set after exiting from record mode
  2015-02-28  0:14 [Bug gdb/18060] New: eflags.TF left set after exiting from record mode dje at google dot com
@ 2015-02-28  0:14 ` dje at google dot com
  2015-02-28  0:26 ` palves at redhat dot com
  1 sibling, 0 replies; 3+ messages in thread
From: dje at google dot com @ 2015-02-28  0:14 UTC (permalink / raw)
  To: gdb-prs

https://sourceware.org/bugzilla/show_bug.cgi?id=18060

dje at google dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|gdb                         |record

-- 
You are receiving this mail because:
You are on the CC list for the bug.


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug record/18060] eflags.TF left set after exiting from record mode
  2015-02-28  0:14 [Bug gdb/18060] New: eflags.TF left set after exiting from record mode dje at google dot com
  2015-02-28  0:14 ` [Bug record/18060] " dje at google dot com
@ 2015-02-28  0:26 ` palves at redhat dot com
  1 sibling, 0 replies; 3+ messages in thread
From: palves at redhat dot com @ 2015-02-28  0:26 UTC (permalink / raw)
  To: gdb-prs

https://sourceware.org/bugzilla/show_bug.cgi?id=18060

Pedro Alves <palves at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |palves at redhat dot com

--- Comment #1 from Pedro Alves <palves at redhat dot com> ---
I'd suspect your recording session stepped into a signal handler while
recording, and then you tripped on the kernel bug behind Bug 17511.

A kernel patch for that bug just made it to the mm tree this week...

-- 
You are receiving this mail because:
You are on the CC list for the bug.


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2015-02-28  0:22 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-02-28  0:14 [Bug gdb/18060] New: eflags.TF left set after exiting from record mode dje at google dot com
2015-02-28  0:14 ` [Bug record/18060] " dje at google dot com
2015-02-28  0:26 ` palves at redhat dot com

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).