linuxolator: fatal trap 12 when compiling libX11

[Alexander Leidinger]

Quoting Scot Hetzel <swhetzel at gmail.com> (from Fri, 19 Jan 2007  
01:52:21 -0600):

> On 1/18/07, Divacky Roman <xdivac02 at stud.fit.vutbr.cz> wrote:
>>> kernel.  Currently, I'm runing 'emerge azureus', and is currently at
>>> 18 of 188 ports.  It usually paniced on the first or second port.
>>>
>>> So it looks like the problem may be solved by P4 Change 113083.
>>
>> hehe... nice things happen :) I really didnt expect this to help
>> but it did :)
>>
> The problem is fixed with this change, as it built 181 of the 188
> ports.  The only port it can't finish building is dbus (remaining
> ports have a dependancy on dbus), but at least it no longer panics the
> kernel.

Roman, would wyou please give him the most recent races-fix patch to  
test it? Scot, would you please test to compile some emerge packages  
with it? I don't expect it to fix the dbus problem. The main  
motivation is to know if this new changes introduces a visible  
regression or not.

> Started bus pid 58623 at
> unix:path=/tmp/dbus-N3npYJ4n1g,guid=6366b045035d377a786f9a79f1f2e000
> Running ./dbus-send --print-reply=literal --dest=org.freedesktop.DBus
> /org/freedesktop/DBus org.freedesktop.DBus.Introspectable.Introspect
> Failed to open connection to session message bus: No reply within
> specified time
> killing message bus 58623
> ./run-with-tmp-session-bus.sh: script "./dbus-send" failed
> gmake[2]: *** [dbus-bus-introspect.xml] Error 1

> Looks like dbus-send is not getting any response thru a socket
> (/tmp/dbus-N3npYJ4n1g)  that dbus-launch is using to communicate with
> it.

First of all: we have a problem in FreeBSD regaring sending zero-size  
data over sockets. Andre is working on fixing this. This may a be the  
cause, or it may not be the cause. I don't think it is the cause.

We have some other problems as indicated in the LTP tests. So I will  
be not surprised if there's something else we have to take care of.

Do you have time/energy to try the network tests in the LTP? You have  
to setup a second box which gives access to a second linux instance  
with the LTP stuff (can maybe done with a jail which starts a linux  
remote access daemon).

Bye,
Alexander.

-- 
A pipe gives a wise man time to think
and a fool something to stick in his mouth.

http://www.Leidinger.net    Alexander @ Leidinger.net: PGP ID = B0063FE7
http://www.FreeBSD.org       netchild @ FreeBSD.org  : PGP ID = 72077137