gnuastro-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[gnuastro-devel] [task #14258] Configure option to run tests with Valgri


From: Mohammad Akhlaghi
Subject: [gnuastro-devel] [task #14258] Configure option to run tests with Valgrind
Date: Thu, 1 Dec 2016 15:25:38 +0000 (UTC)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:50.0) Gecko/20100101 Firefox/50.0

URL:
  <http://savannah.gnu.org/task/?14258>

                 Summary: Configure option to run tests with Valgrind
                 Project: GNU Astronomy Utilities
            Submitted by: makhlaghi
            Submitted on: Fri 02 Dec 2016 12:25:35 AM JST
         Should Start On: Fri 02 Dec 2016 12:00:00 AM JST
   Should be Finished on: Fri 02 Dec 2016 12:00:00 AM JST
                Category: Development
                Priority: 5 - Normal
              Item Group: Crash
                  Status: Postponed
                 Privacy: Public
        Percent Complete: 0%
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
                  Effort: 0.00

    _______________________________________________________

Details:

When a segmentation fault error (or similar opaque errors) are reported, it is
really hard to find the cause of the problem on the user's system. The best
way is use Valgrind <http://valgrind.org/>, which gives a very nice report of
exactly which function caused the memory failure.

Currently the user has to take these steps:

1. Install Valgrind (available in most package managers).

2. Configure Gnuastro while adding the following options for no shared
libraries, with debugging flags, and with no optimization so Valgrind can
report the status accurately as shown below:


$ ./configure --disable-shared CFLAGS="-g -O0"


(This is also described in the manual
<https://www.gnu.org/software/gnuastro/manual/html_node/Building-and-debugging.html>.)

3. Add `valgrind --leak-check=yes' to the start of the command in the script
that produces the memory error.

To facilitate these steps for the user, we can add an option to configure like
`--enable-valgrind-checks'. This option will cause `./configure' to check if
Valgrind is installed, will add those configure options, and will run all the
tests with valgrind appended to the start of the command.

If you can work on this put a comment ;-), I am too busy right now...




    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/task/?14258>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]