gflags segfaults in google::ParseCommandLineFlags

[sharper]

gflags segfaults in google::ParseCommandLineFlags

[GoogleCodeExporter]

hmmm, curious.  Does the program run without segfault when you run it normally 
--
that is, not in valgrind?

The line in question that valgrind seems to be complaining is this one:
  flag_ = new CommandLineFlag(name, help, filename, current, defvalue);

It's in a constructor, so flag_ isn't going to be at 0x0, and I don't know why
valgrind would care if any of the ComandLineFlag arguments were at 0x0, so I'm
confused as to what it's complaining about.  Is there a way to get valgrind to 
emit
more information about what it's thinking?

Original comment by [email protected] on 13 Aug 2007 at 7:51

[GoogleCodeExporter]

Yes, it segfaults when not run through valgrind.  I'm using g++ (GCC) 4.0.3 
(Ubuntu
4.0.3-1ubuntu5).

I don't know how to get valgrind to emit more information, but I tried a few 
more
simple tests.  The same error is raised if I:

- use a non-empty string default
- pass false instead of true for ParseCommandLineFlags
- remove the bool flag
- remove the string flag
- remove both flags

Original comment by [email protected] on 13 Aug 2007 at 8:16

[GoogleCodeExporter]

(I got access to the machine to run the binary.)  Looking at this closer, the 
problem
is that you didn't link in -pthread to your application.  I thought in such 
cases,
glibc put in a dummy pthread implementation (or its own?), but apparently that
doesn't work here, or at least not well.

I'll see if I can get a good workaround for the next release.

Original comment by [email protected] on 13 Aug 2007 at 9:10

• Changed state: Accepted

[GoogleCodeExporter]

I've narrowed down the problem further to a pthread_once call, and have figured 
out a
way to remove it.  I'll make a new release soon

Original comment by [email protected] on 13 Aug 2007 at 9:34

• Changed state: Started

[GoogleCodeExporter]

This should be fixed in gflags 0.6

Original comment by [email protected] on 31 Aug 2007 at 4:24

• Changed state: Fixed

[GoogleCodeExporter]

Confirmed fixed in version 0.6.

Original comment by [email protected] on 31 Aug 2007 at 4:59