|
|
Boost Testing : |
From: Stephen Carson (StephenC_at_[hidden])
Date: 2005-07-17 15:33:03
Jeff Garland asked me:
> I see a couple of the facet based tests
> are just aborting:
> Any chance you can run this in the debugger and get a stack trace for
me? If
> I know why it's aborting there's always a chance it can be fixed.
I'm not getting ideal output from gdb for some reason (no line
numbers), but here is what I get on the crash:
Program received signal EXC_BAD_ACCESS, Could not access
memory.
0x00034f60 in std::basic_streambuf<wchar_t, std::char_traits<wchar_t>
>::sgetc()
Here is what I get from doing a "backtrace":
#0 0x00034f60 in std::basic_streambuf<wchar_t, std::char_traits<
wchar_t> >::sgetc() ()
#1 0x000366b8 in std::istreambuf_iterator<wchar_t, std::char_traits<
wchar_t> >::operator*() const ()
#2 0x00034c64 in boost::date_time::time_input_facet<
boost::posix_time::ptime, wchar_t, std::istreambuf_iterator<wchar_t,
std::char_traits<wchar_t> > >::get(std::istreambuf_iterator<wchar_t,
std::char_traits<wchar_t> >&, std::istreambuf_iterator<wchar_t,
std::char_traits<wchar_t> >&, std::ios_base&, boost::posix_time::ptime&
, std::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<
wchar_t> >&, __bool8) const ()
#3 0x00034184 in boost::date_time::time_input_facet<
boost::posix_time::ptime, wchar_t, std::istreambuf_iterator<wchar_t,
std::char_traits<wchar_t> > >::get_local_time(std::istreambuf_iterator<
wchar_t, std::char_traits<wchar_t> >&, std::istreambuf_iterator<
wchar_t, std::char_traits<wchar_t> >&, std::ios_base&,
boost::posix_time::ptime&, std::basic_string<wchar_t, std::char_traits<
wchar_t>, std::allocator<wchar_t> >&) const ()
#4 0x00033e04 in
_ZN5boost10local_timersIwSt11char_traitsIwEEERSt13basic_istreamI
T_T0_ES8_RNS0_20local_date_time_baseINS_10posix_time5ptimeE
NS_9date_time14time_zone_baseISL_cEEEE ()
#5 0x00004868 in main ()
#6 0x000044dc in _start ()
#7 0x8fe01048 in ?? ()
I have somehow avoided ever really learning gdb, so if anyone wants
to take the trouble to tell me how to get more helpful debug info from
gdb that would be appreciated. I did get this when I started gdb on the
boost test executable, which might explain something:
unable to open symbol file: "/usr/lib/dyld": can't read symbols: File
format not recognized.
warning: Unable to read symbols from "/usr/lib/dyld" (prefix __dyld_).
warning: Unable to read symbols from "/usr/lib/dyld" (prefix __dyld_);
skipping.
Reading symbols for shared libraries .. done
--
Stephen W. Carson
Dirxion Software, St. Louis, MO, USA.
_______________________________________________________
_________
Sent via the WebMail system at Mail.Dirxion.com