Re: Bug#761040: [libqtwebkit4] Browsers based on Webkit crash on loading pages

2014-10-06 Thread Lennart Sorensen
On Sun, Oct 05, 2014 at 10:36:56AM -0300, Lisandro Damián Nicanor Pérez Meyer 
wrote:
 Current sid's qtwebkit (2.3.4.dfsg-2)
 
 ppc users says it crashes upon certain time (which seems to be not much). 
 What 
 I need is a proper backtrace generated with the patched qtwebkit.
 
 JFTR, qtwebkit does not provides proper debug symbols because at the best of 
 my knowledge we don't have a ppc buildd with enough ram to build it. 
 
 Thanks a lot Lennart!

Compiling now.

dpkg-source hates some of the patches in the package and refuses to
unpack it.  quilt is fine with it, and using quilt refresh on the patches
makes dpkg-source happy.  Seems using a/... and b/... is no longer good
enough, it has to be the actual package name instead of b or something
like that.  I have noticed a number of packages are failing due to
dpkg-source becoming more picky for no apparent reason.

-- 
Len Sorensen


-- 
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141006140910.gv4...@csclub.uwaterloo.ca



Re: Bug#761040: [libqtwebkit4] Browsers based on Webkit crash on loading pages

2014-10-06 Thread Lennart Sorensen
On Mon, Oct 06, 2014 at 10:09:10AM -0400, Lennart Sorensen wrote:
 Compiling now.
 
 dpkg-source hates some of the patches in the package and refuses to
 unpack it.  quilt is fine with it, and using quilt refresh on the patches
 makes dpkg-source happy.  Seems using a/... and b/... is no longer good
 enough, it has to be the actual package name instead of b or something
 like that.  I have noticed a number of packages are failing due to
 dpkg-source becoming more picky for no apparent reason.

OK, it has compiled.

-rw-r--r-- 1 root root122790 Oct  6 14:31 
../libqtwebkit-qmlwebkitplugin_2.3.4.dfsg-2_powerpc.deb
-rw-r--r-- 1 root root114572 Oct  6 14:31 
../libqtwebkit-dev_2.3.4.dfsg-2_powerpc.deb
-rw-r--r-- 1 root root   8126916 Oct  6 14:31 
../libqtwebkit4_2.3.4.dfsg-2_powerpc.deb
-rw-r--r-- 1 root root 522638262 Oct  6 14:38 
../libqtwebkit4-dbg_2.3.4.dfsg-2_powerpc.deb

So should I put those somewhere, or should I try to run a test and get
a crash dump?

-- 
Len Sorensen


-- 
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141006144056.gw4...@csclub.uwaterloo.ca



Re: Bug#761040: [libqtwebkit4] Browsers based on Webkit crash on loading pages

2014-10-06 Thread Lennart Sorensen
On Mon, Oct 06, 2014 at 10:40:56AM -0400, Lennart Sorensen wrote:
 On Mon, Oct 06, 2014 at 10:09:10AM -0400, Lennart Sorensen wrote:
  Compiling now.
  
  dpkg-source hates some of the patches in the package and refuses to
  unpack it.  quilt is fine with it, and using quilt refresh on the patches
  makes dpkg-source happy.  Seems using a/... and b/... is no longer good
  enough, it has to be the actual package name instead of b or something
  like that.  I have noticed a number of packages are failing due to
  dpkg-source becoming more picky for no apparent reason.
 
 OK, it has compiled.
 
 -rw-r--r-- 1 root root122790 Oct  6 14:31 
 ../libqtwebkit-qmlwebkitplugin_2.3.4.dfsg-2_powerpc.deb
 -rw-r--r-- 1 root root114572 Oct  6 14:31 
 ../libqtwebkit-dev_2.3.4.dfsg-2_powerpc.deb
 -rw-r--r-- 1 root root   8126916 Oct  6 14:31 
 ../libqtwebkit4_2.3.4.dfsg-2_powerpc.deb
 -rw-r--r-- 1 root root 522638262 Oct  6 14:38 
 ../libqtwebkit4-dbg_2.3.4.dfsg-2_powerpc.deb
 
 So should I put those somewhere, or should I try to run a test and get
 a crash dump?

