I had a problem like last May, though it may not have been the same problem. In
my case it was the optimization settings. I typically used -O0 for valgrind,
and at -O0 the program didn’t crash. At level -O1 or higher it always crashed.
I can’t recall if I ran it in valgrind at -O1 or higher,
On 1/26/19, Eliot Moss wrote:
On 1/26/2019, Peng Yu wrote:
I have an executable. If I just run on its own, there will be
segmentation fault. But if I run it using valgrind, it finishes
successfully. Does anybody how can this happen? How to debug such a
program? Thanks.
Maybe not the sort of
A segfault is usually a bad pointer or something pointing outside
allocated space. Why it stops segfaulting when you run it through
Valgrind I don't know. Compile with -g for either Valgrind or gdb,
and if it still runs in Valgrind try gdb. You can just do gdb
then you'll probably have to type
On 1/26/2019 6:12 PM, Peng Yu wrote:
I have an executable. If I just run on its own, there will be
segmentation fault. But if I run it using valgrind, it finishes
successfully. Does anybody how can this happen? How to debug such a
program? Thanks.
Maybe not the sort of answer you have in
On Sat, 2019-01-26 at 17:12 -0600, Peng Yu wrote:
> Hi,
>
> I have an executable. If I just run on its own, there will be
> segmentation fault. But if I run it using valgrind, it finishes
> successfully. Does anybody how can this happen? How to debug such a
> program? Thanks.
Is valgrind
Hi,
I have an executable. If I just run on its own, there will be
segmentation fault. But if I run it using valgrind, it finishes
successfully. Does anybody how can this happen? How to debug such a
program? Thanks.
--
Regards,
Peng
___
