Comment 2 for bug 1753995

Hi,

My linker/elf experience is limited I'm afraid.
I've built the snap with the apt-installed snapcraft (2.40), the snap one (2.40 - 1328), and the snap --edge one (2.40.1 - 1345), and got the same result with all.

At build time (full logs at https://launchpadlibrarian.net/362677409/buildlog_snap_ubuntu_xenial_amd64_telegraf_BUILDING.txt.gz):
[...]
Staging telegraf
Priming go
Priming snap-wrappers
Priming telegraf
cannot find section
Failed to update '/build/telegraf/prime/bin/telegraf'. Retrying after stripping the .note.go.buildid from the elf file.
Snapping 'telegraf' ...

Snapped telegraf_1.5.3_amd64.snap
[...]

At run time (not sure if this is the same issue ?):

Mar 30 15:14:32 portable systemd[1]: Reloading.
Mar 30 15:14:32 portable systemd[1]: Started Service for snap application telegraf.telegraf.
Mar 30 15:14:32 portable kernel: [22773.720171] telegraf[20023]: segfault at 400318 ip 00007f5176441949 sp 00007fff554d
81a0 error 7 in ld-2.23.so[7f517643e000+26000]
Mar 30 15:14:33 portable systemd[1]: snap.telegraf.telegraf.service: Main process exited, code=dumped, status=11/SEGV
Mar 30 15:14:33 portable systemd[1]: snap.telegraf.telegraf.service: Failed with result 'core-dump'.
Mar 30 15:14:33 portable systemd[1]: snap.telegraf.telegraf.service: Service hold-off time over, scheduling restart.
Mar 30 15:14:33 portable systemd[1]: snap.telegraf.telegraf.service: Scheduled restart job, restart counter is at 1.
Mar 30 15:14:33 portable systemd[1]: Stopped Service for snap application telegraf.telegraf.
Mar 30 15:14:33 portable systemd[1]: Started Service for snap application telegraf.telegraf.
Mar 30 15:14:33 portable kernel: [22774.090611] telegraf[20063]: segfault at 400318 ip 00007fc5f1180949 sp 00007fffd908
3d10 error 7 in ld-2.23.so[7fc5f117d000+26000]
Mar 30 15:14:33 portable systemd[1]: snap.telegraf.telegraf.service: Main process exited, code=dumped, status=11/SEGV
Mar 30 15:14:33 portable systemd[1]: snap.telegraf.telegraf.service: Failed with result 'core-dump'.