By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
431,991 Members | 1,737 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 431,991 IT Pros & Developers. It's quick & easy.

Memory segment error in dlopen call

P: n/a
Hello!

I'm using KAI C++ Compiler (KCC) Version 4.0d on Sparc Solaris 8 with
Sun WorkShop[tm] 6 update 2 backend (KCC compiles C++ code to C than
uses the Sun compiler to produce machine executables). When I run our
program under purify to check for memory errors, I get the following
interesting error messages:

MSE: Memory segment error:
* This is occurring while in:
_init [libnsl.so.1]
call_init [util.c]
dlmopen_intn [dlfcns.c]
dlopen []
DLOpEN [rtlib.o]
SO_per_src_lookup [nss_deffinder.c]
* Accessing a memory range that crosses a memory segment boundary.
Addressing 0xfd6f42b8 for 4 bytes ending at 0xfd6f42bc,
which is neither in the heap nor the main stack.

MSE: Memory segment error (19 times):
* This is occurring while in:
mutex_init [libthread.so.1]
_libnsl_lock_init [mt_misc.c]
_init [libnsl.so.1]
call_init [util.c]
dlmopen_intn [dlfcns.c]
dlopen []
* Accessing a memory range that crosses a memory segment boundary.
Addressing 0xfd6fe890 for 2 bytes ending at 0xfd6fe892,
which is neither in the heap nor the main stack.
I've used purify earlier but never seen this message. I'm not even sure
where is the error - in the dynamic library loader, in the libraries
itself, in the linker or in our code - and I don't have any idea how to
get rid of this message (apart from surpressing it :-). Do you have
any idea whether this is an error at all, or just purify thinks it is an
error?
Bye,NAR
Jul 19 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
On Wed, 29 Oct 2003 17:37:19 +0000 (UTC),
At*****************@ericsson.com wrote in comp.lang.c++:
Hello!

I'm using KAI C++ Compiler (KCC) Version 4.0d on Sparc Solaris 8 with
Sun WorkShop[tm] 6 update 2 backend (KCC compiles C++ code to C than
uses the Sun compiler to produce machine executables). When I run our
program under purify to check for memory errors, I get the following
interesting error messages:


[off-topic material snipped]

Ask this in a Solaris or perhaps generic UNIX programming group. The
C++ language, the topic of this group, does not define or support
anything called dlopen or memory segments. This is all platform
specific.

--
Jack Klein
Home: http://JK-Technology.Com
FAQs for
comp.lang.c http://www.eskimo.com/~scs/C-faq/top.html
comp.lang.c++ http://www.parashift.com/c++-faq-lite/
alt.comp.lang.learn.c-c++ ftp://snurse-l.org/pub/acllc-c++/faq
Jul 19 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.