I fixed this problem. Just in case this is helpful to others. It seems syscall emulation config file (se.py) can receive a file containing necessary environment variables for the guest process (--env option). So, I added the LD_LIBRARY_PATH environment variable and the guest process' loader was able to pick up the shared library just like I wanted.
Kudos to the developers for making good progress on this extremely useful feature. - Kanad On Wed, Mar 1, 2017 at 9:24 PM, Kanad Sinha <[email protected]> wrote: > > Hi, > > I know the FAQ says shared libraries are not supported in the syscall > emulation mode. However, the slides at http://www.gem5.org/wiki/ > images/0/0c/2015_ws_08_dynamic-linker.pdf seem to indicate that > preliminary fixes are being integrated. > > I am running gem5 with Linux/x86_64 host and target. I tried running a > basic program that uses a custom compiled shared library (whose path I > added with LD_LIBRARY_PATH environment variable). But execution failed with > gem5 exiting with the following error message which seems to be coming from > the ld.so being loaded for the target program (but I could be wrong): > > error while loading shared libraries: libclang_rt.asan-x86_64.so: cannot > open shared object file: No such file or directory > > Is there any way to make this work? I'm fine with writing simple > modifications to the gem5's loader module too if necessary. Any help is > appreciated. > > Thanks in advance, > Kanad >
_______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
