On 30 September 2011 10:23, Peter Chubb <peter.ch...@nicta.com.au> wrote: >>>>>> "Peter" == Peter Maydell <peter.mayd...@linaro.org> writes: > Peter> hw_error() is a fatal error -- don't use it for conditions that > Peter> can be triggered by a malicious guest. (And since it's noreturn > Peter> there's not much point putting any code after it...) > > Is there a better `tell the programmer s/he's done something stupid' > error function? The plxxx.c files all used hw_error() for bad > offsets.
Unfortunately there isn't really a good infrastructure for this kind of error. At the moment we have a mix of hw_error(), printing to stderr, printing to stderr only if debug macros were enabled at compile time, and silently ignoring things, all of which have obvious drawbacks. -- PMM
