Hi all,
There are currently problems with the current MW debugger and POSE 2.1d28,
which normally shows itself as the second problem. We (Palm and Metrowerks)
are both looking into it right now, but at present we don't have a solution
as yet. If possible I would suggest using POSE 2.1d26 for the moment until
this problem gets ironed out. I realize this solution is not ideal and I
apologize for any inconvenience this may cause.
Rgds,
JK Lam
Metrowerks Technical Support
----- Original Message -----
From: Christian Vandendorpe <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, June 17, 1999 12:39 PM
Subject: Re: POSE 2.1d28 lockup problem
> I have been experiencing strange problems with POSE 2.1d28 as well, it
> involves POSE hanging but has nothing to do with gremlins. If I leave POSE
> running in the background and then come back to it after an hour or two it
> is hung. I can still access the menus via a right-click but none of the
> palm buttons respond. Only solution is to quit and restart it. I have
> noticed that if I go through a debug cycle with CW debugger, many times
> POSE is hung after the debugging is over. I never had any problems with
> POSE, where can I get 2.1d26??
>
> Chris
>
>
> At 11:27 AM 6/17/99 -0500, you wrote:
> >I'm running into a strange situation. Using POSE 2.1d28 on Win95, CW 5.1
> >with patch, when I run gremlins, sooner or later the gremlin count stops
> >incrementing. POSE is semi-frozen, meaning that none of the Palm
> >functionality works but I can access the POSE menus via right clicking. I
> >can stop/start gremlins via the dialog box but nothing happens. If my app
> >has killed POSE in some manner, it would be nice to find it. I can't
think
> >of anything I would be doing that could pull the rug out from under POSE.
I
> >have fixed some bugs via using POSE 2.1d24 but can't explain the lockups
> >under 2.1d28.
> >
> >BTW, I am still experiencing the situation of during the compile, run,
debug
> >cycle, the CW debugger window does not display, POSE is locked, and I
have
> >to kill the debugger from the menu, close down CW and POSE then start
them
> >again in order to continue. The max number of times I can run debugging
> >sessions in a row is 4 before this occurs. Is anyone else still
> >experiencing?
> >
> >Thanks.
> >--Alan
> >
>
> ---
> Christian Vandendorpe ([EMAIL PROTECTED])
> http://www.zorglub.com
>
