Aren/NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
e663963d4a
NetBSD/doc/TODO.ptrace

38 lines
1.9 KiB
Plaintext
Raw Normal View History

Add new entry in TODO.ptrace about PT_STEP with a signal Added: GDB Remote Protocol expects a case with a step with a signal to be sent, this is currently unsupported on NetBSD
2017-03-02 17:25:41 +03:00
$NetBSD: TODO.ptrace,v 1.25 2017/03/02 14:25:41 kamil Exp $
Add initial TODO list for the ptrace(2) (and procfs) interface. Sponsored by <The NetBSD Foundation>
2016-12-13 12:44:35 +03:00
Items we (currently) plan to finish in the ptrace(2) field:
- verify ppid of core dump generated with PT_DUMPCORE
it must point to the real parent, not tracer
- adapt OpenBSD regress test (regress/sys/ptrace/ptrace.c) for the ATF context
Update TODO.ptrace Added: - reiterate over FreeBSD tests and add missing ones if applicable Sponsored by <The NetBSD Foundation>
2017-01-26 04:12:13 +03:00
- reiterate over FreeBSD tests and add missing ones if applicable
Add initial TODO list for the ptrace(2) (and procfs) interface. Sponsored by <The NetBSD Foundation>
2016-12-13 12:44:35 +03:00
- add PT_DUMPCORE tests in the ATF framework
- add ATF tests for PT_WRITE_I and PIOD_WRITE_I - test mprotect restrictions
- add tests for the procfs interface covering all functions available on the
same level as ptrace(2)
Update TODO.ptrace Note BSD4.4-like /proc debugging removal Explain kevent(2)-based debugging proposal Sponsored by <The NetBSD Foundation>
2017-02-13 18:29:18 +03:00
- remove 4.4BSD tracing with /proc, restrict /proc to Linux compat, to be
superseded with kevent tracing, the original purpose of /proc debugging is
long gone (performance issues with PT_WRITE_* and PT_READ_*)
- research kevent support for tracing a process over a file descriptor,
this means alternative to wait(2)-based events with passing events over the
kqueue API - signal handlers are global per application and they clash with
GUI toolkits (and perhaps other libraries) - this is long term wishlist in
GDB for Linux - the current approach is to fork and debug through GDB remote
protocol (this is how it is done in LLDB)
Update TODO.ptrace Add new entries: - add support for PT_STEP, PT_GETREGS, PT_SETREGS, PT_GETFPREGS, PT_SETFPREGS in all ports - integrate all ptrace(2) features in gdb - add ptrace(2) NetBSD support in LLDB Sponsored by <The NetBSD Foundation>
2016-12-14 09:26:04 +03:00
- add support for PT_STEP, PT_GETREGS, PT_SETREGS, PT_GETFPREGS, PT_SETFPREGS
in all ports
Update TODO.ptrace Removed: - evaluate equivalent for PTRACE_O_TRACECLONE from Linux clone(2)-like calls are traced with PTRACE_FORK, PTRACE_VFORK and PTRACE_VFORK_DONE. VFORK ones block parent till termination or execve(2) of its child. Added: - add proper implementation of PTRACE_VFORK for vfork(2)-like events Currently PTRACE_VFORK is a stub. Sponsored by <The NetBSD Foundation>
2017-01-14 04:36:28 +03:00
- add proper implementation of PTRACE_VFORK for vfork(2)-like events
Add new entry in TODO.ptrace New entry: - add ATF tests for SIGCHLD
2016-12-24 08:43:31 +03:00
- add ATF tests for SIGCHLD
Update TODO.ptrace Note PT_WATCHPOINT change to PT_*ETDBREGS. Remove GDB and LLDB related entries from generic ptrace(2) TODO. Note need for TRAP_SCE and TRAP_SCX si_codes in PT_SYSCALL*. Note removal request of pthread_dbg(3). Sponsord by <The NetBSD Foundation>
2017-02-07 19:15:05 +03:00
- add si_code values for PT_SYSCALL: TRAP_SCE and TRAP_SCX
Update TODO.ptrace Remove entries: - remove exect(3) from libc - there is no usecase for it Interface has been marked obsolete and it's on the queue to be removed for. - research what happens when a tracee masks signals (including SIGTRAP) and a breakpoint is triggered It has been researched and ATF tests added (signal1 .. signal10). It's currently broken on NetBSD. Add: - research support PT_SYSCALL & PT_STEP combined like in Linux There are circumstances when we want to sstep and catch syscall events. Sponsored by <The NetBSD Foundation>
2017-02-11 22:10:04 +03:00
- research support PT_SYSCALL & PT_STEP combined like in Linux
Update TODO.ptrace with new entries Added entries: - add support to read debugger events via a file descriptor in procfs (kevent(2)), it's still useful in cases when a parent traces tracee and has to call waitpid(2) for its child - as this clashes with GUI toolkits - fix more calls for netbsd32 compat Sponsored by <The NetBSD Foundation>
2017-02-12 08:21:34 +03:00
- fix more calls for netbsd32 compat
Add new entry to TODO.ptrace research ipkdb(4) Sponsored by <The NetBSD Foundation>
2017-02-14 21:38:07 +03:00
- research ipkdb(4)
Add new entry in TODO.ptrace Research kgdb. It should be supported by GDB and LLDB. Sponsored by <The NetBSD Foundation>
2017-02-18 00:22:02 +03:00
- research kgdb(4)
Add new entry to TODO.ptrace check 64-bit debugger on 64-bit kernel tracing capabilities of 32-bit tracee Sponsored by <The NetBSD Foundation>
2017-02-20 06:37:24 +03:00
- check 64-bit debugger on 64-bit kernel tracing capabilities of 32-bit tracee
Add new entry in TODO.ptrace about PT_STEP with a signal Added: GDB Remote Protocol expects a case with a step with a signal to be sent, this is currently unsupported on NetBSD
2017-03-02 17:25:41 +03:00
- GDB Remote Protocol expects a case with a step with a signal to be sent,
this is currently unsupported on NetBSD
Add initial TODO list for the ptrace(2) (and procfs) interface. Sponsored by <The NetBSD Foundation>
2016-12-13 12:44:35 +03:00
and of course: fix as many bugs as possible.
Features in ELF, DWARF, CTF, DTrace are out of scope of the above list.
Reference in New Issue Copy Permalink