re: Crashes with latest gtk+2.0-2.2.2 package
On Wed, Jul 16, 2003 at 09:45:21AM +0900, Akira TAGOH wrote:
> >>>>> On Tue, 15 Jul 2003 15:14:40 -0500,
> >>>>> "AH" == Art Haas <ahaas@airmail.net> wrote:
>
> What do you mean 'when the dialog box is being removed'?
> just pressed the cancel button? or selected the filename,
> then pressed the ok button?
The hangs have happened when hitting either button. The dialog box
erased from the screen, then the program just sits there and fails to
redraw itself. I saw this with both the eog and gnumeric I'd built (both
from CVS). I also have problems with my CVS PyGTK build when it tries to
display the "File Open" dialog. I was able to get a backtrace on that
and the crash was in mallopt(), suggesting some sort of memory
corruption. I can send it along if wanted.
> actually eog and gnumeric works on purely the latest sid
> box, though.
I build lots of stuff with CVS, but have been relying on the Debian
packages for the core libraries - glib, atk, pango, and gtk. I've been
building with CVS gcc-3.3-branch compilers, building them weekly or so
and using them instead of the Debian packaged GCC. As I build and use so
much stuff from CVS builds I was and am very hesistant to file a bug
report on the new GTK package. My mozilla build using the GTK-2.0
libraries and xft works nicely, and other GTK stuff works too. It is
just something peculiar about the 'File Open' dialog that has so far
been a hiccup.
Art Haas
--
Man once surrendering his reason, has no remaining guard against absurdities
the most monstrous, and like a ship without rudder, is the sport of every wind.
-Thomas Jefferson to James Smith, 1822
Reply to: