Re: [OE-core] GO runtime crashes
Khem, you can find some backtraces here: https://github.com/prometheus/node_exporter/issues/1244, don't know if this is enough? Le dim. 3 mars 2019 à 16:43, Khem Raj a écrit : > On Sun, Mar 3, 2019 at 2:45 AM Vincent Prince > wrote: > > > > Khem, > > > > I'm not sure if we considere this issue as closed or if we need to dig > root-cause here? > > > > I don't have any Go stuff on my build machine nor build docker. > > Also, those random crashes came with Thud version, I didn't have any in > Sumo, but there was a lot of changes between these two versions. > > > > Please tell me if I can help, > > I think it needs some root causing, but we know the symptoms. So > debugging to crash and some backtraces might help > > > Vincent > > > > > > Le jeu. 28 févr. 2019 à 19:24, Khem Raj a écrit : > >> > >> On Thu, Feb 28, 2019 at 10:19 AM Damien Riegel > wrote: > >> > > >> > Hi, > >> > > >> > On Thu, 28 Feb 2019 at 09:04, Vincent Prince > >> > wrote: > >> > > > >> > > Hi Khem, > >> > > > >> > > GO_DYNLINK_x86-64 = "" solution works as well, > >> > > > >> > > Best regards, > >> > > Vincent > >> > > > >> > > Le jeu. 28 févr. 2019 à 14:14, Khem Raj a > écrit : > >> > >> > >> > >> On Thu, Feb 28, 2019 at 1:35 AM Vincent Prince > >> > >> wrote: > >> > >> > > >> > >> > Hi Damien, > >> > >> > > >> > >> > With GO_LINKSHARED = "" it work fine. > >> > >> > > >> > >> > >> > >> Please set > >> > >> GO_DYNLINK_x86-64 = "1" > >> > >> to > >> > >> GO_DYNLINK_x86-64 = "" > >> > >> in goarch.bbclass > >> > > >> > Well, making a change in the goarch.bbclass is way more intrusive than > >> > changing the value in a single recipe, so it would be nice to (at > least) > >> > give some justification about this solution. > >> > > >> > >> this will make static binaries instead, so I wonder if its doing some > >> linking from host. > >> > >> > >> > >> > >> > I'm very new to Go, does it mean that there is a mixing issue in > go modules from Yocto and from node_exporter vendor folder, so it links > wrongly at runtime? > >> > > >> > As to why the GO_LINKSHARED ="" works, I cannot tell. I just noticed > >> > that our application was linked differently on my machine (where it > >> > worked) and in Yocto (where it didn't work), so I tweaked link flags > >> > until I got it to work. > >> > > >> > Cheers, > >> > Damien > -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] GO runtime crashes
On Sun, Mar 3, 2019 at 2:45 AM Vincent Prince wrote: > > Khem, > > I'm not sure if we considere this issue as closed or if we need to dig > root-cause here? > > I don't have any Go stuff on my build machine nor build docker. > Also, those random crashes came with Thud version, I didn't have any in Sumo, > but there was a lot of changes between these two versions. > > Please tell me if I can help, I think it needs some root causing, but we know the symptoms. So debugging to crash and some backtraces might help > Vincent > > > Le jeu. 28 févr. 2019 à 19:24, Khem Raj a écrit : >> >> On Thu, Feb 28, 2019 at 10:19 AM Damien Riegel >> wrote: >> > >> > Hi, >> > >> > On Thu, 28 Feb 2019 at 09:04, Vincent Prince >> > wrote: >> > > >> > > Hi Khem, >> > > >> > > GO_DYNLINK_x86-64 = "" solution works as well, >> > > >> > > Best regards, >> > > Vincent >> > > >> > > Le jeu. 28 févr. 2019 à 14:14, Khem Raj a écrit : >> > >> >> > >> On Thu, Feb 28, 2019 at 1:35 AM Vincent Prince >> > >> wrote: >> > >> > >> > >> > Hi Damien, >> > >> > >> > >> > With GO_LINKSHARED = "" it work fine. >> > >> > >> > >> >> > >> Please set >> > >> GO_DYNLINK_x86-64 = "1" >> > >> to >> > >> GO_DYNLINK_x86-64 = "" >> > >> in goarch.bbclass >> > >> > Well, making a change in the goarch.bbclass is way more intrusive than >> > changing the value in a single recipe, so it would be nice to (at least) >> > give some justification about this solution. >> > >> >> this will make static binaries instead, so I wonder if its doing some >> linking from host. >> >> > >> >> > >> > I'm very new to Go, does it mean that there is a mixing issue in go >> > >> > modules from Yocto and from node_exporter vendor folder, so it links >> > >> > wrongly at runtime? >> > >> > As to why the GO_LINKSHARED ="" works, I cannot tell. I just noticed >> > that our application was linked differently on my machine (where it >> > worked) and in Yocto (where it didn't work), so I tweaked link flags >> > until I got it to work. >> > >> > Cheers, >> > Damien -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] GO runtime crashes
Khem, I'm not sure if we considere this issue as closed or if we need to dig root-cause here? I don't have any Go stuff on my build machine nor build docker. Also, those random crashes came with Thud version, I didn't have any in Sumo, but there was a lot of changes between these two versions. Please tell me if I can help, Vincent Le jeu. 28 févr. 2019 à 19:24, Khem Raj a écrit : > On Thu, Feb 28, 2019 at 10:19 AM Damien Riegel > wrote: > > > > Hi, > > > > On Thu, 28 Feb 2019 at 09:04, Vincent Prince > > wrote: > > > > > > Hi Khem, > > > > > > GO_DYNLINK_x86-64 = "" solution works as well, > > > > > > Best regards, > > > Vincent > > > > > > Le jeu. 28 févr. 2019 à 14:14, Khem Raj a écrit : > > >> > > >> On Thu, Feb 28, 2019 at 1:35 AM Vincent Prince > > >> wrote: > > >> > > > >> > Hi Damien, > > >> > > > >> > With GO_LINKSHARED = "" it work fine. > > >> > > > >> > > >> Please set > > >> GO_DYNLINK_x86-64 = "1" > > >> to > > >> GO_DYNLINK_x86-64 = "" > > >> in goarch.bbclass > > > > Well, making a change in the goarch.bbclass is way more intrusive than > > changing the value in a single recipe, so it would be nice to (at least) > > give some justification about this solution. > > > > this will make static binaries instead, so I wonder if its doing some > linking from host. > > > >> > > >> > I'm very new to Go, does it mean that there is a mixing issue in go > modules from Yocto and from node_exporter vendor folder, so it links > wrongly at runtime? > > > > As to why the GO_LINKSHARED ="" works, I cannot tell. I just noticed > > that our application was linked differently on my machine (where it > > worked) and in Yocto (where it didn't work), so I tweaked link flags > > until I got it to work. > > > > Cheers, > > Damien > -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] GO runtime crashes
On Thu, Feb 28, 2019 at 10:19 AM Damien Riegel wrote: > > Hi, > > On Thu, 28 Feb 2019 at 09:04, Vincent Prince > wrote: > > > > Hi Khem, > > > > GO_DYNLINK_x86-64 = "" solution works as well, > > > > Best regards, > > Vincent > > > > Le jeu. 28 févr. 2019 à 14:14, Khem Raj a écrit : > >> > >> On Thu, Feb 28, 2019 at 1:35 AM Vincent Prince > >> wrote: > >> > > >> > Hi Damien, > >> > > >> > With GO_LINKSHARED = "" it work fine. > >> > > >> > >> Please set > >> GO_DYNLINK_x86-64 = "1" > >> to > >> GO_DYNLINK_x86-64 = "" > >> in goarch.bbclass > > Well, making a change in the goarch.bbclass is way more intrusive than > changing the value in a single recipe, so it would be nice to (at least) > give some justification about this solution. > this will make static binaries instead, so I wonder if its doing some linking from host. > >> > >> > I'm very new to Go, does it mean that there is a mixing issue in go > >> > modules from Yocto and from node_exporter vendor folder, so it links > >> > wrongly at runtime? > > As to why the GO_LINKSHARED ="" works, I cannot tell. I just noticed > that our application was linked differently on my machine (where it > worked) and in Yocto (where it didn't work), so I tweaked link flags > until I got it to work. > > Cheers, > Damien -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] GO runtime crashes
Hi, On Thu, 28 Feb 2019 at 09:04, Vincent Prince wrote: > > Hi Khem, > > GO_DYNLINK_x86-64 = "" solution works as well, > > Best regards, > Vincent > > Le jeu. 28 févr. 2019 à 14:14, Khem Raj a écrit : >> >> On Thu, Feb 28, 2019 at 1:35 AM Vincent Prince >> wrote: >> > >> > Hi Damien, >> > >> > With GO_LINKSHARED = "" it work fine. >> > >> >> Please set >> GO_DYNLINK_x86-64 = "1" >> to >> GO_DYNLINK_x86-64 = "" >> in goarch.bbclass Well, making a change in the goarch.bbclass is way more intrusive than changing the value in a single recipe, so it would be nice to (at least) give some justification about this solution. >> >> > I'm very new to Go, does it mean that there is a mixing issue in go >> > modules from Yocto and from node_exporter vendor folder, so it links >> > wrongly at runtime? As to why the GO_LINKSHARED ="" works, I cannot tell. I just noticed that our application was linked differently on my machine (where it worked) and in Yocto (where it didn't work), so I tweaked link flags until I got it to work. Cheers, Damien -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] GO runtime crashes
Hi Khem, GO_DYNLINK_x86-64 = "" solution works as well, Best regards, Vincent Le jeu. 28 févr. 2019 à 14:14, Khem Raj a écrit : > On Thu, Feb 28, 2019 at 1:35 AM Vincent Prince > wrote: > > > > Hi Damien, > > > > With GO_LINKSHARED = "" it work fine. > > > > Please set > GO_DYNLINK_x86-64 = "1" > to > GO_DYNLINK_x86-64 = "" > in goarch.bbclass > > > I'm very new to Go, does it mean that there is a mixing issue in go > modules from Yocto and from node_exporter vendor folder, so it links > wrongly at runtime? > > > > Thanks for the quickfix, > > Vincent > > > > > > > > > > Le mer. 27 févr. 2019 à 23:22, Damien Riegel > a écrit : > >> > >> On Wed, 27 Feb 2019 at 12:10, Vincent Prince > >> wrote: > >> > > >> > Hello everyone, > >> > > >> > I'm trying to add node_exporter from Prometheus project to an Intel > x86-64 machine. > >> > I made the following recipe: > >> > > >> > > https://github.com/nefethael/meta-random/blob/master/recipes-connectivity/prometheus/go-nodeexporter_0.18.0.bb > >> > > >> > node_exporter is crashing with multiple different runtime errors, so > I raised an issue on github: > >> > https://github.com/prometheus/node_exporter/issues/1244 > >> > >> I've faced the same kind of issue with a custom application of ours. > >> The fix was to add the following line to the recipe: > >> GO_LINKSHARED = "" > >> > >> Let me know if that helps. > >> > >> Cheers, > >> Damien > -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] GO runtime crashes
On Thu, Feb 28, 2019 at 1:35 AM Vincent Prince wrote: > > Hi Damien, > > With GO_LINKSHARED = "" it work fine. > Please set GO_DYNLINK_x86-64 = "1" to GO_DYNLINK_x86-64 = "" in goarch.bbclass > I'm very new to Go, does it mean that there is a mixing issue in go modules > from Yocto and from node_exporter vendor folder, so it links wrongly at > runtime? > > Thanks for the quickfix, > Vincent > > > > > Le mer. 27 févr. 2019 à 23:22, Damien Riegel a > écrit : >> >> On Wed, 27 Feb 2019 at 12:10, Vincent Prince >> wrote: >> > >> > Hello everyone, >> > >> > I'm trying to add node_exporter from Prometheus project to an Intel x86-64 >> > machine. >> > I made the following recipe: >> > >> > https://github.com/nefethael/meta-random/blob/master/recipes-connectivity/prometheus/go-nodeexporter_0.18.0.bb >> > >> > node_exporter is crashing with multiple different runtime errors, so I >> > raised an issue on github: >> > https://github.com/prometheus/node_exporter/issues/1244 >> >> I've faced the same kind of issue with a custom application of ours. >> The fix was to add the following line to the recipe: >> GO_LINKSHARED = "" >> >> Let me know if that helps. >> >> Cheers, >> Damien -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] GO runtime crashes
Hi Damien, With GO_LINKSHARED = "" it work fine. I'm very new to Go, does it mean that there is a mixing issue in go modules from Yocto and from node_exporter vendor folder, so it links wrongly at runtime? Thanks for the quickfix, Vincent Le mer. 27 févr. 2019 à 23:22, Damien Riegel a écrit : > On Wed, 27 Feb 2019 at 12:10, Vincent Prince > wrote: > > > > Hello everyone, > > > > I'm trying to add node_exporter from Prometheus project to an Intel > x86-64 machine. > > I made the following recipe: > > > > > https://github.com/nefethael/meta-random/blob/master/recipes-connectivity/prometheus/go-nodeexporter_0.18.0.bb > > > > node_exporter is crashing with multiple different runtime errors, so I > raised an issue on github: > > https://github.com/prometheus/node_exporter/issues/1244 > > I've faced the same kind of issue with a custom application of ours. > The fix was to add the following line to the recipe: > GO_LINKSHARED = "" > > Let me know if that helps. > > Cheers, > Damien > -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] GO runtime crashes
On Wed, 27 Feb 2019 at 12:10, Vincent Prince wrote: > > Hello everyone, > > I'm trying to add node_exporter from Prometheus project to an Intel x86-64 > machine. > I made the following recipe: > > https://github.com/nefethael/meta-random/blob/master/recipes-connectivity/prometheus/go-nodeexporter_0.18.0.bb > > node_exporter is crashing with multiple different runtime errors, so I raised > an issue on github: > https://github.com/prometheus/node_exporter/issues/1244 I've faced the same kind of issue with a custom application of ours. The fix was to add the following line to the recipe: GO_LINKSHARED = "" Let me know if that helps. Cheers, Damien -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] GO runtime crashes
Hello everyone, I'm trying to add node_exporter from Prometheus project to an Intel x86-64 machine. I made the following recipe: https://github.com/nefethael/meta-random/blob/master/recipes-connectivity/prometheus/go-nodeexporter_0.18.0.bb node_exporter is crashing with multiple different runtime errors, so I raised an issue on github: https://github.com/prometheus/node_exporter/issues/1244 I just tested node_exporter binary without cross-compiling it with Yocto and it does not crash. So now I'm stuck with it and nobody seems to complain about golang on ML, so if there are some GO experts here to help me on that, Thanks, Vincent -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
