1. xrdb dumping core (RedHat 4.1, Infomagic CD April 1997, XFree 3.2)
I just installed RedHat 4.1 from the Infomagic April 1997 CD. I've
got a really strange problem.
When I run xrdb with the default cpp, it dumps core. The message is
Segmentation fault (core dumped)
cpp: : I/O error
And then I wind up with the string "xterm" in my shell's input stream
(yes it's really there - if I hit <enter>, I get an xterm)!
After some digging, I found that xrdb apparently runs /lib/cpp, which
is a link to /usr/lib/gcc-lib/i386-linux/220.127.116.11/cpp. If I do
xrdb -cpp /usr/lib/gcc-lib/i386-linux/18.104.22.168/cpp
it works, but if I do
xrdb -cpp /lib/cpp
it coredumps. *EVEN THOUGH /lib/cpp IS JUST A LINK TO THE OTHER ONE!*
By replacing cpp with a script that prints out the cpp command before
executing it, I found that xrdb is calling cpp with about 12 lines of
-D options. When it works, the last one is -DCLASS_StaticGray_8=37;
when it doesn't it gets printed as -DCLASS_StaticG\nxterm (where \n is
a newline, and the 'xterm' is actually in my input buffer).
Has anyone seen anything like this? It looks like a serious memory
leak somewhere. I'll probably try XFree 3.3 first, then a fresh
installation (probably try Slackware this time), but I'm really
curious what's going on here.
System specifics: IBM 6587, S3 server (Trio64V+), XFree 3.2, RedHat
4.1, kernel 2.0.27.
John A. Breen | I teleported home one night with Ron & Sid & Meg.
| - Douglas Adams
3. xrdb dumps core
4. Select returning 0
5. Getting the function name..
6. HELP: xrdb core dumps!
7. how to debug a deadlock'ed kernel?
8. dump core or not dump core
9. core dumps core dumps everywhere...
10. Get "Segmentation fault (core dumped)" but no core file found
11. Apache problem - core dumps (httpd.core) all over the place
12. XF86_SVGA core dumped, but where is the core file?