Bugs item #1323802, was opened at 2005-10-11 14:19 Message generated for change (Comment added) made by boncz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=482468&aid=1323802&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: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: Wouter Alink (vzzzbx) Assigned to: Wouter Alink (vzzzbx) Summary: Mserver/XQuery: Segfault on Ctrl-C Initial Comment: Suppose you don't want to wait for the answer to an XQuery issued from a MapiClient. In that case I found the option on the Mserver-console to press Ctrl-C most useful. The expected behaviour is that Mserver exits 'clean', but if it is busy with an XQuery, it exits accompanied with a Segfault. ---------------------------------------------------------------------- >Comment By: Peter Boncz (boncz) Date: 2007-05-25 02:29 Message: Logged In: YES user_id=591107 Originator: NO closing this one then ---------------------------------------------------------------------- Comment By: Wouter Alink (vzzzbx) Date: 2007-05-24 23:48 Message: Logged In: YES user_id=621590 Originator: YES i'm still using Ctrl-C quite often these days, but i haven't seen Mserver segfault anymore (neither 0.12 nor 0.16) for quite a while. When i reported the bug it almost always segfaulted on ctrl-c. Is this enough reason to close the bug? i will reopen the bug on the first ctrl-c segfault i encounter. about finding a test query: i don't know how to slow down monetdb without monetdb being (memory) I/O bound. the best xquery test i can come up with at the moment is: count(1 to 125000000) which at least has to allocate about 1GB of memory (which often takes at least a second), but it is difficult to guarantee a certain duration. On systems with little available memory it might cause other errors, and on high-end systems it might not even take a second. ---------------------------------------------------------------------- Comment By: Sjoerd Mullender (sjoerd) Date: 2007-02-27 16:43 Message: Logged In: YES user_id=43607 Originator: NO Assigned to Wouter since he was asked a question. ---------------------------------------------------------------------- Comment By: Fabian (mr-meltdown) Date: 2006-06-06 21:04 Message: Logged In: YES user_id=963970 Wouter, is this still working for you? Also is it possible to create a long-running query (with a small dataset) that Mtest can timeout on? ---------------------------------------------------------------------- Comment By: Niels Nes (nielsnes) Date: 2005-12-19 21:18 Message: Logged In: YES user_id=43556 BugDay_2005-12-19, Niels: RELEASED / REASSIGN Could maybe be tested using a long running xquery query, but with a low timeout ---------------------------------------------------------------------- Comment By: Wouter Alink (vzzzbx) Date: 2005-10-11 14:28 Message: Logged In: YES user_id=621590 now that i'm thinking of it... if a MapiClient gets killed with Ctrl-C, it would be nice of MapiClient if it at least tries to send a "i'm dying" message to the Mserver before it actually dies, so that Mserver can stop computing the answer. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=482468&aid=1323802&group_id=56967 ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Monetdb-bugs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/monetdb-bugs
