search for: dlopen'ing

...eb 16, 2015 at 10:38:52PM +0100, Daniel Albuschat wrote: > > Hello there, > > > > tl;dr: > > Is it a known behaviour that using llvm-3.4 and llvm-3.6 at the same time > > in the same process (while llvm-3.6 is used from a linked shared library > > and llvm-3.4 is dlopen'ed - with a strange detail: Especially if > -rdynamic > > is used when linking the program). > > If so, is there a workaround? > > If not, can it be fixed in llvm-3.6? > > The NVIDIA proprietary driver does not use mesa at all. Also based on > your backtrace, you...

On 08/22/2015 04:27 PM, Pau Garcia i Quiles wrote: > But I guess the problem is not source-compatibility for > wine but binary-compatibility for CrossOver. In that case, I'd suggest > dlopen'ing and checking for the symbol you want. There's also issues with structure changes which won't be caught that way. libwmapro sounds like the sanest solution, short of doing the same thing with Wine.

Hello there, tl;dr: Is it a known behaviour that using llvm-3.4 and llvm-3.6 at the same time in the same process (while llvm-3.6 is used from a linked shared library and llvm-3.4 is dlopen'ed - with a strange detail: Especially if -rdynamic is used when linking the program). If so, is there a workaround? If not, can it be fixed in llvm-3.6? Long story: I am writing a program that creates binaries using llvm-3.6 and has a Qt frontend. I noticed that, when running it on Ubuntu Lin...

...ame feature is because they were different in speed, and we have to use (formerly) slow models when we know less about their run-time memory layout at compile-time or link-time. So, there was a trade-off between generality and performance. For example, if you want to use thread-local variables in a dlopen(2)'able DSO, you need to choose the slowest model. If a linker knows at link-time that a more restricted access model is applicable (e.g. if it is linking a main executable, it knows for sure that it is not creating a DSO that will be used via dlopen), the linker is allowed to rewrite instructi...

...is involved in the link (note that there is no mapping from symbol to odr table name). If two .o files contain different hash values for the same name, we have detected an ODR violation and issue a diagnostic. Finally, teach the loader (RuntimeDyld) to do verification and catch ODR violations when dlopen'ing a shared library. Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130711/cde5bf59/attachment.html>

I have a working implementation of the new xaudio2 API in my tree. Microsoft is treating it as a replacement for dsound[1], and as a result, this new API is used by lots of recent games; see Bug 26808[2] for some examples. Most games that use the xaudio2 API use a version of Microsoft's WMA codec. Wine doesn't currently have the ability to decode this audio for playback. In order for the

...d in the link (note that there is no mapping from symbol to odr table name). If two .o files contain different hash values for the same name, we have detected an ODR violation and issue a diagnostic. > > Finally, teach the loader (RuntimeDyld) to do verification and catch ODR violations when dlopen'ing a shared library. This is the right basic design, but I'm curious why you're suggesting that the payload should just be a hash instead of an arbitrary string. This isn't going to be performant enough to do unconditionally at every load no matter how much you shrink it. Also,...

...there is no mapping from symbol to odr table name). If two > .o files contain different hash values for the same name, we have detected > an ODR violation and issue a diagnostic. > > > > Finally, teach the loader (RuntimeDyld) to do verification and catch ODR > violations when dlopen'ing a shared library. > > This is the right basic design, but I'm curious why you're suggesting that > the payload should just be a hash instead of an arbitrary string. What are you suggesting goes into this string? > This isn't going to be performant enough to do un...

Hi all, and thanks for everyone's work on the 4.0 release! There's been recent discussion on the OpenSC mailing list about getting better/updated smartcard support into OpenSSH. Originating from an OpenSSH package maintainer's desire to keep dependencies to a minimum, the idea to load OpenSC dynamically popped up. Now the question is whether this is an approach that would be favored

Hi! Is this the correct place to ask about libao? I'm having a bit of trouble getting libao-0.8.4 running on OS/X 10.2.8 - libao builds fine but dlopen'ing the macosx plugin keeps failing with undefined symbols (from the CoreAudio framework it appears). Steven Schultz --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to '...

...link (note that there is no mapping from symbol to odr table name). If two .o files contain different hash values for the same name, we have detected an ODR violation and issue a diagnostic. > > > > Finally, teach the loader (RuntimeDyld) to do verification and catch ODR violations when dlopen'ing a shared library. > > This is the right basic design, but I'm curious why you're suggesting that the payload should just be a hash instead of an arbitrary string. > > What are you suggesting goes into this string? The same sorts of things that you were planning on has...

...from symbol to odr table name). If two >> .o files contain different hash values for the same name, we have detected >> an ODR violation and issue a diagnostic. >> > >> > Finally, teach the loader (RuntimeDyld) to do verification and catch >> ODR violations when dlopen'ing a shared library. >> >> This is the right basic design, but I'm curious why you're suggesting >> that the payload should just be a hash instead of an arbitrary string. > > > What are you suggesting goes into this string? > > > The same sorts of th...

...from symbol to odr table name). If two >> .o files contain different hash values for the same name, we have detected >> an ODR violation and issue a diagnostic. >> > >> > Finally, teach the loader (RuntimeDyld) to do verification and catch >> ODR violations when dlopen'ing a shared library. >> >> This is the right basic design, but I'm curious why you're suggesting >> that the payload should just be a hash instead of an arbitrary string. > > > What are you suggesting goes into this string? > > > The same sorts of th...

...te that there is no mapping from symbol to odr table name). If two .o files contain different hash values for the same name, we have detected an ODR violation and issue a diagnostic. >> > >> > Finally, teach the loader (RuntimeDyld) to do verification and catch ODR violations when dlopen'ing a shared library. >> >> This is the right basic design, but I'm curious why you're suggesting that the payload should just be a hash instead of an arbitrary string. >> >> What are you suggesting goes into this string? > > The same sorts of things tha...

...table name). If two >>> .o files contain different hash values for the same name, we have detected >>> an ODR violation and issue a diagnostic. >>> > >>> > Finally, teach the loader (RuntimeDyld) to do verification and catch >>> ODR violations when dlopen'ing a shared library. >>> >>> This is the right basic design, but I'm curious why you're suggesting >>> that the payload should just be a hash instead of an arbitrary string. >> >> >> What are you suggesting goes into this string? >> &g...

...te that there is no mapping from symbol to odr table name). If two .o files contain different hash values for the same name, we have detected an ODR violation and issue a diagnostic. >> > >> > Finally, teach the loader (RuntimeDyld) to do verification and catch ODR violations when dlopen'ing a shared library. >> >> This is the right basic design, but I'm curious why you're suggesting that the payload should just be a hash instead of an arbitrary string. >> >> What are you suggesting goes into this string? > > The same sorts of things tha...

...fferent in speed, and we have to use (formerly) slow models when we > know > > less about their run-time memory layout at compile-time or link-time. So, > > there was a trade-off between generality and performance. For example, if > > you want to use thread-local variables in a dlopen(2)'able DSO, you need > to > > choose the slowest model. If a linker knows at link-time that a more > > restricted access model is applicable (e.g. if it is linking a main > > executable, it knows for sure that it is not creating a DSO that will be > > used via dlopen...

...table name). If two >>> .o files contain different hash values for the same name, we have detected >>> an ODR violation and issue a diagnostic. >>> > >>> > Finally, teach the loader (RuntimeDyld) to do verification and catch >>> ODR violations when dlopen'ing a shared library. >>> >>> This is the right basic design, but I'm curious why you're suggesting >>> that the payload should just be a hash instead of an arbitrary string. >> >> >> What are you suggesting goes into this string? >> &g...