Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 10.0.10
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Environment:Arch Linux, gcc 4.9, Akonadi 1.12.1
Description
Originally reported here:
https://bugs.archlinux.org/task/40191
https://bugs.archlinux.org/task/40186
After I've put MariaDB 10.0 in our [testing] repository, KDE users are reporting issues with Akonadi; mysqld segfaults whether the database is old (5.5.x) or freshly created. See attachments for more detailed logs.
I'm not really sure what's the culprit,, I'm not excluding packaging issue…
The problem has been also reported on KDE bugtracker: https://bugs.kde.org/show_bug.cgi?id=334205
Gliffy Diagrams
Attachments
Issue Links
- relates to
-
-
- Closed
-
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
I tried to build with gcc 4.9 (on Sid), didn't get a crash, so there should be something else in addition to the compiler version.
I also tried an upgrade from 5.5, no crash either.
But it still looks suspicious that, according to your log, mysql_upgrade was not run after upgrade. Did you try to run it manually and see if the problem goes away?
May it be glibc or binutils? I'll try to rebuild everything with debug flags and see if anything more interesting in backtrace shows up. Changing the priority as it's not blocker, thanks Elena.
Discussion in the KDE bug tracker has a suggestion that this might be related to a gcc-4.9 bug. This bug causes libQtScript to crash (when compiled with gcc 4.9) and there's a further link to the gcc bug report and a patch.
Anyway, the crash happens only when Akonadi uses Qt, compiled with gcc-4.8, and libmariadbd, compiled with gcc-4.9. May be there's something unsafe in this configuration.
We tried rebuilding Akonadi and Qt with the new gcc, but it had no effect.
However our toolchain maintainer recently uploaded gcc built from new snapshot dated 20140507 with an additional patch[1]. Since then everything builds and works as expected.
Okay, thanks.
For the reference, this is the corresponding (to this patch) bug report in the gcc bug tracker: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60902
I'm going to close this issue then.
Apparently the new snapshot hasn't fixed everything. I have added -fno-delete-null-pointer-checks to CFLAGS and CXXFLAGS and now MariaDB behaves as it should.
Seems that gcc 4.9 is the problem… When Maria is built using 4.8, everything works as expected.