public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
* [Bug breakpoints/17468] New: syscalls not recorded with arch (or some such) @ 2014-10-08 16:27 dje at google dot com 2014-10-08 19:10 ` [Bug breakpoints/17468] " sergiodj at redhat dot com 2014-10-08 19:13 ` dje at google dot com 0 siblings, 2 replies; 3+ messages in thread From: dje at google dot com @ 2014-10-08 16:27 UTC (permalink / raw) To: gdb-prs https://sourceware.org/bugzilla/show_bug.cgi?id=17468 Bug ID: 17468 Summary: syscalls not recorded with arch (or some such) Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: breakpoints Assignee: unassigned at sourceware dot org Reporter: dje at google dot com I happened to stumble on this. On amd64, where there is an "accept" syscall for amd64 but not i386 (at least not in the xml file) $ make run (gdb) catch syscall accept Unknown syscall name 'accept'. (gdb) file ~/hello.x64 ... (gdb) catch syscall accept. Unknown syscall name 'accept'. Start over and select the executable first. $ make run (gdb) file ~/hello.x64 ... (gdb) catch syscall accept Catchpoint 1 ... The syscall file name is stored in a global, as a record of whether it has been loaded, and once set is assumed to be ok for life. This should be recorded with the arch or some such. -- 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 breakpoints/17468] syscalls not recorded with arch (or some such) 2014-10-08 16:27 [Bug breakpoints/17468] New: syscalls not recorded with arch (or some such) dje at google dot com @ 2014-10-08 19:10 ` sergiodj at redhat dot com 2014-10-08 19:13 ` dje at google dot com 1 sibling, 0 replies; 3+ messages in thread From: sergiodj at redhat dot com @ 2014-10-08 19:10 UTC (permalink / raw) To: gdb-prs https://sourceware.org/bugzilla/show_bug.cgi?id=17468 Sergio Durigan Junior <sergiodj at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |sergiodj at redhat dot com Resolution|--- |DUPLICATE --- Comment #1 from Sergio Durigan Junior <sergiodj at redhat dot com> --- There is already a bug for this (I am taking care of it). I am closing as duplicate. *** This bug has been marked as a duplicate of bug 10737 *** -- 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 breakpoints/17468] syscalls not recorded with arch (or some such) 2014-10-08 16:27 [Bug breakpoints/17468] New: syscalls not recorded with arch (or some such) dje at google dot com 2014-10-08 19:10 ` [Bug breakpoints/17468] " sergiodj at redhat dot com @ 2014-10-08 19:13 ` dje at google dot com 1 sibling, 0 replies; 3+ messages in thread From: dje at google dot com @ 2014-10-08 19:13 UTC (permalink / raw) To: gdb-prs https://sourceware.org/bugzilla/show_bug.cgi?id=17468 --- Comment #2 from dje at google dot com --- (In reply to Sergio Durigan Junior from comment #1) > There is already a bug for this (I am taking care of it). I am closing as > duplicate. > > *** This bug has been marked as a duplicate of bug 10737 *** Thanks. I had hoped bugzilla would give me the existing CL while I was filing it (like it tries to do). Oh well, no worries. -- 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:[~2014-10-08 19:13 UTC | newest] Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2014-10-08 16:27 [Bug breakpoints/17468] New: syscalls not recorded with arch (or some such) dje at google dot com 2014-10-08 19:10 ` [Bug breakpoints/17468] " sergiodj at redhat dot com 2014-10-08 19:13 ` dje at google 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).