From 2779e230f15ee716d30a89a109f8cd994aa7a215 Mon Sep 17 00:00:00 2001 From: tofergus Date: Tue, 26 Jul 2016 20:37:00 +0000 Subject: [PATCH] Add link to 'gdb' debugging bug. --- docs/howtos/HowToDebugVKernels/index.mdwn | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/howtos/HowToDebugVKernels/index.mdwn b/docs/howtos/HowToDebugVKernels/index.mdwn index d8878969..17b4de7c 100644 --- a/docs/howtos/HowToDebugVKernels/index.mdwn +++ b/docs/howtos/HowToDebugVKernels/index.mdwn @@ -224,7 +224,7 @@ Among other things, you can have a look at vkernel's process list using ps: gdb and vkernel (SMP or not) don't play well together anymore. It is possible to get into a state where the vkernel is in state "stop" and the vkernel is in "wait", and nothing moves on. The only help is to kill gdb, which either makes the vkernel run again, or kills it as well. -See also [[!df-bug 1301]]). +See also [[!df-bug 1301]]. Experience has shown that running vkernel with -n1, that is telling it to emulate only 1 CPU, alleviates the issue. @@ -232,4 +232,6 @@ Experience has shown that running vkernel with -n1, that is telling it to emulat > > [...] 4.4-RELEASE DragonFly v4.4.3.9.ge5cb2-RELEASE #0: Fri Jul 15 03:04:52 UTC 2016 [...]/X86_64_GENERIC x86_64 > +> See [[!df-bug 2931]] for details. +> > -- [[tofergus]] -- 2.41.0