Bug 296433 - kdelibs4 segfault on FreeBSD ia64
Summary: kdelibs4 segfault on FreeBSD ia64
Status: RESOLVED WORKSFORME
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: kdecore (show other bugs)
Version: 4.7
Platform: unspecified FreeBSD
: NOR crash
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-20 13:44 UTC by mexas
Modified: 2021-01-12 04:34 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mexas 2012-03-20 13:44:27 UTC
On FreeBSD 10-current ia64 I've built
rekonq 0.8.1_1 from ports. On startup
it dumps core. More details:
http://seis.bris.ac.uk/~mexas/freebsd/ia64/browsers.html#rekonq

Please advise
Comment 1 Andrea Diamantini 2012-03-20 14:57:55 UTC
uhm... don't you have a backtrace to attach, instead of the useless gdb startup loading? Can you please also try with rekonq 0.9.x?
Comment 2 mexas 2012-03-20 17:28:54 UTC
The bt is there at the end:

(gdb) bt
#0  0x000000012799c931 in KSharedDataCache::find () from /usr/local/kde4/lib/libkdecore.so.7
#1  0x000000012537c350 in KIconLoader::~KIconLoader () from /usr/local/kde4/lib/libkdeui.so.7
#2  0x0000000000000000 in ?? ()
Previous frame identical to this frame (corrupt stack?)
(gdb) 

I understand rekonq is scheduled for update in FreeBSD ports,
but is waiting for qt4 to be updated first. Although I might have misunderstood.
Comment 3 Andrea Diamantini 2012-03-21 23:00:08 UTC
ah, sorry. Didn't notice it. I see you have the same problem with same backtrace with konqueror. I just can think this is a more generic problem than something in my own app.
Needs investigation.
Comment 4 mexas 2012-03-22 09:44:18 UTC
Yes, you are right, I missed that.
I updated the summary to reflect this.

Right now I'm rebuilding both konqueror and rekonq
with WITH_DEBUG, which does no optimisation
or stripping and adds no-strict-aliasing  and "-g" flags.