I tried running qupzilla and got this:

Program received signal SIGSEGV, Segmentation fault.
JSC::LLInt::CLoop::execute (callFrame=0xf42c2040, bootstrapOpcodeId=628, 
bootstrapOpcodeId@entry=JSC::llint_function_for_call_prologue, 
isInitializationPass=isInitializationPass@entry=false) at 
generated/LLIntAssembly.h:31
31  t1.i = *CASTintptr_t*(t1.i8p + 56);// 
/tmp/qtwebkit-2.3.4.dfsg/Source/JavaScriptCore/llint/LowLevelInterpreter.asm:268
(gdb) bt
#0  JSC::LLInt::CLoop::execute (callFrame=0xf42c2040, bootstrapOpcodeId=628, 
bootstrapOpcodeId@entry=JSC::llint_function_for_call_prologue, 
isInitializationPass=isInitializationPass@entry=false) at 
generated/LLIntAssembly.h:31
#1  0x0f122000 in JSC::Interpreter::executeCall (this=0xf76077e0, 
callFrame=callFrame@entry=0xf41afba8, function=0xf41efe60, 
callType=callType@entry=JSC::CallTypeJS, 
callData=..., thisValue=..., args=...) at 
/tmp/qtwebkit-2.3.4.dfsg/Source/JavaScriptCore/interpreter/Interpreter.cpp:1052
#2  0x0f1db12c in JSC::call (exec=exec@entry=0xf41afba8, functionObject=error 
reading variable: value has been optimized out, 
callType=callType@entry=JSC::CallTypeJS, 
callData=..., thisValue=..., args=...) at 
/tmp/qtwebkit-2.3.4.dfsg/Source/JavaScriptCore/runtime/CallData.cpp:39
#3  0x0d9478f4 in call (args=..., thisValue=..., callData=..., 
callType=JSC::CallTypeJS, functionObject=..., exec=0xf41afba8)
at 
/tmp/qtwebkit-2.3.4.dfsg/Source/WebCore/bindings/js/JSMainThreadExecState.h:56
#4  WebCore::JSEventListener::handleEvent (this=0xf766be70, 
scriptExecutionContext=0xf76283cc, event=0xf768b188)
at 
/tmp/qtwebkit-2.3.4.dfsg/Source/WebCore/bindings/js/JSEventListener.cpp:130
#5  0x0dbcfd90 in WebCore::EventTarget::fireEventListeners 
(this=this@entry=0xf762ad10, event=event@entry=0xf768b188, 
d=d@entry=0xf762ad88, entry=...)
at /tmp/qtwebkit-2.3.4.dfsg/Source/WebCore/dom/EventTarget.cpp:210
#6  0x0dbd008c in WebCore::EventTarget::fireEventListeners 
(this=this@entry=0xf762ad10, event=event@entry=0xf768b188)
at /tmp/qtwebkit-2.3.4.dfsg/Source/WebCore/dom/EventTarget.cpp:175
#7  0x0e0ec1a4 in WebCore::DOMWindow::dispatchEvent 
(this=this@entry=0xf762ad10, prpEvent=..., prpTarget=...)
at /tmp/qtwebkit-2.3.4.dfsg/Source/WebCore/page/DOMWindow.cpp:1676
#8  0x0e0ec43c in WebCore::DOMWindow::dispatchLoadEvent (this=0xf762ad10) at 
/tmp/qtwebkit-2.3.4.dfsg/Source/WebCore/page/DOMWindow.cpp:1650
#9  0x0db8f060 in dispatchWindowLoadEvent (this=0xf7628380) at 
/tmp/qtwebkit-2.3.4.dfsg/Source/WebCore/dom/Document.cpp:3656
#10 WebCore::Document::implicitClose (this=0xf7628380) at 
/tmp/qtwebkit-2.3.4.dfsg/Source/WebCore/dom/Document.cpp:2422
#11 0x0e040d38 in WebCore::FrameLoader::checkCallImplicitClose (this=optimized 
out) at /tmp/qtwebkit-2.3.4.dfsg/Source/WebCore/loader/FrameLoader.cpp:830
#12 0x0e0498e8 in WebCore::FrameLoader::checkCompleted (this=0xf760f048) at 
/tmp/qtwebkit-2.3.4.dfsg/Source/WebCore/loader/FrameLoader.cpp:773
#13 0x0e04b55c in WebCore::FrameLoader::loadDone (this=optimized out) at 
/tmp/qtwebkit-2.3.4.dfsg/Source/WebCore/loader/FrameLoader.cpp:719
#14 0x0e025b38 in WebCore::CachedResourceLoader::loadDone (this=0xf75fa480) at 
/tmp/qtwebkit-2.3.4.dfsg/Source/WebCore/loader/cache/CachedResourceLoader.cpp:699
#15 0x0e08faac in WebCore::SubresourceLoader::releaseResources 
(this=0xf7636600) at 
/tmp/qtwebkit-2.3.4.dfsg/Source/WebCore/loader/SubresourceLoader.cpp:318
#16 0x0e080b08 in WebCore::ResourceLoader::didFinishLoading 
(this=this@entry=0xf7636600, finishTime=finishTime@entry=0)
at /tmp/qtwebkit-2.3.4.dfsg/Source/WebCore/loader/ResourceLoader.cpp:314
#17 0x0e08f668 in WebCore::SubresourceLoader::didFinishLoading 
(this=0xf7636600, finishTime=0)
at /tmp/qtwebkit-2.3.4.dfsg/Source/WebCore/loader/SubresourceLoader.cpp:277
#18 0x0e07fb3c in WebCore::ResourceLoader::didFinishLoading (this=optimized 
out, 

