ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
when I try to use the operator new (for any type)
I get this message :
"operator new (sz=1228) at ../../../../gcc-3.4.1/libstdc++-v3/libsupc++/new_op.cc:46
46 ../../../../gcc-3.4.1/libstdc++-v3/libsupc++/new_op.cc: No such file or directory.
in ../../../../gcc-3.4.1/libstdc++-v3/libsupc++/new_op.cc
Program recieved signal SIGSEGV, Segmentation fault.
malloc_consolidate (av=0x40b2a780) at malloc.c:4391
4391 malloc.c:No such file of directory.
in malloc.c"
I'm surprised the top of the stack traceback starts somewhere in gcc instead of some line in your program's code ... but often times the same memory corruption that caused the SIGSEGV will also corrupt your stack.
I'd take the stack traceback with a grain of salt - you're probably NOT seeing the actual point of failure.
Strong suggestion:
1. Compile your app with "-g"
2. Execute it inside of gdb
3. If you know where the "new" is occurring - great. Set a breakpoint just
before you create the object.
4. Otherwise, see if you can use gdb to home in on which class/object
is failing.
5. *Definitely* double-check the constructors (*all* the constructors) of
any class object you suspect.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.