$ uname -a
CYGWIN_NT-5.1 DULI2 1.5.19s(0.150/4/2) 20060110 00:01:37 i686 unknown
unknown Cygwin
$ cat foo.cpp
#include string
int main(){
std::string str;
}
$ g++ -g foo.cpp -o foo
[EMAIL PROTECTED] /cygdrive/d/programowanie/moje/Topcoder/prob
$ gdb ./foo
GNU gdb
Krzysztof Duleba wrote:
Program received signal SIGSEGV, Segmentation fault.
0x610aea58 in pthread_key_create () from /usr/bin/cygwin1.dll
This is a regression from 1.5.18.
That's normal. You can just continue. There was a thread about this
recently. pthread_key_create checks to see if
Brian Dessent wrote:
Program received signal SIGSEGV, Segmentation fault.
0x610aea58 in pthread_key_create () from /usr/bin/cygwin1.dll
This is a regression from 1.5.18.
That's normal. You can just continue.
Thanks. I don't like the idea of seeing this message anytime I debug code
that's
Krzysztof Duleba wrote:
Thanks. I don't like the idea of seeing this message anytime I debug code
that's using std::string, though, and I don't think it's normal.
If it bothers you, comment out the if (pthread_key::is_good_object
(key)) check in thread.cc. I'm not sure if it's possible for
Brian Dessent
Thanks. I don't like the idea of seeing this message anytime I debug
code
that's using std::string, though, and I don't think it's normal.
If it bothers you, comment out the if (pthread_key::is_good_object
(key)) check in thread.cc.
It does bother me.
tread.cc from 1.5.18 and
On Tue, Jan 10, 2006 at 06:38:54PM +0100, Krzysztof Duleba wrote:
Brian Dessent
Thanks. I don't like the idea of seeing this message anytime I debug
code
that's using std::string, though, and I don't think it's normal.
If it bothers you, comment out the if (pthread_key::is_good_object
(key))
Christopher Faylor wrote:
tread.cc from 1.5.18 and from the cvs are very alike and both call
pthread_key::is_good_object in the same fashion. Why only 1.5.19 is
having
this problem?
Either it is because we are purposely trying to annoy you or it may be
because cygwin 1.5.19 changed the way
7 matches
Mail list logo
