[DragonFlyBSD - Bug #2524] (Closed) vkernel{32, 64} DDB traces not working

Antonio M. Huete Jimenez via Redmine bugtracker-admin at leaf.dragonflybsd.org
Mon Mar 4 23:27:36 PST 2013

Issue #2524 has been updated by tuxillo.

Status changed from New to Closed

27a084b96f9fc3e6a273da6e7673553a85132986 fixes at least vkernel's backtrace when triggered by a normal panic.

debug.panic2 sysctl isn't supposed to work on vkernels.

Bug #2524: vkernel{32,64} DDB traces not working

Author: tuxillo
Status: Closed
Priority: High
Target version: 


DDB traces do not work when vkernels are compiled with gcc47.
To trigger it, just boot a vkernel built with gcc47 and 'sysctl debug.panic=1' or 'sysctl debug.panic2=1'

vkernel64 it will either SIGILL or print just fail to find any stack frame:

0x8033d56590 does not look like a stack frame, skipping
0x8033d56598 does not look like a stack frame, skipping
Unable to find anything that looks like a stack frame

vkernel32 will simply SIGILL (100% times I've tested it).

vkernels built with gcc44 don't show this behaviour.

Antonio Huete

You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account

More information about the Bugs mailing list