itself. > >How does one debug that? gdb -> valgrind -> app? > >That segfaults even earlier and gives a totally useless >backtrace without any >debug info... > >Hints? >From my recent experience debugging valgrind (I am busy working on having gdb able to properly debug a process which is running under valgrind):
Valgrind uses SIGSEGV for some internal house keeping. So, when you debug valgrind, you have some "normal" SIGSEGV and some "abnormal SIGSEGV" indicating a real problem in valgrind. What I have seen is that the "normal" SIGSEGV have a not understandable backtrace. Just "continue" till you arrive on the SIGSEGV which is really interesting you: this one should have a proper backtrace showing correctly the valgrind code which triggers the unexpected SIGSEGV. Philippe ____ This message and any files transmitted with it are legally privileged and intended for the sole use of the individual(s) or entity to whom they are addressed. If you are not the intended recipient, please notify the sender by reply and delete the message and any attachments from your system. Any unauthorised use or disclosure of the content of this message is strictly prohibited and may be unlawful. Nothing in this e-mail message amounts to a contractual or legal commitment on the part of EUROCONTROL, unless it is confirmed by appropriately signed hard copy. Any views expressed in this message are those of the sender. ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
