Continuing digging deeper into debugging approaches. Apparently gcc has it's own signal handling system and crash is not seen to gdb / ddd debugger. There exists some instructructions - like here: http://gcc.gnu.org/bugs/segfault.html http://gcc.gnu.org/ml/gcc-help/2004-03/msg00332.html
but even with --enable-checking I was not able to get rid of "internal compiler error" signal handler: ---------------------------------------------------------------------------------------------------------------------------------------- /usr/include/stdio.h:528: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. ---------------------------------------------------------------------------------------------------------------------------------------- So dehydra plugin looks like it's a part of gcc process and handled by the same gcc's handler. So it's not even possible to catch it at crash point. Still awaiting for some comments on dehydra plugin debugging. _______________________________________________ dev-static-analysis mailing list [email protected] https://lists.mozilla.org/listinfo/dev-static-analysis
