[Vm-dev] Re: Issue 132 in cog: Build Fails on OpenBSD. ucontext is not available

Eliot Miranda eliot.miranda at gmail.com
Tue Oct 8 18:08:47 UTC 2013

Hi James,

On Mon, Oct 7, 2013 at 1:03 PM, James Wright <james_wright at cox.net> wrote:

> Eliot Miranda <eliot.miranda <at> gmail.com> writes:
> >
> >
> >
> > OK, I'll fix this and make printing the registers unavailable on FreeBSD.
>  But that means no profiler either
> > On Sun, Oct 6, 2013 at 7:37 AM,  <cog <at> googlecode.com> wrote:
> Or you could use one of the alternatives to the ucontext functions: POSIX
> threads or sigaltstack + *jmp (there doesn't seem to be a hard requirement
> for ucontext).

Can you hum a few more bars of this?  I'm using ucontext to obtain the
register state of the program when a signal was delivered in a signal

 Qemu uses the latter (and includes equivalent ucontext
> support too, useful for comparison) and many projects likely use the former
> without having considered using ucontext at all.  It seems like replacing
> ucontent instead of reducing certain platforms' functionality merely to
> enable use of a no longer supported, obsoleted and removed set of functions
> would be a good idea, a small step to increase code portability.  This is,
> after all, Unix not Linux.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20131008/1b44a9df/attachment.htm

More information about the Vm-dev mailing list