Message-ID: <20050309164807.GA29692@andromeda> Date: Wed, 9 Mar 2005 11:48:12 -0500 From: Justin Pryzby <email address hidden> To: <email address hidden> Subject: gimp crash
Hello,
You recently submitted a bug report on Debian's Gimp package [0]; cou you provide more information?
If you
cd; ulimit -c unlimited; rm -fr .gimp*; gimp;
you should get a 'core' file. Does
gdb core $(which gimp) bt
give a sane backtrace (or does it say "stack corrupted?").
Was this problem present on previous version of gimp? Is it only present when removing ~/.gimp*? Did gimp work immediately before remove those files?
What if you run LANG=C gimp instead?
Thanks, Justin
References
[0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=298723
Message-ID: <20050309164807 .GA29692@ andromeda>
Date: Wed, 9 Mar 2005 11:48:12 -0500
From: Justin Pryzby <email address hidden>
To: <email address hidden>
Subject: gimp crash
Hello,
You recently submitted a bug report on Debian's Gimp package [0]; cou
you provide more information?
If you
cd;
ulimit -c unlimited;
rm -fr .gimp*;
gimp;
you should get a 'core' file. Does
gdb core $(which gimp)
bt
give a sane backtrace (or does it say "stack corrupted?").
Was this problem present on previous version of gimp? Is it only
present when removing ~/.gimp*? Did gimp work immediately before
remove those files?
What if you run LANG=C gimp instead?
Thanks,
Justin
References
[0] http:// bugs.debian. org/cgi- bin/bugreport. cgi?bug= 298723