Bug#663871: SIGSEGV in WebCore::GraphicsContext::platformInit

2014-05-30 Thread Steven Chamberlain
On 18:37, Steven Chamberlain wrote: To see the real issue on mipsel I'll have to try again with proc mounted. Okay, I think I have a backtrace of the actual bug now. (attached) Regards, -- Steven Chamberlain ste...@pyro.eu.org Program received signal SIGBUS, Bus error. 0x75298728 in

Bug#663871: SIGSEGV in WebCore::GraphicsContext::platformInit

2014-05-28 Thread Steven Chamberlain
Hi, Here's a backtrace of the midori crash on mipsel with webkit/2.4.2-1 - an alignment issue somewhere: Program received signal SIGBUS, Bus error. 0x7529058c in WTFCrash () from /usr/lib/mipsel-linux-gnu/libjavascriptcoregtk-1.0.so.0 (gdb) bt full #0 0x7529058c in WTFCrash () from

Bug#663871: SIGSEGV in WebCore::GraphicsContext::platformInit

2014-05-28 Thread Emilio Pozuelo Monfort
On 28/05/14 18:38, Steven Chamberlain wrote: Hi, Here's a backtrace of the midori crash on mipsel with webkit/2.4.2-1 - an alignment issue somewhere: Program received signal SIGBUS, Bus error. 0x7529058c in WTFCrash () from /usr/lib/mipsel-linux-gnu/libjavascriptcoregtk-1.0.so.0 (gdb)

Bug#663871: SIGSEGV in WebCore::GraphicsContext::platformInit

2014-05-28 Thread Steven Chamberlain
On 28/05/14 17:54, Emilio Pozuelo Monfort wrote: Seems similar to the crash in #748456 (reported for amd64). Ahhh yes I forgot to mount /proc in my chroot, and that must be what triggers this early crash in both cases. To see the real issue on mipsel I'll have to try again with proc mounted.

Bug#663871: SIGSEGV in WebCore::GraphicsContext::platformInit

2014-05-21 Thread Steven Chamberlain
Hi, On 20:14, Alberto Garcia wrote: You can try the MiniBrowser, though, which uses the WebKit 2 API. It's under /usr/lib/*/webkit2gtk-3.0/libexec/MiniBrowser in the libwebkit2gtk-3.0-25 package. It seems able to navigate to a page and execute JavaScript, but nothing renders! Just a blank

Bug#663871: SIGSEGV in WebCore::GraphicsContext::platformInit

2014-05-13 Thread Steven Chamberlain
On 11:54, Alberto Garcia wrote: Can you test with the latest package and tell me if you're still having problems? What happened to GtkLauncher? It's gone from both libwebkitgtk-1.0-0 and libwebkitgtk-3.0-0 in jessie Midori using libwebkitgtk-1.0-0/2.2.6-1 crashes quite quickly which may be

Bug#663871: SIGSEGV in WebCore::GraphicsContext::platformInit

2014-05-13 Thread Alberto Garcia
On Tue, May 13, 2014 at 05:40:29PM +0100, Steven Chamberlain wrote: What happened to GtkLauncher? It's gone from both libwebkitgtk-1.0-0 and libwebkitgtk-3.0-0 in jessie It was removed at some point but never repackaged again, GtkLauncher uses the WebKit 1 API which will disappear soon. You

Bug#663871: SIGSEGV in WebCore::GraphicsContext::platformInit

2014-05-03 Thread Alberto Garcia
On Mon, Mar 24, 2014 at 11:54:49AM +0200, Alberto Garcia wrote: While trying to reproduce crashes in Midori I turned up the attached backtrace from GtkLauncher, while I was scrolling down a page using the cursor keys. It appears different to the actual issue I was looking for, and

Bug#663871: SIGSEGV in WebCore::GraphicsContext::platformInit

2014-03-24 Thread Alberto Garcia
On Wed, Mar 14, 2012 at 04:53:58PM +, Steven Chamberlain wrote: While trying to reproduce crashes in Midori I turned up the attached backtrace from GtkLauncher, while I was scrolling down a page using the cursor keys. It appears different to the actual issue I was looking for, and

Bug#663871: SIGSEGV in WebCore::GraphicsContext::platformInit

2012-03-14 Thread Steven Chamberlain
Package: libwebkitgtk-1.0-0 Version: 1.6.3-1 Severity: important File: /usr/lib/webkitgtk-1.0-0/libexec/GtkLauncher Hi, While trying to reproduce crashes in Midori I turned up the attached backtrace from GtkLauncher, while I was scrolling down a page using the cursor keys. It appears