Re: [MonetDB-users] MServer crashing: Random Segmentation fault

I forgot, output from bt: (gdb) bt #0 0x0047c201 in ll_upwards () from /home/xxx/Development/pftijah/lib/MonetDB4/lib/lib_pf_support.so #1 0x011e0006 in seqscan_LH_sht_void_tloc_var_var () from /home/xxx/Development/pftijah/lib/libbat.so.0 #2 0x00000000 in ?? () junte On Fri, Apr 18, 2008 at 4:21 PM, jz@uva wrote:

On Fri, Apr 18, 2008 at 3:41 PM, Jan Rittinger wrote:

...

You could give us a hint by starting the Mserver in a debugging session:

$ gdb --args Mserver --dbinit='module(pathfinder); mil_start();'

start the Mserver with: run and create a dump as soon as you triggered the segmentation fault with: bt

This should give us an idea where your problem is located.

Thanks, this is the error I am getting:

MonetDB>[New Thread -1319306352 (LWP 18169)]

Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1319306352 (LWP 18169)] 0x0047c201 in ll_upwards () from /home/xxx/Development/pftijah/lib/MonetDB4/lib/lib_pf_support.so Missing separate debuginfos, use: debuginfo-install bzip2.i386 e2fsprogs.i386 glibc.i686 keyutils.i386 krb5.i386 libselinux.i386 openssl.i686 zlib.i386

I hope this helps....

junte

...

------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javao... _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users