Hi all,

I spent today with finding an error, I found it, though I don't no why.
I have a class with static constants, like this:

class EXPORT_API BusConstants {
public:
static const std::string PIPE_DIRECTORY;
};

Somewhere else, I declare the String:

const std::string BusConstants::PIPE_DIRECTORY

Then, in some other class, I want to initialize a static logger with
this string:

Category& UBusHelper::logger =
Category::getInstance(BusConstants::PIPE_DIRECTORY );

What is very weird is that I get segmentation faults on Linux and
Solaris, but everything seems to work fine on Windows. My workaround is
to define the string as "const char*", and then it works, because the
compiler automatically remarks this and seems to create a new string
object when I call Category::getInstance. Here is how it works:

class EXPORT_API BusConstants {
public:
static const char* PIPE_DIRECTORY;
};

Somewhere else, I declare the char pointer:

const char* BusConstants::PIPE_DIRECTORY

Does somebody have any idea? My only guess is that static const strings
are not created until some constructor or anything is called. Because
in the class with my constants (BusConstants) I don't have any
constructor, this is why it is only initialized when some other method
of BusConstants is called.I used to program quite a bit in Java, there
this is different? I very appreciate if anybody could reassure my
assumption. Sorry, if this is a bit a naive question.

By the way: The segmentation fault did not happen every time. It only
happened when I had some weird order in how I linked my object files
(one object file per C++ class).

Thanks a lot.
Michael

msaladin@gmx.net wrote:[color=blue]
> Hi all,
>
> I spent today with finding an error, I found it, though I don't no why.
> I have a class with static constants, like this:
>
> class EXPORT_API BusConstants {
> public:
> static const std::string PIPE_DIRECTORY;
> };
>
> Somewhere else, I declare the String:
>
> const std::string BusConstants::PIPE_DIRECTORY
>
> Then, in some other class, I want to initialize a static logger with
> this string:
>
> Category& UBusHelper::logger =
> Category::getInstance(BusConstants::PIPE_DIRECTORY );
>
> What is very weird is that I get segmentation faults on Linux and
> Solaris, but everything seems to work fine on Windows. My workaround is
> to define the string as "const char*", and then it works, because the
> compiler automatically remarks this and seems to create a new string
> object when I call Category::getInstance. Here is how it works:[/color]

This is a FAQ:

http://www.parashift.com/c++-faq-lit...html#faq-10.12

There are solutions there as well.

Ben Pope
--
I'm not just a number. To many, I'm known as a string...

msaladin@gmx.net wrote:
[color=blue]
> Hi all,
>
> I spent today with finding an error, I found it, though I don't no why.
> I have a class with static constants, like this:
>
> class EXPORT_API BusConstants {
> public:
> static const std::string PIPE_DIRECTORY;
> };[/color]

It's a good idea to reserve names with all uppercase for macros only.
[color=blue]
> Somewhere else, I declare the String:[/color]

You mean you define it. The above was the declaration.
[color=blue]
> const std::string BusConstants::PIPE_DIRECTORY[/color]

Without an initializer, a constant is pretty useless.
[color=blue]
> Then, in some other class, I want to initialize a static logger with
> this string:
>
> Category& UBusHelper::logger =
> Category::getInstance(BusConstants::PIPE_DIRECTORY );
>
> What is very weird is that I get segmentation faults on Linux and
> Solaris, but everything seems to work fine on Windows.
> My workaround is to define the string as "const char*", and then it
> works, because the compiler automatically remarks this and seems to create
> a new string object when I call Category::getInstance. Here is how it
> works:
>
> class EXPORT_API BusConstants {
> public:
> static const char* PIPE_DIRECTORY;
> };
>
> Somewhere else, I declare the char pointer:
>
> const char* BusConstants::PIPE_DIRECTORY
>
> Does somebody have any idea? My only guess is that static const strings
> are not created until some constructor or anything is called.[/color]

Well, static class members are created at program startup, and part of that
creation is that the constructor is called. However, there is no specific
order in which objects defined in different translation units are created.
So it's likely that on the Linux and Solaris machines, you were lucky,
because the string was created after the logger. Otherwise, you wouldn't
have noticed the error.
[color=blue]
> Because in the class with my constants (BusConstants) I don't have any
> constructor, this is why it is only initialized when some other method
> of BusConstants is called.[/color]

Static members don't have anything to do with the constructor. They belong
to the class, not to instances of it. They are all created at program
startup.
[color=blue]
> I used to program quite a bit in Java, there this is different? I very
> appreciate if anybody could reassure my assumption. Sorry, if this is a
> bit a naive question.
>
> By the way: The segmentation fault did not happen every time. It only
> happened when I had some weird order in how I linked my object files
> (one object file per C++ class).[/color]

The oder of initialization might (but isn't required to) depend on the order
in which you give the object files to the linker.