From: Curtis Cameron [EMAIL PROTECTED]
The suggestion to turn on all compiler warnings was the one that did the
trick to solve the original problem, though. ...
(snip)
... I think the compiler warning that really solved the problem was
when it found two times in MainFormHandleEvent() when I
On Jan 9, 2005, at 9:26 PM, Curtis Cameron wrote:
...I think the compiler warning that really solved the problem was
when it found two times in MainFormHandleEvent() when I simply used
return instead of return handled. I was surprised to learn that
you have to enable all warnings to see
Chris Tutty wrote:
All compilers have this sort of issue, however - the example
that always amazed me was that Visual Studio (prior to .NET)
treated an assignment within an if statement as a level four warning
and, by default, only reported up to level three (or the other
way around).
Thanks to those who offered help about my problem. I took care of the
problem of the warning by declaring s to be const char * and that
fixed the warning.
The suggestion to turn on all compiler warnings was the one that did the
trick to solve the original problem, though. Besides for having
Subject: Re: Debug app works, Release doesn't
From: Chris Tutty [EMAIL PROTECTED]
Date: Fri, 7 Jan 2005 15:23:11 +1300
From: Robert Moynihan [EMAIL PROTECTED]
(char*) s = CtlGetLabel(GetObjectPtr(ReadyButton));
... that might get rid of your error message, but might not solve the
problem
Roger Stringer wrote:
Subject: Re: Debug app works, Release doesn't
From: Chris Tutty [EMAIL PROTECTED]
Date: Fri, 7 Jan 2005 15:23:11 +1300
From: Robert Moynihan [EMAIL PROTECTED]
(char*) s = CtlGetLabel(GetObjectPtr(ReadyButton));
... that might get rid of your error message, but might
From: Roger Stringer [EMAIL PROTECTED]
From: Chris Tutty [EMAIL PROTECTED]
From: Robert Moynihan [EMAIL PROTECTED]
(char*) s = CtlGetLabel(GetObjectPtr(ReadyButton));
... that might get rid of your error message, but might not solve the
problem that you are asking about.
How on
Chris Tutty wrote:
Often this is a sign of memory corruption, unitialised
pointers, use of freed memory, etc.
Thanks for the inputs. I've checked over my code, and I use pointers minimally.
I normally declare strings as arrays (with dimensions), not just pointers, but
there is one case that
Try...
(char*) s = CtlGetLabel(GetObjectPtr(ReadyButton));
... that might get rid of your error message, but might not solve the
problem that you are asking about.
Bob.
Curtis wrote:
Chris Tutty wrote:
Often this is a sign of memory corruption, unitialised
pointers, use of freed memory, etc.
Oops, my mistake - that statement doesn't cause another value to change. Since
the Global Variables list in my debugger is off by two bytes, I mis-translated
and was looking at the wrong variable. That statement seems to work OK, but
still the question remains about the warning.
Also, is it OK
From: Robert Moynihan [EMAIL PROTECTED]
(char*) s = CtlGetLabel(GetObjectPtr(ReadyButton));
... that might get rid of your error message, but might not solve the
problem that you are asking about.
How on earth is this going to make any difference? Aside from
the questionable approach of
From: Curtis [EMAIL PROTECTED]
Chris Tutty wrote:
Often this is a sign of memory corruption, unitialised
pointers, use of freed memory, etc.
(snip) I have a string pointer declared as char *s, then use it like
this:
s = CtlGetLabel(GetObjectPtr(ReadyButton));
This has always given me
Chris Tutty wrote:
From: Robert Moynihan [EMAIL PROTECTED]
(char*) s = CtlGetLabel(GetObjectPtr(ReadyButton));
... that might get rid of your error message, but might not solve the
problem that you are asking about.
How on earth is this going to make any difference? Aside from
the
Forum
Subject: Re: Debug app works, Release doesn't
Chris Tutty wrote:
From: Robert Moynihan [EMAIL PROTECTED]
(char*) s = CtlGetLabel(GetObjectPtr(ReadyButton));
... that might get rid of your error message, but might not solve the
problem that you are asking about.
How on earth
]
Mobile 253-691-8812
-Original Message-
From: Robert Moynihan [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 06, 2005 7:14 PM
To: Palm Developer Forum
Subject: Re: Debug app works, Release doesn't
Chris Tutty wrote:
From: Robert Moynihan [EMAIL PROTECTED]
(char*) s = CtlGetLabel
From: Robert Moynihan [EMAIL PROTECTED]
Chris Tutty wrote:
How on earth is this going to make any difference? Aside from
the questionable approach of trying to eliminate a warning rather
than fix the underlying problem, how would casting a variable
defined as char * to char * change
What kind of things could cause my 68K app (developed w/ PODS 1.1,
multi-section) to run fine when compiled as Debug, but not as Release?
Thanks to others in this forum, I've carefully put all my function prototypes
in one .h file, with the annotations for which section that function is in. I
Often a problem is uninitialized variables. For example, a simple buggy program:
Char buf[20];
StrCat(buf, hello);
This piece of code sometimes work, sometimes doesn't. buf contains
undefined characters. If buf[0] happens to be 0, this code will work.
If it happens to be non-zero, it won't. It
From: Curtis [EMAIL PROTECTED]
What kind of things could cause my 68K app (developed
w/ PODS 1.1, multi-section) to run fine when compiled as
Debug, but not as Release?
Often this is a sign of memory corruption, unitialised
pointers, use of freed memory, etc. These problems can be
masked
19 matches
Mail list logo
