Tracking down segfaults

james on 2003-01-30T11:24:24

A couple of us spent ages tracking down a segfault last night. This fault has been annoying us for a while, as we couldn't isolate when and where it was happening. Yesterday we found out roughly where it happened, and called the pack to chase. After about four hours of gdb, printlines and hoping for the segfault to appear we got it. One line in the MIME::Lite module, that occasionally would cause the system to segfault:

open SENDMAIL, "|$sendmailcmd"

Phffft. Something is going wrong in open somewhere, sometimes. Time to change the implementation methinks.


Yes, but *what* is going wrong?

nicholas on 2003-01-30T12:15:11

Phffft. Something is going wrong in open somewhere, sometimes.

Did you try running it under valgrind to get a backtrace of exactly where in the C source the SEGV was? If you can get a line number and argument backtrace from a -g> build that would make an interesting perl bug report.