On Nov 19, 2006, at 12:00 PM, Abdelrazak Younes wrote:
Bennett Helm wrote:
On Nov 19, 2006, at 7:36 AM, Peter Kümmel wrote:
It looks like we rely on a Qt bug on Windows and on Linux.
Bennett could you please try the attached patch.
Thanks, Peter. However, I still get a crash. Here's the only
backtrace I get:
This is not a crash on exit but on startup right?
Starting program: /Applications/LyX-150.app/Contents/MacOS/lyx
splash screen requested
show banner: 1
LyXComm: Pipe /Users/bennett/Library/Application Support/
LyX-1.4/.lyxpipe.in already exists.
If no other LyX program is active, please delete the pipe by hand
and try again.
So, if you delete that file what happens?
Program received signal EXC_BAD_ACCESS, Could not access memory.
This is yet something else I guess...
Abdel.
Reason: KERN_INVALID_ADDRESS at address: 0x50207473
0x50207473 in ?? ()
(gdb) bt
#0 0x50207473 in ?? ()
Bennett
The crash I got was on exit, not on startup. This time I
deleted .lyxpipe.in (from another instance of LyX I had running), and
tried 1.5 again. Again, a crash on exit, but a more informative
backtrace:
(gdb) run
Starting program: /Applications/LyX-150.app/Contents/MacOS/lyx
Reading symbols for shared
libraries ..............................................................
..... done
Reading symbols for shared libraries . done
Reading symbols for shared libraries . done
Reading symbols for shared libraries . done
Reading symbols for shared libraries . done
Reading symbols for shared libraries . done
Reading symbols for shared libraries . done
Reading symbols for shared libraries . done
splash screen requested
show banner: 1
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0x50207473
0x50207473 in ?? ()
(gdb) bt
#0 0x50207473 in ?? ()
#1 0x0008bd51 in lyx::LyXComm::endPipe (this=Cannot access memory at
address 0x9
) at lyxserver.C:209
Cannot access memory at address 0x1
Previous frame inner to this frame (corrupt stack?)
(gdb)
Bennett
