Differences between revisions 1 and 2
Revision 1 as of 2006-07-23 20:43:16
Size: 986
Editor: dsl093-172-095
Comment:
Revision 2 as of 2006-07-23 20:44:16
Size: 996
Editor: dsl093-172-095
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
'''General
''' * There are lots of bugs in the GNATS database. Everyone is welcome to look at them, reproduce them, comment on them, fix them, et cetera!
'''General'''

* There are lots of bugs in the GNATS database. Everyone is welcome to look at them, reproduce them, comment on them, fix them, et cetera!
Line 4: Line 6:
Line 5: Line 8:
'''gdbserver
''' * Gdbserver for GNU/Linux uses timeouts and waits for child processes repeatedly. Try stracing it while running a program to see what this means. GDB uses sigsuspend and catches SIGCHLD instead. It would be more efficient for gdbserver to do the same thing. This requires a bit of reorganization for the backend to handle SIGCHLD.

'''gdbserver'''

* Gdbserver for GNU/Linux uses timeouts and waits for child processes repeatedly. Try stracing it while running a program to see what this means. GDB uses sigsuspend and catches SIGCHLD instead. It would be more efficient for gdbserver to do the same thing. This requires a bit of reorganization for the backend to handle SIGCHLD.

General

  • There are lots of bugs in the GNATS database. Everyone is welcome to look at them, reproduce them, comment on them, fix them, et cetera!

Watchpoints

  • GDB issues an error if you try to set a hardware watchpoint on an unreadable address (for instance, an address which has not been malloc'd yet). It disables watchpoints when addresses become unreadable. Hardware permitting, it would be great to be able to set watchpoints in advance. With address space randomization turned off, as it still is on many systems, this would let you restart a program and find the first write to a heap data structure.

gdbserver

  • Gdbserver for GNU/Linux uses timeouts and waits for child processes repeatedly. Try stracing it while running a program to see what this means. GDB uses sigsuspend and catches SIGCHLD instead. It would be more efficient for gdbserver to do the same thing. This requires a bit of reorganization for the backend to handle SIGCHLD.

None: ProjectIdeas (last edited 2021-03-10 14:25:22 by TomTromey)

All content (C) 2008 Free Software Foundation. For terms of use, redistribution, and modification, please see the WikiLicense page.