<div dir="ltr"><div dir="ltr"><div>Khem, you can find some backtraces here: <a href="https://github.com/prometheus/node_exporter/issues/1244">https://github.com/prometheus/node_exporter/issues/1244</a>, don't know if this is enough?</div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le dim. 3 mars 2019 à 16:43, Khem Raj <<a href="mailto:raj.khem@gmail.com">raj.khem@gmail.com</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Sun, Mar 3, 2019 at 2:45 AM Vincent Prince<br>
<<a href="mailto:vincent.prince.fr@gmail.com" target="_blank">vincent.prince.fr@gmail.com</a>> wrote:<br>
><br>
> Khem,<br>
><br>
> I'm not sure if we considere this issue as closed or if we need to dig root-cause here?<br>
><br>
> I don't have any Go stuff on my build machine nor build docker.<br>
> 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.<br>
><br>
> Please tell me if I can help,<br>
<br>
I think it needs some root causing, but we know the symptoms. So<br>
debugging to crash and some backtraces might help<br>
<br>
> Vincent<br>
><br>
><br>
> Le jeu. 28 févr. 2019 à 19:24, Khem Raj <<a href="mailto:raj.khem@gmail.com" target="_blank">raj.khem@gmail.com</a>> a écrit :<br>
>><br>
>> On Thu, Feb 28, 2019 at 10:19 AM Damien Riegel <<a href="mailto:damien.riegel@gmail.com" target="_blank">damien.riegel@gmail.com</a>> wrote:<br>
>> ><br>
>> > Hi,<br>
>> ><br>
>> > On Thu, 28 Feb 2019 at 09:04, Vincent Prince<br>
>> > <<a href="mailto:vincent.prince.fr@gmail.com" target="_blank">vincent.prince.fr@gmail.com</a>> wrote:<br>
>> > ><br>
>> > > Hi Khem,<br>
>> > ><br>
>> > > GO_DYNLINK_x86-64 = "" solution works as well,<br>
>> > ><br>
>> > > Best regards,<br>
>> > > Vincent<br>
>> > ><br>
>> > > Le jeu. 28 févr. 2019 à 14:14, Khem Raj <<a href="mailto:raj.khem@gmail.com" target="_blank">raj.khem@gmail.com</a>> a écrit :<br>
>> > >><br>
>> > >> On Thu, Feb 28, 2019 at 1:35 AM Vincent Prince<br>
>> > >> <<a href="mailto:vincent.prince.fr@gmail.com" target="_blank">vincent.prince.fr@gmail.com</a>> wrote:<br>
>> > >> ><br>
>> > >> > Hi Damien,<br>
>> > >> ><br>
>> > >> > With GO_LINKSHARED = "" it work fine.<br>
>> > >> ><br>
>> > >><br>
>> > >> Please set<br>
>> > >> GO_DYNLINK_x86-64 = "1"<br>
>> > >> to<br>
>> > >> GO_DYNLINK_x86-64 = ""<br>
>> > >> in goarch.bbclass<br>
>> ><br>
>> > Well, making a change in the goarch.bbclass is way more intrusive than<br>
>> > changing the value in a single recipe, so it would be nice to (at least)<br>
>> > give some justification about this solution.<br>
>> ><br>
>><br>
>> this will make static binaries instead, so I wonder if its doing some<br>
>> linking from host.<br>
>><br>
>> > >><br>
>> > >> > 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?<br>
>> ><br>
>> > As to why the GO_LINKSHARED ="" works, I cannot tell. I just noticed<br>
>> > that our application was linked differently on my machine (where it<br>
>> > worked) and in Yocto (where it didn't work), so I tweaked link flags<br>
>> > until I got it to work.<br>
>> ><br>
>> > Cheers,<br>
>> > Damien<br>
</blockquote></div>