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

Michael Kappert via Sbcl-help <[email protected]>
Newsgroups gmane.lisp.steel-bank.general
Message-ID <[email protected]> 
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?
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.