Databases
StackOverflow2013
Postsdbo
POProgram terminates early with valgrind memcheck
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POProgram terminates early with valgrind memcheck
    primarykey
    data
    text
    <p>I have a C-programm (a lot of numerics and too long to post) which I compile with </p> <pre><code>gcc -g -O0 program.c -o program </code></pre> <p>I am trying to debug it using gdb and valgrind memcheck. After some changes on the code I found that </p> <pre><code>valgrind --tool=memcheck --log-file=output.log ./program </code></pre> <p>gives</p> <pre><code>==15866== Memcheck, a memory error detector ==15866== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al. ==15866== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info ==15866== Command: ./program ==15866== Parent PID: 3362 ==15866== ==15866== Warning: client switching stacks? SP change: 0xbe88bcd8 --&gt; 0xbe4e1f70 ==15866== to suppress, use: --max-stackframe=3841384 or greater ==15866== Invalid write of size 4 ==15866== at 0x804B7BE: main (program.c:1396) ==15866== Address 0xbe4e1f74 is on thread 1's stack ==15866== ==15866== Invalid write of size 4 ==15866== at 0x804B7C2: main (program.c:1396) ==15866== Address 0xbe4e1f70 is on thread 1's stack ==15866== ==15866== Invalid read of size 4 ==15866== at 0x4320011: on_exit (on_exit.c:34) ==15866== by 0x43064D2: (below main) (libc-start.c:226) ==15866== Address 0xbe4e1f70 is on thread 1's stack ==15866== ==15866== Invalid read of size 4 ==15866== at 0x4320022: on_exit (on_exit.c:37) ==15866== by 0x43064D2: (below main) (libc-start.c:226) ==15866== Address 0xbe4e1f74 is on thread 1's stack </code></pre> <p>and many more of this kind. </p> <pre><code>valgrind --tool=memcheck --max-stackframe=3841384 --log-file=output.log ./program </code></pre> <p>does not print any errors. But what puzzles me is that with both valgrind calls the program exits early (without error messages) and does not do the computation it is supposed to do. The behaviour with same compiler options but run without valgrind is entirely different and looks pretty normal. I suspect a memory error however and want to use valgrind to find it. My question therefore: What kind of error can make a program bahave so differently when executed with valgrind? And if these are memory related errors how can I identify it? Note that it is clear to me that I can "debug by hand" to locate it. But can I maybe run gdb with valgrind to see where it exits.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USsimonc
    1. UShighsciguy
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POProgram terminates early with valgrind memcheck
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    2. VO
      singulars
      1. POProgram terminates early with valgrind memcheck
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POProgram terminates early with valgrind memcheck
      1. This table or related slice is empty.
      1. VTUpMod
    1. COYou're probably causing a stack overflow. Are you allocating "large" arrays on the stack? E.g. `double myArray[10000000];` If so then you should replace such allocations with heap memory using `malloc` and `free`.
      singulars
      1. POProgram terminates early with valgrind memcheck
      1. USDouglas B. Staple
    2. CO_What kind of error can make a program bahave so differently when executed with valgrind?_ Undefined behavior.
      singulars
      1. POProgram terminates early with valgrind memcheck
      1. USShahbaz
    3. COHave you tried `--leak-check=full`?
      singulars
      1. POProgram terminates early with valgrind memcheck
      1. USShahbaz
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload