[Monetdb-developers] Restart mclient

Romulo Antonio Goncalves R.A.Goncalves at cwi.nl
Tue Sep 7 16:02:33 CEST 2010


Hello, 

I updated my default branch and I do the following:

mclient -lmal
>\q
mclient -lmal
>\q

After the second exit I get a crash in the mserver:
>[New Thread 0x7fffdf7ac710 (LWP 19441)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffdf7ac710 (LWP 19441)]
0x00007ffff7cd7198 in MALexitClient (c=0x605b38) at /ufs/goncalve/MonetDB/current/MonetDB5/src/mal/mal_session.mx:522
522             if (c->glb && c->curprg->def->errors == 0)
(gdb) p c->curprg->def
$1 = (struct MALBLK *) 0xdbdbdbdbdbdbdbdb

Similar problem if you do
mclient -lsql
>\q
mclient -lsql

The mserver crashes due to the same problem:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffdf7ac710 (LWP 19561)]
0x00007fffdfe22a60 in SQLparser (c=0x605b38) at /ufs/goncalve/MonetDB/current/sql/src/backends/monet5/sql_scenario.mx:1155
1155            oldvtop = c->curprg->def->vtop;
(gdb) p c->curprg
$5 = (Symbol) 0x7fffd8112198
(gdb) p *c->curprg
$6 = {peer = 0xdbdbdbdbdbdbdbdb, skip = 0xdbdbdbdbdbdbdbdb,
  name = 0xdbdbdbdbdbdbdbdb <Address 0xdbdbdbdbdbdbdbdb out of bounds>, kind = -606348325, def = 0xdbdbdbdbdbdbdbdb}
(gdb)


Were there any changes in the client structure or in the initialization of the of the client threads?

Regards,
Romulo

PS: It does not happen in the Oct2010 branch.




More information about the developers-list mailing list