On 29 April 2013 14:56, Andrew Gaylard wrote:
> On 04/28/13 03:07, Daniel Hartwig wrote:
>>
>> On 28 April 2013 03:57, Andrew Gaylard wrote:
>>>
>>> Those 0x304 values look dodgy to me, and explain why the
>>> SCM_SETCDR causes an invalid memory access.
>>>
>> 0x304 is SCM_EOL.
>
> Hi Daniel,
>
>
Hi Andrew,
Andrew Gaylard writes:
> On 04/28/13 03:07, Daniel Hartwig wrote:
>> On 28 April 2013 03:57, Andrew Gaylard wrote:
>>> Those 0x304 values look dodgy to me, and explain why the
>>> SCM_SETCDR causes an invalid memory access.
>>>
>> 0x304 is SCM_EOL.
> Hi Daniel,
>
> Thanks for the fee
Hello,
On Mon, Apr 29, 2013 at 6:10 AM, Mark H Weaver wrote:
> Any ideas?
>
> Thanks,
>Mark
>
>
It should be possible to use a watchpoint in GDB to figure out what code is
corrupting that piece of memory. It probably won't tell us exactly what's
going on, but it would be interesting
Hi All,
As I told you in an earlier mail I'm back cleaning up and reworking
guile-log and
refreshing the memory of the inner details of that code base enabled me to
rewrite
the spec for redo safe variables considerable. I think that it is much
cleaner now and
should be worthy of a good discussion.
I found the doc, maybe you can take a look!
-- Forwarded message --
From: Stefan Israelsson Tampe
Date: Fri, Feb 8, 2013 at 9:53 PM
Subject: Re: splicing macros
To: Andy Wingo
Cc: guile-devel
Hi,
Here is a git-format-patch of some docs for the ck macro.
enjoy!
On Sun, Jan
