[Ecls-list] cl_boot crash

Juan Jose Garcia-Ripoll juanjose.garciaripoll at googlemail.com
Thu Jul 29 08:20:15 UTC 2010


On Thu, Jul 29, 2010 at 2:34 AM, John DeSoi <desoi at pgedit.com> wrote:

>
> On Jul 28, 2010, at 5:36 AM, Juan Jose Garcia-Ripoll wrote:
>
> > There might be some incompatibility between the garbage collector and
> 4D's code. To ensure this is not the case, remove the call to cl_boot() and
> call instead GC_init(). If the collector still crashes then this is the
> culprit.
>
> It still crashes in the same place using GC_init instead (backtrace below).
> GDB reports:
>
> Program received signal: "EXC_BAD_ACCESS".
>

This is _not_ necessarily a crash. If this is OS X, this signal is used by
the garbage collector to detect when memory is written to, marking it for
inspection later on. What I meant is to really run a program, no GDB
involved, and see whether you experience this crash. If you use GDB then you
have to tell it to ignore this signal (handle EXC_BAD_ACCESS pass nostop
noprint or something like that)

Juanjo

-- 
Instituto de Física Fundamental, CSIC
c/ Serrano, 113b, Madrid 28006 (Spain)
http://juanjose.garciaripoll.googlepages.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/ecl-devel/attachments/20100729/ec03a440/attachment.html>


More information about the ecl-devel mailing list