ish-app / ish-app/ish

Cannot run vale (golang linter)

Open
#2,212 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

unconfirmed
Dominant language
C
Stars
20.5k
Forks
1.5k
PR merge metrics
No merged PRs in 30d

Description

Downloading the [i386 binary](https://github.com/errata-ai/vale/releases/download/v2.28.2/vale_2.28.2_Linux_386.tar.gz) and trying to run it fails with the usual "fatal" errors that I've come to associate with Go binaries:

```
fatal error: fatal error: unexpected signal during runtime execution
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x0]

runtime stack:
runtime.throw({0x891cfb8, 0x2a})
/opt/hostedtoolcache/go/1.20.7/x64/src/runtime/panic.go:1047 +0x4d fp=0xffffdbc4 sp=0xffffdbb0 pc=0x807e21d
runtime: g 0: unexpected return pc for runtime.sigpanic called from 0x0
stack: frame={sp:0xffffdbc4, fp:0xffffdbdc} stack=[0xfffeddd8,0xffffdd70)
0xffffdb44: 0x0807ea93 0x0807e21d 0xffffdbb0 0x00000000
0xffffdb54: 0x091a6940 0x0100fb01 0x0000001f 0x00000000
0xffffdb64: 0x00000000 0x00000001 0x00000001 0x08913754
0xffffdb74: 0x0807e582 0x091a6940 0x0807e21d 0xffffdbb0
0xffffdb84: 0x00000001 0xffffdbb0 0x0807e21d 0x091a6940
0xffffdb94: 0x0807e511 0xffffdb9c 0x0807e520 0x091a6940
0xffffdba4: 0x0807e21d 0xffffdbb0 0x0807e21d 0x00000002
0xffffdbb4: 0x0807e230 0x0891cfb8 0x0000002a 0x080948c8
0xffffdbc4: <0x0891cfb8 0x0000002a 0x00000080 0x00000000
0xffffdbd4: 0x091a6940 !0x00000000 >0x00000000 0xfffffffc
0xffffdbe4: 0x0890e725 0x0807e211 0xffffdbf0 0x0807e230
0xffffdbf4: 0x0890e725 0x00000019 0x080527d4 0x09444550
0xffffdc04: 0x00000000 0xffffffff 0xffffffff 0xffffffff
0xffffdc14: 0xffffffff 0x09406780 0x08083ba7 0x09444550
0xffffdc24: 0x09406780 0x080859cb 0x00000001 0x00000001
0xffffdc34: 0x08052404 0x091a6940 0x08087a9a 0x00000000
0xffffdc44: 0x00000000 0x080525cf 0x091a7358 0x091a6be0
0xffffdc54: 0x00000001 0x080882a6
runtime.sigpanic()
/opt/hostedtoolcache/go/1.20.7/x64/src/runtime/signal_unix.go:825 +0x2b8 fp=0xffffdbdc sp=0xffffdbc4 pc=0x80948c8
```

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No repository file or test is identified. Start by reproducing the failure with the linked i386 Linux vale 2.28.2 binary in iSH, then read the reported Go runtime stack and investigate the relevant architecture or signal-handling support. Done means the binary runs without the fatal SIGSEGV, with a regression check if the affected code can be isolated.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, ios, linux
Domain
cli, operating-systems
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.