PPC Gurus - 911 - Reading a Stack Dump

[Jimm Burk]

Calling all PPC guru's -  911 - 
Can anyone shed some light on this?  The only difference in how I
compiled the files was changing from -ggdb to -gdwarf
Ouch....

Building library VPCore.a
ldppc -r -o VPCore.tmp -Map VPCore.map CritSect.o FRCB.o
TmtGetComponent.o TmtVersaPageInterfaceAccessor.o
PackageUtilityInitializer.o mallocBackEnd.o TmtNewNdeleteFrontEnd.o
TmtPoolMallocBackEnd.o TmtNewNdeleteFrontEndT.o
TmtNewDeleteObjectFactory.o ConfigurationSpecific.o HostSpecific.o
x86win32.o System.o Utility.o MemoryManagement.o  
      0 [main] ldppc 2556 handle_exceptions: Exception:
STATUS_ACCESS_VIOLATION
  15557 [main] ldppc 2556 open_stackdumpfile: Dumping stack trace to
ldppc.exe.stackdump
make: *** [VPCore.a] Error 0x18b00

Exception: STATUS_ACCESS_VIOLATION at eip=00436001
eax=0A44707E ebx=0A447080 ecx=00050012 edx=0A01D468 esi=0022F7B4
edi=0022F7D4
ebp=0022F784 esp=0022F748
program=C:\Tornado\host\x86-win32\bin\ldppc.exe
cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023
Stack trace:
Frame     Function  Args
0022F784  00436001  (0A01D468, 0022F7B4, 0A3EFB9C, 0045CFF5)
0022F7D4  0045D064  (0A3EEA80, 0A3EEAA0, 0022F824, 0045CD3E)
0022F814  0045D135  (0A3EEA80, 0A3EEAA0, 00000004, 0022F938)
0022F884  0045D33E  (0A01D468, 0A01E128, 0A3EC3C8, 00000004)
0022F8D4  00446801  (0A01D468, 0A01E128, 0A3EC3C8, 00000004)
0022FA24  00420082  (610A02B4, 0041C42A, 0022FA50, 0022FA84)
0022FA44  00420467  (0041C428, 0A01D468, 0A01E128, 00000004)
0022FA84  0041C6DC  (00478F0C, 0A029540, 0A01D468, 0A01E128)
0022FB44  0044B4D9  (0A016498, 00478F0C, 0A01D468, 0A01E128)
0022FBE4  0043E987  (0022FC94, 0A01D468, 0022FC84, 00000000)
0022FCD4  0043D1C6  (0A016498, 00478F0C, 00419B61, 004172D7)
0022FD04  0043FCE5  (0A016498, 00478F0C, 0022FD54, 0041A306)
0022FD24  0041D4ED  (00000004, 610A0368, 00000000, 610062D8)
0022FD54  0041A3BE  (00000016, 0A011768, 0A010278, 00000000)
0022FF10  61003F8E  (00000000, 00000000, 00000000, 8242E5C8)
0022FF40  61004282  (00419D00, 00000000, 82193020, 8046D460)
End of stack trace (more stack frames may be present)

Thanks to all....:)

Jimm Burk
jburk@peerless.com
Sr. Embedded Software Engineer
Peerless Systems Imaging Products
20415 72nd Ave South
Suite 400
Kent, Washington 98032
(253) 395-8890 ext. 50


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com