Closed ruipacheco closed 9 years ago
Does it happen with any other shells (e.g. regular bash)?
Latest zsh:
[1] 49828 illegal hardware instruction ./target/release/iotaz
Hm, and this happens immediately?
Yep. As soon as I try to run the binary.
On 12 Jan 2015, at 03:26, Joshua Yanovski notifications@github.com wrote:
Hm, and this happens immediately?
— Reply to this email directly or view it on GitHub https://github.com/gchp/iota/issues/80#issuecomment-69524305.
Hey, I get the same thing! Someone must have screwed up :P I'll see if I can figure out what went wrong, as it obviously was not doing this before.
Maybe one of the dependencies.
Thanks!
On 12 Jan 2015, at 03:32, Joshua Yanovski notifications@github.com wrote:
Hey, I get the same thing! Someone must have screwed up :P I'll see if I can figure out what went wrong, as it obviously was not doing this before.
— Reply to this email directly or view it on GitHub https://github.com/gchp/iota/issues/80#issuecomment-69524506.
Its probably a problem in gapbuffer's indexing introduced with the new changes to slicing. @gchp and I discussed it yesterday
Sent from my android device.
-----Original Message----- From: ruipacheco notifications@github.com To: gchp/iota iota@noreply.github.com Sent: Sun, 11 Jan 2015 6:45 PM Subject: Re: [iota] SIGILL on latest OSX (#80)
Maybe one of the dependencies.
Thanks!
On 12 Jan 2015, at 03:32, Joshua Yanovski notifications@github.com wrote:
Hey, I get the same thing! Someone must have screwed up :P I'll see if I can figure out what went wrong, as it obviously was not doing this before.
— Reply to this email directly or view it on GitHub https://github.com/gchp/iota/issues/80#issuecomment-69524506.
Reply to this email directly or view it on GitHub: https://github.com/gchp/iota/issues/80#issuecomment-69524528
Sorry for late response. As @dlaronson said, this is something to do with the GapBuffer
repo, investigating this at the moment!
Happens on Linux elbridge 3.17.6-1-ARCH #1 SMP PREEMPT Sun Dec 7 23:43:32 UTC 2014 x86_64 GNU/Linux
too, with and without --release
.
Submitted a PR which once merged will fix the issue.
git pull-ed today and the issue was fixed.
git pull
cargo build --release
./target/release/iota
and then
fish: Job 1, './target/release/iota ' terminated by signal SIGILL (Illegal instruction)
(I'm using the fish shell)