Konstantin Belousov
b6d3609050
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
2012-08-14 12:15:01 +00:00
2012-08-14 12:15:01 +00:00
2012-08-11 05:58:56 +00:00
2012-08-13 21:04:01 +00:00
2012-08-12 17:01:07 +00:00
2012-08-05 20:19:27 +00:00
2012-08-14 12:09:36 +00:00
2012-08-13 17:38:38 +00:00
2012-07-24 16:29:33 +00:00
2012-04-12 21:34:58 +00:00
2012-08-14 05:16:35 +00:00
2012-08-14 11:45:47 +00:00
2012-04-12 21:34:58 +00:00
2012-08-10 18:43:29 +00:00
2012-08-01 23:05:57 +00:00
2012-08-13 18:52:51 +00:00
2012-08-05 14:11:42 +00:00
2012-08-11 23:48:39 +00:00
2012-06-11 17:42:39 +00:00
2012-08-13 17:38:38 +00:00
2012-07-30 03:00:58 +00:00
2012-08-05 14:11:42 +00:00
2012-08-08 17:16:06 +00:00
2012-02-28 15:07:05 +00:00
2012-08-03 12:55:31 +00:00
2012-08-07 07:52:25 +00:00
2012-08-02 13:57:49 +00:00
2012-07-22 17:46:05 +00:00
2012-06-01 03:59:08 +00:00
2012-07-10 21:02:59 +00:00
2012-02-03 13:08:44 +00:00
2012-08-14 11:45:47 +00:00
2012-01-31 02:11:05 +00:00
2012-08-05 14:11:42 +00:00
2012-07-09 20:42:08 +00:00
2012-04-16 10:33:46 +00:00
2012-08-04 03:05:01 +00:00
2012-05-03 15:51:34 +00:00
2012-08-05 22:03:13 +00:00
2012-08-12 17:53:06 +00:00
2012-02-21 19:35:59 +00:00
2012-08-05 14:11:42 +00:00
2012-08-14 12:11:48 +00:00
2012-08-07 23:16:11 +00:00
2012-02-29 17:47:01 +00:00
2012-03-20 18:05:15 +00:00
b6d3609050