Hi, I have been using gsl on 64 bit machine for a long time and I have never seen segmentation fault due library unless I am doing something wrong. For 64 bits I find the library is stable. Best thing will be to run gdb/ddd to chck from where the fault is coming from. I would suggest you to run debugger to see where is the problem. Valgrind is useful to find memory leak, but gdb/ddd will very fast take you there from where the error is coming from. Most of the cases it might be a typecast problem or a erroneous delete of an array and so on. Regards, Sumit
On Sat, Jan 30, 2010 at 12:47 AM, Thomas Weber <thomas.weber.m...@gmail.com>wrote: > Please keep the list cc'ed. > > On Fri, Jan 29, 2010 at 12:09:07PM -0700, JongKwan Kim wrote: > > Thanks for your answer. > > I am trying the find the error in my code. > > > > Thanks, > > I've found valgrind extremely helpful in finding these kinds of bugs. > > Thomas > > > _______________________________________________ > Help-gsl mailing list > Help-gsl@gnu.org > http://lists.gnu.org/mailman/listinfo/help-gsl > -- -------------------------------------------- Sumit Adhikari System Design Engineer austriamicrosystems AG Business Unit : Automotive Mob : 00-91-9885271710/00-91-9000161710 _______________________________________________ Help-gsl mailing list Help-gsl@gnu.org http://lists.gnu.org/mailman/listinfo/help-gsl
