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 breakpoints/17468] New: syscalls not recorded with arch (or some such) Date: Wed, 08 Oct 2014 16:27:00 -0000 [thread overview] Message-ID: <bug-17468-4717@http.sourceware.org/bugzilla/> (raw) 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.
next reply other threads:[~2014-10-08 16:27 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-10-08 16:27 dje at google dot com [this message] 2014-10-08 19:10 ` [Bug breakpoints/17468] " sergiodj at redhat dot com 2014-10-08 19:13 ` dje at google 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-17468-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: linkBe 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).