> No, haven't seen that -- I do that all the time with no ill effects.
> Can you put the coredump/file up for ftp/http/something?
I'm not the original poster, but I have seen sporadic crashes as well
when you edit stuff. Here is an example backtrace:
(gdb) bt
#0 0x401b1d97 in gdk_rgb_convert_truecolor_lsb ()
#1 0x401b3798 in gdk_draw_rgb_image_core ()
#2 0x401b387e in gdk_draw_rgb_image ()
#3 0x806dbbe in renderer_libart_copy_to_window (renderer=0x29d02b5,
window=0x8100200, x=2, y=135155412, width=0, height=0)
at render_libart.c:240
#4 0x8138188 in ?? ()
#5 0x10fcc in ?? ()
(gdb) print *renderer
Cannot access memory at address 0x29d02b5.
I don't know why stack levels #4 & 5 are not resolved, but maybe you
know the code well enough to determine the hot spot anyway.
I use Imlib and libart based rendering. I don't have POPT or GNOME
enabled. I run Dia fresh from cvs on a Linux RedHat 5.2 Intel platform.
May I suggest that you add a SIGENV handler such that you do not loose
your work when Dia crashes? I.e. take a look at LyX which emergency
saves all your open documents when LyX crashes. That has saved many
people a lot of grief.
Greets,
Asger Alstrup
