We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
Hi,
I'm writing a C++ program that will run on an STM3210E-EVAL board and I'm having some problems using STL vectors. I'm wondering what I'm doing wrong. (Or if STL vectors are even supported.)
Here's a snippet:
#include <vector> . . . void func() { std::vector<int> temp; temp.push_back(5); }
When I try to run the debugger on my target, I end up somewhere in assembly land and never reach the beginning of my main() function. (I am not familiar with assembly so, I'm not quite sure where I am or how I got there.)
When I run in simulator mode, everything works fine. (I end up at the beginning of my main() function like I expect.)
It appears that whenever I make any command that increases the size of my vector, I get the same result. If I never insert into my vector or resize it, then the debugger brings me to the beginning of main(), like I'd expect.
The last time I saw something like this was when my heap was 0 and I tried newing something on the heap. If anyone has any ideas, I'd be grateful.
I'm required to write my program in C++ and though I'm not required to use vectors, I really would like to. (I also have a few ideas of how to implement it differently if it turns out that vectors don't work.)
Thanks,
Using STL will bring in a lot of extra code. C++ can give a smaller program growth when you add one more feature to an existing program. But it tends to produce very large "hello world" applications compared to C programs. And huge "hello world" applications compared to assembler applications.
It does not sound good that your program does not include your main().
Oh, main() is still there. It just decided to remove some other portions of my code... (Not sure which parts though...)
Using STL will bring in a lot of extra code.
I absolutely agree. I've got space for the time being. Hopefully, the reusability of the code is worth the code bloat.
http://www.keil.com/support/man/docs/armlib/armlib_cihdfbhe.htm
Are you doing something I/O related in your startup file?
Anybody - is it "normal" for IO functions to be invoked upon initialization of the C runtime library used by the RealView compiler? If not, what on earth is happening here?!