| Summary: | Konqueror crashes on certain web pages | ||
|---|---|---|---|
| Product: | [Applications] konqueror | Reporter: | Krzysztof Jurewicz <krzysztof.jurewicz> |
| Component: | kjs | Assignee: | Konqueror Bugs <konqueror-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | cfeck, maksim |
| Priority: | NOR | Keywords: | triaged |
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | FreeBSD Ports | ||
| OS: | FreeBSD | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Krzysztof Jurewicz
2008-08-12 16:02:12 UTC
Thanks for the report
#6 0x2c06de63 in KJS::Collector::markStackObjectsConservatively (
start=0xbfbfba90, end=0xbfbfba90)
If this frame from GDB is right than the stack detection in the GC somehow got broken on FBSD....
The first thing to check would be whether kjs/config.h in the build directory of kdelibs has HAVE_PTHREAD_NP_H defined, I don't know how easy that is to check w/ports build. Though, in all likelyhood one would have to figure out what currentThreadStackBase() in collector.cpp is doing (wrong).
Now, I don't have FBSD, so I guess unless you feel like being adventurous/generous, and debugging this by yourself, I'll likely have to chase down some contacts to get this right... So I'd appreciate if you let me know what FreeBSD version this is, on what architecture (it looks like x86 from BT, but just in case...), and if there is anything unusual about the ports you're using that any FreeBSD people I talk to may want to know about.
I feel a bit adventurous, but I absolutely don't feel qualified, so it would be a good idea if someone else do debugging. HAVE_PTHREAD_NP_H is defined. Here is system information from Konqueror's user agent string: FreeBSD 7.0-RELEASE-p2; X11; i386. The system uses GENERIC kernel. KDE is compiled with -march=pentium-m, there should be nothing unusual in ports i'm using. And the FreeBSD ports' Makefile's version: $FreeBSD: ports/x11/kdelibs4/Makefile,v 1.227 2008/08/09 16:52:27 miwi Exp $ This crash report is at least 3 years old and there were no further comments or status updates since then. Therefore we believe that this crash is already fixed in recent KDE 4 versions or the backtrace is no longer applicable to the current KDE 4 sources. If the crash still happens with a recent KDE version (4.10.5 or 4.11), please add an updated backtrace or provide steps to reproduce. For more information, see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports (To prevent automatic closing of this bug in the future, please set the bug status to ASSIGNED or CONFIRMED) 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 set the bug status 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! Dear Bug Submitter, 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! |