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
src/index.ts import { ver } from '../macros/ver' with { type: "macro" }; console.log(ver())
macros/ver.ts
`
import { $ } from 'bun'
export async function ver() {
const v = await $echo "0.0.1".text()
return v
}
`
program started with bun .\src\index.ts
Relevant log output
PS C:\Users\geekg\Desktop\Elysia\app> bun .\src\index.ts
============================================================
Bun v1.1.12 (43f0913c) Windows x64
Args: "C:\Users\geekg\.bun\bin\bun.exe"".\src\index.ts"
Features: jsc macros(2) shell tsconfig(2)
Builtins: "bun:main"
Elapsed: 41ms | User: 0ms | Sys: 0ms
RSS: 103.65MB | Peak: 103.65MB | Commit: 0.15GB | Faults: 25523
panic(main thread): Segmentation fault at address 0x8
oh no: Bun has crashed. This indicates a bug in Bun, not your code.
To send a redacted crash report to Bun's team,please file a GitHub issue using the link below: https://bun.report/1.1.12/wa143f0913AiggglEg59+2CkyyrIutq8Qw7u8Qu6soKonu3aqq4lY479zTuxygUmx+zTA2AQ
Stack Trace (bun.report)
Bun v1.1.12 (43f0913) on windows x86_64 [AutoCommand]
How can we reproduce the crash?
Just a simple program with no libraries
src/index.ts
import { ver } from '../macros/ver' with { type: "macro" }; console.log(ver())
macros/ver.ts
`
import { $ } from 'bun'
export async function ver() {
const v = await $
echo "0.0.1"
.text()return v
}
`
program started with
bun .\src\index.ts
Relevant log output
Stack Trace (bun.report)
Bun v1.1.12 (
43f0913
) on windows x86_64 [AutoCommand]Segmentation fault at address 0x00000008
us_wakeup_loop
interpreter.zig:322
:close
interpreter.zig:742
:deinitImpl
interpreter.zig:2570
:finish
interpreter.zig:5461
:done
interpreter.zig:6831
:start
interpreter.zig:5171
:callImpl
interpreter.zig:4495
:transitionToExecStateAndYield
interpreter.zig:1916
:next
interpreter.zig:1802
:start
The text was updated successfully, but these errors were encountered: