Cloudflare Workers throws error with latest wrangler

Problem description: If you update wrangler in the cloudflare workers template to the latest version, ^3.15.0, the console throws an error as follows:

workerd/util/symbolizer.c++:98: warning: Not symbolizing stack traces because $LLVM_SYMBOLIZER is not set. To symbolize stack traces, set $LLVM_SYMBOLIZER to the location of the llvm-symbolizer binary. When running tests under bazel, use `--test_env=LLVM_SYMBOLIZER=<path>`.
workerd/server/server.c++:2885: error: Uncaught exception: kj/compat/url.c++:165: failed: expected tryParse(url, context, options) != nullptr; invalid URL; url = *
stack:

Expected behavior: Should just work with latest version on wrangler.

Actual behavior: doesn’t work.

Steps to reproduce: just upgrade per above

Bug appears at this link:

Plan (Free, Hacker, Pro Plan): Hacker

1 Like

Make sure you have llvm-symbolizer installed. If it’s already installed, locate the llvm-symbolizer binary. Typically, you can find it by searching in the terminal with commands like which llvm-symbolizer or find / -name llvm-symbolizer. Once you have the path, set the $LLVM_SYMBOLIZER environment variable accordingly. For instance, in a bash shell, you would use the following command:

export LLVM_SYMBOLIZER=/path/to/llvm-symbolizer
1 Like

Thanks. When I run the find command, I get the error below:

find: ‘/var/cache/ldconfig’: Permission denied
find: ‘/var/cache/apt/archives/partial’: Permission denied
find: ‘/proc/tty/driver’: Permission denied
find: ‘/etc/ssl/private’: Permission denied
1 Like

Hello! I’m unable to reproduce the issue in a brand new Cloudflare Workers Repl. Can you share the Repl URL with me so I can diagnose the issue a little more closely? Thanks!

1 Like

Sorry, no, it is private. But I can assure you the error is there on the latest wrangler version, “wrangler”: “^3.15.0”. I’m not sure why you can’t recreate it. I recreated it a few times today. Just use the Replit Cloudflare Workers template and then upgrade Wrangler and when you run the Replit you will see an error Not symbolizing stack traces because $LLVM_SYMBOLIZER is not set. To symbolize stack traces, set $LLVM_SYMBOLIZER to the location of the llvm-symbolizer binary. When running tests under bazel, Anyway, i guess it doesn’t matter, as all the other wrangler functionality works fine and we can deploy to cloudflare without any problems.

I experienced this.

On MacOS I resolved it with:

brew install llvm
echo 'export PATH="/usr/local/opt/llvm/bin:$PATH"' >> /Users/{username}/.bash_profile
export LLVM_SYMBOLIZER=/usr/local/opt/llvm/bin/llvm-symbolizer

It now spews out lots of

?? at ??:0:0 messages during build.