mirror of
https://github.com/NationalSecurityAgency/ghidra.git
synced 2025-10-06 03:50:02 +02:00
GP-0: Fixing yield keyword conflict when compiling with JDK 17
compliance.
This commit is contained in:
parent
046623b1f7
commit
1996cdacd1
1 changed files with 2 additions and 2 deletions
|
@ -577,7 +577,7 @@ public class AutoAnalysisManager implements DomainObjectListener, DomainObjectCl
|
|||
Integer originalPriority = activeTask.taskPriority;
|
||||
activeTask.taskPriority = limitPriority;
|
||||
try {
|
||||
yield(limitPriority, monitor);
|
||||
this.yield(limitPriority, monitor);
|
||||
}
|
||||
finally {
|
||||
activeTask.taskPriority = originalPriority;
|
||||
|
@ -652,7 +652,7 @@ public class AutoAnalysisManager implements DomainObjectListener, DomainObjectCl
|
|||
// Thinking was that if some analysis causes disassembly to occur,
|
||||
// then that disassembly and it's analysis will keep other analysis out of trouble.
|
||||
// However for single threaded, this might not be worthwhile in the long run.
|
||||
yield(activeTask.taskPriority, monitor);
|
||||
this.yield(activeTask.taskPriority, monitor);
|
||||
}
|
||||
else if (analysisThread != null || !isEnabled) {
|
||||
// this could be a sub-thread of a task, don't yield, or flush domain objects
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue