search for: __wrap

...to *fnb*, fnb is going to have a seperate virtualaddress from fna. But you essentially wanted fna, fnb to have the same virtual address right ? Am I misreading something that you said ? > > >> I was thinking to model this for ELF for the below functionalities :- >> >> a) __wrap >> >> For example : --wrap fn >> >> What I plan to do here is, >> >> create a undefined function fn atom >> create a defined weak atom fn >> create a alias reference to __wrap_fn which is a undefined atom. > I don’t see how those steps will achieve...

Hi Nick, This would work only if an alias is another name for the same symbol(weak symbols). If what is being aliased is another function definition, which is a non zero sized atom, aliasing will not work. I was thinking to model this for ELF for the below functionalities :- a) __wrap For example : --wrap fn What I plan to do here is, create a undefined function fn atom create a defined weak atom fn create a alias reference to __wrap_fn which is a undefined atom. b) --defsym option For example : --defsym A = B the defsym option is going to have a undefined atom for A creat...

...> If what is being aliased is another function definition, which is a non zero sized atom, aliasing will not work. That is the exact scenario I think it *will* work in. What do you think won’t work. > > I was thinking to model this for ELF for the below functionalities :- > > a) __wrap > > For example : --wrap fn > > What I plan to do here is, > > create a undefined function fn atom > create a defined weak atom fn > create a alias reference to __wrap_fn which is a undefined atom. I don’t see how those steps will achieve wrapping functionality. Say you...

On 9/13/2013 8:51 PM, Nick Kledzik wrote: >> If I alias the atom, and add a layoutBefore from fna to fnb, fnb is going to have a seperate virtualaddress from fna. > This sounds like you mean “alias” to mean take one implementation and override another implementation (that has a different name) Yes. I think ELF could treat it as a Layout-Before reference too. This way Darwin can share the

...hat has a different name). -Nick > > But you essentially wanted fna, fnb to have the same virtual address right ? > > Am I misreading something that you said ? >> >>> I was thinking to model this for ELF for the below functionalities :- >>> >>> a) __wrap >>> >>> For example : --wrap fn >>> >>> What I plan to do here is, >>> >>> create a undefined function fn atom >>> create a defined weak atom fn >>> create a alias reference to __wrap_fn which is a undefined atom. >> I...

Can an “alias” atom just be a zero sized atom with one reference of kindLayoutBefore to its target? The layout engine should then place the alias atom right before the real atom, so you wind up with two symbols at one address. -Nick On Sep 12, 2013, at 3:02 PM, Shankar Easwaran <shankare at codeaurora.org> wrote: > Hi Nick, > > In addition to what you mentioned, I think there

Hi Nick, In addition to what you mentioned, I think there needs a special *AliasReference* that need to be created which the DefinedAtom points to. Thanks Shankar Easwaran -------- Original Message -------- Subject: Re: [PATCH] Add a fallback mechanism for undefined atom. Date: Thu, 29 Aug 2013 15:15:49 -0700 From: kledzik at apple.com <kledzik at apple.com> Reply-To: