Date: Mon, 30 Jun 2003 19:04:17 -0500 From: Jeremy Messenger <mezz7@cox.net> To: Joe Marcus Clarke <marcus@marcuscom.com> Cc: freebsd-gnome@freebsd.org Subject: Re: Nautilus2 (2.3.6) always crash (seg fault) in -CURRENT.. Message-ID: <oprrluhfeh8ckrg5@smtp.central.cox.net> In-Reply-To: <oprrlro1wh8ckrg5@smtp.central.cox.net> References: <oprrliz4x68ckrg5@smtp.central.cox.net> <1057013965.312.66.camel@gyros> <oprrlro1wh8ckrg5@smtp.central.cox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 30 Jun 2003 18:04:03 -0500, Jeremy Messenger <mezz7@cox.net> wrote:
> On 30 Jun 2003 18:59:26 -0400, Joe Marcus Clarke <marcus@marcuscom.com>
> wrote:
>
>> On Mon, 2003-06-30 at 15:56, Jeremy Messenger wrote:
>>> Last night, I upgraded everything what the marcus CVS has updated last
>>> weekend and very few from ports tree such as libtool.. Now, the
>>> Nautilus2 will not work anymore, which it will always crash (seg fault)
>>> . I have ran it with gdb and I think I have seen this before; not
>>> sure..
>>
>> This is now fixed.
>
> I saw, thanks! I am rebuilding it right now.. :-)
Hey, I think the ggv and gst-register might have the same problem? Because,
I tried to debug Nautilus2 with libthr before update to 2.3.6_1 and I get
the same error messages as ggv and gst-register in the gdb. It's kind of
weird, because I don't get crash if I use libc_r with ggv/gst-register
thought. Must be one of library that has the problem with thread by libtool
change?
Here's error msg:
=========================
$ gdb nautilus
(gdb) r
Starting program: /usr/X11R6/bin/nautilus
GThread-ERROR **: file gthread-posix.c: line 135 (): error 'Invalid
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
(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=0x28ac31c1 "GThread",
log_level=G_LOG_LEVEL_ERROR, format=0x0, args1=0x0) at gmessages.c:508
#3 0x28aee704 in g_log (log_domain=0x0, log_level=0, format=0x0)
at gmessages.c:527
#4 0x28ac142e in g_thread_impl_init () at gthread-posix.c:135
#5 0x28ac2692 in g_thread_init (init=0x0) at gthread-impl.c:330
#6 0x2851d7ab in bonobo_activation_pre_args_parse (program=0x0,
mod_info=0x0)
at gnome-init.c:117
#7 0x285198f3 in gnome_program_preinit (program=0x80cdb40,
app_id=0x1 <Error reading address 0x1: Bad address>, app_version=0x0,
argc=1, argv=0xbfbffb98) at gnome-program.c:1323
#8 0x2851a687 in gnome_program_initv (type=135078912, app_id=0x0,
app_version=0x0, module_info=0x80cdb40, argc=1, argv=0xbfbffb98,
first_property_name=0x0, args=0x0) at gnome-program.c:1872
#9 0x2851a30a in gnome_program_init (
app_id=0x855c <Error reading address 0x855c: Bad address>,
app_version=0x855c <Error reading address 0x855c: Bad address>,
module_info=0x855c, argc=34140, argv=0x855c,
first_property_name=0x855c <Error reading address 0x855c: Bad address>)
at gnome-program.c:1680
#10 0x0806ed72 in main (argc=34140, argv=0xbfbffb98) at nautilus-main.c:193
---Type <return> to continue, or q <return> to quit---
#11 0x08063579 in _start ()
=========================
After upgrade to 2.3.6_1 and the error with libthr is gone; it works fine
same as with libc_r. Tonight, I will try to hunt around and see if I can
catch..
Cheers,
Mezz
> Cheers,
> Mezz
>
>> Joe
>>
>>>
>>> =================================
> <snip>
>>> =================================
>>>
>>> BTW: I am doing the buildworld/update kernel right now..
>>>
>>> Cheers,
>>> Mezz
--
bsdforums.org 's moderator, mezz.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?oprrluhfeh8ckrg5>