mem: Output precise range when XBar has conflicts
authorCurtis Dunham <Curtis.Dunham@arm.com>
Sat, 27 Sep 2014 13:08:32 +0000 (09:08 -0400)
committerCurtis Dunham <Curtis.Dunham@arm.com>
Sat, 27 Sep 2014 13:08:32 +0000 (09:08 -0400)
src/mem/xbar.cc

index 6e4630fb642ef9a0ed2eae920b80d9e1dce2a43d..d56e726d56ba10e096de97632c0ab198e653c3bb 100644 (file)
@@ -407,8 +407,9 @@ BaseXBar::recvRangeChange(PortID master_port_id)
                     r.to_string(), master_port_id);
             if (portMap.insert(r, master_port_id) == portMap.end()) {
                 PortID conflict_id = portMap.find(r)->second;
-                fatal("%s has two ports with same range:\n\t%s\n\t%s\n",
+                fatal("%s has two ports responding within range %s:\n\t%s\n\t%s\n",
                       name(),
+                      r.to_string(),
                       masterPorts[master_port_id]->getSlavePort().name(),
                       masterPorts[conflict_id]->getSlavePort().name());
             }