Re: CE 5.0 crashes in editor during "intellisense"
- From: "John Berting" <berting@xxxxxxxxxxxx>
- Date: Fri, 15 Feb 2008 20:42:55 -0500
Michel ---
I can't even count the number of times I've done that with my own
applications, and I would never have thought about doing that with somebody
else's...!!! Nice hack, and I'm embarrassed I didn't think of it on my own.
(I even had the debugger open and didn't think of it...) Thanks very much,
I think that makes my "best suggestion of the month that I should have
thought of myself" award for February.
My heart usually sinks if I've been very focused and forgotten to save when
one of these things happen. Usually not an hour's worth of work, but
something that won't be rewritten the same way when I do it over. Now at
least I won't feel quite as stupid...
Thanks for the awesome suggestion.
--- John Berting
"Michel Verhagen (eMVP)" <michel@xxxxxxxxxx> wrote in message
news:eGqzKUBcIHA.288@xxxxxxxxxxxxxxxxxxxxxxx
<HACKHACK>
What I always do when this happens is answer "yes" to the question if I
want to debug PB. Then VS attaches as a debugger to PB and opens a disasm
window with the PC at the point of the crash (usually an AV xcept). I then
move the PC to the end of the current function (of course remember to set
it at the point where the stack is restored) and let it run again. Then PB
just continues and you can at least save your file and you don't loose any
data.
</HACKHACK>
Saved me a couple of hours work at more than 1 occasion!
Good luck,
Michel Verhagen, eMVP
Check out my blog: http://GuruCE.com/blog
GuruCE
http://GuruCE.com
Consultancy, training and development services.
John Berting wrote:
Dean ---
You're right, I have seen it on simpler projects too... On smaller
projects it has always been a more infrequent and random crash that I
never bothered to track down because it always worked correctly on the
next run. This is the first time the IDE became completely
non-functional on a repeatable basis.
In fact, I seem to remember that if you install the raw CE 5.0
distribution from CD without any patches that the text editor keels over
if you look at it cross-eyed. That was why I was hopeful that one of the
patches I hadn't applied might be a fix for the problem. Guess not...
The problem I was seeing before it started reliably crashing was an
occasional "pregnant pause" whenever I typed a left parenthesis. The
system would hang for a couple of seconds (longer sometimes), enough to
let me type 5 or 6 keystrokes that weren't being echoed. It bothered me
the most while I was typing an "if" statement. I'd already have the
curly-brace entered and the left paren hadn't been echoed yet. Very
disorienting.
Hopefully MS will have some sort of answer... Even if it's just "oops,
sorry"...
--- John Berting
"Dean Ramsier" <ramsiernospam@xxxxxxxxxx> wrote in message
news:eU3GUW$bIHA.4332@xxxxxxxxxxxxxxxxxxxxxxx
If I'm not mistaken, this is a problem that has always been here. It
isn't limited to the size of your project, it'll happen on HelloWorld.
If I recall correctly, you have to be careful to not leave those
parenthesis open too long or the crash will occur. Makes it not very
useful...
--
Dean Ramsier - eMVP
BSQUARE Corporation
"John Berting" <xxxbertingxxx@xxxxxxxxxxxx> wrote in message
news:OZS4D39bIHA.484@xxxxxxxxxxxxxxxxxxxxxxx
This is a pretty specific problem. My WinCE 5.0 application has grown
in complexity enough that the "intellisesne" feature of the IDE text
editor now has a nervous breakdown when it tries to parse my source
files...
Specifically, FEACP.DLL throws a "stack overflow" exception whenever I
type a left parenthesis in certain source files. The top-level error
is an attempted read of a null pointer as a result of the overflow. I
just installed all of the posted updates up to December 2007, and this
problem is obviously one that was never fixed. My FEACP.DLL is build
13.10.3077.0.
I have noticed that there are other 13.10 generation DLLs with higher
build numbers (3100 to 3200) that were used with some of the VS.NET
products and service packs. Can anyone from MS tell me if this bug was
addressed in any of the subsequent builds? (And where I can get them
from, since our VS.NET installations have V14 DLLs, that I suspect
would be incompatible.)
For right now I have turned off the intellisense features of the
editor, but to be very honest I've grown fond of that little popup that
lists the passed parameters for the function call I'm typing...
If anyone has any hints about how to not have a stack overflow crash in
the Platform Builder IDE I'd love to hear about it. Thanks.
--- John Berting
.
- References:
- CE 5.0 crashes in editor during "intellisense"
- From: John Berting
- Re: CE 5.0 crashes in editor during "intellisense"
- From: Dean Ramsier
- Re: CE 5.0 crashes in editor during "intellisense"
- From: John Berting
- Re: CE 5.0 crashes in editor during "intellisense"
- From: Michel Verhagen (eMVP)
- CE 5.0 crashes in editor during "intellisense"
- Prev by Date: Re: Using the new "System Event Log"
- Next by Date: Re: Console Application on windows CE 5.0
- Previous by thread: Re: CE 5.0 crashes in editor during "intellisense"
- Next by thread: pWriteRegistryToOEM & pReadRegistryFromOEM in CE6
- Index(es):
Relevant Pages
|
