Segfaults in multiple programmes
Running NetBSD but had the same problems in Alpine Linux. I already posted to multiple lists, though received no answer.
All my GTK+2 apps segfault on keyboard input. lxappearance for example, when looking for a theme you can start pressing keys and it will search. But in my case it dumps core with /usr/lib/libpthread.so.1, /usr/lib/libc.so.12 and /usr/pkg/lib/libXcursor.so.1. The same thing happens when typing something into a GTK+2 text editor, leafpad, or looking for something in Ctrl+O window in firefox or gimp or any other programme. gimp can't even run inside gdb because of: Code:
Program received signal SIGTRAP, Trace/breakpoint trap. lxappearance also dumps core when clicking Apply after changing something (themes, cursor or icon themes, fonts etc.) with another output: Code:
#0 0x00007f7fefcb27ba in ?? () from /usr/lib/libc.so.12 sxiv, an image viewer, segfaults with this: Code:
#0 0x00007f7ff64b209f in ?? () from /usr/lib/libc.so.12 mpg321 dumps core and says "Memory fault" with this backtrace: Code:
#0 0x00007f7ff78068b1 in sem_post () from /usr/lib/libpthread.so.1 Thanks everyone for any kind of help. |
A real segmentation fault is a memory paging fault. It dates to the 80286, which had 20 address lines, but only 16 bit registers. How do you put data in the top 4 address bits? The answer was 4 bit paging registers. Except when you addressed a page with no memory on it, you got a segmentation error. Nowadays, they're any memory error.
On 2 separate Operating Systems, we can eliminate software. You're left with ( in rough order) 1. Memory errors. 2. Disk errors. 3. Some weird motherboard error. The big ASICs you get today can cause errors that are next to impossible to trace. Heat can also bring them on. 4. Power supply problems. If you're overclocking, stop. Check all cooling. Run overnight on memtest86. Check the disks with smartmontools as well as the filesystem utilities. Borrow someone's power supply to check that. That eliminates all except the motherboard. |
Quote:
Dell's ePSA includes all kinds of tests, keyboard, hard drive, memory, fans, CPU. It didn't return any errors. I may try longer memtests but yet I am not convinced that these are hardware problems. |
if not hardware related, then probably you have incompatible libraries
|
Ubuntu with glibc and Void with musl seem ti eliminate memory, and most of the motherboard. It still leaves disks, and the psu errors become more remote.
Check the disks. Install something properly. You should not have segfaults. |
It looks like your ports tree is out of sync with the base system (hence the libc related core dumps). As you've provided next to no info of the release version of NetBSD you're running, it's hard to say for sure.
As you've installed binary packages and have also been building via pkgsrc that could also be part of the issue. What repository do you have defined in: /usr/pkg/etc/pkgin/repositories.conf ? |
Does BSD have anything comparable to Linux's /sbin/ldconfig command? A loader name-cache that must be updated (by re-running this privileged command ...) whenever libraries change?
Basically, it does sound like "incompatible libraries." If one library attempts to call another, and it doesn't actually know what the parameter-list should be, how parameters are to be passed and so-forth, then basically "all hell breaks loose real quick." :eek: For instance, a parameter got added to a function in version 3.x of the library. The function-call pushes three items onto the stack: the called function pops-off four. Not only is its "fourth parameter" garbage, but, "say goodbye to your stack!" You're headed for a hard fall, and probably a totally-useless stack trace. "Basically, 'the stack got munged.'" And in this case, the information found in a traceback probably is neither meaningful nor correct – because the content and thus the expected structure of the stack was hosed. |
Yes, ldconfig(8) has been around in various BSD's since the early days.
However, NetBSD in particular seems to be moving away from it: https://www.netbsd.org/docs/elf.html |
Cág did post a dmesg earlier today at daemonforums, looking for NetBSD-specific help. It's NetBSD 7.0.2, amd64, on an Ivy Bridge CPU.
|
Quote:
However, my "gut take" on this particular situation is probably that it is something much more basic –*such as quite-literal "library incompatibility," or something that didn't get re-compiled, and so on. It's "just not nice™" when pieces of computer software can't play well together . . . :rolleyes: |
I ran testdisk and two things caught my attention:
Code:
Warning: Bad starting head (CHS and LBA don't match) Code:
PCH transcoder FIFO underrun /* it has always been on this machine) */ A note about mplayer: as I said on DF, it receives SIGILL if running alone and SIGSEGV if inside gdb and in different spots: Code:
Program terminated with signal SIGILL, Illegal instruction. Code:
Program received signal SIGSEGV, Segmentation fault. Code:
http://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/$arch/7.0/All ldconfig(8) is disabled as advised. |
Quote:
Nearly certainly you should be set on 255 heads; There is only 2, but it was about the one number with room in it. but altering the heads setting may break up data on the partition. Graphics is another area where software lies have affected hardware designs, as nobody thought about vga when the pc was designed. The competition was from CP/M mini computers on 80x25 consoles, and mainframes on something similar. Consoles were for printing ascii, and incapable of graphics, although that, like everything else changed. My suggestion: Ignore the graphics errors(my system says most of that); Back up, change to 255 heads and see what breaks; there's usually an autodetect in the bios these days; You have an acpi problem. I'd delete and reinstall that. Then see what shows. |
Quote:
Quote:
|
I'm not familiar with "testdisk" so not sure if that error referring to the drive geometry is relevant. Can you post your fdisk and disklabel outputs? For disklabel you will need to specify the device node.
|
Drive geometry should have nothing to do with segfaults. Unless I completely misunderstand.
|
All times are GMT -5. The time now is 10:12 PM. |