Summary: | kjsembed 3.4.0_rc1 fails on amd64 with Uncaught TypeError on some examples | ||
---|---|---|---|
Product: | [Frameworks and Libraries] kjsembed | Reporter: | Marcus D. Hanwell <marcus> |
Component: | Core | Assignee: | KJSEmbed ML <kjsembed> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | cfeck |
Priority: | NOR | Keywords: | investigated, triaged |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Marcus D. Hanwell
2005-03-13 15:06:40 UTC
Forgot about this bug, just to add that I have tried it again with kjsembed-3.5.0 and it still fails with an Uncaught TypeError, although the number is slightly different now and looks less like an integer overflow, xmlgui: WARNING: addBindingsClass() KJSEmbed::KJSEmbedPart not known xmlgui: WARNING: addBindingsClass() KJSEmbed::Bindings::Config not known xmlgui: WARNING: addBindingsClass() KApplication not known Uncaught TypeError exception at: 7 Undefined value I have not received any feedback on this issue, and cannot be certain if this is an error in the script or a 64 bit issue (still using amd64 processor). If there are any tests you would like me to perform then please let me know. This crash report is at least 4 years old and there were no further comments or status updates since then. Therefore we believe that this crash is already fixed in KDE 4 or the backtrace is no longer applicable to KDE 4. If the crash still happens with a recent KDE version (4.7.4 or 4.8), 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 NEW) 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! |