Date: Sun, 11 May 2003 02:34:55 +0200 (CEST) From: "Franz Klammer" <klammer@webonaut.com> To: "Joe Marcus Clarke" <marcus@marcuscom.com> Cc: FreeBSD GNOME Users <gnome@freebsd.org> Subject: Re: HEADS UP TESTERS: Recent GNOME 2.3 problems Message-ID: <49853.212.41.243.28.1052613295.squirrel@mail.webonaut.com> In-Reply-To: <1052603575.98015.21.camel@shumai.marcuscom.com> References: <1052595957.98015.18.camel@shumai.marcuscom.com> <2484.212.41.243.29.1052603366.squirrel@mail.webonaut.com> <1052603575.98015.21.camel@shumai.marcuscom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
------=_20030511023455_95273
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
Joe Marcus Clarke sagte:
> On Sat, 2003-05-10 at 17:49, Franz Klammer wrote:
>> hi!
>>
>> maybe i'm completely wrong but i think here's a typo in
>> bonobo-activation/bonobo-activation-fork-server.c on line 364:
>>
>> } else if ((childpid = fork ())) {
>> _exit (0); /* de-zombifier process, just exit */
>>
>> my knowledge of C tells me that this should look like
>>
>> } else if ((childpid == fork ())) {
>>
>> i've changed it and it seem's this removes at least the thing with the
>> zombie.
>
> No, the code is correct the way it is. What it's saying is:
>
> if (((childpid = fork()) != 0)) {
>
> Which basically says, "if, after the fork, the code is executing in the
> parent, do the following."
>
ok! (i think) i understand. but what i don't understand is:
childpid=fork()
... some code ...
if (childpid != 0)
... some code ...
else if ((childpid=fork())) (a second fork??)
... more code ...
if i change it to the wrong code resp. if((childpid == fork())) the
zombie disappears.
but this doesn't matter. i'm sure i that's to deep for my knowledge. :-)
by the way: in the script-output from one build i've seen that libbonobo
set BONOBO_ACTIVATION_LOCALEDIR to /usr/local/lib/locale - attached a patch.
franz.
> Joe
>
>>
>> franz
>>
>> Joe Marcus Clarke sagte:
>> > This ain't good news. The recent updates to libbonobo and Nautilus
>> > (possibly gnomevfs2 actually) causes applications to lockup and/or
>> crash
>> > on -CURRENT. -STABLE seems to be unaffected, and working quite well.
>> > For that reason, I recommend sticking with nautilus2-2.2.4, and
>> > gnomevfs2-2.2.4 as well as libbonobo-2.2.1 and
>> bonobo-activation-2.2.1.1
>> > for the time being. If you want to help me track down the problem, by
>> > all means, upgrade to the "bad" versions, and start troubleshooting.
>> I
>> > spent last night hammering away at the bonobo problems, and ended up
>> > filing:
>> >
>> > http://bugzilla.gnome.org/show_bug.cgi?id=112725
>> >
>> > Joe
--
http://webonaut.com/
mailto:klammer@webonaut.com
------=_20030511023455_95273
Content-Type: application/octet-stream; name="Makefile.diff"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="Makefile.diff"
LS0tIE1ha2VmaWxlLm9yaWcJU3VuIE1heSAxMSAwMjoyMToyMiAyMDAzCisrKyBNYWtlZmlsZQlT
dW4gTWF5IDExIDAyOjIxOjMyIDIwMDMKQEAgLTIyLDYgKzIyLDcgQEAKIEdOVV9DT05GSUdVUkU9
CXllcwogVVNFX1BFUkw1PQl5ZXMKIFVTRV9HTk9NRT0JZ25vbWVoYWNrIGxpYnhtbDIgb3JiaXQy
CitVU0VfUkVJTlBMQUNFPQl5ZXMKIENPTkZJR1VSRV9BUkdTPQktLXdpdGgtaHRtbC1kaXI9JHtQ
UkVGSVh9L3NoYXJlL2RvYyBcCiAJCS0tZGlzYWJsZS1ndGstZG9jCiBDT05GSUdVUkVfRU5WPQlD
UFBGTEFHUz0iLUkke0xPQ0FMQkFTRX0vaW5jbHVkZSIgXApAQCAtMjksNSArMzAsOSBAQAogTUFL
RV9FTlY9CWdub21lbG9jYWxlZGlyPSR7UFJFRklYfS9zaGFyZS9sb2NhbGUKIAogTUFOMT0JCWJv
bm9iby1hY3RpdmF0aW9uLXNlcnZlci4xCisKK3ByZS1jb25maWd1cmU6CisJQCR7RklORH0gJHtX
UktTUkN9IC1uYW1lIE1ha2VmaWxlLmluIHwgJHtYQVJHU30gJHtSRUlOUExBQ0VfQ01EfSAtZSBc
CisJCSdzfEBEQVRBRElSTkFNRUB8c2hhcmV8JwogCiAuaW5jbHVkZSA8YnNkLnBvcnQubWs+Cg==
------=_20030511023455_95273--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49853.212.41.243.28.1052613295.squirrel>