Re: Valgrind warnings with -1.8.6

[Andrew Gaylard]

On Mon, Apr 6, 2009 at 5:05 PM, Andrew Gaylard <address@hidden> 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 digging, I'm a bit closer.  Building from today's git
shows fewer problems:

grep '^==[0-9]*== [a-zA-Z]' ./hello-world.vg |
awk '/FILE DESCRIPTORS/ {x=0} x==1 {print} /My PID/ {x=1}' |
 sort | uniq -c
     25 ==3551== Conditional jump or move depends on uninitialised value(s)
     15 ==3551== Use of uninitialised value of size 4
      1 ==3551== Warning: bad signal number 0 in sigaction()

Also, something that may or may not be related...
I've seen that a build without optimisation, i.e.:

make distclean ; ./autogen.sh ; CFLAGS=-g ./configure ;  make

fails like this:

make[2]: Entering directory `/home/apg/tmp/guile-git/guile/module'
/bin/mkdir -p `dirname ice-9/psyntax-pp.go`
../meta/uninstalled-env guile-tools compile -o "ice-9/psyntax-pp.go"
"ice-9/psyntax-pp.scm"
ERROR: Stack overflow
make[2]: *** [ice-9/psyntax-pp.go] Error 1

But doing the same without specifying the CFLAGS
(i.e. using the default CFLAGS  of "-g -O2") builds fine:

make distclean ; ./autogen.sh ; ./configure ;  make

(This is on Linux (Ubuntu-8.04).)

- Andrew