Found it! A trivial error (missing a break in a switch statement) that only
impacts things if multiple sockets are specified in the slot_list. CMR filed to
include the fix in 1.6.4
Thanks for your patience
Ralph
On Jan 24, 2013, at 7:50 PM, Ralph Castain wrote:
> I built the current 1.6 branc
I built the current 1.6 branch (which hasn't seen any changes that would impact
this function) and was able to execute it just fine on a single socket machine.
I then gave it your slot-list, which of course failed as I don't have two
active sockets (one is empty), but it appeared to parse the li
