Operating System - HP-UX
1758355 Members
2312 Online
108868 Solutions
New Discussion юеВ

a library with debugging information is working fine but without that is not working.

 
SOLVED
Go to solution
Arunvijai_4
Honored Contributor

Re: a library with debugging information is working fine but without that is not working.

Hi Ankur,

You can post this question to the following Mailing lists, you will defintely find an answer there.

http://h21007.www2.hp.com/dspp/ml/ml_MailingLists_IDX/1,1275,,00.html#24

C++ Mailing list

http://h21007.www2.hp.com/dspp/ml/ml_MailingLists_IDX/1,1275,,00.html#4

HP-UC Dev tools mailing list.

Also, Do you have PHSS_32509 installed on your system, just check that as well.

http://www2.itrc.hp.com/service/patch/patchDetail.do?BC=patch.breadcrumb.main|patch.breadcrumb.search|&patchid=PHSS_32509&context=hpux:800:11:11

-Arun

P.S Rememer to assign points.
"A ship in the harbor is safe, but that is not what ships are built for"
ankur saxena
Occasional Advisor

Re: a library with debugging information is working fine but without that is not working.

hi Arun,
i have applied the patch PSS_32509 and then built the library.
its still not working.
kindly give me another approach of solving the problem.

-Ankur
Arunvijai_4
Honored Contributor

Re: a library with debugging information is working fine but without that is not working.

Hi Anukur,

Have you posted your question to HP C++ mailing lists ? If not, do so now.. Compiler gurus from HP will answer your question right away.

-Arun
"A ship in the harbor is safe, but that is not what ships are built for"
Andrew Merritt_2
Honored Contributor

Re: a library with debugging information is working fine but without that is not working.

No definite answers, but some suggestions.

If the problem doesn't occur with symbols present, but does without, that most likely indicates a problem with the C code you're compiling. It doesn't necesarily mean a problem with the compiler. (By the way, is it C or C++ code?)

This can happen if the code is accessing locations it shouldn't, e.g. due to unitialised values. When you compile with symbols included that can hide the problem because you might land on memory locations that have sensible values in.

You should check your malloc() usage, and make sure everything is initialised before use.

Use lint, and pay attention to any warnings from the compiler, too. Use a memory checking library, or a tool such as purify (if that's still around) to make sure your only using initialised memory. (For example, one fault is to malloc some memory, free it, but still use the pointer to it later.)

Andrew