Hi Florian,

Thanks.
I added this information, slightly rewritten, to the muse wiki.
http://muse-sequencer.org/index.php/Support#Bug_reporting_.2F_Troubleshooting

Regards,
Robert

2011/9/30 Florian Jung <florian.a.jung@web.de>
Hi

there are often bug reports like "muse segfaults when i do [foo]". when
i or the dev fixing that bug tries to reproduce them, he often can't
(that's these nasty small non-reproducible bugs which _really_ suck).

i'd like you all to run a simple small command whenever using muse:

ulimit -c unlimited

this enables core dumps. that is, when muse crashes, its memory is
written to a file called "core".

"gdb muse2 core" allows you to get very, very usable information. like a
backtrace for the beginning ("bt")

a bug report without a backtrace or at least "heavyDebug" turned on
("muse2 -DD") is almost useless.


running that command, or putting it into your bashrc doesn't hurt
(except you have 20MB of free disk space left) and helps IF there's a
segfault. (compiling muse with build type = debug also helps xD)

thanks
flo


------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
_______________________________________________
Lmuse-developer mailing list
Lmuse-developer@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lmuse-developer