Frama-C-discuss mailing list archives
This page gathers the archives of the old Frama-C-discuss archives, that was hosted by Inria's gforge before its demise at the end of 2020. To search for mails newer than September 2020, please visit the page of the new mailing list on Renater.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Frama-c-discuss] problem about initial values for pointer type
- Subject: [Frama-c-discuss] problem about initial values for pointer type
- From: kevin09fjw at gmail.com (kevin fu)
- Date: Mon, 14 Mar 2011 11:55:30 +0800
Hello, I've been told a pointer type is assumed to point at the beginning of an array of two elements. And all remaining cells are made to contain a non-deterministic superposition of the first ones. but, when I define an global array ----- int *(array[5]) ------ frama-c tells me that the array is initialed to array[0..4] {0; }, not something like array[0] {{&NULL, &s_b_0_t}} which i think it should be. Can somebody explain this problem ? thank u. kevin -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gforge.inria.fr/pipermail/frama-c-discuss/attachments/20110314/539f22de/attachment.htm>
- Follow-Ups:
- [Frama-c-discuss] problem about initial values for pointer type
- From: jens.gerlach at first.fraunhofer.de (Jens Gerlach)
- [Frama-c-discuss] problem about initial values for pointer type
- From: pascal.cuoq at gmail.com (Pascal Cuoq)
- [Frama-c-discuss] problem about initial values for pointer type
- Prev by Date: [Frama-c-discuss] embedded loops
- Next by Date: [Frama-c-discuss] problem about initial values for pointer type
- Previous by thread: [Frama-c-discuss] embedded loops
- Next by thread: [Frama-c-discuss] problem about initial values for pointer type
- Index(es):