NO

Author Topic: POIDE crash while in debugger.  (Read 3079 times)

Innoventor

  • Guest
POIDE crash while in debugger.
« on: July 14, 2007, 03:35:15 AM »
POIDE sometimes crashes when I run the debugger: 

If I have no breakpoints set, it stops by default at WinMain.  When I continue with F5, it then gives this message:

Module 'POIDE.EXE' caused an 'Access violation' exception at address 0x00424556

Sometimes, if it doesn't crash, it will stop at a second breakpoint (that I didn't set).

The 'Debug' tab says this when stopped at the unkown breakpoint:

Loading MCD32.dll at 61DD0000
Unloading MCD32.dll
ODS: HEAP[PathwayWizardV0.exe]:
ODS: HEAP: Free Heap block 913770 modified at 913c54 after it was freed

The Call stack enters ntdll.dll and into a number of function calls in there and stops at DbgBreakPoint ()

This second problem isn't much of a nuisance, but it might be related to POIDE crashing.


Pelles C doesn't always crash when I enter the debugger, or stop at the second breakpoint, but when it does, it usually does consistenly, untill I change something.  Sometimes it'll go away with something as simple as setting a breakpoint somewhere, or when I add or change some code in my program, but not always.

I don't think it's dependent on the computer since the same project can consistently crash when run on both my computer and laptop until I find some change that fixes it.  Both use Windows XP, but other than that they're pretty different.

I'm not sure if anyone else has experienced this problem.  Anyway, I hope the info I gave helps!  And I'll be happy to answer any other questions about this problem.

-Innoventor

Offline Pelle

  • Administrator
  • Member
  • *****
  • Posts: 2266
    • http://www.smorgasbordet.com
Re: POIDE crash while in debugger.
« Reply #1 on: July 15, 2007, 01:16:22 PM »
If my records are correct, the exception at address 0x00424556 is in a function that retrieves debugging information for a (single) structure. The most likely cause of this is corrupt debugging information. A bug in this area was fixed on April 2, 2007 - for structures larger than 32767 bytes.

If this is the case for you, and you are not using POLINK version 4.50.3, the problem may already be fixed - try downloading the latest version and relink.

Otherwise:

1) I don't know what "PathwayWizardV0.exe" is, and I'm not sure if it affects POIDE, but the HEAP message can't be good at least.
2) I need an executable with debugging information, so I can have a look at my own computer (otherwise it is too much guesswork...)


/Pelle

Innoventor

  • Guest
Re: POIDE crash while in debugger.
« Reply #2 on: July 26, 2007, 04:37:35 AM »
Thanks for the reply!  I am using POLINK Version 4.50.3.  PathwayWizardV0.exe is just the tentative name for the program I'm writing.  It doesn't use large structures, but the program itself is rather large.  I'll try doing some troubleshooting tests like seeing if I can get this problem to happen when debugging small projects, then I could post that here for you to test.  Also, since I'm planning to release this program as commercially available software, I'd prefer to not have it open-source. 

In general, I am very happy with PellesC.  I've been using it for over a year now, and it's easlily the best C compiler I've tried!  I'm also very thankful that it's free.  That helps a lot now, and I plan to donate money to you when I get my company established, as a way of thanking you.

Offline Stefan Pendl

  • Global Moderator
  • Member
  • *****
  • Posts: 582
    • Homepage
Re: POIDE crash while in debugger.
« Reply #3 on: July 26, 2007, 08:31:54 AM »
Also, since I'm planning to release this program as commercially available software, I'd prefer to not have it open-source. 
No need to post the program on the forum, send it to Pelle via private mail.
---
Stefan

Proud member of the UltraDefrag Development Team