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 gdb/10736] New: GDB doesn't reread the syscall xml when the user changes the data-directory.


When the user changes the data-directory, gdb doesn't try
to re-read the syscall file.  This means no amount of
"set data-directory" to point at the real data directory path
fixes "catch syscall" after gdb having noticed it didn't find
the xml once.

E.g.:

 (gdb) catch syscall 1
 warning: Could not open "syscalls/i386-linux.xml"
 warning: Could not load the syscall XML file `syscalls/i386-linux.xml'.
 GDB will not be able to display syscall names.
 warning: The number '1' does not represent a known syscall.
 Catchpoint 1 (syscall 1)

<ooops, I need to set the data-directory>

 (gdb) set data-directory ../../src/gdb
 (gdb) catch syscall 2
 warning: The number '2' does not represent a known syscall.
 Catchpoint 2 (syscall 2)
 (gdb)

<still no go>

vs 

<restart gdb,losing the debug session>

 (gdb) set data-directory ../../src/gdb
 (gdb) catch syscall 2
 Catchpoint 1 (syscall 'fork' [2])

-- 
           Summary: GDB doesn't reread the syscall xml when the user changes
                    the data-directory.
           Product: gdb
           Version: 6.50
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: gdb
        AssignedTo: unassigned at sourceware dot org
        ReportedBy: pedro at codesourcery dot com
                CC: gdb-prs at sourceware dot org


http://sourceware.org/bugzilla/show_bug.cgi?id=10736

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


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