iiimf-csconv [was: Re: Can't build gtk20, no ideas....]
From: Volker Stolz (vs_at_freebsd.org)
Date: 04/21/04
- Previous message: FreeBSD Tinderbox: "[releng_4 tinderbox] failure on i386/pc98"
- In reply to: Kris Kennaway: "Re: Can't build gtk20, no ideas...."
- Next in thread: Kris Kennaway: "Re: iiimf-csconv [was: Re: Can't build gtk20, no ideas....]"
- Reply: Kris Kennaway: "Re: iiimf-csconv [was: Re: Can't build gtk20, no ideas....]"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 21 Apr 2004 11:26:59 +0200 To: Kris Kennaway <kris@obsecurity.org>
In local.freebsd-stable, you wrote:
> I see similar errors repeatably on non-gnome ports on bento, e.g.
> http://bento.freebsd.org/errorlogs/i386-4-full/iiimf-csconv-r11.4_1.log
> I've not been able to track down what is calling rcmdsh [1], let alone why
> it's failing.
Just to add a data point in case somebody wants to look at this:
Looks like a smashed stack: gdb'ing drops you dead in libc's _start() when
you get back from the "call main", if you use "exit" instead of "return" in
main, something else goes wrong...Interestingly, the problem goes away when
linking with ElectricFence.
Volker
-- http://www-i2.informatik.rwth-aachen.de/stolz/ *** PGP *** S/MIME Neu! Ändern Sie den Anfangstag Ihrer Woche _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
- Previous message: FreeBSD Tinderbox: "[releng_4 tinderbox] failure on i386/pc98"
- In reply to: Kris Kennaway: "Re: Can't build gtk20, no ideas...."
- Next in thread: Kris Kennaway: "Re: iiimf-csconv [was: Re: Can't build gtk20, no ideas....]"
- Reply: Kris Kennaway: "Re: iiimf-csconv [was: Re: Can't build gtk20, no ideas....]"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]