• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
same function, different mangled names
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

same function, different mangled names


  • Subject: same function, different mangled names
  • From: Stefan Werner <email@hidden>
  • Date: Wed, 3 Aug 2005 17:32:50 +0200

Hi,

why do identical C++ symbols get different mangled names? For example:
I build a dynamic library that exports these two symbols:

002f2b68 s __ZN15wxDocChildFrameD0Ev
002f2b28 s __ZN15wxDocChildFrameD1Ev

My project, built with the same headers, linking against this dylib, won't link because it's missing this symbol:

__ZN15wxDocChildFrameD1Ev

When I unmangle them with c++filt, all three of them return

wxDocChildFrame::~wxDocChildFrame()

Why are there three different mangled names for the same destructor, and more important: How do I get my program to link correctly? Is something wrong with my build settings? I'm using gcc3.3 in both cases.

Thanks for your help,
Stefan
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: same function, different mangled names
      • From: Eric Albert <email@hidden>
  • Prev by Date: At a loss with cross development
  • Next by Date: Re: At a loss with cross development
  • Previous by thread: Re: At a loss with cross development
  • Next by thread: Re: same function, different mangled names
  • Index(es):
    • Date
    • Thread