[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mesa3d-users
Subject:    Re: [Mesa-users] dlsym
From:       Daniel Melo Jorge da Cunha <dmjcunha () gmail ! com>
Date:       2014-02-01 16:37:02
Message-ID: CANbfre4OuKCNhGKuvPXNE5JC+eO7m6YW1=VncCD80+urHSmKpQ () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


2014-02-01 Daniel Melo Jorge da Cunha <dmjcunha@gmail.com>:

> Hi, I use fedora and X and I am in .../src/mesa/main/dlopen.h.
> Is dlsym really calling _mesa_dlsym(...)?
>
> First, I found no #define statement for __blrts in the entire mesa's tree.
>
> I think in my case (fedora and X) it goes to #elif defined(HAVE_DLOPEN),
> which is strange because u.v = dlsym(handle, fname) would enter in an
> infinite recursion if dlsym is _mesa_dlsym.
>
> I also found strange the fact that the parameters void *handle and const
> char *fname are not attributed to any variable in _mesa_dlsym(..)
>
> Because of that I don't see the purpose of
> ../src/gallium/auxiliary/util/u_dl.c util_dl_get_proc_address(...) function
> when it calls:
>
> return (util_dl_proc) pointer_to_func(dlsym((void *)library, procname));
>
> If the answer is in the assembly code generated by scripts someone could
> please give me a basic idea of what's going on because I have no knowledge
> of assembly and scripts.
>
> Thanks in advance.
>

Please, disregard this question. I hate this. I spent a long time trying to
understand and when I give up and ask for help, I can understand. So,
please disregard this question. I have others more complicated :)

[Attachment #5 (text/html)]

<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">2014-02-01 Daniel \
Melo Jorge da Cunha <span dir="ltr">&lt;<a href="mailto:dmjcunha@gmail.com" \
target="_blank">dmjcunha@gmail.com</a>&gt;</span>:<br><blockquote class="gmail_quote" \
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div \
dir="ltr"><div><div><div><div><div><div>Hi, I use fedora and X and I am in \
.../src/mesa/main/dlopen.h.<br></div>Is dlsym really calling \
_mesa_dlsym(...)?<br><br></div>First, I found no #define statement for __blrts in the \
entire mesa&#39;s tree.<br>

<br></div>I think in my case (fedora and X) it goes to #elif defined(HAVE_DLOPEN), \
which is strange because u.v = dlsym(handle, fname) would enter in an infinite \
recursion if dlsym is _mesa_dlsym.<br><br></div>I also found strange the fact that \
the parameters void *handle and const char *fname are not attributed to any variable \
in _mesa_dlsym(..)<br>

<br></div><div>Because of that I don&#39;t see the purpose of \
../src/gallium/auxiliary/util/u_dl.c util_dl_get_proc_address(...) function when it \
calls:<br><br>return (util_dl_proc) pointer_to_func(dlsym((void *)library, \
procname));<br>

</div><div><br></div>If the answer is in the assembly code generated by scripts \
someone could please give me a basic idea of what&#39;s going on because I have no \
knowledge of assembly and scripts.<br><br></div>Thanks in advance.<br>

</div>
</blockquote></div><br></div><div class="gmail_extra">Please, disregard this \
question. I hate this. I spent a long time trying to understand and when I give up \
and ask for help, I can understand. So, please disregard this question. I have others \
more complicated :)<br> </div></div>



_______________________________________________
mesa-users mailing list
mesa-users@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-users


[prev in list] [next in list] [prev in thread] [next in thread]