[HTCondor-users] Segfault in condor_master, HTCondor 8.1.0 built from source on Mac OS Mountain Lion

[Leo Singer <lsinger@xxxxxxxxxxx>]

Hello,

I am working on updating the MacPorts port of HTCondor to version 8.1.0. I have built HTCondor from the 'V8_1_0' tag on Mac OS X Mountain Lion. condor_master segfaults before any of the daemons start up. A backtrace obtained with gdb looks like this:

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0x000000000000000b
std::tr1::__detail::_Hashtable_iterator<std::pair<std::string const, classad::ExprTree*>, false, false>::_Hashtable_iterator () at /usr/include/c++/4.2.1/tr1/hashtable_policy.h:388
388	      : _Hashtable_iterator_base<_Value, __cache>(*__b, __b) { }
(gdb) bt
#0  std::tr1::__detail::_Hashtable_iterator<std::pair<std::string const, classad::ExprTree*>, false, false>::_Hashtable_iterator () at /usr/include/c++/4.2.1/tr1/hashtable_policy.h:388
#1  std::tr1::_Hashtable<std::string, std::pair<std::string const, classad::ExprTree*>, std::allocator<std::pair<std::string const, classad::ExprTree*> >, std::_Select1st<std::pair<std::string const, classad::ExprTree*> >, classad::CaseIgnEqStr, classad::ClassadAttrNameHash, std::tr1::__detail::_Mod_range_hashing, std::tr1::__detail::_Default_ranged_hash, std::tr1::__detail::_Prime_rehash_policy, false, false, true>::begin () at hashtable_policy.h:243
#2  0x0000000100041373 in compat_classad::ClassAd::NextExpr (this=0x7fff5fbef910, name=@0x7fff5fbef908, value=@0x7fff5fbef900) at compat_classad.cpp:2082
#3  0x0000000100145fd6 in SecMan::ExportSecSessionInfo (this=0x7fff5fbef910, session_id=0x100b25ac8 "45878d0b0300e8b03c28a833d439028997ef562356643f35", session_info=@0x7fff5fbefd78) at condor_secman.cpp:3067
#4  0x000000010019273c in DaemonCore::Create_Process (priv=PRIV_ROOT, this=0x7fff5fbff3d0, executable=0x7fff5fbff3d0 "???_?", args=@0x7fff5fbff3d0, reaper_id=1606415312, want_command_port=1606415312, env=0x100b22b40, cwd=0x0, family_info=0x7fff5fbff6e8, sock_inherit_list=0x0, std=0x0, fd_inherit_list=0x0, nice_inc=0, sigmask=0x0, job_opt_mask=0, core_hard_limit=0x0, affinity_mask=0x0, daemon_sock=0x0, err_return_msg=0x0, remap=0x0, as_hard_limit=0) at daemon_core.cpp:6614
#5  0x000000010000de7d in daemon::RealStart (this=0x7fff5fbff9e0) at masterDaemon.cpp:806
#6  0x000000010000e399 in Daemons::StartDaemonHere (this=0x100b22ad0, daemon=0x100b23650) at masterDaemon.cpp:1916
#7  0x000000010000e3eb in Daemons::StartAllDaemons (this=0x100b22ad0) at masterDaemon.cpp:1901
#8  0x00000001000062d0 in main_init (argc=11676368, argv=0x100008450) at master.cpp:367
#9  0x000000010019efca in dc_main (argc=1606417376, argv=0x7fff5fbffc10) at daemon_core_main.cpp:2528
#10 0x00007fff926317e1 in start ()

In stack frame #3 (SecMan::ExportSecSessionInfo in condor_secman.cpp), I noticed that exp_policy.chained_parent_ad is a pointer with the suspiciously low address 0xC.

Any idea what is going wrong here?

Thanks,
Leo Singer
Graduate Student @ LIGO-Caltech