Operating System - HP-UX
1829752 Members
1778 Online
109992 Solutions
New Discussion

Re: Core dump with BUS_ADRALN error

 
SOLVED
Go to solution
Dennis Handly
Acclaimed Contributor

Re: Core dump with BUS_ADRALN error

>+DSmontecito +FPD -Wl,+pi,1M -Wl,+pd,1M -Wl,+mergeseg -Wl,+s +Z +w1 -D_REENTRANT
>What are these flags good for?

Most of these options are for performance. Some come from +faster: +FPD -Wl,+pi,1M -Wl,+pd,1M -Wl,+mergeseg

They basically say flush FP denorms to zero, use large pages for code and data. And merge the data areas of shlibs.
+DSmontecito schedules for that machine.

+Z is ignored.
+w1 should be replaced by +wlint or +w.

Correctness issues:
-Wl,+s this enables LD_LIBRARY_PATH.
-D_REENTRANT probably should add -mt.
K!rn Kumr
Frequent Advisor

Re: Core dump with BUS_ADRALN error

"/opt/aCC/include/memory", line 493: error #2020: identifier "bad_alloc" is undefined
RWSTD_THROW_NO_MSG(tmp == 0, bad_alloc);

I get this error when i try to compile my code. I have included the path /opt/aCC/include where it finds all includes. In file memory there is an include new in the ifndef. And thats not being picked up in my case. how to solve this.
K!rn Kumr
Frequent Advisor

Re: Core dump with BUS_ADRALN error

Following is the code in library memory. And bad_alloc is defined in new which in included in below fashion. I believe it is picking new.h instead of new. But how do i make it pick new. How to check if "RWSTD_NO_NEW_HEADER" is defined.

#ifndef RWSTD_NO_NEW_HEADER
#include
#include
#include
#include
#else
#include
#include
#include
#include
Dennis Handly
Acclaimed Contributor

Re: Core dump with BUS_ADRALN error

>I have included the path /opt/aCC/include where it finds all includes.

Never ever add the default aC++ include paths or shlibs, let the driver do this. This path is NOT valid for -AA!