==> Building on shinx ==> Checking for remote environment... ==> Syncing package to remote host... sending incremental file list created directory packages/trurl ./ .SRCINFO 428 100% 0.00kB/s 0:00:00 428 100% 0.00kB/s 0:00:00 (xfr#1, to-chk=3/5) .nvchecker.toml 85 100% 83.01kB/s 0:00:00 85 100% 83.01kB/s 0:00:00 (xfr#2, to-chk=2/5) PKGBUILD 820 100% 800.78kB/s 0:00:00 820 100% 800.78kB/s 0:00:00 (xfr#3, to-chk=1/5) trurl-0.12-1.log 228 100% 222.66kB/s 0:00:00 228 100% 222.66kB/s 0:00:00 (xfr#4, to-chk=0/5) sent 1,281 bytes received 132 bytes 565.20 bytes/sec total size is 1,525 speedup is 1.08 ==> Patching arch to riscv64... ==> Running extra-riscv64-build -- -d /home/felix/packages/riscv64-pkg-cache:/var/cache/pacman/pkg -l root28 on remote host... [?25l:: Synchronizing package databases... core downloading... extra downloading... :: Starting full system upgrade... resolving dependencies... looking for conflicting packages... Package (1) Old Version New Version Net Change Download Size core/gmp 6.3.0-1 6.3.0-2 0.00 MiB 0.40 MiB Total Download Size: 0.40 MiB Total Installed Size: 0.75 MiB Net Upgrade Size: 0.00 MiB :: Proceed with installation? [Y/n] :: Retrieving packages... gmp-6.3.0-2-riscv64 downloading... checking keyring... checking package integrity... loading package files... checking for file conflicts... :: Processing package changes... upgrading gmp... :: Running post-transaction hooks... (1/1) Updating the info directory file... [?25h==> Building in chroot for [extra] (riscv64)... ==> Synchronizing chroot copy [/var/lib/archbuild/extra-riscv64/root] -> [root28]...done ==> Making package: trurl 0.12-1 (Fri Apr 19 05:56:06 2024) ==> Retrieving sources...  -> Downloading trurl-0.12.tar.gz... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 10088 0 10088 0 0 21350 0 --:--:-- --:--:-- --:--:-- 21350 100 45860 0 45860 0 0 87105 0 --:--:-- --:--:-- --:--:-- 659k ==> Validating source files with sha256sums... trurl-0.12.tar.gz ... Passed ==> Making package: trurl 0.12-1 (Fri Apr 19 05:56:18 2024) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Installing missing dependencies... [?25lresolving dependencies... looking for conflicting packages... Package (4) New Version Net Change Download Size core/debuginfod 0.191-1 0.28 MiB core/libmicrohttpd 1.0.1-1 0.56 MiB core/python 3.11.8-1 107.82 MiB extra/valgrind 3.22.0-3 18.79 MiB 3.11 MiB Total Download Size: 3.11 MiB Total Installed Size: 127.46 MiB :: Proceed with installation? [Y/n] :: Retrieving packages... valgrind-3.22.0-3-riscv64 downloading... checking keyring... checking package integrity... loading package files... checking for file conflicts... :: Processing package changes... installing python... Optional dependencies for python python-setuptools: for building Python packages using tooling that is usually bundled with Python python-pip: for installing Python packages using tooling that is usually bundled with Python python-pipx: for installing Python software not packaged on Arch Linux sqlite: for a default database integration [installed] mpdecimal: for decimal xz: for lzma [installed] tk: for tkinter installing libmicrohttpd... installing debuginfod... Optional dependencies for debuginfod elfutils=0.191: for translations installing valgrind... Optional dependencies for valgrind python: cg_* scripts [installed] :: Running post-transaction hooks... (1/1) Updating the info directory file... [?25h==> Retrieving sources...  -> Found trurl-0.12.tar.gz ==> WARNING: Skipping all source file integrity checks. ==> Extracting sources...  -> Extracting trurl-0.12.tar.gz with bsdtar ==> Starting build()... cc -march=rv64gc -mabi=lp64d -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security -fstack-clash-protection -g -ffile-prefix-map=/build/trurl/src=/usr/src/debug/trurl -flto=auto $(curl-config --cflags) -W -Wall -Wshadow -Werror -pedantic -Wconversion -Wmissing-prototypes -Wwrite-strings -Wsign-compare -Wno-sign-conversion -g -c -o trurl.o trurl.c cc trurl.o -o trurl -Wl,-O1 -Wl,--sort-common -Wl,--as-needed -Wl,-z,relro -Wl,-z,now -flto=auto $(curl-config --libs) ==> Starting check()... 1: passed example.com 2: passed http://example.com 3: passed https://example.com 4: passed hp://example.com 5: passed 6: passed ftp.example.com 7: passed https://example.com/../moo 8: passed https://example.com/.././moo 9: passed https://example.com/test/../moo 10: passed localhost --append path=moo 11: passed localhost -a path=moo 12: passed --set host=moo --set scheme=http 13: passed -s host=moo -s scheme=http 14: passed --set host=moo --set scheme=https --set port=999 15: passed --set host=moo --set scheme=ftps --set path=/hello 16: passed --url https://curl.se --set host=example.com 17: passed --set host=example.com --set scheme=ftp 18: passed --url https://curl.se/we/are.html --redirect here.html 19: passed --url https://curl.se/we/../are.html --set port=8080 20: passed imap://curl.se:22/ -s port=143 21: passed --keep-port https://curl.se:22/ -s port=443 22: passed --keep-port https://curl.se:22/ -s port=443 --get '{url}' 23: passed --url https://curl.se/we/are.html --get '{path}' 24: passed --default-port --url imap://curl.se/we/are.html --get '{port}' 25: passed --url https://curl.se/we/are.html --get '{scheme}' 26: passed --url https://hello@curl.se/we/are.html --get '{user}' 27: passed --url https://hello:secret@curl.se/we/are.html --get '{password}' 28: passed --url 'imap://hello:secret;crazy@curl.se/we/are.html' --get '{options}' 29: passed --url https://curl.se/we/are.html --get '{host}' 30: passed --url https://10.1/we/are.html --get '{host}' 31: passed --url 'https://[fe80::0000:20c:29ff:fe9c:409b]:8080/we/are.html' --get '{host}' 32: passed --url 'https://[fe80::0000:20c:29ff:fe9c:409b%euth0]:8080/we/are.html' --get '{zoneid}' 33: passed --url 'https://[fe80::0000:20c:29ff:fe9c:409b%eth0]:8080/we/are.html' --get '{zoneid}' 34: passed --url 'https://curl.se/we/are.html?user=many#more' --get '{query}' 35: passed --url 'https://curl.se/we/are.html?user=many#more' --get '{fragment}' 36: passed --url imap://curl.se/we/are.html -g '{default:port}' 37: passed --url https://curl.se/hello --append path=you 38: passed --url https://curl.se/hello --append 'path=you index.html' 39: passed --url 'https://curl.se?name=hello' --append query=search=string 40: passed --url https://curl.se/hello --set user=:hej: 41: passed --url https://curl.se/hello --set user=hej --set password=secret 42: passed --url https://curl.se/hello --set query:=user=me 43: passed --url https://curl.se/hello --set query=user=me 44: passed --url https://curl.se/hello --set 'fragment= hello' 45: passed --url https://curl.se/hello --set fragment:=%20hello 46: passed localhost --append query=hello=foo 47: passed localhost -a query=hello=foo 48: passed 'https://example.com?search=hello&utm_source=tracker' --trim 'query=utm_*' 49: passed 'https://example.com?search=hello&utm_source=tracker&more=data' --trim 'query=utm_*' 50: passed 'https://example.com?search=hello&more=data' --trim 'query=utm_*' 51: passed 'https://example.com?utm_source=tracker' --trim 'query=utm_*' 52: passed 'https://example.com?search=hello&utm_source=tracker&more=data' --trim query=utm_source 53: passed 'https://example.com?search=hello&utm_source=tracker&more=data' --trim query=utm_source --trim query=more --trim query=search 54: passed --accept-space --url 'gopher://localhost/ with space' 55: passed --accept-space --url 'https://localhost/?with space' 56: passed https://daniel@curl.se:22/ -s port= -s user= 57: passed 'https://example.com?moo&search=hello' --trim query=search 58: passed 'https://example.com?search=hello&moo' --trim query=search 59: passed 'https://example.com?search=hello' --trim query=search --append query=moo 60: passed --keep-port https://hello:443/foo 61: passed --keep-port ftp://hello:21/foo 62: passed https://hello:443/foo -s scheme=ftp 63: passed --keep-port ftp://hello:443/foo -s scheme=https 64: passed 'https://example.com?utm_source=tra%20cker&address%20=home&here=now&thisthen' -g '{query:utm_source}' 65: passed 'https://example.com?utm_source=tra%20cker&address%20=home&here=now&thisthen' -g '{:query:utm_source}' 66: passed 'https://example.com?utm_source=tra%20cker&address%20=home&here=now&thisthen' -g '{:query:utm_}' 67: passed 'https://example.com?utm_source=tra%20cker&address%20=home&here=now&thisthen' -g '{:query:UTM_SOURCE}' 68: passed 'https://example.com?utm_source=tracker&monkey=123' --sort-query 69: passed 'https://example.com?a=b&c=d&' --sort-query 70: passed 'https://example.com?a=b&c=d&' --sort-query --trim query=a 71: passed example.com:29 --set port= 72: passed --url HTTPS://example.com 73: passed --url https://EXAMPLE.com 74: passed --url https://example.com/FOO/BAR 75: passed --url '[2001:0db8:0000:0000:0000:ff00:0042:8329]' 76: passed 'https://example.com?utm=tra%20cker:address%20=home:here=now:thisthen' --sort-query --query-separator : 77: passed 'foo?a=bCd=eCe=f' --query-separator C --trim query=d 78: passed localhost -g '{scheme} {host' 79: passed localhost -g '[scheme] [host' 80: passed localhost -g '\{{scheme}\[' 81: passed localhost -g '\\[' 82: passed 'https://u:s@foo?moo' -g '[scheme][user][password][query]' 83: passed 'hej?a=b&a=c&a=d&b=a' -g '{query-all:a}' 84: passed 'https://curl.se?name=mr%00smith' --get '{query:name}' 85: passed --keep-port https://curl.se --iterate 'port=80 81 443' 86: passed https://curl.se --iterate 'port=81 443' --iterate 'scheme=sftp moo' 87: passed https://curl.se --iterate 'port=81 443' --iterate 'scheme=sftp moo' --iterate 'port=2 1' 88: passed https://curl.se -s host=localhost --iterate 'port=22 23' 89: passed hello@localhost --iterate 'host=one two' -g '{host} {user}' 90: passed 'https://example.com?utm=tra%20cker&address%20=home&here=now&thisthen' --json 91: passed 'ftp://smith:secret@example.com:33/path?search=me#where' --json 92: passed example.com --json 93: passed example.com other.com --json 94: passed localhost --iterate 'host=one two' --json 95: passed --json -s scheme=irc -s host=curl.se 96: passed --json -s host=curl.se 97: passed --verify --json ftp://example.org '' git://curl.se/ 98: passed -s scheme=imap 99: passed -g '{query:}' 'http://localhost/?=bar' 100: passed --json 'https://curl.se/?&&&' 101: passed --json --trim 'query=f*' 'localhost?foo&bar=ar' 102: passed 'https://example.com?search=hello&utm_source=tracker&utm_block&testing' --trim 'query=utm_*' --json 103: passed 'https://räksmörgås.se' -g '{default:puny:url}' 104: passed 'https://räksmörgås.se' -g '{puny:url}' 105: passed 'https://räksmörgås.se' -g '{puny:host}' 106: passed 'imap://user:password;crazy@[ff00::1234%hello]:1234/path?a=b&c=d#fragment' --json 107: passed imap://example.com/ --get 'port: {port}, default:port: {default:port}' 108: passed http://example.com:8080/ --get 'port: {port}, default:port: {default:port}' 109: passed localhost -s host=foo --iterate 'host=bar baz' 110: passed emanuele6://curl.se/trurl '' https://example.org 111: passed --verify --no-guess-scheme hello 112: passed --verify -f testfiles/test0000.txt 113: passed -f testfiles/test0001.txt 114: passed --no-guess-scheme foo hi https://example.org hey git://curl.se 115: passed -f testfiles/test0002.txt --json 116: passed --accept-space -s 'query:=x=10&x=2 3' localhost 117: passed -s 'path=\\' -g '{path}\n{:path}' localhost 118: passed -s 'path=\\' --json localhost 119: passed -s 'path=\\' -g '{path}\n{:path}' --urlencode localhost 120: passed -s 'path=abc\\' -s 'query:=a&b&a%26b' --urlencode --json localhost 121: passed -s scheme:=http -s host:=localhost -s path:=/ABC%5C%5C -s 'query:=a&b&a%26b' 122: passed -g '{query:b}\t{query-all:a}\n{:query:b}\t{:query-all:a}' 'https://example.org/foo?a=1&b=%23&a=%26#hello' 123: passed --urlencode -g '{query:b}\t{query-all:a}\n{:query:b}\t{:query-all:a}' 'https://example.org/foo?a=1&b=%23&a=%26#hello' 124: passed -a query=c=moo --sort-query 'https://example.org/foo?x=hi#rye' 125: passed --trim query=a -a query=a=ciao -a query=b=salve 'https://example.org/foo?a=hi&b=hello&x=y' 126: passed 'http://example.com/?q=mr%00smith' --json 127: passed 'http://example.com/?q=mr%00sm%00ith' --json 128: passed 'http://example.com/?q=mr%00%00%00smith' --json 129: passed --url 'https://curl.se/we/are.html?*=moo&user=many#more' --trim 'query=\*' 130: passed --url http://xn--rksmrgs-5wao1o/ --as-idn 131: passed --url http://xn--rksmrgs-5wao1o/ -g '{idn:host}' 132: passed --url http://xn-----/ --as-idn --quiet 133: passed --url http://xn-----/ --as-idn 134: passed --verify -f testfiles/test0000.txt --quiet 135: passed --curl --verify foo://bar 136: passed 'http://test.org/?key=val' --replace key=foo 137: passed 'http://test.org/?that=thing&key=val' --replace key=foo 138: passed 'http://test.org/?that=thing&key' --replace key=foo 139: passed 'http://test.org/?that=thing&key=foo' --replace key 140: passed 'https://example.com?a=123&b=321&b=987' --replace b=foo 141: passed 'example.org/?quest=best' --replace quest=%00 --json 142: passed example.com --replace 143: passed 'http://test.org/?that=thing' --force-replace key=foo 144: passed '0?00%000000000000000000000=0000000000' 145: passed --json '0?0%000000000000000000000000000000000' 146: passed --json '0?0%000000000000000000000000000000000=000%0000000000' 147: passed example.com --set 'host=[::1]' Finished: Passed! - Failed: 0, Passed: 147, Skipped: 0, Total: 147 1: failed example.com --- stdout --- expected: 'http://example.com/\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 2: failed http://example.com --- stdout --- expected: 'http://example.com/\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 3: failed https://example.com --- stdout --- expected: 'https://example.com/\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 4: failed hp://example.com --- stdout --- expected: 'hp://example.com/\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 5: failed  --- stdout --- expected: '' got: '' --- stderr --- expected: 'trurl error: not enough input for a URL\ntrurl error: Try trurl -h for help\n' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 7 got: 1 6: failed ftp.example.com --- stdout --- expected: 'ftp://ftp.example.com/\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 7: failed https://example.com/../moo --- stdout --- expected: 'https://example.com/moo\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 8: failed https://example.com/.././moo --- stdout --- expected: 'https://example.com/moo\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 9: failed https://example.com/test/../moo --- stdout --- expected: 'https://example.com/moo\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 10: failed localhost --append path=moo --- stdout --- expected: 'http://localhost/moo\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 11: failed localhost -a path=moo --- stdout --- expected: 'http://localhost/moo\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 12: failed --set host=moo --set scheme=http --- stdout --- expected: 'http://moo/\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 13: failed -s host=moo -s scheme=http --- stdout --- expected: 'http://moo/\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 14: failed --set host=moo --set scheme=https --set port=999 --- stdout --- expected: 'https://moo:999/\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 15: failed --set host=moo --set scheme=ftps --set path=/hello --- stdout --- expected: 'ftps://moo/hello\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 16: failed --url https://curl.se --set host=example.com --- stdout --- expected: 'https://example.com/\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 17: failed --set host=example.com --set scheme=ftp --- stdout --- expected: 'ftp://example.com/\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 18: failed --url https://curl.se/we/are.html --redirect here.html --- stdout --- expected: 'https://curl.se/we/here.html\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 19: failed --url https://curl.se/we/../are.html --set port=8080 --- stdout --- expected: 'https://curl.se:8080/are.html\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 20: failed imap://curl.se:22/ -s port=143 --- stdout --- expected: 'imap://curl.se/\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 21: failed --keep-port https://curl.se:22/ -s port=443 --- stdout --- expected: 'https://curl.se:443/\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 22: failed --keep-port https://curl.se:22/ -s port=443 --get '{url}' --- stdout --- expected: 'https://curl.se:443/\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 23: failed --url https://curl.se/we/are.html --get '{path}' --- stdout --- expected: '/we/are.html\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 24: failed --default-port --url imap://curl.se/we/are.html --get '{port}' --- stdout --- expected: '143\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 25: failed --url https://curl.se/we/are.html --get '{scheme}' --- stdout --- expected: 'https\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 26: failed --url https://hello@curl.se/we/are.html --get '{user}' --- stdout --- expected: 'hello\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 27: failed --url https://hello:secret@curl.se/we/are.html --get '{password}' --- stdout --- expected: 'secret\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 28: failed --url 'imap://hello:secret;crazy@curl.se/we/are.html' --get '{options}' --- stdout --- expected: 'crazy\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 29: failed --url https://curl.se/we/are.html --get '{host}' --- stdout --- expected: 'curl.se\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 30: failed --url https://10.1/we/are.html --get '{host}' --- stdout --- expected: '10.0.0.1\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 31: failed --url 'https://[fe80::0000:20c:29ff:fe9c:409b]:8080/we/are.html' --get '{host}' --- stdout --- expected: '[fe80::20c:29ff:fe9c:409b]\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 32: failed --url 'https://[fe80::0000:20c:29ff:fe9c:409b%euth0]:8080/we/are.html' --get '{zoneid}' --- stdout --- expected: 'euth0\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 33: failed --url 'https://[fe80::0000:20c:29ff:fe9c:409b%eth0]:8080/we/are.html' --get '{zoneid}' --- stdout --- expected: 'eth0\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 34: failed --url 'https://curl.se/we/are.html?user=many#more' --get '{query}' --- stdout --- expected: 'user=many\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 35: failed --url 'https://curl.se/we/are.html?user=many#more' --get '{fragment}' --- stdout --- expected: 'more\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 36: failed --url imap://curl.se/we/are.html -g '{default:port}' --- stdout --- expected: '143\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 37: failed --url https://curl.se/hello --append path=you --- stdout --- expected: 'https://curl.se/hello/you\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 38: failed --url https://curl.se/hello --append 'path=you index.html' --- stdout --- expected: 'https://curl.se/hello/you%20index.html\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 39: failed --url 'https://curl.se?name=hello' --append query=search=string --- stdout --- expected: 'https://curl.se/?name=hello&search=string\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 40: failed --url https://curl.se/hello --set user=:hej: --- stdout --- expected: 'https://%3ahej%3a@curl.se/hello\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 41: failed --url https://curl.se/hello --set user=hej --set password=secret --- stdout --- expected: 'https://hej:secret@curl.se/hello\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 42: failed --url https://curl.se/hello --set query:=user=me --- stdout --- expected: 'https://curl.se/hello?user=me\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 43: failed --url https://curl.se/hello --set query=user=me --- stdout --- expected: 'https://curl.se/hello?user%3dme\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 44: failed --url https://curl.se/hello --set 'fragment= hello' --- stdout --- expected: 'https://curl.se/hello#%20hello\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 45: failed --url https://curl.se/hello --set fragment:=%20hello --- stdout --- expected: 'https://curl.se/hello#%20hello\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 46: failed localhost --append query=hello=foo --- stdout --- expected: 'http://localhost/?hello=foo\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 47: failed localhost -a query=hello=foo --- stdout --- expected: 'http://localhost/?hello=foo\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 48: failed 'https://example.com?search=hello&utm_source=tracker' --trim 'query=utm_*' --- stdout --- expected: 'https://example.com/?search=hello\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 49: failed 'https://example.com?search=hello&utm_source=tracker&more=data' --trim 'query=utm_*' --- stdout --- expected: 'https://example.com/?search=hello&more=data\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 50: failed 'https://example.com?search=hello&more=data' --trim 'query=utm_*' --- stdout --- expected: 'https://example.com/?search=hello&more=data\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 51: failed 'https://example.com?utm_source=tracker' --trim 'query=utm_*' --- stdout --- expected: 'https://example.com/\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 52: failed 'https://example.com?search=hello&utm_source=tracker&more=data' --trim query=utm_source --- stdout --- expected: 'https://example.com/?search=hello&more=data\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 53: failed 'https://example.com?search=hello&utm_source=tracker&more=data' --trim query=utm_source --trim query=more --trim query=search --- stdout --- expected: 'https://example.com/\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 54: failed --accept-space --url 'gopher://localhost/ with space' --- stdout --- expected: 'gopher://localhost/%20with%20space\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 55: failed --accept-space --url 'https://localhost/?with space' --- stdout --- expected: 'https://localhost/?with+space\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 56: failed https://daniel@curl.se:22/ -s port= -s user= --- stdout --- expected: 'https://curl.se/\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 57: failed 'https://example.com?moo&search=hello' --trim query=search --- stdout --- expected: 'https://example.com/?moo\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 58: failed 'https://example.com?search=hello&moo' --trim query=search --- stdout --- expected: 'https://example.com/?moo\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 59: failed 'https://example.com?search=hello' --trim query=search --append query=moo --- stdout --- expected: 'https://example.com/?moo\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 60: failed --keep-port https://hello:443/foo --- stdout --- expected: 'https://hello:443/foo\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 61: failed --keep-port ftp://hello:21/foo --- stdout --- expected: 'ftp://hello:21/foo\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 62: failed https://hello:443/foo -s scheme=ftp --- stdout --- expected: 'ftp://hello:443/foo\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 63: failed --keep-port ftp://hello:443/foo -s scheme=https --- stdout --- expected: 'https://hello:443/foo\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 64: failed 'https://example.com?utm_source=tra%20cker&address%20=home&here=now&thisthen' -g '{query:utm_source}' --- stdout --- expected: 'tra cker\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 65: failed 'https://example.com?utm_source=tra%20cker&address%20=home&here=now&thisthen' -g '{:query:utm_source}' --- stdout --- expected: 'tra%20cker\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 66: failed 'https://example.com?utm_source=tra%20cker&address%20=home&here=now&thisthen' -g '{:query:utm_}' --- stdout --- expected: '\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 67: failed 'https://example.com?utm_source=tra%20cker&address%20=home&here=now&thisthen' -g '{:query:UTM_SOURCE}' --- stdout --- expected: '\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 68: failed 'https://example.com?utm_source=tracker&monkey=123' --sort-query --- stdout --- expected: 'https://example.com/?monkey=123&utm_source=tracker\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 69: failed 'https://example.com?a=b&c=d&' --sort-query --- stdout --- expected: 'https://example.com/?a=b&c=d\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 70: failed 'https://example.com?a=b&c=d&' --sort-query --trim query=a --- stdout --- expected: 'https://example.com/?c=d\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 71: failed example.com:29 --set port= --- stdout --- expected: 'http://example.com/\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 72: failed --url HTTPS://example.com --- stdout --- expected: 'https://example.com/\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 73: failed --url https://EXAMPLE.com --- stdout --- expected: 'https://EXAMPLE.com/\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 74: failed --url https://example.com/FOO/BAR --- stdout --- expected: 'https://example.com/FOO/BAR\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 75: failed --url '[2001:0db8:0000:0000:0000:ff00:0042:8329]' --- stdout --- expected: 'http://[2001:db8::ff00:42:8329]/\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 76: failed 'https://example.com?utm=tra%20cker:address%20=home:here=now:thisthen' --sort-query --query-separator : --- stdout --- expected: 'https://example.com/?address%20=home:here=now:thisthen:utm=tra%20cker\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 77: failed 'foo?a=bCd=eCe=f' --query-separator C --trim query=d --- stdout --- expected: 'http://foo/?a=bCe=f\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 78: failed localhost -g '{scheme} {host' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 --- stdout --- expected: 'http {host\n' got: '' 79: failed localhost -g '[scheme] [host' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 --- stdout --- expected: 'http [host\n' got: '' 80: failed localhost -g '\{{scheme}\[' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 --- stdout --- expected: '{http[\n' got: '' 81: failed localhost -g '\\[' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 --- stdout --- expected: '\\[\n' got: '' 82: failed 'https://u:s@foo?moo' -g '[scheme][user][password][query]' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 --- stdout --- expected: 'httpsusmoo\n' got: '' 83: failed 'hej?a=b&a=c&a=d&b=a' -g '{query-all:a}' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 --- stdout --- expected: 'b c d\n' got: '' 84: failed 'https://curl.se?name=mr%00smith' --get '{query:name}' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 --- stdout --- expected: 'mr.smith\n' got: '' 85: failed --keep-port https://curl.se --iterate 'port=80 81 443' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 --- stdout --- expected: 'https://curl.se:80/\nhttps://curl.se:81/\nhttps://curl.se:443/\n' got: '' 86: failed https://curl.se --iterate 'port=81 443' --iterate 'scheme=sftp moo' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 --- stdout --- expected: 'sftp://curl.se:81/\nmoo://curl.se:81/\nsftp://curl.se:443/\nmoo://curl.se:443/\n' got: '' 87: failed https://curl.se --iterate 'port=81 443' --iterate 'scheme=sftp moo' --iterate 'port=2 1' --- stderr --- expected: 'trurl error: duplicate component for iterate: port\ntrurl error: Try trurl -h for help\n' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 11 got: 1 --- stdout --- expected: '' got: '' 88: failed https://curl.se -s host=localhost --iterate 'port=22 23' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 --- stdout --- expected: 'https://localhost:22/\nhttps://localhost:23/\n' got: '' 89: failed hello@localhost --iterate 'host=one two' -g '{host} {user}' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 --- stdout --- expected: 'one hello\ntwo hello\n' got: '' 90: failed 'https://example.com?utm=tra%20cker&address%20=home&here=now&thisthen' --json --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 --- stdout --- expected: [{'url': 'https://example.com/?utm=tra%20cker&address%20=home&here=now&thisthen', 'parts': {'scheme': 'https', 'host': 'example.com', 'path': '/', 'query': 'utm=tra cker&address =home&here=now&thisthen'}, 'params': [{'key': 'utm', 'value': 'tra cker'}, {'key': 'address ', 'value': 'home'}, {'key': 'here', 'value': 'now'}, {'key': 'thisthen', 'value': ''}]}] got: None 91: failed 'ftp://smith:secret@example.com:33/path?search=me#where' --json --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 --- stdout --- expected: [{'url': 'ftp://smith:secret@example.com:33/path?search=me#where', 'parts': {'scheme': 'ftp', 'user': 'smith', 'password': 'secret', 'host': 'example.com', 'port': '33', 'path': '/path', 'query': 'search=me', 'fragment': 'where'}, 'params': [{'key': 'search', 'value': 'me'}]}] got: None 92: failed example.com --json --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 --- stdout --- expected: [{'url': 'http://example.com/', 'parts': {'scheme': 'http', 'host': 'example.com', 'path': '/'}}] got: None 93: failed example.com other.com --json --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 --- stdout --- expected: [{'url': 'http://example.com/', 'parts': {'scheme': 'http', 'host': 'example.com', 'path': '/'}}, {'url': 'http://other.com/', 'parts': {'scheme': 'http', 'host': 'other.com', 'path': '/'}}] got: None 94: failed localhost --iterate 'host=one two' --json --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 --- stdout --- expected: [{'url': 'http://one/', 'parts': {'scheme': 'http', 'host': 'one', 'path': '/'}}, {'url': 'http://two/', 'parts': {'scheme': 'http', 'host': 'two', 'path': '/'}}] got: None 95: failed --json -s scheme=irc -s host=curl.se --- stdout --- expected: [{'url': 'irc://curl.se/', 'parts': {'scheme': 'irc', 'host': 'curl.se', 'path': '/'}}] got: None --- returncode --- expected: 0 got: 1 --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" 96: failed --json -s host=curl.se --- stdout --- expected: [] got: None --- returncode --- expected: 7 got: 1 --- stderr --- expected: 'trurl error: not enough input for a URL\ntrurl error: Try trurl -h for help\n' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" 97: failed --verify --json ftp://example.org '' git://curl.se/ --- stdout --- expected: [{'url': 'ftp://example.org/', 'parts': {'scheme': 'ftp', 'host': 'example.org', 'path': '/'}}] got: None --- returncode --- expected: 9 got: 1 --- stderr --- expected: something got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" 98: failed -s scheme=imap --- stdout --- expected: '' got: '' --- returncode --- expected: 7 got: 1 --- stderr --- expected: 'trurl error: not enough input for a URL\ntrurl error: Try trurl -h for help\n' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" 99: failed -g '{query:}' 'http://localhost/?=bar' --- stdout --- expected: 'bar\n' got: '' --- returncode --- expected: 0 got: 1 --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" 100: failed --json 'https://curl.se/?&&&' --- stdout --- expected: [{'url': 'https://curl.se/?&&&', 'parts': {'scheme': 'https', 'host': 'curl.se', 'path': '/', 'query': '&&&'}, 'params': []}] got: None --- returncode --- expected: 0 got: 1 --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" 101: failed --json --trim 'query=f*' 'localhost?foo&bar=ar' --- stdout --- expected: [{'url': 'http://localhost/?bar=ar', 'parts': {'scheme': 'http', 'host': 'localhost', 'path': '/', 'query': 'bar=ar'}, 'params': [{'key': 'bar', 'value': 'ar'}]}] got: None --- returncode --- expected: 0 got: 1 --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" 102: failed 'https://example.com?search=hello&utm_source=tracker&utm_block&testing' --trim 'query=utm_*' --json --- stdout --- expected: [{'url': 'https://example.com/?search=hello&testing', 'parts': {'scheme': 'https', 'host': 'example.com', 'path': '/', 'query': 'search=hello&testing'}, 'params': [{'key': 'search', 'value': 'hello'}, {'key': 'testing', 'value': ''}]}] got: None --- returncode --- expected: 0 got: 1 --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" 103: failed 'https://räksmörgås.se' -g '{default:puny:url}' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 --- stdout --- expected: 'https://xn--rksmrgs-5wao1o.se:443/\n' got: '' 104: failed 'https://räksmörgås.se' -g '{puny:url}' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 --- stdout --- expected: 'https://xn--rksmrgs-5wao1o.se/\n' got: '' 105: failed 'https://räksmörgås.se' -g '{puny:host}' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 --- stdout --- expected: 'xn--rksmrgs-5wao1o.se\n' got: '' 106: failed 'imap://user:password;crazy@[ff00::1234%hello]:1234/path?a=b&c=d#fragment' --json --- returncode --- expected: 0 got: 1 --- stdout --- expected: [{'url': 'imap://user:password;crazy@[ff00::1234%25hello]:1234/path?a=b&c=d#fragment', 'parts': {'scheme': 'imap', 'user': 'user', 'password': 'password', 'options': 'crazy', 'host': '[ff00::1234]', 'port': '1234', 'path': '/path', 'query': 'a=b&c=d', 'fragment': 'fragment', 'zoneid': 'hello'}, 'params': [{'key': 'a', 'value': 'b'}, {'key': 'c', 'value': 'd'}]}] got: None 107: failed imap://example.com/ --get 'port: {port}, default:port: {default:port}' --- returncode --- expected: 0 got: 1 --- stdout --- expected: 'port: , default:port: 143\n' got: '' 108: failed http://example.com:8080/ --get 'port: {port}, default:port: {default:port}' --- returncode --- expected: 0 got: 1 --- stdout --- expected: 'port: 8080, default:port: 8080\n' got: '' 109: failed localhost -s host=foo --iterate 'host=bar baz' --- stdout --- expected: '' got: '' --- returncode --- expected: 11 got: 1 --- stderr --- expected: 'trurl error: duplicate --iterate and --set for component host\ntrurl error: Try trurl -h for help\n' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" 110: failed emanuele6://curl.se/trurl '' https://example.org --- stdout --- expected: 'emanuele6://curl.se/trurl\nhttps://example.org/\n' got: '' --- returncode --- expected: 0 got: 1 --- stderr --- expected: something got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" 111: failed --verify --no-guess-scheme hello --- stdout --- expected: '' got: '' --- returncode --- expected: 9 got: 1 --- stderr --- expected: 'trurl error: Bad scheme [hello]\ntrurl error: Try trurl -h for help\n' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" 112: failed --verify -f testfiles/test0000.txt --- stdout --- expected: 'http://example.org/\n' got: '' --- returncode --- expected: 0 got: 1 --- stderr --- expected: 'trurl note: skipping long line\n' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" 113: failed -f testfiles/test0001.txt --- stdout --- expected: 'https://curl.se/\nhttps://docs.python.org/\ngit://github.com/curl/curl.git\nhttp://example.org/\nxyz://hello/?hi\n' got: '' --- returncode --- expected: 0 got: 1 --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" 114: failed --no-guess-scheme foo hi https://example.org hey git://curl.se --- stdout --- expected: 'https://example.org/\ngit://curl.se/\n' got: '' --- returncode --- expected: 0 got: 1 --- stderr --- expected: 'trurl note: Bad scheme [foo]\ntrurl note: Bad scheme [hi]\ntrurl note: Bad scheme [hey]\n' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" 115: failed -f testfiles/test0002.txt --json --- stdout --- expected: '[]\n' got: '' --- returncode --- expected: 0 got: 1 --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" 116: failed --accept-space -s 'query:=x=10&x=2 3' localhost --- stdout --- expected: 'http://localhost/?x=10&x=2+3\n' got: '' --- returncode --- expected: 0 got: 1 --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" 117: failed -s 'path=\\' -g '{path}\n{:path}' localhost --- stdout --- expected: '/\\\\\n/%5c%5c\n' got: '' --- returncode --- expected: 0 got: 1 --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" 118: failed -s 'path=\\' --json localhost --- stdout --- expected: [{'url': 'http://localhost/%5c%5c', 'parts': {'scheme': 'http', 'host': 'localhost', 'path': '/\\\\'}}] got: None --- returncode --- expected: 0 got: 1 --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" 119: failed -s 'path=\\' -g '{path}\n{:path}' --urlencode localhost --- stdout --- expected: '/%5c%5c\n/%5c%5c\n' got: '' --- returncode --- expected: 0 got: 1 --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" 120: failed -s 'path=abc\\' -s 'query:=a&b&a%26b' --urlencode --json localhost --- stdout --- expected: [{'url': 'http://localhost/abc%5c%5c?a&b&a%26b', 'parts': {'scheme': 'http', 'host': 'localhost', 'path': '/abc%5c%5c', 'query': 'a&b&a%26b'}, 'params': [{'key': 'a', 'value': ''}, {'key': 'b', 'value': ''}, {'key': 'a&b', 'value': ''}]}] got: None --- returncode --- expected: 0 got: 1 --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" 121: failed -s scheme:=http -s host:=localhost -s path:=/ABC%5C%5C -s 'query:=a&b&a%26b' --- stdout --- expected: 'http://localhost/ABC%5c%5c?a&b&a%26b\n' got: '' --- returncode --- expected: 0 got: 1 --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" 122: failed -g '{query:b}\t{query-all:a}\n{:query:b}\t{:query-all:a}' 'https://example.org/foo?a=1&b=%23&a=%26#hello' --- stdout --- expected: '#\t1 &\n%23\t1 %26\n' got: '' --- returncode --- expected: 0 got: 1 --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" 123: failed --urlencode -g '{query:b}\t{query-all:a}\n{:query:b}\t{:query-all:a}' 'https://example.org/foo?a=1&b=%23&a=%26#hello' --- stdout --- expected: '%23\t1 %26\n%23\t1 %26\n' got: '' --- returncode --- expected: 0 got: 1 --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" 124: failed -a query=c=moo --sort-query 'https://example.org/foo?x=hi#rye' --- stdout --- expected: 'https://example.org/foo?c=moo&x=hi#rye\n' got: '' --- returncode --- expected: 0 got: 1 --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" 125: failed --trim query=a -a query=a=ciao -a query=b=salve 'https://example.org/foo?a=hi&b=hello&x=y' --- stdout --- expected: 'https://example.org/foo?b=hello&x=y&a=ciao&b=salve\n' got: '' --- returncode --- expected: 0 got: 1 --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" 126: failed 'http://example.com/?q=mr%00smith' --json --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 --- stdout --- expected: [{'url': 'http://example.com/?q=mr%00smith', 'parts': {'scheme': 'http', 'host': 'example.com', 'path': '/'}, 'params': [{'key': 'q', 'value': 'mr\x00smith'}]}] got: None 127: failed 'http://example.com/?q=mr%00sm%00ith' --json --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 --- stdout --- expected: [{'url': 'http://example.com/?q=mr%00sm%00ith', 'parts': {'scheme': 'http', 'host': 'example.com', 'path': '/'}, 'params': [{'key': 'q', 'value': 'mr\x00sm\x00ith'}]}] got: None 128: failed 'http://example.com/?q=mr%00%00%00smith' --json --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 --- stdout --- expected: [{'url': 'http://example.com/?q=mr%00%00%00smith', 'parts': {'scheme': 'http', 'host': 'example.com', 'path': '/'}, 'params': [{'key': 'q', 'value': 'mr\x00\x00\x00smith'}]}] got: None 129: failed --url 'https://curl.se/we/are.html?*=moo&user=many#more' --trim 'query=\*' --- stdout --- expected: 'https://curl.se/we/are.html?user=many#more\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 130: failed --url http://xn--rksmrgs-5wao1o/ --as-idn --- stdout --- expected: 'http://räksmörgås/\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 131: failed --url http://xn--rksmrgs-5wao1o/ -g '{idn:host}' --- stdout --- expected: 'räksmörgås\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 132: failed --url http://xn-----/ --as-idn --quiet --- stdout --- expected: 'http://xn-----/\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 133: failed --url http://xn-----/ --as-idn --- stdout --- expected: 'http://xn-----/\n' got: '' --- stderr --- expected: 'trurl note: Error converting url to IDN [Bad hostname]\n' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 134: failed --verify -f testfiles/test0000.txt --quiet --- stdout --- expected: 'http://example.org/\n' got: '' --- returncode --- expected: 0 got: 1 --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" 135: failed --curl --verify foo://bar --- stdout --- expected: '' got: '' --- stderr --- expected: something got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 9 got: 1 136: failed 'http://test.org/?key=val' --replace key=foo --- stdout --- expected: 'http://test.org/?key=foo\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 137: failed 'http://test.org/?that=thing&key=val' --replace key=foo --- stdout --- expected: 'http://test.org/?that=thing&key=foo\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 138: failed 'http://test.org/?that=thing&key' --replace key=foo --- stdout --- expected: 'http://test.org/?that=thing&key=foo\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 139: failed 'http://test.org/?that=thing&key=foo' --replace key --- stdout --- expected: 'http://test.org/?that=thing&key\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 140: failed 'https://example.com?a=123&b=321&b=987' --replace b=foo --- stdout --- expected: 'https://example.com/?a=123&b=foo\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 141: failed 'example.org/?quest=best' --replace quest=%00 --json --- stdout --- expected: [{'url': 'http://example.org/?quest=%00', 'parts': {'scheme': 'http', 'host': 'example.org', 'path': '/'}, 'params': [{'key': 'quest', 'value': '\x00'}]}] got: None --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 142: failed example.com --replace --- stderr --- expected: 'trurl error: No data passed to replace component\ntrurl error: Try trurl -h for help\n' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- stdout --- expected: '' got: '' --- returncode --- expected: 12 got: 1 143: failed 'http://test.org/?that=thing' --force-replace key=foo --- stdout --- expected: 'http://test.org/?that=thing&key=foo\n' got: '' --- stderr --- expected: "trurl note: key 'key' not in url, appending to query\n" got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 144: failed '0?00%000000000000000000000=0000000000' --- stdout --- expected: 'http://0.0.0.0/?00%000000000000000000000=0000000000\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 145: failed --json '0?0%000000000000000000000000000000000' --- returncode --- expected: 0 got: 1 --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- stdout --- expected: [{'url': 'http://0.0.0.0/?0%000000000000000000000000000000000', 'parts': {'scheme': 'http', 'host': '0.0.0.0', 'path': '/'}, 'params': [{'key': '0\x000000000000000000000000000000000', 'value': ''}]}] got: None 146: failed --json '0?0%000000000000000000000000000000000=000%0000000000' --- returncode --- expected: 0 got: 1 --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- stdout --- expected: [{'url': 'http://0.0.0.0/?0%000000000000000000000000000000000=000%0000000000', 'parts': {'scheme': 'http', 'host': '0.0.0.0', 'path': '/'}, 'params': [{'key': '0\x000000000000000000000000000000000', 'value': '000\x0000000000'}]}] got: None 147: failed example.com --set 'host=[::1]' --- stdout --- expected: 'http://[::1]/\n' got: '' --- stderr --- expected: '' got: "\nvalgrind: Fatal error at startup: a function redirection\nvalgrind: which is mandatory for this platform-tool combination\nvalgrind: cannot be set up. Details of the redirection are:\nvalgrind: \nvalgrind: A must-be-redirected function\nvalgrind: whose name matches the pattern: index\nvalgrind: in an object with soname matching: ld-linux-riscv64-lp64d.so.1\nvalgrind: was not found whilst processing\nvalgrind: symbols from the object with soname: ld-linux-riscv64-lp64d.so.1\nvalgrind: \nvalgrind: Possible fixes: (1, short term): install glibc's debuginfo\nvalgrind: package on this machine. (2, longer term): ask the packagers\nvalgrind: for your Linux distribution to please in future ship a non-\nvalgrind: stripped ld.so (or whatever the dynamic linker .so is called)\nvalgrind: that exports the above-named function using the standard\nvalgrind: calling conventions for this platform. The package you need\nvalgrind: to install for fix (1) is called\nvalgrind: \nvalgrind: On Debian, Ubuntu: libc6-dbg\nvalgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo\nvalgrind: \nvalgrind: Note that if you are debugging a 32 bit process on a\nvalgrind: 64 bit system, you will need a corresponding 32 bit debuginfo\nvalgrind: package (e.g. libc6-dbg:i386).\nvalgrind: \nvalgrind: Cannot continue -- exiting now. Sorry.\n\n" --- returncode --- expected: 0 got: 1 Finished: Failed! - Failed: 147, Passed: 0, Skipped: 0, Total: 147 make: *** [Makefile:67: test-memory] Error 1 ==> ERROR: A failure occurred in check().  Aborting... ==> ERROR: Build failed, check /var/lib/archbuild/extra-riscv64/root28/build [?25h[?25hreceiving incremental file list trurl-0.12-1-riscv64-build.log trurl-0.12-1-riscv64-check.log sent 62 bytes received 9,527 bytes 2,130.89 bytes/sec total size is 248,496 speedup is 25.91