On Wednesday 27 February 2002 12:23 pm, Martin Vermeer wrote:
> I don't know if this is related -- but there are still clear problems with the
> new graphics.
>
> - I don't ever manage to get a child processes dialog that is *not* greyed out,
> or has any entries in it.
Well, the browsers are only active if a forked process is running. So this is correct.
Things should change automagically as you launch a process and as it finishes.
> - Under some circumstances (after the graphics have rendered, and very regularly)
> I do not manage to exit. LyX goes dead on me, nothing works, not even the 'x'
> in the top right window corner. Pressing ^C prints 'Bye' and then again nothing.
> I have to hard kill the window to get out.
This is the same as the bug in grfx::GImageXPM::Data::~Data that you report below
I think.
> - Frequently I get a SIGSEGV on exit, after rendering is done. This happens
> always when some image has been in the field of view for a small amount of time,
> even if it doesn't render to visibility. If I don't scroll to the picture area,
> no matter how long I wait, no SIGSEGV.
Well that's because the image isn't loaded! You requested that!
> Program received signal SIGSEGV, Segmentation fault.
> 0x40227010 in chunk_free (ar_ptr=0x18014d, p=0x84f9648) at malloc.c:3051
> 3051 malloc.c: No such file or directory.
> Current language: auto; currently c
> (gdb) info stack
> #0 0x40227010 in chunk_free (ar_ptr=0x18014d, p=0x84f9648) at malloc.c:3051
> #1 0x40226fba in __libc_free (mem=0x84f9650) at malloc.c:3023
> #2 0x81ed9a5 in grfx::GImageXPM::Data::~Data (this=0x84f5a1c, __in_chrg=2)
> at ../../src/support/utility.h:44
Is this with current cvs which has
grfx::GImageXPM::Data::~Data{}
rather than
grfx::GImageXPM::Data::~Data{ free_color_table }
?
Angus
