tools/libxc: Identify problematic file in error messages
authorAndrew Cooper <andrew.cooper3@citrix.com>
Mon, 7 Dec 2015 13:09:08 +0000 (13:09 +0000)
committerIan Campbell <ian.campbell@citrix.com>
Tue, 8 Dec 2015 16:53:49 +0000 (16:53 +0000)
commit0091eb7f40b2b0a6567263d1cc097c2529084045
tree93586df6ccfdb6242a3d80241e568c6ddd30c6a1
parent95f2101a81747df03e3da6fd5a03b86474261564
tools/libxc: Identify problematic file in error messages

Error messages along the lines of:

   xc: error: panic: xc_dom_core.c:207: failed to open file: No such file or
   directory: Internal error

are of very little use.

Include the filename in the error messages, so the user does not have to
resort to debug level logging to identify the problem.

Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Acked-by: Ian Campbell <ian.campbell@citrix.com>
tools/libxc/xc_dom_core.c