You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't really know whether that's a bug in Amp but I think it's better if I report it anyways. I was casually editing a file (it was an already existing file if that's important) and then I got this message:
fish: 'amp filename.rs' terminated by signal SIGSEGV (Address boundary error)
The error occured right after I woke my laptop from sleep and pressed a few keys in Amp.
Info:
Amp 0.5.0
MacOS 10.14.1
The text was updated successfully, but these errors were encountered:
Hi @micouy! Nice find. The only place we do anything unsafe in Amp that would trigger a segfault like that is in the gap buffer implementation, in the scribe crate.
It shouldn't matter if the file exists or not, but I wish I knew which keys you'd pressed. Was the file empty? Also, was it a UTF-8 file, or another encoding?
I don't really know whether that's a bug in Amp but I think it's better if I report it anyways. I was casually editing a file (it was an already existing file if that's important) and then I got this message:
The error occured right after I woke my laptop from sleep and pressed a few keys in Amp.
Info:
The text was updated successfully, but these errors were encountered: