DragonFly BSD
DragonFly bugs List (threaded) for 2013-03
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

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


From: "Antonio M. Huete Jimenez via Redmine" <bugtracker-admin@xxxxxxxxxxxxxxxxxxxxx>
Date: Mon, 4 Mar 2013 15:42:38 -0800

Issue #2524 has been reported by tuxillo.

----------------------------------------
Bug #2524: vkernel{32,64} DDB traces not working
http://bugs.dragonflybsd.org/issues/2524

Author: tuxillo
Status: New
Priority: High
Assignee: 
Category: 
Target version: 


Hi,

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
Debugger("panic")

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

vkernels built with gcc44 don't show this behaviour.

Cheers,
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



[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]