I probably will end up looking for the source and re-building it as a static
lib.

As for the hard reset, yes it was a HARD reset.  Basically, the Kyocera 6035
that I'm testing on (running OS 3.5.2) freezes then the screen blanks out.
Once I press the reset button on the back, the device does a hard reset.  No
debugging/logging info at all that way.  Strange thing is that the same test
cases run fine without problems on other devices, including Samsung I300.

I suspect memory allocation somewhere in the ZLib source may be the problem.
The smaller data sets decompress fine on both devices, but the larger (>
16KB) causes problems on the 6035 and not the I300...

Y.


"Scott Johnson" <[EMAIL PROTECTED]> wrote in message
news:95441@palm-dev-forum...
>
> From: Young S. Cho [mailto:[EMAIL PROTECTED]]
> > The problem I am currently having with 1.1.3 of syszlib.prc is if
> > the buffer to be inflated (decompressed) is larger than about 16KB,
> > the call to inflateInit2() (macro to ZLibinflateinit2()) hangs the
device.
>
> As you can see, it's hard to debug a 3rd party shared library if you don't
> have the source code.  If the shared library source isn't available, then
> consider building it as a static library instead so you can debug.
(Search
> the archive for that topic.)
>
> > Even worst, sometimes the device does a hard reset.
>
> Do you really mean a HARD reset (total wipeout) or a regular soft reset?
I
> once encountered an apparently software-induced hard reset but was never
> able to track down the cause.  It was one of the weirdest things I've
seen.
>
> -slj-
>
>
>



-- 
For information on using the Palm Developer Forums, or to unsubscribe, please see 
http://www.palmos.com/dev/support/forums/

Reply via email to