CW crash with runtime error 217

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

CW crash with runtime error 217

2,302 Views
badaboom
Contributor I

Hello,

 

I can't relate this IDE crash... anyone?

 

It occurs, every now and then, when compiling the project, or 

while linking it.

 

Any ideas welcome.

 

 

 Dialog error box

 

 

 

 

 

 

 

 

 

 

 

 

 

Env.:

- Windows Vista (SP1)

- Code Warrior Dev. Studio for Coldfire, 7.1 build 14

- target: MCF52235

 

 

Crash dump= att.

Labels (1)
0 Kudos
4 Replies

555 Views
J2MEJediMaster
Specialist I

Are you running 64-bit Vista by any chance? CW for ColdFire 7.1 is compatible with 32-bit Vista.

 

---Tom

 

0 Kudos

555 Views
badaboom
Contributor I

Hi,

Nope it's a 32bit Vista business version.

 

René

 

btw I've now attached the dump file

0 Kudos

555 Views
ludov
Contributor I

Hi,

I have the same problem (error 217) with XP pro.

I use CW 7.1.1a patch, build 9, IDE 5.9.0 build 3024.

Thank you for any help

Regards

Ludo

0 Kudos

555 Views
RichTestardi
Senior Contributor II

I had a similar problem with CW 7.1.1a on XP Pro, which I tracked to an "assert" statement in my code (which is #defined and uses __LINE__) deep in the bowls of a large switch statement.  I changed that statement (using a binary search to find it) and have not had CW blow up since.  I had identical behavior on CW 6.2 as well.  I imagine each crash is likely different however and I was not able to isolate mine to a small program to submit a service request.

 

What I'd suggest for anyone with similar problems (assuming the error occurs in the compile phase) is as follows:

 

1. identify the source file that causes the error.

2. cut off the second half of the file at a function boundary with a large #if 0...#endif

3. recompile (you'll certainly get link errors now if you make it past the compile)

4. if you don't get the runtime error, make the #if 0 smaller; otherwise make it bigger.

5. once you've identified the function causing the problem, cut it up with a similar #if 0 inside it until you find the offending line.

6. change the line. :smileyhappy:

 

I hope this helps.  Again, like I said, every runtime error is likely different, so your mileage will vary.

 

-- Rich

 

0 Kudos