Bugs item #1760168, was opened at 2007-07-25 11:39
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=482468&aid=1760168&group_id=56967

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Jan Rittinger (tsheyar)
Assigned to: Nobody/Anonymous (nobody)
Summary: Mserver crashes in gdk_atoms.mx

Initial Comment:
If I run the following XQuery query:

declare function int-check($ylist as xs:integer*) { $ylist };
int-check(distinct-values(1 to 3))

MonetDB exits with a segfault:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1342772320 (LWP 11960)]
lngFromStr (src=0xe454dabb <Address 0xe454dabb out of bounds>, len=0xaff683fc, 
dst=0xaff68400) at /local_tmp/work/MonetDB/src/gdk/gdk_atoms.mx:1528
1528            while (GDKisspace(*p))
(gdb) bt
#0  lngFromStr (src=0xe454dabb <Address 0xe454dabb out of bounds>, 
len=0xaff683fc, dst=0xaff68400) at 
/local_tmp/work/MonetDB/src/gdk/gdk_atoms.mx:1528
#1  0xb7e182e7 in interpret_batcast (atom=0xb7c44060 "lng", argc=2, 
val=0xaff68684, res=0xaff6d3ac) at 
/local_tmp/work/MonetDB4/src/monet/monet_interpreter.mx:1684
#2  0xb7e1cf3d in interpret (stk=560, lt=0x818ade0, res=0xaff6d3ac) at 
/local_tmp/work/MonetDB4/src/monet/monet_interpreter.mx:1188

If I run the same query with debug=10 I get the following error message:

MAPI  = [EMAIL PROTECTED]:50000
QUERY = declare function int-check($ylist as xs:integer*) { $ylist };
        int-check(distinct-values(1 to 3))
ERROR = !ERROR: err:FORG0001: could not cast value from string to integer.

The reason is either the typing of fn:distinct-values or the implementation of 
distinct-values. The former provides values of type untypedAtomic* whereas the 
MIL implementation produces the more specific int*. The result is that the MIL 
implementation tries to lookup values in the wrong container.

To come back to the real bug report: Mserver shouldn't segfault!

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=482468&aid=1760168&group_id=56967

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Monetdb-bugs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/monetdb-bugs

Reply via email to