Ryan Zezeski writes: > > The predominant issue is that the test gets stuck in various ways. I'm > not sure if this is an lx issue or a mono issue (passes just fine on > KVM) or maybe a little of both. > > ...and then it hits me...Are you saying that maybe mono's > SIGABRT/SIGSEGV handlers are hiding underlying issues? I see some code > about signal chaining, alternate stacks, ignoring SIGABRT in certain > contexts, and all this other stuff that looks way complicated and > fragile. I suppose I could try running as you said an see what happens. >
Two updates: 1) The test passes on master, or at least is has passed 5 times in a row thus far. 2) I decided to try to build 4.0.2.4 but with the alternate signal stack disabled. But the build got stock. Interesting enough it got stuck in the same place before when I was writing my original report but after sitting there for a few minutes it eventually kicked itself free (or maybe me poking around caused it to unstick). Anyways, I wrote up a report of what I saw: https://gist.github.com/rzezeski/8a967f9cfdd3976869eb#comment-1479293 -Z ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
