Skip to content
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

[SR-9317] Crash involving PackageGraph.DependencyResolver #4884

Open
swift-ci opened this issue Nov 22, 2018 · 3 comments
Open

[SR-9317] Crash involving PackageGraph.DependencyResolver #4884

swift-ci opened this issue Nov 22, 2018 · 3 comments
Labels

Comments

@swift-ci
Copy link
Contributor

Previous ID SR-9317
Radar None
Original Reporter camden@phusion.nl (JIRA User)
Type Bug
Environment

macOS 10.14.1 running docker for mac, so a linux vm via hypervisor.framework which runs docker images, in this case specifically a Debian:9 docker image in this case.

Additional Detail from JIRA
Votes 0
Component/s Package Manager
Labels Bug, RunTimeCrash
Assignee None
Priority Medium

md5: 50405ce2d68b6b3c938a106cce94d2ff

Issue Description:

I have a reproducible crash when trying to build the vapor toolbox using my swift toolchain I built on Debian.

I'm not sure if it's due to a problem with how I built the swift toolchain or a problem with the source or a problem with the interaction between the tools and the source.

I have a core dump, but there's an upload size limitation of 10MB and the core dump is 111MB, so if there's another way to provide it I'd be happy to do so.

What I found investigating the backtrace is that the stop reason = signal SIGILL and the top frame is doing something in the PackageGraph.DependencyResolver.

I realize this bug report is kinda short on details, I really want to provide any and all useful info, I'm just not sure what all would be helpful. Let me know and I'll provide that info.

For now, I'll describe what I did to get to where I am (note the env info for why I don't use sudo here, this is run as the root user).

cat > /etc/apt/preferences.d/security.pref <<EOL
Package: *
Pin: release l=Debian-Security
Pin-Priority: 1000
EOL
cat > /etc/apt/preferences.d/stable.pref <<EOL
Package: *
Pin: release a=stable
Pin-Priority: 900
EOL
cat > /etc/apt/preferences.d/testing.pref <<EOL
Package: *
Pin: release a=testing
Pin-Priority: 750
EOL
cat > /etc/apt/sources.list.d/testing.list <<EOL
deb http://deb.debian.org/debian testing main
deb-src http://deb.debian.org/debian testing main
EOL
apt-get update
apt install -y --allow-downgrades git cmake ninja-build clang python uuid-dev libicu-dev icu-devtools libbsd-dev libedit-dev libxml2-dev libsqlite3-dev swig/testing libpython-dev libncurses5-dev pkg-config libblocksruntime-dev libcurl4-openssl-dev systemtap-sdt-dev tzdata rsync

mkdir ~/swift-src
cd ~/swift-src
git clone https://github.com/apple/swift.git
cd ~/swift-src/swift
VERSION='swift-4.2.1-RELEASE'
git checkout $VERSION
./utils/update-checkout --clone --tag $VERSION

./utils/build-toolchain org.swift
mkdir /opt/swift
tar -xzf swift-*.tar.gz -C /opt/swift
export PATH=$PATH:/opt/swift/usr/bin

mkdir ~/vapor-src
cd ~/vapor-src
git clone https://github.com/vapor/toolbox.git
cd toolbox

if [ ! -f ~/.ssh/id_*.pub ]; then
    ssh-keygen -t rsa -b 4096 -C 'git@github.com'
fi

while [[ "$(ssh -T git@github.com 2>&1)" != *"You've successfully authenticated, but GitHub does not provide shell access." ]] ; do
    echo
    cat ~/.ssh/id_*.pub
    echo
    read -p 'add pub key to https://github.com/settings/keys then hit [return] to continue'
done

swift build -c release

I'm sorry for the steps requiring a github account, it might be possible to use the https protocol instead of ssh for that dependency, but I wanted to do this without patching the repo.

@belkadan
Copy link

cc @aciidb0mb3r

@ankitspd
Copy link
Member

Can you share the dump with dropbox or something? Or maybe file a radar?

@swift-ci
Copy link
Contributor Author

Comment by Camden Narzt (JIRA)

Sure thing: https://www.dropbox.com/sh/aalj240hzjgcl9r/AABHKXtA_dDhB2QJ1ebAwx2ha?dl=0

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
@shahmishal shahmishal transferred this issue from apple/swift May 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants