On Thu 30 Apr 2009 23:09, l...@gnu.org (Ludovic Courtès) writes:
> Andrew Gaylard writes:
>
>> I've seen that a build without optimisation, i.e.:
>
> That is expected: the evaluator and/or bytecode interpreter eat up too
> much stack space with `-O0'.
Actually I didn't expect that, after the rec
Hello,
Andrew Gaylard writes:
> After some digging, I'm a bit closer. Building from today's git
> shows fewer problems:
You're referring to `master', right?
> grep '^==[0-9]*== [a-zA-Z]' ./hello-world.vg |
> awk '/FILE DESCRIPTORS/ {x=0} x==1 {print} /My PID/ {x=1}' |
> sort | uniq -c
>
On Mon, Apr 6, 2009 at 5:05 PM, Andrew Gaylard wrote:
> Hi,
>
> I'm linking with libguile on Linux, built from source, to extend my
> C application with Scheme. I'm seeing a lot of warnings from
> valgrind. The same warnings appear when using Guile standalone.
> Should I be worried?
After some d
l...@gnu.org (Ludovic Courtès) writes:
> Hello,
>
> Neil Jerram writes:
>
>> That is fundamentally true; however, we have recently addressed some
>> genuine Valgrind warnings in the 1.8.x development branch.
>
> These were Helgrind warnings, not Memcheck warnings, right?
Yes, good point!
N
Ludovic Courtès wrote:
Hello,
Neil Jerram writes:
That is fundamentally true; however, we have recently addressed some
genuine Valgrind warnings in the 1.8.x development branch.
These were Helgrind warnings, not Memcheck warnings, right?
There's a suppression file there:
http://
Hello,
Neil Jerram writes:
> That is fundamentally true; however, we have recently addressed some
> genuine Valgrind warnings in the 1.8.x development branch.
These were Helgrind warnings, not Memcheck warnings, right?
There's a suppression file there:
http://www.mail-archive.com/guile-de..
Hi,
I'm linking with libguile on Linux, built from source, to extend my
C application with Scheme. I'm seeing a lot of warnings from
valgrind. The same warnings appear when using Guile standalone.
Should I be worried?
The following steps show the problem:
Use this as hello-world.scm:
#!/usr/lo
Andreas Rottmann writes:
> Andrew Gaylard writes:
>
>> Hi,
>>
>> I'm linking with libguile on Linux, built from source, to extend my
>> C application with Scheme. I'm seeing a lot of warnings from
>> valgrind. The same warnings appear when using Guile standalone.
>> Should I be worried?
>>
> No
Andrew Gaylard writes:
> Hi,
>
> I'm linking with libguile on Linux, built from source, to extend my
> C application with Scheme. I'm seeing a lot of warnings from
> valgrind. The same warnings appear when using Guile standalone.
> Should I be worried?
>
No, this is normal AFAIK. The garbage col
Hi,
I'm linking with libguile on Linux, built from source, to extend my
C application with Scheme. I'm seeing a lot of warnings from
valgrind. The same warnings appear when using Guile standalone.
Should I be worried?
The following steps show the problem.
Use this as hello-world.scm:
#!/usr/lo
10 matches
Mail list logo
