[issue1614] x86_64 garbled backtrace

New submission from Alex Hornung <[e-mail]>:

We really need to fix the garbled output of the db> trace on x86_64, it mak=
es it=20
difficult to debug a number of issues.
Does anyone have any insight on why this happens?

Cheers,
Alex Hornung

----------
messages: 7835
nosy: alexh
priority: critical
status: unread
title: x86_64 garbled backtrace

_____________________________________________________
DragonFly issue tracker <[e-mail]>
<http://bugs.dragonflybsd.org/issue1614>
_____________________________________________________