Re: Unexpected non-local transfer on doing SAP to pointer coercion

You can set break-on-signals to T, just mind that you'll get into a loop 
break every time a condition is signaled. Either CONTINUE your way out 
of the uninteresting conditions until you get to an interesting one, or 
try setting that value to some narrower type than T, for example ERROR.

On 5.06.2024 23:28, Michael Kappert via Sbcl-help wrote:
> On 05/06/2024 10.36 pm, Douglas Katzman wrote:
>> You say "error" but it's not an error to call compiler-notify.
>> I can't discern whether you're asking why there is a note, or why the
>> compiler entered a break loop.
>> These would be two completely different issues with different causes.
>> Did you purposely or inadvertently escalate compiler-notes into errors
>> via a handler-bind, and/or set break-on-signals to a non-nil value?
>
> Thanks!
>
> I set break-on-signals to T to see where the error is happening, but I'm
> not escalating compiler-notes into errors on purpose.
> So I guess the question is where that happens. Could it be ASDF, which
> I'm using, CFFI or SBCL itself?
>
>
>
>
>
> _______________________________________________
> Sbcl-help mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/sbcl-help