With error_propagate, the stack trace from any error_abort/fatal usage will start from the error_propagate() call, which is largely useless. Using ERRP_GUARD ensures the stack trace starts from the origin that reported the error. Reviewed-by: Paolo Bonzini <pbonzini@redhat.com> Reviewed-by: Markus Armbruster <armbru@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> |
||
|---|---|---|
| .. | ||
| container.c | ||
| meson.build | ||
| object.c | ||
| object_interfaces.c | ||
| qom-hmp-cmds.c | ||
| qom-qmp-cmds.c | ||
| qom-qobject.c | ||
| trace-events | ||
| trace.h | ||