Re: Bug#761040: [libqtwebkit4] Browsers based on Webkit crash on loading pages

2014-10-06 Thread Lisandro Damián Nicanor Pérez Meyer
On Monday 06 October 2014 12:28:46 Lennart Sorensen wrote:
 On Mon, Oct 06, 2014 at 10:40:56AM -0400, Lennart Sorensen wrote:
  On Mon, Oct 06, 2014 at 10:09:10AM -0400, Lennart Sorensen wrote:
   Compiling now.
   
   dpkg-source hates some of the patches in the package and refuses to
   unpack it.  quilt is fine with it, and using quilt refresh on the
   patches
   makes dpkg-source happy.  Seems using a/... and b/... is no longer good
   enough, it has to be the actual package name instead of b or something
   like that.  I have noticed a number of packages are failing due to
   dpkg-source becoming more picky for no apparent reason.
  
  OK, it has compiled.
  
  -rw-r--r-- 1 root root122790 Oct  6 14:31
  ../libqtwebkit-qmlwebkitplugin_2.3.4.dfsg-2_powerpc.deb -rw-r--r-- 1 root
  root114572 Oct  6 14:31 ../libqtwebkit-dev_2.3.4.dfsg-2_powerpc.deb
  -rw-r--r-- 1 root root   8126916 Oct  6 14:31
  ../libqtwebkit4_2.3.4.dfsg-2_powerpc.deb -rw-r--r-- 1 root root 522638262
  Oct  6 14:38 ../libqtwebkit4-dbg_2.3.4.dfsg-2_powerpc.deb
  
  So should I put those somewhere, or should I try to run a test and get
  a crash dump?
 
 I tried running qupzilla and got this:

\o/ This is *exactly* what I needed! *Thanks a lot*!

Will try to make upstream take a look :)


-- 
elruso angasule: tenes el teletransportador encendido?
gurtaj :P
angasule si
elruso Yo no :-P
angasule lo arme con el PIC16F84, una batata y algo que estaba adentro de
   una zapatilla vieja
elruso angasule: yo tenia uno andando pero speedy te bloquea el puerto...

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.