Date: 30 Jun 2003 22:11:23 -0400 From: Joe Marcus Clarke <marcus@marcuscom.com> To: Jeremy Messenger <mezz7@cox.net> Cc: freebsd-gnome@freebsd.org Subject: Re: Nautilus2 (2.3.6) always crash (seg fault) in -CURRENT.. Message-ID: <1057025483.6752.3.camel@shumai.marcuscom.com> In-Reply-To: <oprrluhfeh8ckrg5@smtp.central.cox.net> References: <oprrliz4x68ckrg5@smtp.central.cox.net> <oprrlro1wh8ckrg5@smtp.central.cox.net> <oprrluhfeh8ckrg5@smtp.central.cox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-PwpuGxThr3gLJ6fGMv90
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
On Mon, 2003-06-30 at 20:04, Jeremy Messenger wrote:
> On Mon, 30 Jun 2003 18:04:03 -0500, Jeremy Messenger <mezz7@cox.net> wrot=
e:
>=20
> > On 30 Jun 2003 18:59:26 -0400, Joe Marcus Clarke <marcus@marcuscom.com>=
=20
> > wrote:
> >
> >> On Mon, 2003-06-30 at 15:56, Jeremy Messenger wrote:
> >>> Last night, I upgraded everything what the marcus CVS has updated las=
t=20
> >>> weekend and very few from ports tree such as libtool.. Now, the=20
> >>> Nautilus2 will not work anymore, which it will always crash (seg faul=
t)=20
> >>> . I have ran it with gdb and I think I have seen this before; not=20
> >>> sure..
> >>
> >> This is now fixed.
> >
> > I saw, thanks! I am rebuilding it right now.. :-)
>=20
> Hey, I think the ggv and gst-register might have the same problem? Becaus=
e,=20
> I tried to debug Nautilus2 with libthr before update to 2.3.6_1 and I get=
=20
> the same error messages as ggv and gst-register in the gdb. It's kind of=20
> weird, because I don't get crash if I use libc_r with ggv/gst-register=20
> thought. Must be one of library that has the problem with thread by libto=
ol=20
> change?
This problem only affects apps linked to libc_r on -CURRENT. Note,
libthr was broken for a while, and you have to update to -CURRENT from
today to fix it. Other than that, I don't know. Since libthr is not
the default, I only test with libc_r. If you find problems switching to
libthr, you should report them to the libthr authors. They're most
likely not problems with the ports themselves.
Joe
>=20
> Here's error msg:
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D
> $ gdb nautilus
>=20
> (gdb) r
> Starting program: /usr/X11R6/bin/nautilus
> GThread-ERROR **: file gthread-posix.c: line 135 (): error 'Invalid=20
> argument' during 'pthread_getschedparam (pthread_self(), &policy, &sched)=
'
> aborting...
> Program received signal SIGABRT, Aborted.
> 0x28d4efb3 in kill () at {standard input}:15
> 15 {standard input}: No such file or directory.
> in {standard input}
> Current language: auto; currently asm
>=20
> (gdb) bt
> #0 0x28d4efb3 in kill () at {standard input}:15
> #1 0x28dba7cc in abort () at /usr/src/lib/libc/stdlib/abort.c:72
> #2 0x28aee63b in g_logv (log_domain=3D0x28ac31c1 "GThread",
> log_level=3DG_LOG_LEVEL_ERROR, format=3D0x0, args1=3D0x0) at gmessage=
s.c:508
> #3 0x28aee704 in g_log (log_domain=3D0x0, log_level=3D0, format=3D0x0)
> at gmessages.c:527
> #4 0x28ac142e in g_thread_impl_init () at gthread-posix.c:135
> #5 0x28ac2692 in g_thread_init (init=3D0x0) at gthread-impl.c:330
> #6 0x2851d7ab in bonobo_activation_pre_args_parse (program=3D0x0,=20
> mod_info=3D0x0)
> at gnome-init.c:117
> #7 0x285198f3 in gnome_program_preinit (program=3D0x80cdb40,
> app_id=3D0x1 <Error reading address 0x1: Bad address>, app_version=3D=
0x0,
> argc=3D1, argv=3D0xbfbffb98) at gnome-program.c:1323
> #8 0x2851a687 in gnome_program_initv (type=3D135078912, app_id=3D0x0,
> app_version=3D0x0, module_info=3D0x80cdb40, argc=3D1, argv=3D0xbfbffb=
98,
> first_property_name=3D0x0, args=3D0x0) at gnome-program.c:1872
> #9 0x2851a30a in gnome_program_init (
> app_id=3D0x855c <Error reading address 0x855c: Bad address>,
> app_version=3D0x855c <Error reading address 0x855c: Bad address>,
> module_info=3D0x855c, argc=3D34140, argv=3D0x855c,
> first_property_name=3D0x855c <Error reading address 0x855c: Bad addre=
ss>)
> at gnome-program.c:1680
> #10 0x0806ed72 in main (argc=3D34140, argv=3D0xbfbffb98) at nautilus-main=
.c:193
> ---Type <return> to continue, or q <return> to quit---
> #11 0x08063579 in _start ()
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D
>=20
> After upgrade to 2.3.6_1 and the error with libthr is gone; it works fine=
=20
> same as with libc_r. Tonight, I will try to hunt around and see if I can=20
> catch..
>=20
> Cheers,
> Mezz
>=20
> > Cheers,
> > Mezz
> >
> >> Joe
> >>
> >>>
> >>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > <snip>
> >>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >>>
> >>> BTW: I am doing the buildworld/update kernel right now..
> >>>
> >>> Cheers,
> >>> Mezz
--=20
PGP Key : http://www.marcuscom.com/pgp.asc
--=-PwpuGxThr3gLJ6fGMv90
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (FreeBSD)
iD8DBQA/AO3Lb2iPiv4Uz4cRAk0iAJ9KMt63/ondQWjjeeaQe5PIMDhJ3ACgpW7r
sQUK0WuAzyzr/6VnbbvUj00=
=B7xD
-----END PGP SIGNATURE-----
--=-PwpuGxThr3gLJ6fGMv90--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1057025483.6752.3.camel>