Bug 101424 - kjsembed 3.4.0_rc1 fails on amd64 with Uncaught TypeError on some examples
Summary: kjsembed 3.4.0_rc1 fails on amd64 with Uncaught TypeError on some examples
Status: RESOLVED WORKSFORME
Alias: None
Product: kjsembed
Classification: Frameworks and Libraries
Component: Core (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR crash
Target Milestone: ---
Assignee: KJSEmbed ML
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2005-03-13 15:06 UTC by Marcus D. Hanwell
Modified: 2018-10-27 02:08 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 Marcus D. Hanwell 2005-03-13 15:06:40 UTC
Version:            (using KDE KDE 3.4.0)
Installed from:    Gentoo Packages
Compiler:          GCC 3.4.3 gcc version 3.4.3 20050110 (Gentoo Linux 3.4.3.20050110, ssp-3.4.3.20050110-0, pie-8.7.7)
OS:                Linux

I was testing kjsembed on the amd64 architecture for Gentoo. Version 3.3.1 was able to run and display the xmlgui.js example available on the kjsembed web site without any problems, but when testing it using kjsembed 3.4.0_rc1 it gave the following failure message and the example did not run,

marcus@cryos ~ $ /usr/kde/3.4/bin/kjscmd xmlgui.js
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: -2147483648
Undefined value

I can't see anything obviously wrong with the example script, and so I think it is an issue with the kjsembed core. If you need any more details at all then please let me know. Both versions are installed on the same system, using CFLAGS/CXXFLAGS="-march=k8 -O2 -pipe". I checked with lddd and the 3.4 version is only linking against 3.4 libs. Other examples do run OK. I have reproduced this on two systems - one using our old monolithic ebuilds, and the other using the newer split ebuilds.
Comment 1 Marcus D. Hanwell 2005-12-12 19:15:21 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.
Comment 2 Christoph Feck 2011-12-20 02:58:02 UTC
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)
Comment 3 Andrew Crouthamel 2018-09-22 02:07:15 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 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!
Comment 4 Andrew Crouthamel 2018-10-27 02:08:12 UTC
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!