very minor frame manager segfault bug
Brought to you by:
robinrowe
Kind of a nitpicky-bug I guess, but what the hey:
When a new frame manager is created for a picture, and
the frame manager window brought up, a segfault occurs
when the advance button is clicked (there are no more
frames to advance to).
This is the stack trace:
#0 0x4018d638 in g_on_error_stack_trace () from
/usr/lib/libglib-1.2.so.0
#1 0x4018d55e in g_on_error_query () from
/usr/lib/libglib-1.2.so.0
#2 0x080cf268 in fatal_error (fmt=0x817729d "sigsegv
caught") at errors.c:55
#3 <signal handler called>
#4 0x4031934f in strlen () from /lib/libc.so.6