summaryrefslogtreecommitdiffstats
path: root/libexec
diff options
context:
space:
mode:
authorkib <kib@FreeBSD.org>2012-08-14 12:15:01 +0000
committerkib <kib@FreeBSD.org>2012-08-14 12:15:01 +0000
commit92b79b92fb839b664e41c671fcfd29ebfe578dc4 (patch)
tree080fe1902f5d341c66e9a38440d49b82b606b56e /libexec
parent11621fbf7f3f18c2e71e0074b0e680b15336b0bf (diff)
downloadFreeBSD-src-92b79b92fb839b664e41c671fcfd29ebfe578dc4.zip
FreeBSD-src-92b79b92fb839b664e41c671fcfd29ebfe578dc4.tar.gz
Add a hackish debugging facility to provide a bit of information about
reason for generated trap. The dump of basic signal information and 8 bytes of the faulting instruction are printed on the controlling terminal of the process, if the machdep.uprintf_signal syscal is enabled. The print is the only practical way to debug traps from a.out processes I am aware of. Because I have to reimplement it each time I debug an issue with a.out support on amd64, commit the hack to main tree. MFC after: 1 week
Diffstat (limited to 'libexec')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud