Hi,
I had a big piece of code that ran smoothly on gcc 3.2.2. For some reason,
I had to start using that code on a machine with GCC 4.2.1. Now, it would throw
segmentation faults (invalid free pointer etc) and abort the program. I presume
this happens because the glibc with gcc 4.2.1 is smarter than the one with gcc
3.2.2. Hence, what was missed during execution with 3.2.2 was caught in 4.2.1
While it is great to catch as many errors as possible, will it not be
better that execution support for code running on earlier versions was
provided? May be what was missed in earlier versions should be flagged as
"error with the current gcc version" or something like that and it does not
abort the program thus continuing its execution leaving the developer with the
option to fix the error later.
Since, the code size in my case is very big and the original developer is not
there to support, it is extremely difficult to resolve this issue.
Regards,
Sharad Sinha
------------------------------------------------------------
Research Scholar,
Center for High Performance Embedded Systems,
Level 3, Border X-Block,
Research Techno Plaza,
Nanyang Technological University,
Singapore-637553
------------------------------------------------------------
