Zig build causes segfault when package manager depends on .url from github with https

[edyu]

Zig Version

0.11.0-dev.3879+5804f3f75

Steps to Reproduce and Observed Behavior

This is more of informational than exact step. I don't know enough of the internals to pinpoint where the error originated from but maybe someone who does can see what would cause this problem.
I have 2 laptops (one has intel and the other has amd). Both run windows 11 and I use both with Ubuntu 22.04 LTS WSL2.
On one of them when I call zig build on for example the zigzap/zap repository, it would cause the following error:
signal SIGSEGV (Address boundary error)
However, after I installed gdb with sudo apt install gdb the problem went away. SEE BELOW

EDIT: It didn't go away as I now realized that once I download it once (using a workaround of localhost serving the package with http not https) and it gets cached.

EDIT2: The package IS available at the url as I can download the package manually.

Expected Behavior

Should compile ok without installing gdb first.

[edyu]

Maybe it's caused by the new package manager and when .url in the .dependencies for a package is unavailable, it would cause this problem.
'zig build' terminated by signal SIGSEGV (Address boundary error)

[DraagrenKirneh]

@edyu are you invoking zig build on package located in a windows folder or a subsystem folder?

[edyu]

@edyu are you invoking zig build on package located in a windows folder or a subsystem folder?

On subsystem folder.

[edyu]

Here is the config that would've have caused it.

.{
    .name = "My example project",
    .version = "0.0.1",

    .dependencies = .{
        // zap release-0.0.20
        .zap = .{
            .url = "https://github.com/zigzap/zap/archive/refs/tags/release-0.0.20.tar.gz",
            .hash = "12200772b594bc50bbdc18b14aa3c7461991a33179f9c254de05eb34d214662971da",
        }
    }
}

[DraagrenKirneh]

Can confirm that this is happening on WSL, when gdb is not present.

zig init-exe
touch build.zig.zon
# copy the content from the comment above
zig build
# Segmentation fault (core dumped)

Builds as expected if I remove the zon file.

[nektro]

on linux that yields the following, though it is also weird how there's an extra line between the caret and the message

/home/meghan/src/temp/build.zig.zon:1:1: error: expected expression, found 'EOF'

^

[edyu]

As of zig version 0.11.0-dev.3206+b9d2e0e30, I'm not seeing this problem anymore. Maybe it's related to the TLS fix.

[edyu]

Now the error is error: TlsFailure
version is now error: 0.11.0-dev.3286+dcc1b4fd1

[edyu]

And sometimes error: BadReaderState

[edyu]

Still having the following error at 0.11.0-dev.3312+ab37ab33c
'zig build' terminated by signal SIGSEGV (Address boundary error)

.{
    .name = "mytest",
    .version = "0.0.2",

    .dependencies = .{
        // zap v0.1.4-pre
        .zap = .{
            .url = "https://github.com/zigzap/zap/archive/refs/tags/v0.1.4-pre.tar.gz",
            .hash = "12204613bae513282f2b7e468045401cbae09bb19e42baeca193b9c98ff6f2ceb6ef",
        }
    }
}

[edyu]

And I can confirm that if i replace the url with a localhost serving the tar.gz such as python and I change the .url to http://localhost:8000/v0.1.4-pre.tar.gz, the zig build would work. So it's most likely something screwy in the package fetching code.

[edyu]

btw, I'm running Ubuntu 22.04 LTS in WSL2 on an AMD 5800HS (not sure how relevant).