How best to debug a SIGSEGV segmentation fault in QNX app

I have a multithreaded QNX 6.2.1 application running on an embedded x86 target which is terminating randomly with a memory fault. Running the application in the QNX IDE debugger has shown the problem is generating a SIGSEGV signal and the debugger call stack shows all the threads suspended, but how can I find the thread and source code line which generated the fault? Trying to use the debugger in a post-mortem mode with a core dump file generated from the dumper utility has been unsuccessful. When the core dump file is loaded in the debugger, it shows nothing in the debug or information panes. Any ideas or hints on how to use the debugger to find this problem would be greatly appreciated.


Your bild variant is “debug”? What show command: gdb prog prog.core ?

Thanks for the suggestion. Yes I am using a debug variant build. By trying to evoke gdb debugger from the command line as suggested I found the issue is in the Momentic IDE. It does not appear to handle windows directory names with spaces for the path to the core dump file. After a directory rename I can now load the core dump file into the IDE debugger and see the thread states at the seg fault. Unfortunately it still is not very clear were the seg fault happened and what the cause was.


This print filter can have a segmentation fault when running with the -Q2 quality. When you create a QNX project in the IDE, a static+shared+debug will occur. If you get any solution please do share with all of us.

646-204 questions | 642-901 questions | 642-892 questions