summaryrefslogtreecommitdiffstats
path: root/sbin/fsck_msdosfs
diff options
context:
space:
mode:
authorcracauer <cracauer@FreeBSD.org>2003-12-28 01:20:03 +0000
committercracauer <cracauer@FreeBSD.org>2003-12-28 01:20:03 +0000
commitbbe09cbe06f729e0a06e15b026b1ade56dce13af (patch)
tree114c3af040a49fd371e182844f014e4d59b976af /sbin/fsck_msdosfs
parentf71dce4e637140c74c8880133b19f5a0bab93c5f (diff)
downloadFreeBSD-src-bbe09cbe06f729e0a06e15b026b1ade56dce13af.zip
FreeBSD-src-bbe09cbe06f729e0a06e15b026b1ade56dce13af.tar.gz
Fix signal behaviour.
In my last change I made sure that the signal as reported from a truss exit is the same as if truss wasn't between parent and trussed program. I was smart enough to not have it coredump on SIGQUIT but it didn't ocur to me SIGSEGV might cause a coredump, too :-) So get rid of SIGQUIT extra hack and limit coredumpsize to zero instead. Tested: still works, correct signal reported. No more codedumps from SIGSEGV in the trussed proces. This file compiles cleanly on AMD64 (sledge). PR: Submitted by: Reviewed by: Approved by: Obtained from: MFC after:
Diffstat (limited to 'sbin/fsck_msdosfs')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud