On Fri, 18 Sep 2015, Lennart Sorensen wrote:
On the other hand the crash I can backtrace nicely in gdb. The assert I
might not be able to (not sure really). So the assert may actually
hinder debuging.
It should work. It should call abort() and core dump and exit, much as
SEGV should. Either way, the debugger should notice I think (presumably by
catching the SIGABRT or SEGV?).
The main difference is:
# ./test assert
test: test.c:10: main: Assertion `0' failed.
Aborted (core dumped)
# ./test 0
Segmentation fault (core dumped)
Which means we should get a bit more information by default from users in
the initial problem report, I hope.
OK, as long as it can't just happen because of a received packet from
elsewhere.
Yeah, that's bad.
As discussed previously we have that at present, but to mitigate even
worse problems. We should still do better. :)
regards,
--
Paul Jakma p...@jakma.org @pjakma Key ID: 64A2FF6A
Fortune:
Know what I hate most? Rhetorical questions.
-- Henry N. Camp
_______________________________________________
Quagga-dev mailing list
Quagga-dev@lists.quagga.net
https://lists.quagga.net/mailman/listinfo/quagga-dev
