From 5543abb0363c4228fd025de641e1535d29a17eae Mon Sep 17 00:00:00 2001 From: Jason Molenda Date: Thu, 20 Aug 2015 03:05:09 +0000 Subject: When the target definition is unparseable, print an error message to the user. e.g. specified via the plugin.process.gdb-remote.target-definition-file setting. Currently we silently ignore the target definition if there is a parse error. llvm-svn: 245536 --- lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp | 7 +++++++ 1 file changed, 7 insertions(+) (limited to 'lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp') diff --git a/lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp b/lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp index 16a966dba42..ed660238375 100644 --- a/lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp +++ b/lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp @@ -529,7 +529,14 @@ ProcessGDBRemote::BuildDynamicRegisterInfo (bool force) { // See if we can get register definitions from a python file if (ParsePythonTargetDefinition (target_definition_fspec)) + { return; + } + else + { + StreamSP stream_sp = GetTarget().GetDebugger().GetAsyncOutputStream(); + stream_sp->Printf ("ERROR: target description file %s failed to parse.\n", target_definition_fspec.GetPath().c_str()); + } } if (GetGDBServerRegisterInfo ()) -- cgit v1.2.3