then hit Windows-R and at the command prompt, type “drwtsn32 -p ProcessID” (replacing the Process ID). View > Select Columns and make sure that PID (Process Identifier) is checked. ![]() Under Windows, hit Ctrl Alt Del and go to the Task Manager and go to the Processes tab. Under Windows, it’ll be a good 400 or 500 lines from the top, and is the first occurrence of “*-> Stack Back Trace Stack Back Trace Send Signal to Process: Abort (SIGABRT). esign.Package and Preflight 0x1cc3a9b2 GetPlugIn 259458Ģ. esign.Package and Preflight 0x1ccb0267 GetPlugIn 740919ġ. Under Mac OS X, it’s the 4th or 5th paragraph of the report, starting with “Thread 0 Crashed”: Thread 0 Crashed: Dispatch queue: -threadĠ. ![]() The “stack trace” is a diagnostic that tells you what function was running in the program, and what function it was called from, what function the second function was called from, and so-on and so-forth until you get to the start first part of the program. Step 2: Find the stack trace of the running thread. Windows just keeps adding new crash logs to that file, so go to the end and search backwards for “App: ” and make sure you’ve got the correct crash (InDesign.exe). Under Windows, hit Windows-R and paste in “%AllUsersProfile%\Application Data\Microsoft\Dr Watson” and then open DRWTSN32.LOG.
0 Comments
Leave a Reply. |