Hi Alan,
>Ok, I'm running the EXACT same prc on a real PIIIx and on POSE with the
>IIIx Debug ROM. My program uses a shared library, calling SysLibLoad() on
>launch and SysLibRemove() on quit. It works perfectly, returning no error
>on either device. BUT, on the real device, the 15th time I run the app it
>crashes with a chunk overlocked in SysLibLoad().
A couple possibilities here...
Is the shared library in RAM or ROM (e.g. are you using the SPT1500 tools to add it to a ROM image)?
Are you certain SysLibLoad and SysLibRemove are BOTH returning zero (no error)?
Take a peek at GSysLibTableP after you SysLibLoad and see if your library's SysLibTblEntryPtr->codeRscH is non-zero. If it's zero, SysLibInstall failed (perhaps in the library's install handler).
Also, are you running any hacks or patches to the SysLibXXX routines that could be affecting this?
Regards,
Jim Schram
3Com/Palm Computing
Partner Engineering
- Very ood problem with Shared Libraries on... Alan Pinstein
- Re: Very ood problem with Shared Lib... Jim Schram
- Re: Very ood problem with Shared Lib... Creative Digital Publishing Inc.
- Re: Very ood problem with Shared Lib... krollin
- Re: Very ood problem with Shared Lib... Alan Pinstein
- Re: Very ood problem with Shared Lib... Alan Pinstein
- RE: Very ood problem with Shared Lib... Alan Johnson
- RE: Very ood problem with Shared Lib... Creative Digital Publishing Inc.
- RE: Very ood problem with Shared Lib... krollin
- RE: Very ood problem with Shared Lib... Ade Barkah
- RE: Very ood problem with Shared Lib... Richard Hartman
- Re: Very ood problem with Shared Lib... Ion Popescu
