Akkarin Posted November 8, 2012 Group: Forum Manager Topic Count: 282 Topics Per Day: 0.06 Content Count: 3144 Reputation: 1632 Joined: 03/26/12 Last Seen: April 15 Share Posted November 8, 2012 Morning all! I was browsing the core section on the bug tracker and thought "i has idea!". I don't know how feasible it'd be, or even if we'd be able to obtain the desired results.. but would it be possible to have, for example, the map server capture the last few lines of output, and send a trace to us before crashing completely? Under certain strict conditions ofcourse, otherwise we'd end up with reports from script-kiddies attempts at changing their src. It might give our core devs something concrete to look at instead of half-arsed bug reports with half the info missing. We do it for data collection, could we do it for this too? Just an idea. Quote Link to comment Share on other sites More sharing options...
Euphy Posted November 8, 2012 Group: Members Topic Count: 72 Topics Per Day: 0.02 Content Count: 2997 Reputation: 1132 Joined: 05/27/12 Last Seen: June 1, 2017 Share Posted November 8, 2012 It sounds good in concept, but how feasible is this, exactly? Is there a way to limit reports to unmodified source files, and if so, would that even be useful anymore? (seeing as almost everyone has to modify their source at some point) Quote Link to comment Share on other sites More sharing options...
Ind Posted November 8, 2012 Group: Members Topic Count: 169 Topics Per Day: 0.03 Content Count: 1260 Reputation: 750 Joined: 11/19/11 Last Seen: April 11, 2013 Share Posted November 8, 2012 its far more evasive than the stat reporter, and at most cases pretty pointless -- there is little to no useful information it outputs prior to crashing. 1 Quote Link to comment Share on other sites More sharing options...
Cookie Posted November 9, 2012 Group: Members Topic Count: 20 Topics Per Day: 0.00 Content Count: 213 Reputation: 109 Joined: 05/21/12 Last Seen: December 27, 2014 Share Posted November 9, 2012 Hm, it's not a bad idea but I sort of agree with Ind. In all honesty, the core dumps are really helpful (themselves) especially for printing variables and such for null pointers with gdb. Not only that, this seems slightly more invasive. Quote Link to comment Share on other sites More sharing options...
Brian Posted November 9, 2012 Group: Members Topic Count: 75 Topics Per Day: 0.02 Content Count: 2223 Reputation: 593 Joined: 10/26/11 Last Seen: June 2, 2018 Share Posted November 9, 2012 Any crash info it sends prior to actually crashing would not be as valuable as the dump after crashing, right? What if we add a script (Bash, Perl, PHP, something) in /tools that users can run? - it would search ../ for core dumps - run them through GDB to get 'bt full' - send that to us (via email, HTML Post, or the easiest method we can think of) - would it be necessary to send copies or blocks of certain source files so we can see what line numbers are being referenced? - optionally delete the core dump after (so it doesn't resend it next time) or we can do the filtering on our end to ignore duplicates The script would be completely optional and would require them to run it in order for it to send anything. Quote Link to comment Share on other sites More sharing options...
xazax Posted November 9, 2012 Group: Members Topic Count: 11 Topics Per Day: 0.00 Content Count: 427 Reputation: 123 Joined: 11/17/11 Last Seen: December 31, 2022 Share Posted November 9, 2012 What I used to use with my server was a script which detected if the server crashed and issues the following command: gdb -q -s $1 -c core -ex 'bt full' -ex 'quit' >> crashdump.log where $1 was the name of the server. Of course the script executed ulimit -c unlimited before it started the servers. I think it is pretty easy to implement some shell script for automatic dumps, the problem might be to make it platform independent, I don't know how big the differencies are across linux distributions for instance. 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.