Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

segfault at mal_session.c:521 #3528

Closed
monetdb-team opened this issue Nov 30, 2020 · 0 comments
Closed

segfault at mal_session.c:521 #3528

monetdb-team opened this issue Nov 30, 2020 · 0 comments

Comments

@monetdb-team
Copy link

@monetdb-team monetdb-team commented Nov 30, 2020

Date: 2014-08-06 15:27:17 +0200
From: @skinkie
To: MonetDB5 devs <>
Version: 11.17.21 (Jan2014-SP3)
CC: @mlkersten

Last updated: 2014-10-31 14:14:25 +0100

Comment 19966

Date: 2014-08-06 15:27:17 +0200
From: @skinkie

User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/37.0.2062.58 Safari/537.36
Build Identifier:

I am trying to run MonetDB from monetdbd inside gdb. I copied over the commandline from ps aux and removed some arguments. I find it typical that this does not work at all, as if there is a completely different syntax used. I'll file a separate bug.

!IOException:mal_mapi.listen:operation failed: bind to stream socket port 50000 failed: Address already in use
!SyntaxException:parseError:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
!SyntaxException:parseError: ^';' expected

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff78d801d in MALreader (c=0x645680) at mal_session.c:521
521 if (r < 0 && c->fdin->eof == 0)
!IOException:mal_mapi.listen:operation failed: bind to stream socket port 50000 failed: Address already in use
!SyntaxException:parseError:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
!SyntaxException:parseError: ^';' expected

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff78d801d in MALreader (c=0x645680) at mal_session.c:521
521 if (r < 0 && c->fdin->eof == 0)

Reproducible: Always

MonetDB 5 server v11.17.22 (64-bit, 64-bit oids)
This is an unreleased version
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2014 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Found 31.4GiB available memory, 8 available cpu cores
Libraries:
libpcre: 8.33 2013-05-28 (compiled with 8.33)
openssl: OpenSSL 1.0.1h 5 Jun 2014 (compiled with OpenSSL 1.0.1h 5 Jun 2014)
libxml2: 2.9.1 (compiled with 2.9.1)
Compiled by: skinkie@bigdata.openebs.nl (x86_64-unknown-linux-gnu)
Compilation: gcc -g -Werror -Wall -Wextra -W -Werror-implicit-function-declaration -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wformat=2 -Wno-format-nonliteral -Winit-self -Winvalid-pch -Wmissing-declarations -Wmissing-format-attribute -Wmissing-prototypes -Wold-style-definition -Wpacked -Wunknown-pragmas -Wvariadic-macros -fstack-protector-all -Wstack-protector -Wpacked-bitfield-compat -Wsync-nand -Wjump-misses-init -Wmissing-include-dirs -Wlogical-op -Wunreachable-code
Linking : /usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64

Comment 19981

Date: 2014-08-06 19:05:07 +0200
From: @mlkersten

It looks like you forgot to add --dbinit="sql.start();" as an argument to the list you extract from merovingian.log

Comment 19991

Date: 2014-08-06 21:16:09 +0200
From: @skinkie

Created attachment 293
Guard reading c->fdin when it has not been allocated

(In reply to comment 1)

It looks like you forgot to add --dbinit="sql.start();" as an argument to
the list you extract from merovingian.log

Is forgetting - or not - an excuse to bail out with a segfault?

Attached file: guard_c_fdin_null-3528.diff (text/plain, 354 bytes)
Description: Guard reading c->fdin when it has not been allocated

Comment 19992

Date: 2014-08-06 21:22:23 +0200
From: @mlkersten

Indeed, for the expert user a few more defense lines could be added to the core.

thx, Martin

Comment 20370

Date: 2014-10-31 14:14:25 +0100
From: @sjoerdmullender

Oct2014 has been released.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant