* dlsym() on C++ symbols
@ 2000-07-05 18:25 Munagala V. S. Ramanath
2000-07-05 20:39 ` Alexandre Oliva
0 siblings, 1 reply; 2+ messages in thread
From: Munagala V. S. Ramanath @ 2000-07-05 18:25 UTC (permalink / raw)
To: gcc-help
Hi,
After some experimentation (gcc-2.95.2, sparc-sun-solaris2.7) it seems
that I need to supply the mangled name of symbols to dlsym(). This
presents a problem because I would have to manually create the mangled
name for each symbol I need from a dynamically loaded C++ library.
Is there an easier way to do this ? I looked in the GCC docs as well
as the dlopen/dlsym man pages but saw no discussion of this issue. Any
pointers would be much appreciated. Thanks.
Ram
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: dlsym() on C++ symbols
2000-07-05 18:25 dlsym() on C++ symbols Munagala V. S. Ramanath
@ 2000-07-05 20:39 ` Alexandre Oliva
0 siblings, 0 replies; 2+ messages in thread
From: Alexandre Oliva @ 2000-07-05 20:39 UTC (permalink / raw)
To: Munagala V. S. Ramanath; +Cc: gcc-help
On Jul 5, 2000, "Munagala V. S. Ramanath" <ram@netcom.com> wrote:
> After some experimentation (gcc-2.95.2, sparc-sun-solaris2.7) it seems
> that I need to supply the mangled name of symbols to dlsym().
Yup.
> Is there an easier way to do this?
Create a `map' in the shared library that maps user-specified names to
symbol addresses? Or use the name mangling/unmangling routines from
libiberty.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2000-07-05 20:39 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-07-05 18:25 dlsym() on C++ symbols Munagala V. S. Ramanath
2000-07-05 20:39 ` Alexandre Oliva
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).