Will see if it adds anything useful to backtraces.
Comment 6 Andrea Diamantini 2012-03-22 14:39:43 UTC
(In reply to comment #4)
> Yes, you are right, I missed that.
> I updated the summary to reflect this.
> 
> Right now I'm rebuilding both konqueror and rekonq
> with WITH_DEBUG, which does no optimisation
> or stripping and adds no-strict-aliasing  and "-g" flags.

No, the crash in the backtrace is from kdelibs. You should rebuild them with that option. Rebuilding rekonq and konqueror won't help too much, I fear.

> Will see if it adds anything useful to backtraces.
Comment 7 mexas 2012-03-22 16:00:42 UTC
> No, the crash in the backtrace is from kdelibs. You should rebuild them with
> that option. Rebuilding rekonq and konqueror won't help too much, I fear.

Yes, I figured I should start with kdelibs.
I changed the subject line again.

I get multiple segfaults when building kdelibs, but intermittent.
So after restarting make 10 times of so, I'm usually able to complete the build.
Now I see that ignoring those segfaults was foolish.

The first segfault is always with automoc4, but it's not reproducible, i.e.
it segfaults on different files each time, e.g.:

# cd /usr/ports/x11/kdelibs4
# make clean
# make WITH_DEBUG=yes
*skip*
Generating moc_klibloadertest4_module.cpp
Generating kssld.moc
Segmentation fault (core dumped)
*** Error code 139

# gdb /usr/local/bin/automoc4 ./work/kdelibs-4.7.4/build/kdecore/tests/automoc4.core 
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "ia64-marcel-freebsd"...(no debugging symbols found)...
Core was generated by `automoc4'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /usr/local/lib/qt4/libQtCore.so.4...done.
Loaded symbols for /usr/local/lib/qt4/libQtCore.so.4
Reading symbols from /usr/lib/libstdc++.so.6...done.
Loaded symbols for /usr/lib/libstdc++.so.6
Reading symbols from /lib/libm.so.5...done.
Loaded symbols for /lib/libm.so.5
Reading symbols from /lib/libgcc_s.so.1...done.
Loaded symbols for /lib/libgcc_s.so.1
Reading symbols from /lib/libthr.so.3...done.
Loaded symbols for /lib/libthr.so.3
Reading symbols from /lib/libc.so.7...done.
Loaded symbols for /lib/libc.so.7
Reading symbols from /lib/libz.so.6...done.
Loaded symbols for /lib/libz.so.6
Reading symbols from /usr/local/lib/libgthread-2.0.so.0...done.
Loaded symbols for /usr/local/lib/libgthread-2.0.so.0
Reading symbols from /usr/local/lib/libglib-2.0.so.0...done.
Loaded symbols for /usr/local/lib/libglib-2.0.so.0
Reading symbols from /usr/local/lib/libiconv.so.3...done.
Loaded symbols for /usr/local/lib/libiconv.so.3
Reading symbols from /usr/local/lib/libicui18n.so.48...done.
Loaded symbols for /usr/local/lib/libicui18n.so.48
Reading symbols from /usr/local/lib/libintl.so.9...done.
Loaded symbols for /usr/local/lib/libintl.so.9
Reading symbols from /usr/local/lib/libpcre.so.1...done.
Loaded symbols for /usr/local/lib/libpcre.so.1
Reading symbols from /usr/local/lib/libicuuc.so.48...done.
Loaded symbols for /usr/local/lib/libicuuc.so.48
Reading symbols from /usr/local/lib/libicudata.so.48...done.
Loaded symbols for /usr/local/lib/libicudata.so.48
Reading symbols from /libexec/ld-elf.so.1...done.
Loaded symbols for /libexec/ld-elf.so.1
#0  0x00000001208b89c0 in thread_start () from /lib/libthr.so.3
[New Thread 122805800 (LWP 101347/automoc4)]
[New Thread 122804400 (LWP 100680/automoc4)]
(gdb) bt
#0  0x00000001208b89c0 in thread_start () from /lib/libthr.so.3
#1  0x0000000000000000 in ?? ()
Previous frame identical to this frame (corrupt stack?)
(gdb) 

Probably I first have to rebuild automoc4 with WITH_DEBUG, right?

Anyway, starting the kdelibs4 build from clean, I get a segfault on another file:

# make clean && make WITH_DEBUG=yes
*skip*
Generating kcommentwidget_p.moc
Generating jobclasses.moc
Segmentation fault (core dumped)
*** Error code 139

# find . -name "*.core"
./work/kdelibs-4.7.4/build/kio/automoc4.core
# gdb /usr/local/bin/automoc4 ./work/kdelibs-4.7.4/build/kio/automoc4.core
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "ia64-marcel-freebsd"...(no debugging symbols found)...
Core was generated by `automoc4'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /usr/local/lib/qt4/libQtCore.so.4...done.
Loaded symbols for /usr/local/lib/qt4/libQtCore.so.4
Reading symbols from /usr/lib/libstdc++.so.6...done.
Loaded symbols for /usr/lib/libstdc++.so.6
Reading symbols from /lib/libm.so.5...done.
Loaded symbols for /lib/libm.so.5
Reading symbols from /lib/libgcc_s.so.1...done.
Loaded symbols for /lib/libgcc_s.so.1
Reading symbols from /lib/libthr.so.3...done.
Loaded symbols for /lib/libthr.so.3
Reading symbols from /lib/libc.so.7...done.
Loaded symbols for /lib/libc.so.7
Reading symbols from /lib/libz.so.6...done.
Loaded symbols for /lib/libz.so.6
Reading symbols from /usr/local/lib/libgthread-2.0.so.0...done.
Loaded symbols for /usr/local/lib/libgthread-2.0.so.0
Reading symbols from /usr/local/lib/libglib-2.0.so.0...done.
Loaded symbols for /usr/local/lib/libglib-2.0.so.0
Reading symbols from /usr/local/lib/libiconv.so.3...done.
Loaded symbols for /usr/local/lib/libiconv.so.3
Reading symbols from /usr/local/lib/libicui18n.so.48...done.
Loaded symbols for /usr/local/lib/libicui18n.so.48
Reading symbols from /usr/local/lib/libintl.so.9...done.
Loaded symbols for /usr/local/lib/libintl.so.9
Reading symbols from /usr/local/lib/libpcre.so.1...done.
Loaded symbols for /usr/local/lib/libpcre.so.1
Reading symbols from /usr/local/lib/libicuuc.so.48...done.
Loaded symbols for /usr/local/lib/libicuuc.so.48
Reading symbols from /usr/local/lib/libicudata.so.48...done.
Loaded symbols for /usr/local/lib/libicudata.so.48
Reading symbols from /libexec/ld-elf.so.1...done.
Loaded symbols for /libexec/ld-elf.so.1
#0  0x0000000120ca4860 in g_slist_remove () from /usr/local/lib/libglib-2.0.so.0
[New Thread 122805800 (LWP 101358/automoc4)]
[New Thread 122804400 (LWP 100227/automoc4)]
(gdb) bt
#0  0x0000000120ca4860 in g_slist_remove () from /usr/local/lib/libglib-2.0.so.0
#1  0x0000000120c54890 in g_source_remove_poll () from /usr/local/lib/libglib-2.0.so.0
#2  0x000000012048bbd0 in QEventDispatcherGlib::unregisterSocketNotifier ()
   from /usr/local/lib/qt4/libQtCore.so.4
#3  0x0000000120460070 in QSocketNotifier::setEnabled () from /usr/local/lib/qt4/libQtCore.so.4
#4  0x000000012030ac80 in QProcessPrivate::_q_startupNotification ()
   from /usr/local/lib/qt4/libQtCore.so.4
#5  0x00000001203ba3c0 in QProcessPrivate::waitForStarted ()
   from /usr/local/lib/qt4/libQtCore.so.4
#6  0x0000000120309f30 in QProcess::waitForStarted () from /usr/local/lib/qt4/libQtCore.so.4
#7  0x000000012030a080 in QProcess::waitForFinished () from /usr/local/lib/qt4/libQtCore.so.4
#8  0x0000000100017740 in ?? ()
Previous frame identical to this frame (corrupt stack?)
(gdb) 

So I run it twice from clean and got segfaults
in different places (on different files) with automoc4.
The backtraces are also different.
Comment 8 Justin Zobel 2020-12-13 04:25:45 UTC
Thank you for the crash reports.

As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved.

I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you.
Comment 9 Bug Janitor Service 2020-12-28 04:34:40 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 10 Bug Janitor Service 2021-01-12 04:34:17 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!