Skip to content
GitLab
Menu
Projects
Groups
Snippets
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Sign in
Toggle navigation
Menu
Open sidebar
TASTE
buildsupport
Commits
ab4605f0
Commit
ab4605f0
authored
Jul 25, 2017
by
Maxime Perrotin
Browse files
Fix non-caught error when deployment is buggy
reported in
ocarina#5
parent
e32aae96
Changes
1
Hide whitespace changes
Inline
Side-by-side
ada/buildsupport.adb
View file @
ab4605f0
...
...
@@ -1051,13 +1051,12 @@ procedure BuildSupport is
Find_Connected_Bus
(
Tmp_CI
,
Accessed_Bus
,
Accessed_Port
);
if
Accessed_Bus
/=
No_Node
and
then
Accessed_Port
/=
No_Node
Accessed_Port
/=
No_Node
and
then
Associated_Processor_Name
/=
No_Name
then
Accessed_Bus_Name
:=
Name
(
Identifier
(
Accessed_Bus
));
Accessed_Port_Name
:=
Name
(
Identifier
(
Accessed_Port
));
end
if
;
if
Associated_Processor_Name
/=
No_Name
then
C_New_Device
(
Get_Name_String
(
Name
(
Identifier
(
Processes
))),
Get_Name_String
...
...
@@ -1079,6 +1078,13 @@ procedure BuildSupport is
Get_Name_String
(
Device_ASN1_Module
),
Device_ASN1_Module_Len
);
C_End_Device
;
else
Exit_On_Error
(
True
,
"[ERROR] In your deployment view, check the connection of"
&
" this driver: "
&
Get_Name_String
(
Name
(
Identifier
(
Processes
)))
&
" - in processor "
&
Get_Name_String
(
Associated_Processor_Name
));
end
if
;
end
;
end
if
;
...
...
Write
Preview
Supports
Markdown
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment