dcsimg
Login | Register   
RSS Feed
Download our iPhone app
TODAY'S HEADLINES  |   ARTICLE ARCHIVE  |   FORUMS  |   TIP BANK
Browse DevX
Sign up for e-mail newsletters from DevX

By submitting your information, you agree that devx.com may send you DevX offers via email, phone and text message, as well as email offers about other products and services that DevX believes may be of interest to you. DevX will process your information in accordance with the Quinstreet Privacy Policy.


Tip of the Day
Language: C++
Expertise: Beginner
Oct 29, 1998

WEBINAR:

On-Demand

Application Security Testing: An Integral Part of DevOps


Static initialization and free store

Question:
Is it valid to attempt to allocate (via 'new()') dynamic memory prior to 'main()'? I am working on software that has static *'s to class objects, and through some rather nasty macro expansion, these object ptrs attempt to instantiate themselves via the 'new()' operator. I am working on Irix 6.2 and the software used to work fine under the Irix O32 ABI. When we ported to the N32 ABI, it started seg faulting and Purify reports IPR/IPW fatal errors throughout these static initializers.

Answer:
If I understand, you are declaring data outside of any functions something like this:

CData* pData = new CData[100];
In my experience (mostly in Visual C++ for Intel), this works fine. The data is, in fact, allocated, and this line executes before the call to main. I have never run across problems with this. If you are having trouble, it may be specific to the platform you're porting to.
DevX Pro
 
Comment and Contribute

 

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

 

Sitemap
×
We have made updates to our Privacy Policy to reflect the implementation of the General Data Protection Regulation.
Thanks for your registration, follow us on our social networks to keep up-to-date