From: Alan W. I. <ir...@be...> - 2013-11-16 00:33:02
|
On 2013-11-15 14:34-0800 Alan W. Irwin wrote: > If you trigger the segfault, but we cannot spot anything wrong in > those files, I already have some ideas about continuing this segfault > chase by narrowing down the test even more leading eventually to a > simplest possible example of the problem that we can then analyze with > valgrind on your platform and also on ours. > > Thanks very much for reporting this segfault issue in the first place. > They are the very bugger to track down (since the memory management > issue that is typically the cause, may be symptomless on other > platforms except for valgrind warnings). I hope you will stick with > us (probably for several more iterations) until we have it nailed. Hi Alexis: Never mind. The whole point of those detailed instructions was to figure out why you were getting the segfault, and I was not. But something changed from yesterday until today for me (I am not sure what), and now I see that segfault as well. So I can take it from here and will let you know when I have that solved. Alan __________________________ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); the Time Ephemerides project (timeephem.sf.net); PLplot scientific plotting software package (plplot.sf.net); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ |