Analysis of Call Object Crash - CallStacks (for above .dmp file)
We start by looking at the thread which contains jdeLogCallStack() function as this is the thread which encountered the error first.
From that point in the callstack please traverse down to the business function which is being invoked by looking top to bottom until you find jdeCallobjectV2() In this example, it is DetermineIfBlanketPOExists.
Check for any MEM SAR fix for this Bsfn and note the ESU.
As mentioned earlier - this may not be the root cause of the crash - it could be a victim of some other thread/ bsfn corrupting the memory before it.
Search for other active business functions in other threads for this callobject. Use the same methodology:
Evaluate from top to bottom.
Keep going until you hit the jdeCallObjectV2() Function.
The BusinessFunction right above jdeCallObjectV2() is the one closest the point in time when the crash occurred.
In our example these are:
No running BSFN in Thread1. Main thread is waiting for work.
EditSystemExistenceF99410 in Thread2.
No running BSFN in Thread3. Thread is waiting for work.
EditSystemExistenceF99410 in Thread4.
DetermineifBlanketPOExists in Thread 5 (This is the thread which initiated the crash).
EditSystemExistenceF99410 in Thread6.
So from this example, we see that the thread running DetermineifBlanketPOExists initiated a process crash, but there were three instances of EditSystemExistenceF99410 running in three other threads. Therefore, one should look for bugs containing fixes for these two business functions and apply those ESUs.
It's also possible that the corruption in this crashed CallObject was caused by some other business function which was no longer running at the point of crash. Therefore, it is helpful to analyze a few CallObject crash .dmp files so that an overall pattern of suspect business functions appear and we can then use these to select a narrow range of ESUs to apply. This method of analysis is quite focused and presents one with a given set of fixes to apply rather than choose wide swathes of possible ESUs.