lang/mono on amd64 current: Bad signal in suspend_handler

Rob Farmer rfarmer at predatorlabs.net
Sat Oct 16 13:56:51 UTC 2010


Hi,

I'm having an bit of a build problem for lang/mono on amd64 current.
At random points in the build, I will get something like this:

gmake[8]: Entering directory
`/work/a/ports/lang/mono/work/mono-2.6.7/mcs/nunit24/ConsoleRunner/nunit-console'
MCS     [net_1_1] nunit-console-runner.dll
Bad signal in suspend_handler
Stacktrace:

  at System.Security.Cryptography.CryptoStream.Finalize () <0xffffffff>
  at System.Security.Cryptography.CryptoStream.Finalize () <0x00021>
  at (wrapper runtime-invoke)
object.runtime_invoke_virtual_void__this__
(object,intptr,intptr,intptr) <0x00058>
gmake[8]: *** [../../../class/lib/net_1_1/nunit-console-runner.dll]
Abort trap: 6 (core dumped)
gmake[8]: *** Deleting file
`../../../class/lib/net_1_1/nunit-console-runner.dll'
gmake[8]: Leaving directory
`/work/a/ports/lang/mono/work/mono-2.6.7/mcs/nunit24/ConsoleRunner/nunit-console'
gmake[7]: *** [do-all] Error 2

This happens at different places on each build attempt, but it is
virtually guaranteed to happen at some point. If I am building
normally (just running "make" outside tinderbox) I can re-run "make"
right after the failure and it starts working again, but it might have
another "Bad signal in suspend_handler" later on. After several times
though, I can finish the build and it seems to work (compiles/runs
other stuff fine).

Any idea what might be happening or advice for collecting more useful
info? Pointyhat has some failures on amd64 current from Sept. 30 but I
can't tell if they are related.

FreeBSD turquoise.predatorlabs.net 9.0-CURRENT FreeBSD 9.0-CURRENT #0
r213747: Tue Oct 12 15:25:48 PDT 2010
rfarmer at turquoise.predatorlabs.net:/usr/obj/usr/src/sys/TURQUOISE
amd64

Full log from tinderbox:
http://www.predatorlabs.net/dl/mono-2.6.7.log

Thanks,
-- 
Rob Farmer


More information about the freebsd-mono mailing list