| Summary: | dev-db/virtuoso-server-6.1.6 segfault | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | peter <peter> |
| Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | groepaz |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | Removed on 2015/09/17 | ||
| Package list: | Runtime testing required: | --- | |
| Attachments: | emerge --info, world, make.conf | ||
Could you please try with GCC 4.7? If it still fails, could you please try 6.1.8? (In reply to Michael Palimaka (kensington) from comment #1) > Could you please try with GCC 4.7? If it still fails, could you please try > 6.1.8? I've now checked all four combinations, with the same error coming up in each case. Thus: 1. Switched GCC to 4.7.3 and recompiled virtuoso-server. (I didn't remember to recompile virtuoso-odbc.) 2. Added =dev-db/virtuoso-odbc-6.1.8 and =dev-db/virtuoso-server-6.1.8 to package.keywords and recompiled both -odbc and -server. 3. Switched GCC back to 4.8.3 and recompiled -odbc and -server. All gave the same result - segfault as reported. Sorry, but it didn't work. same here, also tried remerging various things, with no change I saw a report with a similiar segfault and it was solved by rebuilding one or more of virtuoso-server, virtuoso-odbc. rasqal, redland, soprano, and/or strigi. Failing that, a backtrace could be useful. i have rebuild various components (like the ones mentioned above) and it made no difference how exactly would i create a backtrace in this case? (it runs in the background, and various instances are started by god knows what other program(s)) (In reply to Michael Palimaka (kensington) from comment #4) > I saw a report with a similiar segfault and it was solved by rebuilding one > or more of virtuoso-server, virtuoso-odbc. rasqal, redland, soprano, and/or > strigi. Failing that, a backtrace could be useful. I remerged all those packages and didn't see another segfault up to the time the next KDE version was installed two or three days later. KDE was upgraded from 4.12.5 to 4.14.3 two days ago, but virtuoso-server, virtuoso-odbc. rasqal, redland, soprano and strigi are all still at their same versions - they haven't been upgraded since I opened this bug. I'm scratching my head now. Did recompiling those progs fix the segfaults, or have other KDE programs stopped feeding bad data? Whichever the case, I no longer see any segfaults at all, whereas they were coming every few minutes. Package removed from tree. https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0b8e1118cc57cbd0f1d08eba405f8a3e6e62a84a |
Created attachment 390128 [details] emerge --info, world, make.conf I get repeated instances of this error in /var/log/messages: virtuoso-t segfault at ffffffffffffffff ip000000000079a5b3 sp <various> error 7 in virtuoso-t[400000+97c000] I remerged virtuoso-server and it made no difference, so I ran emerge -e world overnight, compiled a new kernel and rebooted with it. Still no change. This is an amd64 box (not ~) with the KDE desktop profile selected.