sebastian guttenberg wrote:
No idea what happened this time. Was trying to write an 'A' in an
equation in a footnote :
Fixed.
Abdel.
Stefan Schimanski wrote:
It's the line which sets the buffer for a new inset.
Yes, I added this line and there was not crash before. I guess the
passed inset is null and it wasn't before. Why would we want to insert a
null inset anyway? That seems like a bigger problem to me.
I had a bad fe
It's the line which sets the buffer for a new inset. I had a bad
feeling about this Buffer* patch for insets and now it bites us with
plenty of segfaults :-/
Stefan
Am 29.02.2008 um 18:12 schrieb Abdelrazak Younes:
Stefan Schimanski wrote:
Does it happen all the time? I cannot reproduce it
Stefan Schimanski wrote:
Does it happen all the time? I cannot reproduce it. It would help a lot
if you find a sequence of keypresses or so to trigger the crash.
Alt-i f
Ctrl-m
A
Happens all the time. Must be a recent commit because it didn't happen
before I svn updated.
Abdel.
Stefan
A
Does it happen all the time? I cannot reproduce it. It would help a
lot if you find a sequence of keypresses or so to trigger the crash.
Stefan
Am 29.02.2008 um 16:48 schrieb sebastian guttenberg:
No idea what happened this time. Was trying to write an 'A' in an
equation in a footnote :
No idea what happened this time. Was trying to write an 'A' in an
equation in a footnote :
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1224735024 (LWP 18784)]
0x0926b0cd in ?? ()
(gdb) bt
#0 0x0926b0cd in ?? ()
#1 0xbfc6007b in ?? ()
#2 0x08b746a0 in ?? ()
#3
