Every time I start my App with the latest 3.5 Debug Rom using POSE 3.0a6, I get a Bus
Error in my application. I have been able to isolate it to a call I make to
WinSetClip. The only parameter that this functions takes is a pointer to a Rectangle
type. Now here is the weird part I get this
3, 2000 11:53 AM
To: Palm Developer Forum
Subject: 3.5 Debug ROM
Every time I start my App with the latest 3.5 Debug Rom using POSE 3.0a6, I get a Bus
Error in my application. I have been able to isolate it to a call I make to
WinSetClip. The only parameter that this functions takes is a po
I have a strange problem with the debug version of the 3.5 ROM and am trying
to determine where it comes from.
The problem: WinScreenMode() crashes in WinRGBToIndex() when called with
winScreenModeSet (even with the default settings). After some exploration,
it appeared that WinRGBToIndex() is a
It'd be really nice if there was documentation for all the errors that
pop out of the debug ROMs. My particular issue is the those
generated from within Field.c during Gremlins. A further gripe is
that the "field.c" doesn't display the number of the field object
and you aren't necessarily sure w
Florent,
0x8000 jogged my memory and a search turned up the email of Bob Ebert in January
that seems relevant to your situation. It
follows.
Keith Wolcott
Subject:
Re: Using UI Color Table functions
Date:
Tue, 25 Jan 2000 18:14:46 +0100
From:
Bob E
on 27/04/00 13:52, Keith Wolcott at [EMAIL PROTECTED] wrote:
> Florent,
>
> 0x8000 jogged my memory and a search turned up the email of Bob Ebert in
> January that seems relevant to your situation. It
> follows.
Keith,
Thank you very much! After a long pass of disassembling and step-traci
Hey Palm Folks,
According to the docs, if you try to DmSetDatabaseInfo and give it a
database name that already exists, the function should return
dmErrAlreadyExists. In the release color ROM, this works as advertised.
However, on the debug color ROM, it crashes with:
DataMgr.c, Line: 9014, Bad
Stringer <[EMAIL PROTECTED]> writes:
> Our new confusing error message from a Gremlin run is
> "Invalid Word Wrapping Info" This occurred one place in a
> Gremlin run, and since it is non-fatal we clicked [Continue] and it
> continued on without reoccuring (so far for another 400,000 events
I've seen some discussion about OS 3.5 debug rom will do memory leak
detection, so I did the following test:
I'm using CodeWarrior 5 (with update patch #2).
I let CodeWarrior built a default C++ Starter app, compile it and
loaded it into POSE 3.05a with the dr4 OS 3.5 EZ debug rom an
>According to the docs, if you try to DmSetDatabaseInfo and give it a
>database name that already exists, the function should return
>dmErrAlreadyExists. In the release color ROM, this works as advertised.
>
>However, on the debug color ROM, it crashes...
Yup, it is a bug. Uninitialized variabl
as anyone else noticed the Heap utility commands don't work
correctly with 3.5 Debug ROM? Whenever I try it, I get the following
errors:
#ERROR: Invalid flags field in heap header
#ERROR: Invalid size field in heap header
The HL 0 command shows 1 heap with flags set to 2000. But no
"John Leung" <[EMAIL PROTECTED]> wrote in message news:8253@palm-dev-forum...
>
> I've seen some discussion about OS 3.5 debug rom will do memory leak
> detection, so I did the following test:
>
> I'm using CodeWarrior 5 (with update patch #2).
> I let
>it and then tap on the App "button" to get back to the icon, and I get
>SystemMgr.c Line: 4384, Possible memory leak error message.
I think this will be covered by fourth item at
http://www.palm.com/devzone/docs/palmos35issues.html - and I do recommend
reading all of those things as a FAQ on sw
owners
of CWR5 to CWR6?
Thanks,
Jason
- Original Message -
From: "David Fedor" <[EMAIL PROTECTED]>
To: "Palm Developer Forum" <[EMAIL PROTECTED]>
Sent: Thursday, April 13, 2000 7:27 PM
Subject: Re: Memory leak detection in OS 3.5 debug rom
> >it and th
Thanks. The Starter App is missing a FrmCloseAllForms() call in their
AppStop event. Once it is added the problem disappear.
On Thu, 13 Apr 2000 18:27:18 -0700, David Fedor <[EMAIL PROTECTED]>
wrote:
>
>>it and then tap on the App "button" to get back to the icon, and I get
>>SystemMgr.c Lin
"OBrien, Dan" <[EMAIL PROTECTED]> wrote in message
news:14122@palm-dev-forum...
>
> as anyone else noticed the Heap utility commands don't work
> correctly with 3.5 Debug ROM? Whenever I try it, I get the following
> errors:
>
> #ERROR: Invalid flags field
-
From: "Ben Combee" <[EMAIL PROTECTED]>
Newsgroups: palm-dev-forum
To: "Palm Developer Forum" <[EMAIL PROTECTED]>
Sent: Tuesday, June 13, 2000 10:58 AM
Subject: Re: Console Window errors with 3.5 Debug ROM & CW
> "OBrien, Dan" <[EMAIL PROT
Is this problem of the screen not being refreshed (b/w debug rom),
when a form is popped up over a form that has WinDraw lines and
rectangles, etc., going to be fixed (or is it already), in the debug
ROMs?
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
h
At 9:12 PM -0700 2000/05/18, Mike Davis wrote:
>Is this problem of the screen not being refreshed (b/w debug rom),
>when a form is popped up over a form that has WinDraw lines and
>rectangles, etc., going to be fixed (or is it already), in the debug
>ROMs?
If I understand correctly, you're saying
> At 9:12 PM -0700 2000/05/18, Mike Davis wrote:
> >Is this problem of the screen not being refreshed (b/w debug rom),
> >when a form is popped up over a form that has WinDraw lines and
> >rectangles, etc., going to be fixed (or is it already), in the debug
> >ROMs?
>
> If I understand correctly,
At 09:12 PM 5/18/2000, Mike Davis wrote:
>Is this problem of the screen not being refreshed (b/w debug rom),
>when a form is popped up over a form that has WinDraw lines and
>rectangles, etc., going to be fixed (or is it already), in the debug
>ROMs?
This is intentional. In low memory situations,
> At 09:12 PM 5/18/2000, Mike Davis wrote:
> >Is this problem of the screen not being refreshed (b/w debug rom),
> >when a form is popped up over a form that has WinDraw lines and
> >rectangles, etc., going to be fixed (or is it already), in the debug
> >ROMs?
>
> This is intentional. In low memo
At 12:24 PM 5/19/2000, Mike Davis wrote:
>Why does it work differently on Color Debug ROMs than B/W Debug ROMS?
Because the debug ROMs are always trying to expose latent bugs in applications. On a
release ROM, the bits won't be saved when memory is low, so your app needs to be able
to refresh s
: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Mike
Davis
Sent: Friday, May 19, 2000 3:00 PM
To: Palm Developer Forum
Subject: Re: Screen Refresh Problem OS 3.5 Debug Rom on B/W
> At 09:12 PM 5/18/2000, Mike Davis wrote:
> >Is this problem of the screen not being refreshed (
>> This is intentional. In low memory situations, dialogs
>sometimes can't
>> allocated enough memory to store the portion of the screen they're
>> drawn on top of. In this case, when the dialog is dismissed, the form
>> has to do its own redrawing. The debug ROMs simulate this low memory
>> con
Actually, I just thought of something else:
Store your pixel coordinates in a database or file as you go. Don't
save it as a bitmap, just save the coordinates. Use your updateEvent
handler to redraw the picture based on the coordinates. I don't know
what you are doing exactly, but in this cas
Mike Davis,
On Fri, 19 May 2000 12:24:04 -0700, you said:
>
> This is also a little difficult to manage.
Sorry if this already been stated but I am trying to figure out how to
get around this as well. For various reasons the time to draw my form
is about 1 second long. Not huge, but not the
t might be nice)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of derik
DeVecchio
Sent: Tuesday, May 23, 2000 06:42
To: Palm Developer Forum
Subject: Re: Screen Refresh Problem OS 3.5 Debug Rom on B/W
Mike Davis,
On Fri, 19 May 2000 12:24:04 -0700, you said:
>
I don't understand the problem here. Write your code to properly respond to the update
event. On a debug ROM, this code will be run to update, and it'll be slow. On a
release ROM, the bits will almost always be saved and they'll be used to restore the
screen, so you won't get an update event, a
ntinues to occur. This
error only occurs in 3.5 debug rom, but not in 3.1 debug rom. How can this
error occur if I don't even create a database?
Jeff Ayers
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
> I created a new emulation session without any databases. I start the
> debugger in CodeWarrior, then I tap the Home icon to leave
> the app. The
> error still occurs even though I did not create a single
> database. How is
> this possible? How do I determine which database is open if I
> do n
. This
>error only occurs in 3.5 debug rom, but not in 3.1 debug rom. How can this
>error occur if I don't even create a database?
This probably relates to a previous creation or modification of the
database. Delete the application, so that the databases are deleted
too, then reinst
made sure
> >there were no records left. However, the error continues to occur. This
> >error only occurs in 3.5 debug rom, but not in 3.1 debug rom. How can
this
> >error occur if I don't even create a database?
>
> This probably relates to a previous creation or modific
>UIAppShell (unknown version) called SysFatalAlert with "DataMgr.c,
> > >Line: 8236, Records left locked in closed unprotected DB."
> > >
> > >So, I commented out the creation of all of my databases, and I made sure
> > >there were no records left
In article <87017@palm-dev-forum>, [EMAIL PROTECTED] says...
>
> I've got the same! And only when the CW Debugger runs. Did you find the answer
> meanwhile? Thank you,
> Cheers Werner
>
>
> Ayers Family Member schrieb:
>
> > I created a new emulation session without any databases. I start the
Its a 4.0.1. I think your suggestion is exactly the point: When I made a "PilotMain
only" app without any ressources attached the same thing happened.
Ben Combee schrieb:
> In article <87017@palm-dev-forum>, [EMAIL PROTECTED] says...
> >
> > I've got the same! And only when the CW Debugger runs.
36 matches
Mail list logo
