On Oct 5 2011, Christian Kellermann wrote:
Hi Christian,
Dear Jörg,
* Jörg F. Wittenberger joerg.wittenber...@softeyes.net [111005 22:29]:
While I've been following this valgrind hint I ran into some
code in C_a_i_string_to_number ... as expectable this code
is kinda complicated since the
On Thu, Oct 06, 2011 at 12:47:25PM +0200, Jörg F. Wittenberger wrote:
On Oct 5 2011, Christian Kellermann wrote:
Today I re-read the R5RS, which left me wondering. Would it be
#bi101010.1 or whould it be #b#i101010.1 ?
The latter. See the Lexical Syntax section, it has these productions:
On Oct 6 2011, Peter Bex wrote:
Furthermore:
Also I changed my mind: I'm afraid numbers in Scheme are complex
enough to use a real parser to read them.
I agree. There's pure Scheme code for parsing numbers syntax in trunk
of the numbers egg (and the latest release has it too). It's not
I managed to narrow the valgrind complaint's scope:
Try as a test:
valgrind --log-file=/tmp/csi.vg --track-origins=yes csi -e (vector 'a 'b)
The result in /tmp/csi.vg looks good.
However try:
valgrind --log-file=/tmp/csi.vg --track-origins=yes csi -e 42
and run into an example of the
On Oct 5 2011, Jörg F. Wittenberger wrote:
==13112== Conditional jump or move depends on uninitialised value(s)
==13112== at 0x510393E: C_a_i_string_to_number (in
While I've been following this valgrind hint I ran into some
code in C_a_i_string_to_number ... as expectable this code
is kinda
On Oct 5 2011, Jörg F. Wittenberger wrote:
I found two occurrences of strlen (C_strlen that is), which would
for no good reason scan the memory while the result could be computed
by simple pointer arithmetic:
@@ -7519,19 +7515,19 @@
errno = 0;
...
Sorry. Somehow cutpaste made a mess
Dear Jörg,
* Jörg F. Wittenberger joerg.wittenber...@softeyes.net [111005 22:29]:
While I've been following this valgrind hint I ran into some
code in C_a_i_string_to_number ... as expectable this code
is kinda complicated since the problem it solves is just below
the level where one would
Hallo,
On Thu, Sep 29, 2011 at 10:25 PM, Jörg F. Wittenberger
joerg.wittenber...@softeyes.net wrote:
The pattern is to allocate some space on the stack, fill stuff in,
eventually jump to the continuation. GC will only happen during the
jump, not within the time between allocation and
I'm still asking myself why I can't run chicken program under valgrind.
Since there's a lot going on at this time I'm about to forget.
Hence here an update for those who care and the archive.
I've traced the call coming from irregex.c down to valgrind complaining
as soon as *all-chars* value is
On Thu, Sep 29, 2011 at 09:38:44PM +0200, Jörg F. Wittenberger wrote:
I'm still asking myself why I can't run chicken program under valgrind.
Since there's a lot going on at this time I'm about to forget.
Hence here an update for those who care and the archive.
I've traced the call coming
On Sep 29 2011, Alan Post wrote:
Since it seems as good a day as any for wild-ass speculation, what
about this scenario:
We allocate an object, set the tag pointer, but don't fill out all
of the memory yet. We're yet to need it.
Oops! The gc gets called, and that object has to move. So we
11 matches
Mail list logo
