Since I don't have much of a guess where the problem is, and I wasn't able to
get more information with gdb (because I didn't get the SEGV with it), I will
tell you the history of this problem.
A friend with a scanner created (via Photoshop?) a bitmap .eps file for me.
He said he had scanned at 600 bits per inch; the image is about 2.5 inches
wide by 4.5 inches high. I tried to put it into a figure float in LyX 1.0.1
(built from source without any customization). The figure float expanded to
enormous size, and this message appeared in the xterm in which I had started
LyX:
lyx: SIGSEGV signal caught
Sorry, you have found a bug in LyX. If possible, please read 'Known bugs'
under the Help menu and then send us a full bug report. Thanks!
lyx: Attempting to save document /home/dennis/study/diagrams/den/steps.lyx as...
1) /home/dennis/study/diagrams/den/steps.lyx.emergency
Save seems successful. Phew.
Bye.
I tried to capture the SEGV with gdb, but didn't succeed:
512:~/study/diagrams/den: gdb lyx
GDB 4.15.1 (i486-slackware-linux),
Copyright 1995 Free Software Foundation, Inc...(no debugging symbols found)...
(gdb) run steps.lyx
Starting program: /usr/local/bin/lyx steps.lyx
Error: /undefined in \305\320\323\306\330P
Operand stack:
Execution stack:
%interp_exit () --nostringval-- --nostringval-- --nostringval-- false
--nostringval-- --nostringval-- %runexec_finish --nostringval--
--nostringval-- --nostringval--
Dictionary stack:
--dict:667/701-- --dict:0/20-- --dict:43/200--
Current allocation mode is local
Current file position is 7
When I attempted a "full-screen preview" of the figure, the window that
appeared showed this:
Unrecoverable error: undefined in \305\320\323\306\330P
Unexpected interpreter error -21.
Error object: \305\320\323\306\330P(d84)name(0x8110ed4#bb)
Execution stack at 0x810f384:
0x81186ac: 0x0f oper --F---e-- 0x0000 0x0806e704 = %interp_exit
0x81186b4: 0x12 str --F-rxe-- 0x0000 0x00000000 =
0x81186bc: 0x03 file --L-rxe-- 0x0001 0x0811fee8
0x81186c4: 0x0e null --F---e-- 0x0000 0x080795b8
0x81186cc: 0x03 file --S-rxe-- 0x0001 0x08112604
0x81186d4: 0x0f oper --F---e-- 0x0000 0x08079574 = %runexec_finish
0x81186dc: 0x03 file --S-rxe-- 0x0001 0x08112604
0x81186e4: 0x05 mpry --G-rxe-- 0x0039 0x0814ea7e
Dictionary stack at 0x810f2ac:
0x8118edc: 0x02 dict --Gwrx--- 0x0000 0x0811902c
0x8118ee4: 0x02 dict --Gwrx--- 0x0000 0x0815d098
0x8118eec: 0x02 dict --Lwrx--- 0x0000 0x0811df30
I went into Windows 95 and opened the file in Photoshop. It showed its
resolution as 75 bits per inch, which I guess accounted for the huge figure
size. I then saved it at 600 bits per inch as a binary .eps file. (This
file was about half the size of the original.)
Back in Linux, I started LyX on the same .lyx file, with the new file for the
problem figure float. The outline box for the figure now looked the right
size, but again I got the SEGV message. And again under gdb I didn't get that
but instead got almost (but not quite) the same message as before:
511:~/study/diagrams/den: gdb lyx
GDB 4.15.1 (i486-slackware-linux),
Copyright 1995 Free Software Foundation, Inc...(no debugging symbols found)...
(gdb) run steps.lyx
Starting program: /usr/local/bin/lyx steps.lyx
Error: /undefined in \305\320\323\306r
Operand stack:
Execution stack:
%interp_exit () --nostringval-- --nostringval-- --nostringval-- false
--nostringval-- --nostringval-- %runexec_finish --nostringval--
--nostringval-- --nostringval--
Dictionary stack:
--dict:667/701-- --dict:0/20-- --dict:43/200--
Current allocation mode is local
Current file position is 5
Finally I set "no render" for the figure, which avoided these error messages.
However, then as before, when I selected "View dvi" from the File menu I got
this message:
! Unable to read an entire line---bufsize=3000.
Please ask a wizard to enlarge me.
xdvi: DVI file corrupted
I hope this information is useful. If you need more information or files,
let me know. If you have any advice, I will appreciate that, too.
Dennis
