On Wed, 21 Jul 2004 19:01:49 +0200 (Romance Daylight Time) Vadim Zeitlin <[EMAIL PROTECTED]> wrote:
VZ> NB> VZ> Looks like something is badly corrupted :-( Any chance to run M under VZ> NB> VZ> valgrind? VZ> NB> I used all of them, like that: VZ> NB> valgrind --tool=memcheck --log-file=memcheck src/M VZ> VZ> Oops, sorry, I should have told you to use only memcheck. I don't even VZ> know what do the others do to be honest. VZ> VZ> NB> With some M hanged, with one (massif) valgrind segfaulted, with memcheck VZ> NB> I got following output: VZ> VZ> I didn't have time to look at everything but at least part of the errors VZ> -- and maybe even the one causing the crash -- should be fixed in wxGTK VZ> cvs. VZ> VZ> For the future, it can also be helpful to set env var MALLOC_CHECK_ VZ> (notice trailign underscore!) to 2 and run M under gdb, then it will abort VZ> whenever glibc detects memory corruption (see "man 3 malloc") which should VZ> at least give a meaningful back trace instead of an infinite loop in malloc. Thanks, now I can use M with wxGTK2! I cannot use right click in a Text viewer - GTK2 context menu appears. How to fix it? Regards, Nerijus ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click _______________________________________________ Mahogany-Developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mahogany-developers
