|
From: Pierre-Luc P. <pie...@ho...> - 2012-10-02 18:07:34
|
Well,
This is just initialization for a static member from the class CBase64:
==11125== by 0x8188CED: __static_initialization_and_destruction_0(int, int) (Base64.cpp:29):
27
28 CXString CBase64::m_sBase64Alphabet =
29 "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/";
30
The other line is just the end of the file.
==11125== by 0x8188D2F: global constructors keyed to Base64.cpp (Base64.cpp:121)
My guess is that the constructor code resides at the end of the code for the current file, but this is just my guess. ;-)
Pierre
> From: fa...@kd...
> To: val...@li...
> CC: pie...@ho...
> Subject: Re: [Valgrind-users] Large application SIGSEGV when run in valgrind
> Date: Tue, 2 Oct 2012 18:38:07 +0000
>
> 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 at these two lines, say?
>
> Unless valgrind is wrong, something funky is being done by that code, so it might help to see what it's doing.
>
> --
> David Faure, fa...@kd..., http://www.davidfaure.fr
> Working on KDE, in particular KDE Frameworks 5
>
|