unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Andrew Gaylard <ag@computer.org>
To: guile-user@gnu.org
Subject: Valgrind warnings with -1.8.6
Date: Mon, 6 Apr 2009 17:05:04 +0200	[thread overview]
Message-ID: <9df6f3ea0904060805y450a8ec9gcd550b69728dc886@mail.gmail.com> (raw)

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/local//bin/guile \
-e main -s
!#

(define (main args)
  (display "hello world")
  (newline))

...And run it like this:

$ valgrind --tool=memcheck --gen-suppressions=all --num-callers=30
--track-fds=yes --trace-children=yes --log-file=hello-world.vg
--show-below-main=yes --leak-check=full --show-reachable=yes
--leak-resolution=high ./hello-world.scm

...Now hello-world.vg shows 47 warnings relating to uninitialised values:

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

Thanks,
Andrew




             reply	other threads:[~2009-04-06 15:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-06 15:05 Andrew Gaylard [this message]
2009-04-07 10:40 ` Valgrind warnings with -1.8.6 Andrew Gaylard
2009-04-07 19:47   ` Andreas Rottmann
2009-04-07 21:25     ` Neil Jerram
2009-04-08  7:36       ` Ludovic Courtès
2009-04-08 13:38         ` Paul Emsley
2009-04-12  7:11         ` Neil Jerram
2009-04-30  9:12 ` Andrew Gaylard
2009-04-30 21:09   ` Ludovic Courtès
2009-05-01 10:13     ` Andy Wingo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9df6f3ea0904060805y450a8ec9gcd550b69728dc886@mail.gmail.com \
    --to=ag@computer.org \
    --cc=guile-user@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).