Bugs item #1730547, was opened at 2007-06-04 10:42 Message generated for change (Comment added) made by stmane You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=482468&aid=1730547&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: PF/runtime Group: Pathfinder CVS Head Status: Open Resolution: Fixed Priority: 8 Private: No Submitted By: Wouter Alink (vzzzbx) Assigned to: Stefan Manegold (stmane) Summary: XQ: Mserver crashes on concatenated query Initial Comment: The attached query looks like: "aap", "aap", "aap", "aap", ... (1000 times) "aap", "aap" When given to Mserver, it says: Segmentation Fault (0.12 as well as 0.17 (build last week)). This bug should not have high priority. ---------------------------------------------------------------------- >Comment By: Stefan Manegold (stmane) Date: 2009-11-21 15:34 Message: =================================================================== 2009/11/21 - stmane: pathfinder/runtime/pathfinder.mx,1.462.4.12 use more conservative stack limit (PFmaxstack) for too deep recusion check (PFrecursion_fence()) to prevent segfault (due to too deep recursion and consequent stack overflow) in tests tests/BugTracker/Tests/collection_management.SF-1726599.* tests/BugTracker/Tests/crash_on_concatenated_query.SF-1730547.* cf., https://sourceforge.net/tracker/?func=detail&aid=1607210&group_id=56967&atid=482468 https://sourceforge.net/tracker/?func=detail&aid=1730547&group_id=56967&atid=482468 =================================================================== 2009/11/21 - stmane: pathfinder/tests/BugTracker/Tests/crash_on_concatenated_query.SF-1730547.timeout,1.1.2.1 extended timeout for slow(er) systems =================================================================== Report can be closed once nightly testing confirms the fix for all platforms. ---------------------------------------------------------------------- Comment By: Stefan Manegold (stmane) Date: 2009-11-17 10:15 Message: Instead of a "ERROR = !fatal error: aborted too deep recursion" the test now (again) triggers a timeout or segfault on all platform: http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora10/tests_BugTracker/crash_on_concatenated_query.SF-1730547.err.00.html ---------------------------------------------------------------------- Comment By: Stefan Manegold (stmane) Date: 2008-11-19 14:52 Message: It was the "expected" output, since this test used to trigger a "ERROR = !fatal error: aborted too deep recursion" (and hence produce no output) on all platforms. Apparently, this is no longer the case but now some platforms are able to run the test without error, i.e., producing some (correct? -> to be checked! ...) output. Maybe, we need to split this test into two, a small one that works on all platforms and a huge one that fails (i.e., triggers a reasonable error message) on all platforms ... ---------------------------------------------------------------------- Comment By: Jan Rittinger (tsheyar) Date: 2008-11-19 14:42 Message: Hmm I'm not sure if the 'correct' output is indeed the correct one: http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/Int.64.32.d.1-Fedora8/tests_BugTracker/crash_on_concatenated_query.SF-1730547.out.00.html @ Stefan could you please verify. ---------------------------------------------------------------------- Comment By: Stefan Manegold (stmane) Date: 2007-06-05 20:44 Message: Logged In: YES user_id=572415 Originator: NO Test added in pathfinder/tests/BugTracker/Tests/Attic/crash_on_concatenated_query.SF-1730547.* Thanks to Peter's latest fix, it now correctly triggers "ERROR = !fatal error: aborted too deep recursion" instead of crashing the server. ---------------------------------------------------------------------- Comment By: Peter Boncz (boncz) Date: 2007-06-05 18:31 Message: Logged In: YES user_id=591107 Originator: NO fixed ---------------------------------------------------------------------- Comment By: Peter Boncz (boncz) Date: 2007-06-05 18:31 Message: Logged In: YES user_id=591107 Originator: NO fixed ---------------------------------------------------------------------- Comment By: Stefan Manegold (stmane) Date: 2007-06-04 21:19 Message: Logged In: YES user_id=572415 Originator: NO Debugging releaved that the segfault is indeed caused by burg running out of stack space due to too deep recursion. See also [ 1607210 ] XQ: server-side compilation crash (member benchmark) http://sourceforge.net/tracker/index.php?func=detail&aid=1607210&group_id=56967&atid=482468 ---------------------------------------------------------------------- Comment By: Stefan Manegold (stmane) Date: 2007-06-04 18:21 Message: Logged In: YES user_id=572415 Originator: NO for got to mention: pf "eventually" produces some MIL plan; no error. ---------------------------------------------------------------------- Comment By: Stefan Manegold (stmane) Date: 2007-06-04 18:20 Message: Logged In: YES user_id=572415 Originator: NO Running this through plain pf (0.18), i.e., { for i in `seq 1 999` ; do echo '"aap",' ; done ; echo '"aap"' ; } | pf makes pf grow to 2.7 GB virt (1.8 GB res) on my 64-bit FC6 machine; hence, this might well be a memory and/or burg problem, especially on 32-bit machines. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=482468&aid=1730547&group_id=56967 ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Monetdb-bugs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/monetdb-bugs
