On 4 Mar 2021, at 22:02, Riccardo Mottola <riccardo.mott...@libero.it> wrote: > > Hi, > > I decided to continue working on my ArcticFox efforts on hurd. I found this > patch by Richard Braun: > > https://bugzilla.mozilla.org/show_bug.cgi?id=1029809 > > Being ArcticFox codebase around FF 40-45, it was relatively easy to > adapt&apply! > > However, compilation halts with > > 62:47.37 In file included from ../../dist/include/nsTArray.h:2325, > 62:47.37 from > /home/multix/code/Arctic-Fox/widget/nsIWidget.h:17, > 62:47.37 from ../../dist/include/ipc/IPCMessageUtils.h:26, > 62:47.37 from > /home/multix/code/Arctic-Fox/obj-i686-unknown-gnu0.9/ipc/ipdl/_ipdlheaders/mozilla/dom/PColorPicker.h:12, > 62:47.37 from > /home/multix/code/Arctic-Fox/obj-i686-unknown-gnu0.9/ipc/ipdl/_ipdlheaders/mozilla/dom/PColorPickerParent.h:9, > 62:47.37 from > /home/multix/code/Arctic-Fox/dom/ipc/ColorPickerParent.h:10, > sem_wait: Invalid argumentlibs tools > Segmentation fault (core dumped) > > What did coredump and why? I found one core file and gdb tells me. > > > warning: Unexpected size of section `.reg2/4208' in core file. > Core was generated by `python2.7 ./mach build'. > Program terminated with signal SIGSEGV, Segmentation fault. > > > (gdb) bt > #0 0x0119c69c in ?? () > > The backtrace is not very helpful. I wonder if it is related with the invalid > argument message on sem_wait ? > > I tried relaunching build.. and it may either coredump again, but sometimes > continues too
python2.7 segfaulted and you haven't installed its debugging symbols. Jess
