New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Panic on certain -source calls #1202
Comments
I'm also seeing a panic, and I don't use @zzamboni's alias module. I update
I have to revert the five most recent commits, back to 09829ae, to get a working interactive shell. |
Commenting out my assignment to |
FWIW, I'm seeing a different panic than @iwoloschin reported:
|
I'm also seeing a panic on latest master. I'll post details as soon as I'm
back on my machine.
…On Sat, 26 Dec 2020 at 03:07, Kurtis Rader ***@***.***> wrote:
FWIW, I'm seeing a different panic than @iwoloschin
<https://github.com/iwoloschin> reported:
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x20 pc=0x136f2e6]
goroutine 13819 [running]:github.com/elves/elvish/pkg/eval.(*Ns).lookup(0x0, 0xc00029f383, 0x5, 0xc000489658)
/Users/krader/projects/3rd-party/elvish/pkg/eval/ns.go:68 +0x26github.com/elves/elvish/pkg/eval.(*Ns).indexInner(...)
/Users/krader/projects/3rd-party/elvish/pkg/eval/ns.go:60github.com/elves/elvish/pkg/eval.deref(0xc000bb23f0, 0xc00042dc50, 0x0, 0x0)
/Users/krader/projects/3rd-party/elvish/pkg/eval/var_ref.go:119 +0xf5github.com/elves/elvish/pkg/eval.variableOp.exec(0x137d, 0x1388, 0x0, 0xc00029f37e, 0xa, 0
xc00042dc50, 0xc000bb23f0, 0x8, 0x4, 0x203000, ...)
/Users/krader/projects/3rd-party/elvish/pkg/eval/compile_value.go:320 +0x4dgithub.com/elves/elvish/pkg/eval.compoundOp.exec(0x137d, 0x1388, 0x0, 0xc000428b30, 0x1, 0
x1, 0xc000bb23f0, 0x14738c0, 0x145ed01, 0xc000bb0280, ...)
/Users/krader/projects/3rd-party/elvish/pkg/eval/compile_value.go:75 +0x69github.com/elves/elvish/pkg/eval.seqValuesOp.exec(0x137d, 0x1388, 0xc000428b20, 0x1, 0x1,
0xc000bb23f0, 0xc000ba3f20, 0xc000ba1d10, 0x1489f60, 0xc000ba1d10, ...)
/Users/krader/projects/3rd-party/elvish/pkg/eval/compile_value.go:620 +0xb3github.com/elves/elvish/pkg/eval.(*assignOp).exec(0xc000426740, 0xc000bb23f0, 0xc000489e38
, 0x0)
/Users/krader/projects/3rd-party/elvish/pkg/eval/compile_lvalue.go:110 +0x232github.com/elves/elvish/pkg/eval.(*formOp).exec(0xc000425340, 0xc000bb23f0, 0x0, 0x0)
/Users/krader/projects/3rd-party/elvish/pkg/eval/compile_effect.go:398 +0x862github.com/elves/elvish/pkg/eval.(*pipelineOp).exec.func1(0x152b360, 0xc000425340, 0xc000b
b23f0, 0xc000808748, 0xc0005c9510, 0xc00055aa00)
/Users/krader/projects/3rd-party/elvish/pkg/eval/compile_effect.go:150 +0x3f
created by github.com/elves/elvish/pkg/eval.(*pipelineOp).exec
/Users/krader/projects/3rd-party/elvish/pkg/eval/compile_effect.go:149 +0x225
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1202 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAIA3BMTSO22LPVEBZPBGDSWVAN5ANCNFSM4VJPWWNQ>
.
|
So, more details:
Commenting out
I'll explore further to try and determine which part is causing the panic. |
I can confirm that just loading my
|
Upon further experimentation, the panic seems to be happening when the alias:-load-alias function is called. I modified
Running the commands from
@xiaq any ideas? |
I broke
A minimal repro:
|
I'm getting a panic on starting a new elvish process, but only with @zzamboni's alias module loaded.
Elvish is built locally (via my update module):
If the alias module is
use
d and any aliases are defined in~/.elvish/aliases/
I get a panic:If I comment out the
use
line or remove all aliases from~/.elvish/aliases/
the process starts up and appears to be fine.@krader1961 suggests in the chat that this commit might be to blame. I don't think I'm familiar enough with go or Elvish internals to really have any idea.
The text was updated successfully, but these errors were encountered: