Yesterday night I spent a couple of hours debugging the the code in branches/rivet-namespace run by a recompiled apache instance with symbols included and optimizer disabled. I can provide details of the session, but let me cut it short and ask a question to whom might have strong experience in debugging C code: what generally should be blamed for an argument value that gets changed in the process of passing control from a caller function to the callee? This is a typical mechanic I tend to give as granted....
let me specify that - the argument list of the call is made by 2 pointers (cannot imagine something simpler than that). At least the second pointer is set to zero when the callee gets control of the execution - only one specific line of code is failing this way. - the same call is ok in other circumstances, so it must be a bug! - the same call fails on a slightly different apache 2.2 version. - removing a Tcl_PkgRequire call in a different and apparently unrelated function seems to cure the problem. anyone with a strong experience debugging code has suggestions or directions? -- Massimo On 02/03/2011 08:38 AM, David Welton wrote:
Any hint what caused the segfault or why?
--------------------------------------------------------------------- To unsubscribe, e-mail: rivet-dev-unsubscr...@tcl.apache.org For additional commands, e-mail: rivet-dev-h...@tcl.apache.org
