Using a backtrace, I'm getting the following sort of information after a
segfault:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb7fd3890 (LWP 24134)]
0x01dbaf4a in g_object_get_qdata () from /usr/lib/libgobject-2.0.so.0
(gdb) bt
#0 0x01dbaf4a in g_object_get_qdata () from /usr/lib/libgobject-2.0.so.0
#1 0x0276d3e3 in ?? () from
/usr/lib/gtk-2.0/modules/libcanberra-gtk-module.so
#2 0x0276e9a1 in ?? () from
/usr/lib/gtk-2.0/modules/libcanberra-gtk-module.so
#3 0x022c5998 in ?? () from /usr/lib/libgdk-x11-2.0.so.0
#4 0x01e2f471 in ?? () from /lib/libglib-2.0.so.0
#5 0x01e33c28 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#6 0x01e343f0 in ?? () from /lib/libglib-2.0.so.0
#7 0x01e346a4 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#8 0x00c53d00 in nsAppShell::ProcessNextNativeEvent (this=0xb6a9b330,
mayWait=0) at /tmp/buildd/iceweasel-7.0.1/widget/src/gtk2/nsAppShell.cpp:144
#9 0x00c69bda in nsBaseAppShell::DoProcessNextNativeEvent (this=0xb6a9b330,
mayWait=0) at
/tmp/buildd/iceweasel-7.0.1/widget/src/xpwidgets/nsBaseAppShell.cpp:171
#10 0x00c69e1f in nsBaseAppShell::OnProcessNextEvent (this=0xb6a9b330,
thr=0xb7dc9b20, mayWait=0, recursionDepth=0)
at
/tmp/buildd/iceweasel-7.0.1/widget/src/xpwidgets/nsBaseAppShell.cpp:306
#11 0x00da036a in nsThread::ProcessNextEvent (this=0xb7dc9b20, mayWait=0,
result=0xbfffec6c) at
/tmp/buildd/iceweasel-7.0.1/xpcom/threads/nsThread.cpp:581
#12 0x00d6f2bb in NS_ProcessNextEvent_P (thread=0x8, mayWait=0) at
/tmp/buildd/iceweasel-7.0.1/build-xulrunner/xpcom/build/nsThreadUtils.cpp:245
#13 0x00d0091f in mozilla::ipc::MessagePump::Run (this=0xb7d9ab20,
aDelegate=0xb7d43350) at
/tmp/buildd/iceweasel-7.0.1/ipc/glue/MessagePump.cpp:110
#14 0x00dbe931 in MessageLoop::RunInternal (this=0xb7d43350) at
/tmp/buildd/iceweasel-7.0.1/ipc/chromium/src/base/message_loop.cc:218
#15 0x00dbe976 in MessageLoop::RunHandler (this=0x8) at
/tmp/buildd/iceweasel-7.0.1/ipc/chromium/src/base/message_loop.cc:202
#16 MessageLoop::Run (this=0x8) at
/tmp/buildd/iceweasel-7.0.1/ipc/chromium/src/base/message_loop.cc:176
#17 0x00c69fa7 in nsBaseAppShell::Run (this=0xb6a9b330) at
/tmp/buildd/iceweasel-7.0.1/widget/src/xpwidgets/nsBaseAppShell.cpp:189
#18 0x00b1f634 in nsAppStartup::Run (this=0xb579af70) at
/tmp/buildd/iceweasel-7.0.1/toolkit/components/startup/nsAppStartup.cpp:222
#19 0x0032791d in XRE_main (argc=2, argv=0xbffff348, aAppData=0xb7d16380) at
/tmp/buildd/iceweasel-7.0.1/toolkit/xre/nsAppRunner.cpp:3570
#20 0x0804a129 in main (argc=2, argv=0xbffff348) at
/tmp/buildd/iceweasel-7.0.1/xulrunner/app/nsXULRunnerApp.cpp:383
I don't know enough to interpret this fully, but it looks like it's
connected with GTK somehow?
On 17 October 2011 16:25, John J. Foerch <[email protected]> wrote:
> On Mon, Oct 17, 2011 at 04:18:21PM -0500, Benjamin Slade wrote:
> > Thanks, John. I've been getting my xulrunners from here though: https://
> > ftp.mozilla.org/pub/mozilla.org/xulrunner/releases/ and I don't see any
> > dbg-versions. The .debs for xulrunners have dependencies which are
> difficult
> > for my system to satisfy; likewise for compliing. Any idea where dbg
> linux
> > runtimes could be had from?
> >
> > On 17 October 2011 15:03, John J. Foerch <[email protected]> wrote:
> >
> > On Mon, Oct 17, 2011 at 02:30:00PM -0500, Benjamin Slade wrote:
> > > Doesn't seem to be, or, at least, not exclusively. Sometimes it
> happens
> > when I
> > > go "Back" from a webpage (with no flash on either page).
> > >
> > > No-one else is getting this?
> > >
> > > On 17 October 2011 11:15, John J. Foerch <[email protected]>
> wrote:
> > >
> > > On Sat, Oct 15, 2011 at 01:59:37PM -0500, Benjamin Slade wrote:
> > > > I've been experienced rather more frequently crashing of
> Conkeror
> > in the
> > > past
> > > > week or so then I was before. This is happening using both
> > xulrunner-6
> > > (6.0.2)
> > > > and xulrunner-7 (7.0.1). Is this just me (i.e. something in
> my
> > > .conkerorrc or
> > > > some extension I'm using), or is it happening for other
> people too?
> > > >
> > > > When it crashes, it reports "segmentation fault". And I
> notice that
> > (if I
> > > run
> > > > from the terminal) the segmentation fault tends to be
> preceded by
> > > messages
> > > > like the following:
> > > >
> > > > <snip>
> > >
> > > See if Flash is the culprit.
> > >
> > > --
> > > John Foerch
> > >
> >
> > A backtrace may help narrow things down more.
> >
> > http://conkeror.org/Debugging
> >
> > --
> > John Foerch
>
> no
>
> --
> John Foerch
>
--
-----------------------------------------------------------------------------------------------------
Dr Benjamin Slade <[email protected]>
Dept. of Linguistics & TESOL - University of Texas at Arlington
132E Hammond Hall | Office Hours: tba
[http://ling.uta.edu/~ben/ <http://ling.uta.edu/%7Eben/%20>]
Stæfcræft & Vyākaraṇa (lingblog) - http://staefcraeft.blogspot.com
The Babbage Files (techblog) - http://babbagefiles.blogspot.com
-----------------------------------------------------------------------------------------------------
Ongietan sceal gleaw hæle hu gæstlic bið,
þonne ealre þisse worulde wela weste stondeð.
--*The Wanderer*, ll.
73-4.
_______________________________________________
Conkeror mailing list
[email protected]
https://www.mozdev.org/mailman/listinfo/conkeror
