From e5ecfa27455a8be97429e9f88e8e6582b9819c6f Mon Sep 17 00:00:00 2001 From: Steve Reinhardt Date: Sat, 14 Jul 2007 12:22:04 -0700 Subject: Disable PrintThreadInfo since it causes a panic when using VPtr. See Flyspray #281. --HG-- extra : convert_revision : 199ef802bcabed09f6ea6922c3a3954fea161190 --- src/arch/alpha/linux/system.cc | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/src/arch/alpha/linux/system.cc b/src/arch/alpha/linux/system.cc index 9a452e10f..e8bdc1d66 100644 --- a/src/arch/alpha/linux/system.cc +++ b/src/arch/alpha/linux/system.cc @@ -132,7 +132,12 @@ LinuxAlphaSystem::LinuxAlphaSystem(Params *p) debugPrintkEvent = addKernelFuncEvent("dprintk"); idleStartEvent = addKernelFuncEvent("cpu_idle"); - if (kernelSymtab->findAddress("alpha_switch_to", addr) && DTRACE(Thread)) { + // Disable for now as it runs into panic() calls in VPTr methods + // (see sim/vptr.hh). Once those bugs are fixed, we can + // re-enable, but we should find a better way to turn it on than + // using DTRACE(Thread), since looking at a trace flag at tick 0 + // leads to non-intuitive behavior with --trace-start. + if (false && kernelSymtab->findAddress("alpha_switch_to", addr)) { printThreadEvent = new PrintThreadInfo(&pcEventQueue, "threadinfo", addr + sizeof(MachInst) * 6); } else { -- cgit v1.2.3