This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug breakpoints/17468] New: syscalls not recorded with arch (or some such)


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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]