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?



Reply via email to