[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH v4 0/4] Introduce error_report_{fatal|abort}
From: |
Fam Zheng |
Subject: |
Re: [Qemu-devel] [PATCH v4 0/4] Introduce error_report_{fatal|abort} |
Date: |
Wed, 7 Sep 2016 17:33:08 +0800 |
User-agent: |
Mutt/1.7.0 (2016-08-17) |
On Wed, 09/07 10:23, Alex Bennée wrote:
> Last time I needed to do error reporting I was told the error_setg
> method was the correct way to do it and the report/exit case made sense
> only in the top level. Before we add even more error reporting
> primitives can we update HACKING (or possibly add somethings to docs/)
> that describes when and where the various error report mechanisms should
> be used?
FWIW, the comment of error_setg clarifies the recommended usage now:
...
> * Please don't error_setg(&error_fatal, ...), use error_report() and
> * exit(), because that's more obvious.
> * Likewise, don't error_setg(&error_abort, ...), use assert().
> */
> #define error_setg(errp, fmt, ...) \
...
Fam
- [Qemu-devel] [PATCH v4 0/4] Introduce error_report_{fatal|abort}, Peter Xu, 2016/09/07
- [Qemu-devel] [PATCH v4 1/4] error-report: provide error_report_fatal(), Peter Xu, 2016/09/07
- [Qemu-devel] [PATCH v4 2/4] error-report: provide error_report_abort(), Peter Xu, 2016/09/07
- [Qemu-devel] [PATCH v4 4/4] error-report: leverage error_report_abort(), Peter Xu, 2016/09/07
- [Qemu-devel] [PATCH v4 3/4] error-report: leverage error_report_fatal(), Peter Xu, 2016/09/07
- Re: [Qemu-devel] [PATCH v4 0/4] Introduce error_report_{fatal|abort}, Fam Zheng, 2016/09/07
- Re: [Qemu-devel] [PATCH v4 0/4] Introduce error_report_{fatal|abort}, Alex Bennée, 2016/09/07
- Re: [Qemu-devel] [PATCH v4 0/4] Introduce error_report_{fatal|abort},
Fam Zheng <=
- Re: [Qemu-devel] [PATCH v4 0/4] Introduce error_report_{fatal|abort}, Markus Armbruster, 2016/09/09