Your message dated Fri, 12 Jul 2019 12:17:49 +0300 with message-id <[email protected]> and subject line Re: Bug#852032: libjavascriptcoregtk-4.0-18: Segmentation fault in LLIntAssembly.h:2610 on powerpc64 has caused the Debian Bug report #852032, regarding libjavascriptcoregtk-4.0-18: Segmentation fault in LLIntAssembly.h:2610 on powerpc64 to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 852032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852032 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: libjavascriptcoregtk-4.0-18 Version: 2.14.2-1 Severity: normal -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hello, Segmentation fault in libjavascriptcoregtk-4.0.so.18 causes seed-webkit2 FTBFS on powerpc64. Here's the stacktrace I retrieved on a porterbox: Thread 1 "seed" received signal SIGSEGV, Segmentation fault. JSC::LLInt::CLoop::execute (entryOpcodeID=3019375176, executableAddress=0x0, vm=0x3fffb3fc0000, protoCallFrame=0x3fffffff, isInitializationPass=false) at ./obj-powerpc64-linux-gnu/DerivedSources/JavaScriptCore/LLIntAssembly.h:2610 2610 ./obj-powerpc64-linux-gnu/DerivedSources/JavaScriptCore/LLIntAssembly.h: No such file or directory. (gdb) bt #0 JSC::LLInt::CLoop::execute (entryOpcodeID=3019375176, executableAddress=0x0, vm=0x3fffb3fc0000, protoCallFrame=0x3fffffff, isInitializationPass=false) at ./obj-powerpc64-linux-gnu/DerivedSources/JavaScriptCore/LLIntAssembly.h:2610 #1 0x00003fffb74b8e24 in JSC::vmEntryToJavaScript (executableAddress=<optimized out>, vm=<optimized out>, protoCallFrame=<optimized out>) at ./Source/JavaScriptCore/llint/LLIntThunks.cpp:104 #2 0x00003fffb74a2f18 in JSC::JITCode::execute (this=<optimized out>, vm=0x3fffb3fc0000, protoCallFrame=0x3fffffffdff8) at ./Source/JavaScriptCore/jit/JITCode.cpp:80 #3 0x00003fffb7497820 in JSC::Interpreter::execute (this=<optimized out>, program=0x3fffb2f63e80, callFrame=<optimized out>, thisObj=0x3fffb2f6c6c0) at ./Source/JavaScriptCore/interpreter/Interpreter.cpp:899 #4 0x00003fffb760b7bc in JSC::evaluate (exec=0x3fffb33d80e0, source=..., thisValue=..., returnedException=...) at ./Source/JavaScriptCore/runtime/Completion.cpp:106 #5 0x00003fffb760b9e8 in JSC::profiledEvaluate (exec=0x3fffb33d80e0, reason=<optimized out>, source=..., thisValue=..., returnedException=...) at ./Source/JavaScriptCore/runtime/Completion.cpp:121 #6 0x00003fffb730f7d4 in JSEvaluateScript (ctx=<optimized out>, script=<optimized out>, thisObject=0x0, sourceURL=0x0, startingLineNumber=<optimized out>, exception=0x0) at ./Source/JavaScriptCore/API/JSBase.cpp:68 #7 0x00003fffb7d9138c in seed_simple_evaluate (ctx=0x3fffb33d80e0, source=<optimized out>, exception=0x0) at seed-api.c:308 #8 0x00003fffb7d97938 in seed_init_constrained_with_context_and_group (argc=0x3ffffffff010, argv=0x3fffffffefa8, context=0x3fffb33d80e0, group=0x3fffb3fc0000) at seed-engine.c:1840 #9 0x00003fffb7d97c54 in seed_init_with_context_and_group (argc=<optimized out>, argv=<optimized out>, context=<optimized out>, group=<optimized out>) at seed-engine.c:1905 #10 0x00003fffb7d97d78 in seed_init_with_context_group (argc=0x3ffffffff010, argv=0x3fffffffefa8, group=0x3fffb3fc0000) at seed-engine.c:1939 #11 0x00003fffb7d97df0 in seed_init (argc=0x3ffffffff010, argv=<optimized out>) at seed-engine.c:1962 #12 0x0000000010000fc0 in main (argc=<optimized out>, argv=<optimized out>) at main.c:142 To reproduce, I built seed-webkit2 on ppc64, installed libjavascriptcoregtk-4.0-18-dbgsym and ran in the directory with unpacked package source: $ export LD_LIBRARY_PATH=$(pwd)/libseed/.libs: $ cd doc/modules/readline $ gdb ../../../src/seed (gdb) set args ../../../doc/modules/make-functions.js ../../../doc/modules/readline/readline.js (gdb) run Please have a look at this. - -- Cheers, Andrew -----BEGIN PGP SIGNATURE----- iQExBAEBCAAbBQJYgn/0FBxhbmRyZXdzaEBkZWJpYW4ub3JnAAoJEJ1bI/kYT6UU LkoH/iThKO73KvLO3qPnmeEcwhKVe3GPCDgSrcE5U4w9ml9fNqJcxK1j3gjUzGc3 3HjGdjyau1so4ZELAaZ3PcxUU8NpdwC04YlSSfkTz0woY+ddZI8tuSHEZdIWb/8G QXFo31VQD5XtRaCvT/tCpy7mzLdJyHY1IARrEgpgGSIE6iC/ADBXPGQ9P/y12Y+W h2A2K7droG0ScKXMmYzhnkPPV1UPWGQy+mcSHPo6m65ZyeaITH6vRARwUH3gRnHf /kalXkOMR6/6voVc07z+EOjJ1apXRVbPBQa7io4a9DEo9ekkyuwG8KNr2pmYWzRM eqNsHskL2zS+60MhJyAbvKoLc6E= =yTDu -----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---On Wed, Jun 26, 2019 at 10:32:14AM +0200, Emilio Pozuelo Monfort wrote: > >> webkit2gtk itself builds fine, seed-webkit2 is what fails: > > > > I wanted to test this with the latest versions of WebKitGTK, but > > I don't seem to have access to any porterbox with ppc64 (only > > ppc64el, in which things work fine). > > Apparently there used to be one (pizetti) but that seems down > now. Cc'ing the ppc64 buildd maintainers, maybe they can clarify if > there's another porterbox. I'm closing this for the time being due to inactivity, if the problem is still relevant please reopen. Thanks! Berto
--- End Message ---
