[Monetdb-developers] Restart mclient
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
, 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.
On Tue, Sep 07, 2010 at 04:02:33PM +0200, Romulo Antonio Goncalves wrote:
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
, kind = -606348325, def = 0xdbdbdbdbdbdbdbdb} (gdb)Were there any changes in the client structure or in the initialization of the of the client threads?
if it only happens in a (clean & up-to-date) default branch but not with a (clean & up-to-date) Oct2010 branch, hg diff -rOct2010 -rdefault will tell you where to start looking for differences ... ;-) Stefan
Regards, Romulo
PS: It does not happen in the Oct2010 branch.
------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by:
Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ Monetdb-developers mailing list Monetdb-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-developers
-- | Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl | | CWI, P.O.Box 94079 | http://www.cwi.nl/~manegold/ | | 1090 GB Amsterdam | Tel.: +31 (20) 592-4212 | | The Netherlands | Fax : +31 (20) 592-4199 |
The culprit seems to be changeset f2ceaaf24796:
changeset: 37471:f2ceaaf24796
parent: 37469:3733beae1496
user: Fabian Groffen
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
, 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.
------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by:
Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ Monetdb-developers mailing list Monetdb-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-developers
-- Sjoerd Mullender
participants (3)
-
Romulo Antonio Goncalves -
Sjoerd Mullender -
Stefan Manegold