seg fault - how to track down cause!

Patrick O'Callaghan pocallaghan at gmail.com
Fri Aug 8 09:40:11 UTC 2014


On Thu, 2014-08-07 at 17:51 -0700, Jack Craig wrote:
> yes!  use ps *** to get parent pid to follow, then i think the chant
> is
> something like,
> 
> strace -f -p <pid>
> 
> note, a lot of system call info gets dumped, but IMHO, the needle is
> in
> that haystack!
> 
> you might want to log output to a file, ...
> 
> also, i loved to find a failing clue and then pipe strace -f ... |
> grep
> <myclue>
> 

Or you can attach a gdb instance to it and watch the segfault happening,
get a backtrace etc. That's what debuggers are for.

[Please don't top-post on this list. See the Guidelines]

poc



More information about the users mailing list