Boost logo

Boost Testing :

From: K. Noel Belcourt (kbelco_at_[hidden])
Date: 2008-07-14 23:43:28


Hi Beman,

Process_jam_log is crashing on Max OS 10.5. Interestingly, it fails
in different places depending on whether it was built debug or
release. It also seems that the debug process_jam_log issues this
diagnostic:

Abort: process_jam_log must be run from within a boost directory tree

but running the release process_jam_log from the same (non-boost
directory tree) directory with the same arguments doesn't produce
this message. I haven't had time to debug it yet but I thought I'd
start by sending you what I had.

This is why the Sandia-darwin results for x86 is broken.

-- Noel

// call stack from building release process_jam_log

(gdb) set args "/private/tmp/kbelco/boost/results" < "/private/tmp/
kbelco/boost/results/bjam.log"
(gdb) run
Starting program: /private/tmp/kbelco/boost/tools_regression/build/
bin/darwin-4.0.1/release/process_jam_log "/private/tmp/kbelco/boost/
results" < "/private/tmp/kbelco/boost/results/bjam.log"
Reading symbols for shared libraries +++. done

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_PROTECTION_FAILURE at address: 0x00000000
0x0001053b in
boost::filesystem::initial_path<boost::filesystem::basic_path<std::strin
g, boost::filesystem::path_traits> > ()
(gdb) where
#0 0x0001053b in
boost::filesystem::initial_path<boost::filesystem::basic_path<std::strin
g, boost::filesystem::path_traits> > ()
#1 0x000036b3 in ?? ()
#2 0x00001f96 in ?? ()
(gdb)

// call stack from building debug process_jam_log (run with same
arguments)

(gdb) set args "/private/tmp/kbelco/boost/results" < "/private/tmp/
kbelco/boost/results/bjam.log"
(gdb) run
Starting program: /private/tmp/kbelco/boost/tools_regression/build/
bin/darwin-4.0.1/debug/process_jam_log "/private/tmp/kbelco/boost/
results" < "/private/tmp/kbelco/boost/results/bjam.log"
unlimit: descriptors: Can't remove limit (Invalid argument)
Reading symbols for shared libraries +++. done
boost_root: /private/tmp/kbelco/boost/boost
locate_root: /private/tmp/kbelco/boost/results
Assertion failed: (m_action_name == action_name), function
stop_message, file ../src/process_jam_log.cpp, line 499.

Program received signal SIGABRT, Aborted.
0x90072b9e in __kill ()
(gdb) where
#0 0x90072b9e in __kill ()
#1 0x90072b91 in kill$UNIX2003 ()
#2 0x900e9ec2 in raise ()
#3 0x900f947f in abort ()
#4 0x900eb063 in __assert_rtn ()
#5 0x0000edbc in (anonymous
namespace)::message_manager::stop_message (this=0xbffff790,
action_name=@0xbffff830, target_directory=@0xbffff82c,
result=@0xbffff824, timestamp=@0xbffff820, content=@0xbffff788) at ../
src/process_jam_log.cpp:499
#6 0x000050ff in main (argc=1, argv=0xbffff8d8) at ../src/
process_jam_log.cpp:808


Boost-testing list run by mbergal at meta-comm.com