blob: e66a086f27b26342f5102daffe580fa25b43206f (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
|
[[!meta copyright="Copyright © 2010 Free Software Foundation, Inc."]]
[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
id="license" text="Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License, Version 1.2 or
any later version published by the Free Software Foundation; with no Invariant
Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license
is included in the section entitled [[GNU Free Documentation
License|/fdl]]."]]"""]]
# Existing
We have debugging infrastructure. For example:
* [[GDB]]
* [[GNU Mach debugging|microkernel/mach/gnumach/debugging]]
* [[GNU Hurd debugging|hurd/debugging]], including
[[hurd/debugging/rpctrace]], and more.
# To Do
* [[ltrace]]
* [[latrace]]
* [[profiling]]
* *Checkpoint/restart allows the state of a set of processes to be saved to
persistent storage, then restarted at some future time* -- quoting from
Jonathan Corbet's [2010 Linux Kernel Summit
report](http://lwn.net/Articles/412749/).
This is surely a very useful facility to have for reproducing failures, for
example. But on the other hand it's questionable how it can help with
debugging failures in [[GNU Hurd server|hurd/translator]]s' interactions,
as their state is typically spread between several processes.
Continues: <http://lwn.net/Articles/414264/>, which introduces
<http://dmtcp.sourceforge.net/>.
* [[locking]]
* <http://lwn.net/Articles/415728/>, or <http://lwn.net/Articles/415471/> --
just two examples; there's a lot of such stuff for Linux.
|
