Actually the timer goes off and the UART gets checked manually, and
everything has passed through by that point so execution continues. I
think there's supposed to be an interrupt or something for when the UART
finishes, so there may be an issue with that never showing up.
Gabe Black wrote:
# HG changeset patch
# User Ali Saidi sa...@eecs.umich.edu
# Date 1233270761 18000
# Node ID 5ca5f9050c0362cc54c386d19919c830d9e658f6
# Parent 130e1935985739d0727c51fd94c0d0b26a8b8ce7
Config: Cause a fatal() when a parameter without a default value isn't set(FS
#315).
diff --git
changeset dad5aad2dc2d in /z/repo/m5
details: http://repo.m5sim.org/m5?cmd=changeset;node=dad5aad2dc2d
description:
Fix typo
diffstat:
1 file changed, 1 insertion(+), 1 deletion(-)
src/sim/System.py |2 +-
diffs (12 lines):
diff -r f4a1bcc3b7bc -r dad5aad2dc2d src/sim/System.py
---
Looks like the other error (right above the one you added) should be changed
from a panic to a fatal as well.
Steve
On Thu, Jan 29, 2009 at 3:22 PM, Ali Saidi sa...@umich.edu wrote:
This is a simple patch to fix FlySpray issue #315. We don't panic if a
parameter without a default value isn't
This is a simple patch to fix FlySpray issue #315. We don't panic if a
parameter without a default value isn't set which is a problem if the
reason a default isn't set is that the user really needs to set one.
I'm sending this mostly for Nate to say he is fine with doing it this
way.
Are
On Jan 30, 2009, at 1:38 AM, nathan binkert wrote:
This is a simple patch to fix FlySpray issue #315. We don't panic
if a
parameter without a default value isn't set which is a problem if the
reason a default isn't set is that the user really needs to set one.
I'm sending this mostly for
That sounds like a good idea, but what if I had panic(Soemthing bad)
and changed it to panic(Something bad)? They'd be the same thing but
with different hashes.
Gabe
Ali Saidi wrote:
We've talked for a while about needing better error messages, links,
more descriptions on the website, etc.
Anybody? I was thinking one option would be to extend SyscallDesc to
have a gatherArgs() function and a describe() function. describe() would
just generate a string which would be like disassembly but for syscalls.
Then, every syscall would have a nice line in SE with the syscall
traceflag,
