From: Caleb <[email protected]> Date: Saturday, September 28, 2013 4:52 PM To: Nick Alexander <[email protected]> Cc: <[email protected]> Subject: Re: Including an additional shared library
>> <snip> >> To help with debugging the linker, set the environment variable (on you >> device) MOZ_DEBUG_LINKER=1, as per: >> >> http://mxr.mozilla.org/mozilla-central/source/mozglue/linker/Logging.h#55 >> <http://mxr.mozilla.org/mozilla-central/source/mozglue/linker/Logging.h#55> >> >> There are some tricky aspects to library loading in our configuration; let me >> know how you get on. > > I've attached a log file with the messages that are logged when I attempt a > connection to my testbed environment. I'm pretty sure the "Caught segmentation > fault" messages are unrelated, because a bunch of the same messages are logged > before I attempt to establish a connection. I left them intact in case they > have some meaning that I'm missing. > > My interpretation of the output is that ElfLoader class can't locate the > libgssapi.so file. Looking at the source > (http://mxr.mozilla.org/mozilla-central/source/mozglue/linker/ElfLoader.cpp#29 > 6), I'd guess /data/data/org.mozilla.fennec_caleb/lib isn't a valid search > path. I haven't found a way to manually modify the search path, though, so I > can't test my hypothesis. Any ideas? I am trying to do something that is somewhat similar. I am trying to get libpcsclite and libcoolkey bundled along with pcscd in order to talk to a smart card. I have had success in getting the lib files and service included in the apk and modified BrowserApp.java to start the pcscd service (this is just temporary I am hoping to roll all of this into an extension once it's working). I have been able to add the smart card with the NSS database used by the browser as well, so the libraries are all functional when invoked through modutil and certutil. I initially ran into a failure to load similar to what is described above but got past that by specifying the full path to the so file at load time. At this point, the so is loaded and invoked (at least enough so that I see a PIN prompt for the card). After the PIN prompt, I hit a crash. In the log I also see lots of "Caught segmentation fault" messages that do not appear to cause a problem, until this final one: D GeckoLinker: Caught segmentation fault @0xdeadbaad I've been trying to figure out how to log a call stack at that point. > >> Also, in my experience, integrating the latest release of a library is a >> much smoother process if the recipe for building the library is included >> in the main build routine. This is something of a security concern as >> well, because a smoother integration process means security-related >> fixes are more likely to get integrated promptly. > >> Roger this as well. >> >> We can take this up with the broader community in the future. > > Sure thing--my current priority is getting the basic functionality working. :) > > _______________________________________________ mobile-firefox-dev mailing > list [email protected] > https://mail.mozilla.org/listinfo/mobile-firefox-dev
_______________________________________________ mobile-firefox-dev mailing list [email protected] https://mail.mozilla.org/listinfo/mobile-firefox-dev
