Re: [Chicken-users] segfault is not enough

[Felix Winkelmann]

Joerg F. Wittenberger wrote:
> Hi Felix,
>
> I do have a problem to isolate the problem.  I just have been able to
> fix one instance of the segfault problem by rearranging the
> definitions in the source code.
>
> Now I have:
>
> (define rfc-822-time-string-format "~a, ~d ~b ~Y ~H:~M:~S ~z")
>
> (define (rfc-822-timestring t)
>   (srfi19:date->string t rfc-822-time-string-format))
>
> (define (logerr . args)
>   (display (rfc-822-timestring (current-date (timezone-offset)))
>            (current-error-port))
>   (apply format (current-error-port) args)
>   (flush-output-port (current-error-port)))
>
>
> Before the `rfc-822-timestring' was defined in the same file a few
> more lines after `logerr'.  A test use of logerr appeared immedately
> after it's definition.
>
> Does this info already help?

Hm. No. I assume `flush-output-port' is defined, right?
Are you sure you are not using anything like -unsafe,
(declare (unsafe)), (declare (no-XXx-checks ...)) or
-optimize-level 3?

If nothing helps, could you send me the C-file (one that
reproduces the segfault)?


cheers,
felix