immediate segmentation fault with LLVM/Clang 9

Hello, I don't know where is the appropriate place to ask. I've upgraded my toolchain to LLVM 9 on my Clang based Linux distribution and everything built and ran fine except... busybox. I suspect busybox is built with some incompatible flags because it immediately segfaults at startup of an

Re: immediate segmentation fault with LLVM/Clang 9

Hello, Le 25/10/2019 à 09:54, David Demelier a écrit : > Hello, > > I don't know where is the appropriate place to ask. I've upgraded my toolchain > to LLVM 9 on my Clang based Linux distribution and everything built and ran > fine > except... busybox. > > I suspect busybox is built with some i

Re: immediate segmentation fault with LLVM/Clang 9

Le 25/10/2019 à 10:00, Romain Naour a écrit : There is an initial patch for this issue: http://lists.busybox.net/pipermail/busybox/2019-June/087306.html Thanks for the link, it's strange because I also built busybox with LLVM 8 before upgrading to 9 without any issue so far. I wonder how Luis

Re: immediate segmentation fault with LLVM/Clang 9

On Fri, Oct 25, 2019 at 10:00 AM Romain Naour wrote: > Le 25/10/2019 à 09:54, David Demelier a écrit : > > I don't know where is the appropriate place to ask. I've upgraded my > > toolchain > > to LLVM 9 on my Clang based Linux distribution and everything built and ran > > fine > > except... bus

Re: immediate segmentation fault with LLVM/Clang 9

On Fri, Oct 25, 2019 at 10:57 AM Denys Vlasenko wrote: > On Fri, Oct 25, 2019 at 10:00 AM Romain Naour wrote: > > Le 25/10/2019 à 09:54, David Demelier a écrit : > > > I don't know where is the appropriate place to ask. I've upgraded my > > > toolchain > > > to LLVM 9 on my Clang based Linux dis

Re: immediate segmentation fault with LLVM/Clang 9

Le 25/10/2019 à 10:00, Romain Naour a écrit : There is an initial patch for this issue: http://lists.busybox.net/pipermail/busybox/2019-June/087306.html Do you have a local version of that patch? I can't apply correctly, I guess because the mail was not sent via git-send-email. It says it is

Re: immediate segmentation fault with LLVM/Clang 9

Hi David, Le 28/10/2019 à 08:23, David Demelier a écrit : > Le 25/10/2019 à 10:00, Romain Naour a écrit : >> There is an initial patch for this issue: >> http://lists.busybox.net/pipermail/busybox/2019-June/087306.html > > Do you have a local version of that patch? I can't apply correctly, I gues

Re: immediate segmentation fault with LLVM/Clang 9

On Fri, Nov 8, 2019 at 10:04 AM Romain Naour wrote: > Le 28/10/2019 à 08:23, David Demelier a écrit : > > Le 25/10/2019 à 10:00, Romain Naour a écrit : > >> There is an initial patch for this issue: > >> http://lists.busybox.net/pipermail/busybox/2019-June/087306.html > > > > Do you have a local v

Re: immediate segmentation fault with LLVM/Clang 9

Hi Denys, Le 08/11/2019 à 14:54, Denys Vlasenko a écrit : > On Fri, Nov 8, 2019 at 10:04 AM Romain Naour wrote: >> Le 28/10/2019 à 08:23, David Demelier a écrit : >>> Le 25/10/2019 à 10:00, Romain Naour a écrit : There is an initial patch for this issue: http://lists.busybox.net/piperma

Re: immediate segmentation fault with LLVM/Clang 9

On Tue, Nov 12, 2019 at 6:03 AM Romain Naour wrote: > > Hi Denys, > > Le 08/11/2019 à 14:54, Denys Vlasenko a écrit : > > On Fri, Nov 8, 2019 at 10:04 AM Romain Naour wrote: > >> Le 28/10/2019 à 08:23, David Demelier a écrit : > >>> Le 25/10/2019 à 10:00, Romain Naour a écrit : > There is an

Re: immediate segmentation fault with LLVM/Clang 9

Hi, Im currently trying to run parts of busybox (e.g. ash) on-top of VxWorks. I made some progress and can run multiple apps. With the newest version of VxWorks the clang compiler version 9.0.1.1 is used and now I face the same immediate segfault as described below. I wonder why the "not_const