Searched hist:11299 (Results 1 - 5 of 5) sorted by relevance
| /gem5/src/sim/ | ||
| H A D | init_signals.cc | diff 11299:72046b9b3323 Sun Jan 17 21:27:00 EST 2016 Steve Reinhardt <steve.reinhardt@amd.com> sim: don't ignore SIG_TRAP By ignoring SIG_TRAP, using --debug-break <N> when not connected to a debugger becomes a no-op. Apparently this was intended to be a feature, though the rationale is not clear. If we don't ignore SIG_TRAP, then using --debug-break <N> when not connected to a debugger causes the simulation process to terminate at tick N. This is occasionally useful, e.g., if you just want to collect a trace for a specific window of execution then you can combine this with --debug-start to do exactly that. In addition to not ignoring the signal, this patch also updates the --debug-break help message and deletes a handful of unprotected calls to Debug::breakpoint() that relied on the prior behavior. |
| /gem5/src/dev/net/ | ||
| H A D | sinic.cc | diff 11299:72046b9b3323 Sun Jan 17 21:27:00 EST 2016 Steve Reinhardt <steve.reinhardt@amd.com> sim: don't ignore SIG_TRAP By ignoring SIG_TRAP, using --debug-break <N> when not connected to a debugger becomes a no-op. Apparently this was intended to be a feature, though the rationale is not clear. If we don't ignore SIG_TRAP, then using --debug-break <N> when not connected to a debugger causes the simulation process to terminate at tick N. This is occasionally useful, e.g., if you just want to collect a trace for a specific window of execution then you can combine this with --debug-start to do exactly that. In addition to not ignoring the signal, this patch also updates the --debug-break help message and deletes a handful of unprotected calls to Debug::breakpoint() that relied on the prior behavior. |
| H A D | ns_gige.cc | diff 11299:72046b9b3323 Sun Jan 17 21:27:00 EST 2016 Steve Reinhardt <steve.reinhardt@amd.com> sim: don't ignore SIG_TRAP By ignoring SIG_TRAP, using --debug-break <N> when not connected to a debugger becomes a no-op. Apparently this was intended to be a feature, though the rationale is not clear. If we don't ignore SIG_TRAP, then using --debug-break <N> when not connected to a debugger causes the simulation process to terminate at tick N. This is occasionally useful, e.g., if you just want to collect a trace for a specific window of execution then you can combine this with --debug-start to do exactly that. In addition to not ignoring the signal, this patch also updates the --debug-break help message and deletes a handful of unprotected calls to Debug::breakpoint() that relied on the prior behavior. |
| /gem5/src/python/m5/ | ||
| H A D | main.py | diff 11299:72046b9b3323 Sun Jan 17 21:27:00 EST 2016 Steve Reinhardt <steve.reinhardt@amd.com> sim: don't ignore SIG_TRAP By ignoring SIG_TRAP, using --debug-break <N> when not connected to a debugger becomes a no-op. Apparently this was intended to be a feature, though the rationale is not clear. If we don't ignore SIG_TRAP, then using --debug-break <N> when not connected to a debugger causes the simulation process to terminate at tick N. This is occasionally useful, e.g., if you just want to collect a trace for a specific window of execution then you can combine this with --debug-start to do exactly that. In addition to not ignoring the signal, this patch also updates the --debug-break help message and deletes a handful of unprotected calls to Debug::breakpoint() that relied on the prior behavior. |
| /gem5/src/arch/alpha/ | ||
| H A D | ev5.cc | diff 11299:72046b9b3323 Sun Jan 17 21:27:00 EST 2016 Steve Reinhardt <steve.reinhardt@amd.com> sim: don't ignore SIG_TRAP By ignoring SIG_TRAP, using --debug-break <N> when not connected to a debugger becomes a no-op. Apparently this was intended to be a feature, though the rationale is not clear. If we don't ignore SIG_TRAP, then using --debug-break <N> when not connected to a debugger causes the simulation process to terminate at tick N. This is occasionally useful, e.g., if you just want to collect a trace for a specific window of execution then you can combine this with --debug-start to do exactly that. In addition to not ignoring the signal, this patch also updates the --debug-break help message and deletes a handful of unprotected calls to Debug::breakpoint() that relied on the prior behavior. |
Completed in 25 milliseconds