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
This commit is contained in:
Jason Molenda 2015-08-20 03:05:09 +00:00
parent 9fdce9adee
commit 5543abb036
1 changed files with 7 additions and 0 deletions

View File

@ -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 ())