On Thu, Dec 22, 2005 at 12:29:58AM -0800, Max Alekseyev wrote:
> Steve Langasek wrote:
> >Well, after fixing the dialog crash, the link from the bug report works
> >fine
> >for me on alpha. Perhaps you could test using the patch I sent in the last
> >mail, to confirm the bug still exists?
> Unfortunately it still crashes even with the patch.
Well, then I'm afraid I'm out of ideas; the valgrind output doesn't give any
clear pointers, and I can't reproduce the bug on the only 64-bit system
under my control. But at least the problem seems to be very specific to
d4x, since hundreds of other gtk-based applications have been running fine
using the glib/gtk combination on all architectures for some time.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
<email address hidden> http://www.debian.org/
On Thu, Dec 22, 2005 at 12:29:58AM -0800, Max Alekseyev wrote:
> Steve Langasek wrote:
> >Well, after fixing the dialog crash, the link from the bug report works
> >fine
> >for me on alpha. Perhaps you could test using the patch I sent in the last
> >mail, to confirm the bug still exists?
> Unfortunately it still crashes even with the patch.
Well, then I'm afraid I'm out of ideas; the valgrind output doesn't give any
clear pointers, and I can't reproduce the bug on the only 64-bit system
under my control. But at least the problem seems to be very specific to
d4x, since hundreds of other gtk-based applications have been running fine
using the glib/gtk combination on all architectures for some time.
-- www.debian. org/
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
<email address hidden> http://