Comment 2 for bug 297538

I think this should solve this problem:

paste from the changelog:
"initialized sim_probes with -1 and if not overwritten by the command line parameters, it is set to DEF_SIM_PROBES. If it is greater then max_hops*probes_per_hop, we lower it to this value so we can use it to trace less than 6 hops without explicitly specifying the -N parameter "

this is the line that caused the problem:
if (!sim_probes || sim_probes > max_hops * probes_per_hop)
  ex_error ("sim hops out of range");

by default you get if(16 > 3 * 5)
I've changed this so if you don't specify the sim_probes in the command line parameters and the default value is greater than max_hops*probes_per_hop, sim_probes will be initialised with (max_hops * probes_per_hop), thus avoiding the problem