From: Markus Schöpflin (markus.schoepflin_at_[hidden])
Date: 2006-08-09 04:13:38
John Maddock wrote:
> Markus Schöpflin wrote:
>> John Maddock wrote:
>>> Failing that, if you can run it under gdb and see what traps that
>>> might suggest something.
>> And here is the stack trace when running the program on gdb:
> There seems to be a problem then with exceptions when thrown from a running
> thread not getting caught by the appropriate handler - I can assure you that
> there *is* a handler present for exceptions of type regex_error, indeed the
> code for the multithreaded case is no different from the single threaded
> one. Is this a known gcc problem?
I have no idea. But the thread libs regression tests are all passing.
Looking more closely at the call stack, it seems corrupted. Especially
interesting is frame #14:
#14 0x0000000120191338 in boost::re_detail::basic_regex_parser<char,
boost::cpp_regex_traits<char> >::parse (this=0x0, p1=0x140122180
p2=0x12019178c "ø\037º'd\207½#P", l_flags=1074929976) at
The this pointer is NULL here. And further up we have more strange values.
I have to admit I'm a little lost here.
I do get a warning when compiling the tests about some signed/unsigned
conversion issues. Maybe this is related?
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk