This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug ada/32234] [Ada] Default pointer initialization not occuring - due to the use of <>
- From: "baldrick at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 8 Jun 2007 18:46:54 -0000
- Subject: [Bug ada/32234] [Ada] Default pointer initialization not occuring - due to the use of <>
- References: <bug-32234-13647@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #11 from baldrick at gcc dot gnu dot org 2007-06-08 18:46 -------
> Thank you both for your explanation to a newbie having no experience with
> valgrind tool. I have come up with a simpler version which similar to
> Laurent's. Here it goes.
Thanks - but how is it supposed to work? You didn't dirty memory
like Laurent did (new+free), so Item will contain null and you'll
get a constraint error in Item.all'Valid. [If you are very lucky
Item will contain a non-zero value and you will get a segmentation
fault]. I just ran your example a few thousand times and never
saw anything besides constraint error.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32234