[Xorp-users] OpenBSD-3.6 segfaults

[Pavlin Radoslavov]

> I applied the patches to the latest OPENBSD_3_6 cvs (stable branch), and
> after fixing up a few things, got a kernel out. Some of the things
> have already been applied to the 3.6 stable branch.
> 
> If you are interested, I have a patch against 3.6 at
> http://scl.ameslab.gov/~troy/obsd-3.6-pim.patch

Thanks!

> Any ideas on the segfault? I'm waiting for a complete rebuild at the
> moment on the off chance the PIM headers changing caused something
> goofy. What should I start looking at?
> 
> (FYI, I used the stock openbsd gcc-2.95 compiler)

You may want to look into file xorp/BUILD_NOTES which contains some
notes about OpenBSD as well. E.g., on OpenBSD-3.5 you may have to
use the egcc/eg++ compiler.
I doubt you will see any PIM header related problems, but let me
know if you run into such problem.

BTW, what XORP version are you using? XORP-1.0 or XORP-CVS?
The reason I ask you is because I just tried few days old XORP from
CVS and I am getting the following errors on startup:

[ 2004/12/06 19:14:47  ERROR xorp_rtrmgr:10094 LIBCOMM +499
comm_sock.c comm_sock_connect4 ] Error connecting socket (family =
2, remote_addr = 0.0.0.0, remote_port = 19999): Invalid argument

I've tracked the problem to a startup-time initialization problem
that seems to exist on OpenBSD only. I vaguely remember that I had
seen similar initialization OpenBSD-specific problem with some of
the test programs for XORP-1.0, but that looked to me more like
compiler/linker problem.

I will keep investigating...

Pavlin