<div dir="ltr">Hi James,<div><br><div class="gmail_extra">On Mon, Oct 7, 2013 at 1:03 PM, James Wright <span dir="ltr"><<a href="mailto:james_wright@cox.net" target="_blank">james_wright@cox.net</a>></span> wrote:<br>
<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im"><br>
Eliot Miranda <eliot.miranda <at> <a href="http://gmail.com" target="_blank">gmail.com</a>> writes:<br>
<br>
><br>
><br>
><br>
> OK, I'll fix this and make printing the registers unavailable on FreeBSD.<br>
But that means no profiler either<br>
</div>> On Sun, Oct 6, 2013 at 7:37 AM, <cog <at> <a href="http://googlecode.com" target="_blank">googlecode.com</a>> wrote:<br>
<br>
Or you could use one of the alternatives to the ucontext functions: POSIX<br>
threads or sigaltstack + *jmp (there doesn't seem to be a hard requirement<br>
for ucontext). </blockquote><div><br></div><div>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 handler.</div><div><br></div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Qemu uses the latter (and includes equivalent ucontext<br>
support too, useful for comparison) and many projects likely use the former<br>
without having considered using ucontext at all. It seems like replacing<br>
ucontent instead of reducing certain platforms' functionality merely to<br>
enable use of a no longer supported, obsoleted and removed set of functions<br>
would be a good idea, a small step to increase code portability. This is,<br>
after all, Unix not Linux.<br>
<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>best,<div>Eliot</div>
</div></div></div>