On Fri, 29 Apr 2005, Dan McGhee wrote: > > Number one I don't know how to track down segmentations faults. The > only thing that I can say here is that both applications built and > installed without errors.
A step on the way to tracking repeatable segfaults is to install gdb (a straight configure, make, make install), then something like gdb firefox at the prompt, 'run', then when it segfaults 'bt' to get a back trace Understanding the segfault is a different matter, I guess you've already extracted the message text which is how you found the problem on arch-linux, but you might be able to get some understanding of where the error is happening, by looking at the previous calls (e.g. yesterday I traced a segfault in xmms to the flac plugin - a newer version of flac than is in the book - but got no further than "disable that plugin"). Sometimes, strace can help, [ strace progname 2>tracefile ] but on a threaded desktop app the trace is often hard to make sense of (particularly if the app has started polling for user input). Wild guess - unfortunate choice of optimisation ? Ken -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
