Pelles C forum

Pelles C => General discussions => Topic started by: TimoVJL on April 09, 2014, 07:08:25 PM

Title: How PellesC 8 rc testings goes ?
Post by: TimoVJL on April 09, 2014, 07:08:25 PM
This far i have only debugging problems, no others.
How many are testing this release candidate ?
Title: Re: How PellesC 8 rc testings goes ?
Post by: JohnF on April 09, 2014, 08:18:51 PM
Just discovered that the debugger crashes on malloc for no apparent reason in various places. "POIDE.EXE caused an Access Violation".

An example

   #define BUFSIZE   2047
   wchar_t *szmodn = malloc(BUFSIZE * sizeof(wchar_t));

John
Title: Re: How PellesC 8 rc testings goes ?
Post by: lingo on April 10, 2014, 12:49:52 PM
On the way...
No serious problems here, so far.
Didn't use the debugger yet, because
i just begin with maturity projects.

lingo
Title: Re: How PellesC 8 rc testings goes ?
Post by: Pelle on April 12, 2014, 03:03:56 PM
One of the bug reports lead to a buffer overrun problem in the debugger, when formatting wide string literals. Fixed in v8.0 RC2.
(similar code for plain string literals, so a little too much code was copied to the wide string literal function).

Buffer overruns can cause all kinds of "unrelated" problems, and not everyone is using wide strings. I'm not saying this is to root cause of the problems, but it could be.

Title: Re: How PellesC 8 rc testings goes ?
Post by: Bitbeisser on April 14, 2014, 05:23:53 AM
Have so far only compiled and played with some of the test projects that came up on the forum and it worked ok for me so far, didn't run into the widestring issue apparently...
Hope to do some more testing next weekend, pretty busy at work right now...

Ralf
Title: Re: How PellesC 8 rc testings goes ?
Post by: JohnF on April 14, 2014, 07:37:16 AM
The crashing I saw is now gone.

John