Building WebKit natives with debug symbols on 32 bit Linux
peter.levart at gmail.com
Wed May 28 13:47:45 UTC 2014
The idea that comes to my mind is the following: would it be possible to
cross-compile the openjfx on the 64 bit Linux using 64 bit tools, but
targeted at 32 bit Linux? What would have to be changed in build
environment to accomplish that? I imagine the environment would have to
have access to headers and development libraries of the 32 bit Linux
system - that's no problem - I would just mount the root of a 32 bit
Ubuntu to some directory, but then I would have to force all tools to
use that path instead of the running system one. And the gcc would have
to be given some cross-compiling options too, I guess...
On 05/28/2014 03:39 PM, Peter Levart wrote:
> I'm new to this list and I have searched the archives, but haven't
> found a discussion about this. If I have missed it, please just direct
> me to the archived thread.
> I'm trying to debug a crash in a native part of WebKit-JavaFX bindings
> (https://javafx-jira.kenai.com/browse/RT-33599). I have only been able
> to reproduce it on 32 bit platforms (Windows and Linux so far). I'm
> trying to build the WebKit natives with debugging symbols, so that I
> can pin-point the location of the crash in code using gdb. I have
> managed to do this successfully on 64 bit Linux, producing 1.7 GB
> large libjfxwebkit.so. But on 32 bit Linux, where only I can reproduce
> the crash, the build fails with linker error: "memory exhausted" when
> trying to assemble the libjfxwebkit.so from object files. So far I
> have not been successful in my attempts to circumvent this build
> error. I fave tried the following:
> - added '--no-keep-memory' to linker options. The man page says about it:
> ld normally optimizes for speed over memory usage by
> caching the symbol tables of input files in memory. This option tells
> ld to instead optimize for memory usage, by
> rereading the symbol tables as necessary. This may be
> required if ld runs out of memory space while linking a large executable.
> - booted the 64bit Ubuntu system and chrooted into a 32 bit
> environment. Some say that with 64 bit kernel, each 32 bit user-space
> process has more address space than with 32 bit kernel.
> - both of the above
> My question to the list is: How do you guys produce 32 bit
> libjfxwebkit.so with debugging symbols? Have you been able to? Do you
> have any special tricks in your sleeves?
More information about the openjfx-dev