|
From: Paul A. C. <pa...@us...> - 2003-09-11 15:08:57
|
I had been running with 0.9.6, and just upgraded to 1.0.4. Now, Valgrind faults immediately. Not being a Valgrind developer, this is the best info I could extract for now: $ valgrind blah Segmentation fault (core dumped) $ gdb blah core ... Core was generated by `blah'. Program terminated with signal 11, Segmentation fault. ... #0 process_cmd_line_options () at vg_main.c:642 642 } (gdb) bt #0 process_cmd_line_options () at vg_main.c:642 #1 0x00000000 in ?? () Let me know if I can provide more/better info. Regards, PC |
|
From: Paul A. C. <pa...@us...> - 2003-09-11 15:31:45
|
Wait, nevermind. I'm an idiot. (I confused the versions, thinking 1.9.6 was really 0.9.6, and 1.0.4 was "obviously" an upgrade to it. I've since really upgraded to 20030725, and things work.) Sorry for the multiple intrusions. Regards, Paul Clarke On Thu, 2003-09-11 at 10:08, Paul A. Clarke wrote: > I had been running with 0.9.6, and just upgraded to 1.0.4. Now, > Valgrind faults immediately. Not being a Valgrind developer, this is > the best info I could extract for now: > > $ valgrind blah > Segmentation fault (core dumped) > $ gdb blah core > ... > Core was generated by `blah'. > Program terminated with signal 11, Segmentation fault. > ... > #0 process_cmd_line_options () at vg_main.c:642 > 642 } > (gdb) bt > #0 process_cmd_line_options () at vg_main.c:642 > #1 0x00000000 in ?? () > > Let me know if I can provide more/better info. > Regards, > PC |
|
From: Dirk M. <dm...@gm...> - 2003-09-11 15:38:43
|
On Thursday 11 September 2003 17:08, Paul A. Clarke wrote: > I had been running with 0.9.6, and just upgraded to 1.0.4. upgrading from a stone-age version to an obsolete one? Please try a current version first. |