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
Invalid regex literal causes Swift REPL to segfault #83167
Comments
@llvm/issue-subscribers-lldb Author: None (bbrk24)
```
1> let rgx = #/(.)(?<!.*\1.*\1)/#PLEASE submit a bug report to https://github.com/llvm/llvm-project/issues/ and include the crash backtrace.
Stack dump without symbol names (ensure you have llvm-symbolizer in your PATH or set the environment var `LLVM_SYMBOLIZER_PATH` to point to it):
/home/bbrk24/swift/swift-5.9-RELEASE-ubuntu22.04/usr/bin/lldb(+0x22923)[0x564ff284c923]
/home/bbrk24/swift/swift-5.9-RELEASE-ubuntu22.04/usr/bin/lldb(+0x20cbe)[0x564ff284acbe]
/home/bbrk24/swift/swift-5.9-RELEASE-ubuntu22.04/usr/bin/lldb(+0x22f5a)[0x564ff284cf5a]
/lib/x86_64-linux-gnu/libc.so.6(+0x42520)[0x7faf277a0520]
/home/bbrk24/swift/swift-5.9-RELEASE-ubuntu22.04/usr/bin/../lib/../lib/swift/linux/libswiftCore.so(+0x3ef004)[0x7faf274e1004]
/home/bbrk24/swift/swift-5.9-RELEASE-ubuntu22.04/usr/bin/../lib/../lib/swift/linux/libswiftCore.so(+0x416e96)[0x7faf27508e96]
/home/bbrk24/swift/swift-5.9-RELEASE-ubuntu22.04/usr/bin/../lib/../lib/swift/linux/libswiftCore.so(swift_getWitnessTable+0x1393)[0x7faf275006b3]
/home/bbrk24/swift/swift-5.9-RELEASE-ubuntu22.04/usr/bin/../lib/liblldb.so.13git(+0x19aa84a)[0x7faf296b984a]
💣 Program crashed: Bad pointer dereference at 0x0000000000000000 Thread 22 "gger.io-handler" crashed: 0 0x00007faf274e1004 Segmentation fault
|
Please report issues with Apple-provided things to Apple bugtracker. |
I almost submitted this to apple/swift, but then I saw that the stack dump specifically requested I put it here instead. Is it possible to move the issue? |
IIRC, issues can only be transferred between repos on the same org, so this one probably needs to be refiled manually. Apple should consider changing the stack trace issue URL for their binaries… Perhaps another issue that would be good to file. |
The text was updated successfully, but these errors were encountered: