elinks crashes on new 16 install. How to make it create core file for bug report?
 

I just did a clean install of 16 64 bit. I installed elinks-0.12-0.26.pre5.fc16.x86_64, ran it and it crashed without starting. I looked at the dialog and figured I needed to install the debug package so installed elinks-debuginfo-0.12-0.26.pre5.fc16.x86_64 too and reran elinks with the same crash. Then I ran "gdb elinks core" per the instructions from the resulting dialog and I got on the last line "~/core: No such file or directory." So when I ran "bt" from that it gave "No stack". So where do I go from here? I can't find any bugs on bugzilla related to this and I don't know how to enable core file creation. On a side note I tried compiling elinks from source but it errored out with javascript. Thanks in advance.

May I ask how you were trying to run elinks? :scratch:

I just checked my system, and elinks-0.12-0.26.pre5.fc16.x86_64 (installed by anaconda from the Fedora 16 x64 install disk) runs with no apparent problem on my Athlon II quad-core system. (I tried it both in a terminal window and from a TTY.)

On F16, I think that the automatic core dumps are created as hidden files in /, so you need to do a ls -a / to see them. (But I may miss-remember that detail. It's been a while since I got a kernel oops.)

I ran it both ways, in a console and in a window in X. Same thing happened both times. I ran "ls -la /" as you suggested and did not find the core file. Thanks you for your reply.

I had to do another install. Then another. What a day. But I've finally got elinks working among other non-working things. I'm gonna mark this solved.