Hello,
I am new at using valgrind. I first tried it on a relatively small program, and
everything worked ok.
When I try it with a much larger program (19MB), I get a SIGSEGV before the
main() is actually called. It looks like the program crashes while calling in
the constructor functions.
On Tuesday 02 October 2012 12:27:12 Pierre-Luc Provencal wrote:
==11125==by 0x8188CED: __static_initialization_and_destruction_0(int,
int) (Base64.cpp:29)
==11125==by 0x8188D2F: global constructors keyed to Base64.cpp
(Base64.cpp:121)
Greetings from Provence :-)
What does the code
...@kde.org
To: valgrind-users@lists.sourceforge.net
CC: pierr...@hotmail.com
Subject: Re: [Valgrind-users] Large application SIGSEGV when run in valgrind
Date: Tue, 2 Oct 2012 18:38:07 +
On Tuesday 02 October 2012 12:27:12 Pierre-Luc Provencal wrote:
==11125==by 0x8188CED
On 10/02/2012 09:27 AM, Pierre-Luc Provencal wrote:
Hello,
I am new at using valgrind. I first tried it on a relatively small program,
and everything worked ok.
When I try it with a much larger program (19MB), I get a SIGSEGV before the
main() is actually called. It looks like the
On Tue, 2012-10-02 at 12:48 -0700, John Reiser wrote:
In any case, please run cat /proc/PID/maps (where PID is the numerical
process ID) and show us what the mappings look like for addresses 0xFE00
and above, when the program hits the memcheck error (or shortly before.)
The easiest to
Using valgrind with gdb, the faulty address is now 0xFEABA104:
==29254== Process terminating with default action of signal 11 (SIGSEGV)
==29254== Access not within mapped region at address 0xFEABA104
==29254==at 0x8055129: CStdStrwchar_t::CStdStr(wchar_t const*)
(XString.h:1777)
CC: valgrind-users@lists.sourceforge.net
Subject: Re: [Valgrind-users] Large application SIGSEGV when run in valgrind
Using valgrind with gdb, the faulty address is now 0xFEABA104:
==29254== Process terminating with default action of signal 11 (SIGSEGV)
==29254== Access not within mapped
