** Changed in: golang (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1200255
Title:
go get ... fails with SIGILL on armhf
To manage notifications about th
Excellent. Thanks for getting this sorted.
On Thu, Jul 18, 2013 at 12:44 AM, Bug Watch Updater
<1200...@bugs.launchpad.net> wrote:
> ** Changed in: golang (Debian)
>Status: Unknown => New
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://
** Changed in: golang (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1200255
Title:
go get ... fails with SIGILL on armhf
To manage notifications about this bu
I have verified that this fixes the issue by upgrading an armhf LXC
machine that was reproducing the problem. The problem went away.
** Bug watch added: Debian Bug tracker #717172
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717172
** Also affects: golang (Debian) via
http://bugs.debian
Not stripping should be fine if it causes an issue like this. It's a
should in policy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1200255
Title:
go get ... fails with SIGILL on armhf
To manage no
This bug was fixed in the package golang - 2:1.1.1-3ubuntu3
---
golang (2:1.1.1-3ubuntu3) saucy; urgency=low
* Disable upstream-unsupported stripping of binaries to fix go crash
(LP: #1200255).
-- Robie BasakWed, 17 Jul 2013 10:43:11 +
** Changed in: golang (Ubuntu)
To clarify my previous statements.
* I do not disagree with the debian policy, it is there for a good reason
* Having said that, it stripping Go binaries doesn't work, and nobody is
looking at making it work, so there is that.
Thanks for patching the build formula.
--
You received this bug not
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1200255
Title:
go get ... fails with SIGILL on armhf
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubun
** Patch added: "saucy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/golang/+bug/1200255/+attachment/3738860/+files/saucy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1200255
Title:
Indeed, dropping dh_strip appears to fix the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1200255
Title:
go get ... fails with SIGILL on armhf
To manage notifications about this bug go to:
Thanks Dave.
Debian policy says that binaries should be stripped, which is why we're
doing it: http://www.debian.org/doc/debian-policy/ch-
files.html#s-binaries
I'll certainly try building the package without stripping to verify that
this fixes the problem.
I'm not sure whether not stripping the
Though it does say "should", not "must".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1200255
Title:
go get ... fails with SIGILL on armhf
To manage notifications about this bug go to:
https://bug
We are stripping the binaries.
alarm(~) % file ./go.1
./go.1: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV),
dynamically linked (uses shared libs), stripped
That is why it falis.
On Tue, Jul 16, 2013 at 12:46 AM, Robie Basak
<1200...@bugs.launchpad.net> wrote:
> go binary from saucy at
To quote myself: "Please do not strip Go binaries, it is not
supported, not tested, is often broken, and doesn't do what you want"
To unpack that a bit
* not supported, as in, we don't support it, and recommend against it when asked
* not tested, we don't test stripped binaries as part of the bui
go binary from saucy attached (/usr/bin/go from 2:1.1.1-0ubuntu1). I
couldn't get it to give me a core file - it seems to trap SEGV with
golang-specific handling. Any hints?
** Attachment added: "go"
https://bugs.launchpad.net/ubuntu/+source/golang/+bug/1200255/+attachment/3737603/+files/go
-
It'll take me a while to reproduce this build environment. My pandaboard
does not run saucy. Can anyone provide me with the binary and .core file
?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1200255
Dave,
Thanks for looking. You should be able to reproduce straight from the
archive in Saucy. You just needed golang from Saucy and bzr installed.
See my steps above - I believe only that one line is needed. Let me know
if this is a problem for you and I'll extract the binary for you on
Monday.
-
I'm guessing either
a. it really is an illegal instruction, but that is unlikely
b. unaligned dword mul or something like that
can you please, a upload the juju binary and i'll try it on my machine,
or the binary and the core dump, or at least the gdb backtrace and
disasm.
c. outside possibility
Confirmed. I did:
apt-get install golang bzr
GOPATH=~/gocode go get -u launchpad.net/gocheck
I get SIGSEGV. It seems to get further sometimes. It worked one time.
** Changed in: golang (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ub
** Summary changed:
- go get ... fails with SIGILL
+ go get ... fails with SIGILL on armhf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1200255
Title:
go get ... fails with SIGILL on armhf
To man
20 matches
Mail list logo