Galeon2 crashing on startup

Joe Marcus Clarke marcus at marcuscom.com
Wed Mar 10 14:23:19 PST 2004


On Wed, 2004-03-10 at 17:13, Kevin Oberman wrote:
> > From: Joe Marcus Clarke <marcus at marcuscom.com>
> > Date: Wed, 10 Mar 2004 14:08:01 -0500
> > 
> > 
> > --=-EVoHQ57F2t3/wYq3mvjG
> > Content-Type: text/plain
> > Content-Transfer-Encoding: quoted-printable
> > 
> > On Wed, 2004-03-10 at 14:04, Kevin Oberman wrote:
> > > > From: Joe Marcus Clarke <marcus at marcuscom.com>
> > > > Date: Wed, 10 Mar 2004 13:27:12 -0500
> > > >=20
> > > > On Wed, 2004-03-10 at 13:19, Kevin Oberman wrote:
> > > > > I updated my CURRENT kernel from 2/26/04 to 3/9/04 yesterday. I now g=
> > et
> > > > > a segmentation fault when I start Galeon. I assumed this was related =
> > to
> > > > > the resolver library update and updated gnomevfs2, mozilla, and
> > > > > evolution as Joe had suggested. I also rebuilt galeon2.
> > > >
> > > > > Did I miss something? Any idea what is happening? I tried to use
> > > > > bugbuddy, but it hung in the "collecting information" phase and, afte=
> > r
> > > > > about 10 minutes, I killed it.
> > > >=20
> > > > This is probably pthread related, but you didn't include any relevant
> > > > data, so it's hard to say for sure.  Galeon 2 works fine for me on my
> > > > -CURRENT machine.  Check your ldd output for multiple threading
> > > > libraries.
> > >=20
> > > I doubt it as the thread library issue pre-dated the 2/26/04 kernel and
> > > galeon was working with that kernel. ldd makes no mention of
> > > libc_r. I'll append the complete output. I do see both libpthread and
> > > libgthread, but I don't think that this is an issue.
> > >=20
> > > With bugbuddy failing (I'd like to figure that one out, too), I really
> > > don't know what other information to get for you. I have no core file to
> > > look at and no useful crash information.=20
> > 
> > Try running galeon under gdb, and see if you can get any backtrace.
> 
> Sounds reasonable, but I can't seem to make it work. I re-built galeon
> with -g, and edited the galeon script to invoke gdb, but I get this when
> I try to run it with gdb:
> > galeon
> GNU gdb 5.2.1 (FreeBSD)
> Copyright 2002 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for details.
> This GDB was configured as "i386-undermydesk-freebsd"...
> (gdb) run
> Starting program: /usr/X11R6/bin/galeon-bin
>  
> Program terminated with signal SIGTRAP, Trace/breakpoint trap.
> The program no longer exists.
> (gdb)
> 
> Is there some magic required to get galeon to run with gdb?

I haven't seen an app die on SIGTRAP in a normal environment.  What
plug-ins are you loading?

Joe

-- 
PGP Key : http://www.marcuscom.com/pgp.asc


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-gnome/attachments/20040310/dc39167c/attachment.bin


More information about the freebsd-gnome mailing list