==> Building on aurorus ==> Checking for remote environment... ==> Syncing package to remote host... sending incremental file list created directory packages/trurl ./ .SRCINFO 606 100% 0.00kB/s 0:00:00 606 100% 0.00kB/s 0:00:00 (xfr#1, to-chk=6/8) .nvchecker.toml 85 100% 83.01kB/s 0:00:00 85 100% 83.01kB/s 0:00:00 (xfr#2, to-chk=5/8) PKGBUILD 911 100% 889.65kB/s 0:00:00 911 100% 889.65kB/s 0:00:00 (xfr#3, to-chk=4/8) trurl-0.16-1.1.log 486 100% 474.61kB/s 0:00:00 486 100% 474.61kB/s 0:00:00 (xfr#4, to-chk=3/8) keys/ keys/pgp/ keys/pgp/27EDEAF22F3ABCEB50DB9A125CC908FDB71E12C2.asc 1,680 100% 1.60MB/s 0:00:00 1,680 100% 1.60MB/s 0:00:00 (xfr#5, to-chk=0/8) sent 2,998 bytes received 163 bytes 2,107.33 bytes/sec total size is 3,476 speedup is 1.10 ==> Ensuring required PGP keys are present...  -> Checking for 27EDEAF22F3ABCEB50DB9A125CC908FDB71E12C2... pub rsa2048 2016-04-07 [SC] 27ED EAF2 2F3A BCEB 50DB 9A12 5CC9 08FD B71E 12C2 uid [ unknown] Daniel Stenberg sub rsa2048 2016-04-07 [E] ==> Patching arch to riscv64... ==> Running pkgctl build --arch riscv64 --repo extra on remote host... ==> WARNING: unsupported architecture: riscv64 ==> Building trurl  -> repo: extra  -> arch: riscv64  -> worker: felix-2 ==> Building trurl for [extra] (riscv64) ==> Locking clean chroot...done ]2;🔵 Container arch-nspawn-416096 on aurorus.felixc.at\[?25l:: Synchronizing package databases... core downloading... extra downloading... :: Starting full system upgrade... there is nothing to do [?25h==> Building in chroot for [extra] (riscv64)... ==> Synchronizing chroot copy [/var/lib/archbuild/extra-riscv64/root] -> [felix-2]...done ==> Making package: trurl 0.16-1.1 (Wed Apr 9 19:25:59 2025) ==> Retrieving sources...  -> Downloading trurl-0.16.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 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 59327 100 59327 0 0 36904 0 0:00:01 0:00:01 --:--:-- 66435  -> Downloading trurl-0.16.tar.gz.asc... % 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 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0 100 488 100 488 0 0 327 0 0:00:01 0:00:01 --:--:-- 1012 ==> Validating source files with sha256sums... trurl-0.16.tar.gz ... Passed trurl-0.16.tar.gz.asc ... Skipped ==> Verifying source file signatures with gpg... trurl-0.16.tar.gz ... Passed ]2;🔵 Container arch-nspawn-417274 on aurorus.felixc.at\==> Making package: trurl 0.16-1.1 (Wed Apr 9 19:26:28 2025) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Installing missing dependencies... [?25lresolving dependencies... looking for conflicting packages... Package (5) New Version Net Change core/debuginfod 0.192-4.1 0.33 MiB core/libmicrohttpd 1.0.1-1 0.56 MiB extra/mpdecimal 4.0.0-2 0.29 MiB core/python 3.13.2-1 108.68 MiB extra/valgrind 3.23.0-5 20.41 MiB Total Installed Size: 130.27 MiB :: Proceed with installation? [Y/n] checking keyring... checking package integrity... loading package files... checking for file conflicts... :: Processing package changes... installing mpdecimal... 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] xz: for lzma [installed] tk: for tkinter installing libmicrohttpd... installing debuginfod... Optional dependencies for debuginfod elfutils=0.192: for translations installing valgrind... Optional dependencies for valgrind python: cg_* scripts [installed] :: Running post-transaction hooks... (1/2) Arming ConditionNeedsUpdate... (2/2) Updating the info directory file... [?25h==> Retrieving sources...  -> Found trurl-0.16.tar.gz  -> Found trurl-0.16.tar.gz.asc ==> WARNING: Skipping all source file integrity checks. ==> Extracting sources...  -> Extracting trurl-0.16.tar.gz with bsdtar ==> Starting build()... cc -march=rv64gc -mabi=lp64d -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security -fstack-clash-protection -fno-omit-frame-pointer -g -ffile-prefix-map=/build/trurl/src=/usr/src/debug/trurl -flto=auto $(curl-config --cflags) -W -Wall -Wshadow -pedantic -Wconversion -Wmissing-prototypes -Wwrite-strings -Wsign-compare -Wno-sign-conversion -Werror -g -c -o trurl.o trurl.c cc -Wl,-O1 -Wl,--sort-common -Wl,--as-needed -Wl,-z,relro -Wl,-z,now -flto=auto trurl.o -o trurl $(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 -shost=moo -sscheme=http 14: passed --set=host=moo --set=scheme=http 15: passed -s host=moo -s scheme=http 16: passed --set host=moo --set scheme=https --set port=999 17: passed --set host=moo --set scheme=ftps --set path=/hello 18: passed --url https://curl.se --set host=example.com 19: passed --set host=example.com --set scheme=ftp 20: passed --url https://curl.se/we/are.html --redirect here.html 21: passed --url https://curl.se/we/../are.html --set port=8080 22: passed imap://curl.se:22/ -s port=143 23: passed --keep-port https://curl.se:22/ -s port=443 24: passed --keep-port https://curl.se:22/ -s port=443 --get '{url}' 25: passed --url https://curl.se/we/are.html --get '{path}' 26: passed --url https://curl.se/we/are.html '-g{path}' 27: passed --default-port --url imap://curl.se/we/are.html --get '{port}' 28: passed --url https://curl.se/we/are.html --get '{scheme}' 29: passed --url https://curl.se/we/are.html --get '{:scheme}' 30: passed --url https://curl.se:55/we/are.html --get '{url:port}' 31: passed --url https://curl.se/%2e%61%13 --get '{:path}' 32: passed --url 'https://curl.se?%2e%61%13' --get '{:query}' 33: passed --url 'https://curl.se/#%2e%61%13' --get '{:fragment}' 34: passed --url 'https://example.com/#%2e%61%13%Fa' 35: passed --url https://hello@curl.se/we/are.html --get '{user}' 36: passed --url https://hello:secret@curl.se/we/are.html --get '{password}' 37: passed --url 'imap://hello:secret;crazy@curl.se/we/are.html' --get '{options}' 38: passed --url https://curl.se/we/are.html --get '{host}' 39: passed --url https://10.1/we/are.html --get '{host}' 40: passed --url 'https://[fe80::0000:20c:29ff:fe9c:409b]:8080/we/are.html' --get '{host}' 41: passed --url 'https://[fe80::0000:20c:29ff:fe9c:409b%euth0]:8080/we/are.html' --get '{zoneid}' 42: passed --url 'https://[fe80::0000:20c:29ff:fe9c:409b%eth0]:8080/we/are.html' --get '{zoneid}' 43: passed --url 'https://curl.se/we/are.html?user=many#more' --get '{query}' 44: passed --url 'https://curl.se/we/are.html?user=many#more' --get '{fragment}' 45: passed --url imap://curl.se/we/are.html -g '{default:port}' 46: passed --url https://curl.se/hello --append path=you 47: passed --url https://curl.se/hello --append 'path=you index.html' 48: passed --url 'https://curl.se?name=hello' --append query=search=string 49: passed --url https://curl.se/hello --set user=:hej: 50: passed --url https://curl.se/hello --set user=hej --set password=secret 51: passed --url https://curl.se/hello --set query:=user=me 52: passed --url https://curl.se/hello --set query=user=me 53: passed --url https://curl.se/hello --set 'fragment= hello' 54: passed --url https://curl.se/hello --set fragment:=%20hello 55: passed localhost --append query=hello=foo 56: passed localhost -a query=hello=foo 57: passed 'https://example.com?search=hello&utm_source=tracker' --trim 'query=utm_*' 58: passed 'https://example.com?search=hello&utm_source=tracker' --qtrim 'utm_*' 59: passed 'https://example.com?search=hello&utm_source=tracker&more=data' --trim 'query=utm_*' 60: passed 'https://example.com?search=hello&utm_source=tracker&more=data' --qtrim 'utm_*' 61: passed 'https://example.com?search=hello&more=data' --qtrim 'utm_*' 62: passed 'https://example.com?utm_source=tracker' --trim 'query=utm_*' 63: passed 'https://example.com?search=hello&utm_source=tracker&more=data' --qtrim utm_source 64: passed 'https://example.com?search=hello&utm_source=tracker&more=data' --qtrim utm_source --qtrim more --qtrim search 65: passed --accept-space --url 'gopher://localhost/ with space' 66: passed --accept-space --url 'https://localhost/?with space' 67: passed https://daniel@curl.se:22/ -s port= -s user= 68: passed 'https://example.com?moo&search=hello' --qtrim search 69: passed 'https://example.com?search=hello&moo' --qtrim search 70: passed 'https://example.com?search=hello' --qtrim search --append query=moo 71: passed --keep-port https://hello:443/foo 72: passed --keep-port ftp://hello:21/foo 73: passed https://hello:443/foo -s scheme=ftp 74: passed --keep-port ftp://hello:443/foo -s scheme=https 75: passed 'https://example.com?utm_source=tra%20cker&address%20=home&here=now&thisthen' -g '{query:utm_source}' 76: passed 'https://example.com?utm_source=tra%20cker&address%20=home&here=now&thisthen' -g '{:query:utm_source}' 77: passed 'https://example.com?utm_source=tra%20cker&address%20=home&here=now&thisthen' -g '{:query:utm_}' 78: passed 'https://example.com?utm_source=tra%20cker&address%20=home&here=now&thisthen' -g '{:query:UTM_SOURCE}' 79: passed 'https://example.com?utm_source=tracker&monkey=123' --sort-query 80: passed 'https://example.com?a=b&c=d&' --sort-query 81: passed 'https://example.com?a=b&c=d&' --sort-query --trim query=a 82: passed example.com:29 --set port= 83: passed --url HTTPS://example.com 84: passed --url https://EXAMPLE.com 85: passed --url https://example.com/FOO/BAR 86: passed --url '[2001:0db8:0000:0000:0000:ff00:0042:8329]' 87: passed 'https://example.com?utm=tra%20cker:address%20=home:here=now:thisthen' --sort-query --query-separator : 88: passed 'foo?a=bCd=eCe=f' --query-separator C --trim query=d 89: passed localhost -g '{scheme} {host' 90: passed localhost -g '[scheme] [host' 91: passed localhost -g '\{{scheme}\[' 92: passed localhost -g '\\[' 93: passed 'https://u:s@foo?moo' -g '[scheme][user][password][query]' 94: passed 'hej?a=b&a=c&a=d&b=a' -g '{query-all:a}' 95: passed 'https://curl.se?name=mr%00smith' --get '{query:name}' 96: passed --keep-port https://curl.se --iterate 'port=80 81 443' 97: passed https://curl.se --iterate 'port=81 443' --iterate 'scheme=sftp moo' 98: passed https://curl.se --iterate 'port=81 443' --iterate 'scheme=sftp moo' --iterate 'port=2 1' 99: passed https://curl.se -s host=localhost --iterate 'port=22 23' 100: passed hello@localhost --iterate 'host=one two' -g '{host} {user}' 101: passed 'https://example.com?utm=tra%20cker&address%20=home&here=now&thisthen' --json 102: passed 'ftp://smith:secret@example.com:33/path?search=me#where' --json 103: passed example.com --json 104: passed example.com other.com --json 105: passed localhost --iterate 'host=one two' --json 106: passed --json -s scheme=irc -s host=curl.se 107: passed --json -s host=curl.se 108: passed --verify --json ftp://example.org '' git://curl.se/ 109: passed -s scheme=imap 110: passed -g '{query:}' 'http://localhost/?=bar' 111: passed --json 'https://curl.se/?&&&' 112: passed --json --trim 'query=f*' 'localhost?foo&bar=ar' 113: passed 'https://example.com?search=hello&utm_source=tracker&utm_block&testing' --trim 'query=utm_*' --json 114: passed 'https://räksmörgås.se' -g '{default:puny:url}' 115: passed 'https://räksmörgås.se' -g '{puny:url}' 116: passed 'https://räksmörgås.se' -g '{puny:host}' 117: passed 'imap://user:password;crazy@[ff00::1234%hello]:1234/path?a=b&c=d#fragment' --json 118: passed imap://example.com/ --get 'port: {port}, default:port: {default:port}' 119: passed http://example.com:8080/ --get 'port: {port}, default:port: {default:port}' 120: passed localhost -s host=foo --iterate 'host=bar baz' 121: passed emanuele6://curl.se/trurl '' https://example.org 122: passed --verify --no-guess-scheme hello 123: passed --verify -f testfiles/test0000.txt 124: passed -f testfiles/test0001.txt 125: passed --no-guess-scheme foo hi https://example.org hey git://curl.se 126: passed -f testfiles/test0002.txt --json 127: passed --accept-space -s 'query:=x=10&x=2 3' localhost 128: passed -s 'path=\\' -g '{path}\n{:path}' localhost 129: passed -s 'path=\\' --json localhost 130: passed -s 'path=\\' -g '{path}\n{:path}' --urlencode localhost 131: passed -s 'path=abc\\' -s 'query:=a&b&a%26b' --urlencode --json localhost 132: passed -s scheme:=http -s host:=localhost -s path:=/ABC%5C%5C -s 'query:=a&b&a%26b' 133: 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' 134: 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' 135: passed -a query=c=moo --sort-query 'https://example.org/foo?x=hi#rye' 136: passed --qtrim a -a query=a=ciao -a query=b=salve 'https://example.org/foo?a=hi&b=hello&x=y' 137: passed 'http://example.com/?q=mr%00smith' --json --urlencode 138: passed 'http://example.com/?q=mr%00sm%00ith' --json --urlencode 139: passed 'http://example.com/?q=mr%00%00%00smith' --json --urlencode 140: passed --url 'https://curl.se/we/are.html?*=moo&user=many#more' --qtrim '\*' 141: passed --url http://xn--rksmrgs-5wao1o/ --as-idn 142: passed --url http://xn--rksmrgs-5wao1o/ -g '{idn:host}' 143: passed --url http://xn-----/ --as-idn --quiet 144: passed --url http://xn-----/ --as-idn 145: passed --verify -f testfiles/test0000.txt --quiet 146: passed --curl --verify foo://bar 147: passed 'http://test.org/?key=val' --replace key=foo 148: passed 'http://test.org/?that=thing&key=val' --replace key=foo 149: passed 'http://test.org/?that=thing&key' --replace key=foo 150: passed 'http://test.org/?that=thing&key=foo' --replace key 151: passed 'https://example.com?a=123&b=321&b=987' --replace b=foo 152: passed 'example.org/?quest=best' --replace quest=%00 --json --urlencode 153: passed example.com --replace 154: passed 'http://test.org/?that=thing' --force-replace key=foo 155: passed 'http://test.org/?that=thing' --replace-append key=foo 156: passed '0?00%000000000000000000000=0000000000' 157: passed --json '0?0%000000000000000000000000000000000' --urlencode 158: passed --json '0?0%000000000000000000000000000000000=000%0000000000' --urlencode 159: passed example.com --set 'host=[::1]' 160: passed example.com:88 --set 'port?=99' 161: passed example.com --set 'port?=99' 162: passed example.com --append query=add --iterate 'scheme=http ftp' 163: passed example.com --append path=add --iterate 'scheme=http ftp' 164: passed example.com --append path=add --append path=two 165: passed 'https://curl.se?name=mr%00smith' --get '{query}' 166: passed 'https://curl.se?name=mr%00smith' --get '{strict:query}' 167: passed example.com --set 'scheme?=https' 168: passed ftp://example.com --set 'scheme?=https' 169: passed http://example.org/%18 --json 170: passed http://example.org/%18 --json --urlencode 171: passed https://example.com/one/t%61o/%2F%42/ 172: passed https://example.com/one/t%61o/%2F%42/ --append path=%61 173: passed 'https://ex%61mple.com/h%61s/?wh%61t' 174: passed https://example.com/ --get '{must:query}' 175: passed 'https://example.com/?' --get '{must:query}' 176: passed https://example.com/ --get '{must:fragment}' 177: passed http://example.org/%18 --get '{path}' 178: passed 'http://example.org/?a=&b=1' 179: passed 'http://example.org/?a=1&b=' 180: passed 'http://example.org/?a=1&b=&c=2' 181: passed 'http://example.org/?a=1&b=&c=2' --json 182: passed 'http://example.org/?=1&b=2&c=&=3' 183: passed 'http://example.com/?a=%5D' 184: passed 'http://example.com/?a=%5D&b=%5D' 185: passed 'sftp://us%65r:pwd;giraffe@odd' 186: passed 'imap://us%65r:pwd;gir%41ffe@odd' 187: passed 'sftp://us%65r:pwd;giraffe@odd' --get '[password]' 188: passed 'sftp://us%65r:pwd;giraffe@odd' --get '[:password]' 189: passed --url 'http://åäö/' --punycode -s port=21 190: passed sftp://odd --set port=144 --set port=145 191: passed sftp://odd --get '[port]' --get '{port}' 192: passed url -f testfiles/test0000.txt -f testfiles/test0000.txt 193: passed --url 194: passed url --set 195: passed url --redirect 196: passed url --get 197: passed url --replace 198: passed url --replace-append 199: passed url --append 200: passed url --query-separator ''"'"''"'"'' 201: passed url --query-separator aa 202: passed url --json --get '{port}' 203: passed url --get '{port}' --json Finished: Passed! - Failed: 0, Passed: 203, Skipped: 0, Total: 203 1: failed example.com --- stdout --- expected: 'http://example.com/\n' got: 'http://example.com/\n' --- stderr --- expected: '' got: '--1269-- WARNING: unhandled riscv64-linux syscall: 258\n--1269-- You may be able to write your own handler.\n--1269-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1269-- Nevertheless we consider this a bug. Please report\n--1269-- it at http://valgrind.org/support/bug_reports.html.\n--1269-- WARNING: unhandled riscv64-linux syscall: 258\n--1269-- You may be able to write your own handler.\n--1269-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1269-- Nevertheless we consider this a bug. Please report\n--1269-- it at http://valgrind.org/support/bug_reports.html.\n--1269-- WARNING: unhandled riscv64-linux syscall: 258\n--1269-- You may be able to write your own handler.\n--1269-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1269-- Nevertheless we consider this a bug. Please report\n--1269-- it at http://valgrind.org/support/bug_reports.html.\n--1269-- WARNING: unhandled riscv64-linux syscall: 258\n--1269-- You may be able to write your own handler.\n--1269-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1269-- Nevertheless we consider this a bug. Please report\n--1269-- it at http://valgrind.org/support/bug_reports.html.\n--1269-- WARNING: unhandled riscv64-linux syscall: 258\n--1269-- You may be able to write your own handler.\n--1269-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1269-- Nevertheless we consider this a bug. Please report\n--1269-- it at http://valgrind.org/support/bug_reports.html.\n--1269-- WARNING: unhandled riscv64-linux syscall: 258\n--1269-- You may be able to write your own handler.\n--1269-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1269-- Nevertheless we consider this a bug. Please report\n--1269-- it at http://valgrind.org/support/bug_reports.html.\n--1269-- WARNING: unhandled riscv64-linux syscall: 258\n--1269-- You may be able to write your own handler.\n--1269-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1269-- Nevertheless we consider this a bug. Please report\n--1269-- it at http://valgrind.org/support/bug_reports.html.\n--1269-- WARNING: unhandled riscv64-linux syscall: 258\n--1269-- You may be able to write your own handler.\n--1269-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1269-- Nevertheless we consider this a bug. Please report\n--1269-- it at http://valgrind.org/support/bug_reports.html.\n--1269-- WARNING: unhandled riscv64-linux syscall: 258\n--1269-- You may be able to write your own handler.\n--1269-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1269-- Nevertheless we consider this a bug. Please report\n--1269-- it at http://valgrind.org/support/bug_reports.html.\n--1269-- WARNING: unhandled riscv64-linux syscall: 258\n--1269-- You may be able to write your own handler.\n--1269-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1269-- Nevertheless we consider this a bug. Please report\n--1269-- it at http://valgrind.org/support/bug_reports.html.\n--1269-- WARNING: unhandled riscv64-linux syscall: 258\n--1269-- You may be able to write your own handler.\n--1269-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1269-- Nevertheless we consider this a bug. Please report\n--1269-- it at http://valgrind.org/support/bug_reports.html.\n--1269-- WARNING: unhandled riscv64-linux syscall: 258\n--1269-- You may be able to write your own handler.\n--1269-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1269-- Nevertheless we consider this a bug. Please report\n--1269-- it at http://valgrind.org/support/bug_reports.html.\n--1269-- WARNING: unhandled riscv64-linux syscall: 258\n--1269-- You may be able to write your own handler.\n--1269-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1269-- Nevertheless we consider this a bug. Please report\n--1269-- it at http://valgrind.org/support/bug_reports.html.\n--1269-- WARNING: unhandled riscv64-linux syscall: 258\n--1269-- You may be able to write your own handler.\n--1269-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1269-- Nevertheless we consider this a bug. Please report\n--1269-- it at http://valgrind.org/support/bug_reports.html.\n--1269-- WARNING: unhandled riscv64-linux syscall: 258\n--1269-- You may be able to write your own handler.\n--1269-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1269-- Nevertheless we consider this a bug. Please report\n--1269-- it at http://valgrind.org/support/bug_reports.html.\n--1269-- WARNING: unhandled riscv64-linux syscall: 258\n--1269-- You may be able to write your own handler.\n--1269-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1269-- Nevertheless we consider this a bug. Please report\n--1269-- it at http://valgrind.org/support/bug_reports.html.\n--1269-- WARNING: unhandled riscv64-linux syscall: 258\n--1269-- You may be able to write your own handler.\n--1269-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1269-- Nevertheless we consider this a bug. Please report\n--1269-- it at http://valgrind.org/support/bug_reports.html.\n--1269-- WARNING: unhandled riscv64-linux syscall: 258\n--1269-- You may be able to write your own handler.\n--1269-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1269-- Nevertheless we consider this a bug. Please report\n--1269-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 2: failed http://example.com --- stdout --- expected: 'http://example.com/\n' got: 'http://example.com/\n' --- stderr --- expected: '' got: '--1284-- WARNING: unhandled riscv64-linux syscall: 258\n--1284-- You may be able to write your own handler.\n--1284-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1284-- Nevertheless we consider this a bug. Please report\n--1284-- it at http://valgrind.org/support/bug_reports.html.\n--1284-- WARNING: unhandled riscv64-linux syscall: 258\n--1284-- You may be able to write your own handler.\n--1284-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1284-- Nevertheless we consider this a bug. Please report\n--1284-- it at http://valgrind.org/support/bug_reports.html.\n--1284-- WARNING: unhandled riscv64-linux syscall: 258\n--1284-- You may be able to write your own handler.\n--1284-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1284-- Nevertheless we consider this a bug. Please report\n--1284-- it at http://valgrind.org/support/bug_reports.html.\n--1284-- WARNING: unhandled riscv64-linux syscall: 258\n--1284-- You may be able to write your own handler.\n--1284-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1284-- Nevertheless we consider this a bug. Please report\n--1284-- it at http://valgrind.org/support/bug_reports.html.\n--1284-- WARNING: unhandled riscv64-linux syscall: 258\n--1284-- You may be able to write your own handler.\n--1284-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1284-- Nevertheless we consider this a bug. Please report\n--1284-- it at http://valgrind.org/support/bug_reports.html.\n--1284-- WARNING: unhandled riscv64-linux syscall: 258\n--1284-- You may be able to write your own handler.\n--1284-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1284-- Nevertheless we consider this a bug. Please report\n--1284-- it at http://valgrind.org/support/bug_reports.html.\n--1284-- WARNING: unhandled riscv64-linux syscall: 258\n--1284-- You may be able to write your own handler.\n--1284-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1284-- Nevertheless we consider this a bug. Please report\n--1284-- it at http://valgrind.org/support/bug_reports.html.\n--1284-- WARNING: unhandled riscv64-linux syscall: 258\n--1284-- You may be able to write your own handler.\n--1284-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1284-- Nevertheless we consider this a bug. Please report\n--1284-- it at http://valgrind.org/support/bug_reports.html.\n--1284-- WARNING: unhandled riscv64-linux syscall: 258\n--1284-- You may be able to write your own handler.\n--1284-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1284-- Nevertheless we consider this a bug. Please report\n--1284-- it at http://valgrind.org/support/bug_reports.html.\n--1284-- WARNING: unhandled riscv64-linux syscall: 258\n--1284-- You may be able to write your own handler.\n--1284-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1284-- Nevertheless we consider this a bug. Please report\n--1284-- it at http://valgrind.org/support/bug_reports.html.\n--1284-- WARNING: unhandled riscv64-linux syscall: 258\n--1284-- You may be able to write your own handler.\n--1284-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1284-- Nevertheless we consider this a bug. Please report\n--1284-- it at http://valgrind.org/support/bug_reports.html.\n--1284-- WARNING: unhandled riscv64-linux syscall: 258\n--1284-- You may be able to write your own handler.\n--1284-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1284-- Nevertheless we consider this a bug. Please report\n--1284-- it at http://valgrind.org/support/bug_reports.html.\n--1284-- WARNING: unhandled riscv64-linux syscall: 258\n--1284-- You may be able to write your own handler.\n--1284-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1284-- Nevertheless we consider this a bug. Please report\n--1284-- it at http://valgrind.org/support/bug_reports.html.\n--1284-- WARNING: unhandled riscv64-linux syscall: 258\n--1284-- You may be able to write your own handler.\n--1284-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1284-- Nevertheless we consider this a bug. Please report\n--1284-- it at http://valgrind.org/support/bug_reports.html.\n--1284-- WARNING: unhandled riscv64-linux syscall: 258\n--1284-- You may be able to write your own handler.\n--1284-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1284-- Nevertheless we consider this a bug. Please report\n--1284-- it at http://valgrind.org/support/bug_reports.html.\n--1284-- WARNING: unhandled riscv64-linux syscall: 258\n--1284-- You may be able to write your own handler.\n--1284-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1284-- Nevertheless we consider this a bug. Please report\n--1284-- it at http://valgrind.org/support/bug_reports.html.\n--1284-- WARNING: unhandled riscv64-linux syscall: 258\n--1284-- You may be able to write your own handler.\n--1284-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1284-- Nevertheless we consider this a bug. Please report\n--1284-- it at http://valgrind.org/support/bug_reports.html.\n--1284-- WARNING: unhandled riscv64-linux syscall: 258\n--1284-- You may be able to write your own handler.\n--1284-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1284-- Nevertheless we consider this a bug. Please report\n--1284-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 3: failed https://example.com --- stdout --- expected: 'https://example.com/\n' got: 'https://example.com/\n' --- stderr --- expected: '' got: '--1292-- WARNING: unhandled riscv64-linux syscall: 258\n--1292-- You may be able to write your own handler.\n--1292-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1292-- Nevertheless we consider this a bug. Please report\n--1292-- it at http://valgrind.org/support/bug_reports.html.\n--1292-- WARNING: unhandled riscv64-linux syscall: 258\n--1292-- You may be able to write your own handler.\n--1292-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1292-- Nevertheless we consider this a bug. Please report\n--1292-- it at http://valgrind.org/support/bug_reports.html.\n--1292-- WARNING: unhandled riscv64-linux syscall: 258\n--1292-- You may be able to write your own handler.\n--1292-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1292-- Nevertheless we consider this a bug. Please report\n--1292-- it at http://valgrind.org/support/bug_reports.html.\n--1292-- WARNING: unhandled riscv64-linux syscall: 258\n--1292-- You may be able to write your own handler.\n--1292-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1292-- Nevertheless we consider this a bug. Please report\n--1292-- it at http://valgrind.org/support/bug_reports.html.\n--1292-- WARNING: unhandled riscv64-linux syscall: 258\n--1292-- You may be able to write your own handler.\n--1292-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1292-- Nevertheless we consider this a bug. Please report\n--1292-- it at http://valgrind.org/support/bug_reports.html.\n--1292-- WARNING: unhandled riscv64-linux syscall: 258\n--1292-- You may be able to write your own handler.\n--1292-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1292-- Nevertheless we consider this a bug. Please report\n--1292-- it at http://valgrind.org/support/bug_reports.html.\n--1292-- WARNING: unhandled riscv64-linux syscall: 258\n--1292-- You may be able to write your own handler.\n--1292-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1292-- Nevertheless we consider this a bug. Please report\n--1292-- it at http://valgrind.org/support/bug_reports.html.\n--1292-- WARNING: unhandled riscv64-linux syscall: 258\n--1292-- You may be able to write your own handler.\n--1292-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1292-- Nevertheless we consider this a bug. Please report\n--1292-- it at http://valgrind.org/support/bug_reports.html.\n--1292-- WARNING: unhandled riscv64-linux syscall: 258\n--1292-- You may be able to write your own handler.\n--1292-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1292-- Nevertheless we consider this a bug. Please report\n--1292-- it at http://valgrind.org/support/bug_reports.html.\n--1292-- WARNING: unhandled riscv64-linux syscall: 258\n--1292-- You may be able to write your own handler.\n--1292-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1292-- Nevertheless we consider this a bug. Please report\n--1292-- it at http://valgrind.org/support/bug_reports.html.\n--1292-- WARNING: unhandled riscv64-linux syscall: 258\n--1292-- You may be able to write your own handler.\n--1292-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1292-- Nevertheless we consider this a bug. Please report\n--1292-- it at http://valgrind.org/support/bug_reports.html.\n--1292-- WARNING: unhandled riscv64-linux syscall: 258\n--1292-- You may be able to write your own handler.\n--1292-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1292-- Nevertheless we consider this a bug. Please report\n--1292-- it at http://valgrind.org/support/bug_reports.html.\n--1292-- WARNING: unhandled riscv64-linux syscall: 258\n--1292-- You may be able to write your own handler.\n--1292-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1292-- Nevertheless we consider this a bug. Please report\n--1292-- it at http://valgrind.org/support/bug_reports.html.\n--1292-- WARNING: unhandled riscv64-linux syscall: 258\n--1292-- You may be able to write your own handler.\n--1292-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1292-- Nevertheless we consider this a bug. Please report\n--1292-- it at http://valgrind.org/support/bug_reports.html.\n--1292-- WARNING: unhandled riscv64-linux syscall: 258\n--1292-- You may be able to write your own handler.\n--1292-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1292-- Nevertheless we consider this a bug. Please report\n--1292-- it at http://valgrind.org/support/bug_reports.html.\n--1292-- WARNING: unhandled riscv64-linux syscall: 258\n--1292-- You may be able to write your own handler.\n--1292-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1292-- Nevertheless we consider this a bug. Please report\n--1292-- it at http://valgrind.org/support/bug_reports.html.\n--1292-- WARNING: unhandled riscv64-linux syscall: 258\n--1292-- You may be able to write your own handler.\n--1292-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1292-- Nevertheless we consider this a bug. Please report\n--1292-- it at http://valgrind.org/support/bug_reports.html.\n--1292-- WARNING: unhandled riscv64-linux syscall: 258\n--1292-- You may be able to write your own handler.\n--1292-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1292-- Nevertheless we consider this a bug. Please report\n--1292-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 4: failed hp://example.com --- stdout --- expected: 'hp://example.com/\n' got: 'hp://example.com/\n' --- stderr --- expected: '' got: '--1300-- WARNING: unhandled riscv64-linux syscall: 258\n--1300-- You may be able to write your own handler.\n--1300-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1300-- Nevertheless we consider this a bug. Please report\n--1300-- it at http://valgrind.org/support/bug_reports.html.\n--1300-- WARNING: unhandled riscv64-linux syscall: 258\n--1300-- You may be able to write your own handler.\n--1300-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1300-- Nevertheless we consider this a bug. Please report\n--1300-- it at http://valgrind.org/support/bug_reports.html.\n--1300-- WARNING: unhandled riscv64-linux syscall: 258\n--1300-- You may be able to write your own handler.\n--1300-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1300-- Nevertheless we consider this a bug. Please report\n--1300-- it at http://valgrind.org/support/bug_reports.html.\n--1300-- WARNING: unhandled riscv64-linux syscall: 258\n--1300-- You may be able to write your own handler.\n--1300-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1300-- Nevertheless we consider this a bug. Please report\n--1300-- it at http://valgrind.org/support/bug_reports.html.\n--1300-- WARNING: unhandled riscv64-linux syscall: 258\n--1300-- You may be able to write your own handler.\n--1300-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1300-- Nevertheless we consider this a bug. Please report\n--1300-- it at http://valgrind.org/support/bug_reports.html.\n--1300-- WARNING: unhandled riscv64-linux syscall: 258\n--1300-- You may be able to write your own handler.\n--1300-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1300-- Nevertheless we consider this a bug. Please report\n--1300-- it at http://valgrind.org/support/bug_reports.html.\n--1300-- WARNING: unhandled riscv64-linux syscall: 258\n--1300-- You may be able to write your own handler.\n--1300-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1300-- Nevertheless we consider this a bug. Please report\n--1300-- it at http://valgrind.org/support/bug_reports.html.\n--1300-- WARNING: unhandled riscv64-linux syscall: 258\n--1300-- You may be able to write your own handler.\n--1300-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1300-- Nevertheless we consider this a bug. Please report\n--1300-- it at http://valgrind.org/support/bug_reports.html.\n--1300-- WARNING: unhandled riscv64-linux syscall: 258\n--1300-- You may be able to write your own handler.\n--1300-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1300-- Nevertheless we consider this a bug. Please report\n--1300-- it at http://valgrind.org/support/bug_reports.html.\n--1300-- WARNING: unhandled riscv64-linux syscall: 258\n--1300-- You may be able to write your own handler.\n--1300-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1300-- Nevertheless we consider this a bug. Please report\n--1300-- it at http://valgrind.org/support/bug_reports.html.\n--1300-- WARNING: unhandled riscv64-linux syscall: 258\n--1300-- You may be able to write your own handler.\n--1300-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1300-- Nevertheless we consider this a bug. Please report\n--1300-- it at http://valgrind.org/support/bug_reports.html.\n--1300-- WARNING: unhandled riscv64-linux syscall: 258\n--1300-- You may be able to write your own handler.\n--1300-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1300-- Nevertheless we consider this a bug. Please report\n--1300-- it at http://valgrind.org/support/bug_reports.html.\n--1300-- WARNING: unhandled riscv64-linux syscall: 258\n--1300-- You may be able to write your own handler.\n--1300-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1300-- Nevertheless we consider this a bug. Please report\n--1300-- it at http://valgrind.org/support/bug_reports.html.\n--1300-- WARNING: unhandled riscv64-linux syscall: 258\n--1300-- You may be able to write your own handler.\n--1300-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1300-- Nevertheless we consider this a bug. Please report\n--1300-- it at http://valgrind.org/support/bug_reports.html.\n--1300-- WARNING: unhandled riscv64-linux syscall: 258\n--1300-- You may be able to write your own handler.\n--1300-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1300-- Nevertheless we consider this a bug. Please report\n--1300-- it at http://valgrind.org/support/bug_reports.html.\n--1300-- WARNING: unhandled riscv64-linux syscall: 258\n--1300-- You may be able to write your own handler.\n--1300-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1300-- Nevertheless we consider this a bug. Please report\n--1300-- it at http://valgrind.org/support/bug_reports.html.\n--1300-- WARNING: unhandled riscv64-linux syscall: 258\n--1300-- You may be able to write your own handler.\n--1300-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1300-- Nevertheless we consider this a bug. Please report\n--1300-- it at http://valgrind.org/support/bug_reports.html.\n--1300-- WARNING: unhandled riscv64-linux syscall: 258\n--1300-- You may be able to write your own handler.\n--1300-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1300-- Nevertheless we consider this a bug. Please report\n--1300-- it at http://valgrind.org/support/bug_reports.html.\n==1300== Conditional jump or move depends on uninitialised value(s)\n==1300== at 0x48B7428: UnknownInlinedFun (urlapi.c:932)\n==1300== by 0x48B7428: parseurl_and_replace.lto_priv.0 (urlapi.c:1269)\n==1300== by 0x48BC9E5: curl_url_set (urlapi.c:1784)\n==1300== by 0x10CB5D: UnknownInlinedFun (trurl.c:1674)\n==1300== by 0x10CB5D: singleurl (trurl.c:1780)\n==1300== by 0x109C81: main (trurl.c:2118)\n==1300== \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: '--1308-- WARNING: unhandled riscv64-linux syscall: 258\n--1308-- You may be able to write your own handler.\n--1308-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1308-- Nevertheless we consider this a bug. Please report\n--1308-- it at http://valgrind.org/support/bug_reports.html.\n--1308-- WARNING: unhandled riscv64-linux syscall: 258\n--1308-- You may be able to write your own handler.\n--1308-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1308-- Nevertheless we consider this a bug. Please report\n--1308-- it at http://valgrind.org/support/bug_reports.html.\n--1308-- WARNING: unhandled riscv64-linux syscall: 258\n--1308-- You may be able to write your own handler.\n--1308-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1308-- Nevertheless we consider this a bug. Please report\n--1308-- it at http://valgrind.org/support/bug_reports.html.\n--1308-- WARNING: unhandled riscv64-linux syscall: 258\n--1308-- You may be able to write your own handler.\n--1308-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1308-- Nevertheless we consider this a bug. Please report\n--1308-- it at http://valgrind.org/support/bug_reports.html.\n--1308-- WARNING: unhandled riscv64-linux syscall: 258\n--1308-- You may be able to write your own handler.\n--1308-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1308-- Nevertheless we consider this a bug. Please report\n--1308-- it at http://valgrind.org/support/bug_reports.html.\n--1308-- WARNING: unhandled riscv64-linux syscall: 258\n--1308-- You may be able to write your own handler.\n--1308-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1308-- Nevertheless we consider this a bug. Please report\n--1308-- it at http://valgrind.org/support/bug_reports.html.\n--1308-- WARNING: unhandled riscv64-linux syscall: 258\n--1308-- You may be able to write your own handler.\n--1308-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1308-- Nevertheless we consider this a bug. Please report\n--1308-- it at http://valgrind.org/support/bug_reports.html.\n--1308-- WARNING: unhandled riscv64-linux syscall: 258\n--1308-- You may be able to write your own handler.\n--1308-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1308-- Nevertheless we consider this a bug. Please report\n--1308-- it at http://valgrind.org/support/bug_reports.html.\n--1308-- WARNING: unhandled riscv64-linux syscall: 258\n--1308-- You may be able to write your own handler.\n--1308-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1308-- Nevertheless we consider this a bug. Please report\n--1308-- it at http://valgrind.org/support/bug_reports.html.\n--1308-- WARNING: unhandled riscv64-linux syscall: 258\n--1308-- You may be able to write your own handler.\n--1308-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1308-- Nevertheless we consider this a bug. Please report\n--1308-- it at http://valgrind.org/support/bug_reports.html.\n--1308-- WARNING: unhandled riscv64-linux syscall: 258\n--1308-- You may be able to write your own handler.\n--1308-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1308-- Nevertheless we consider this a bug. Please report\n--1308-- it at http://valgrind.org/support/bug_reports.html.\n--1308-- WARNING: unhandled riscv64-linux syscall: 258\n--1308-- You may be able to write your own handler.\n--1308-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1308-- Nevertheless we consider this a bug. Please report\n--1308-- it at http://valgrind.org/support/bug_reports.html.\n--1308-- WARNING: unhandled riscv64-linux syscall: 258\n--1308-- You may be able to write your own handler.\n--1308-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1308-- Nevertheless we consider this a bug. Please report\n--1308-- it at http://valgrind.org/support/bug_reports.html.\n--1308-- WARNING: unhandled riscv64-linux syscall: 258\n--1308-- You may be able to write your own handler.\n--1308-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1308-- Nevertheless we consider this a bug. Please report\n--1308-- it at http://valgrind.org/support/bug_reports.html.\n--1308-- WARNING: unhandled riscv64-linux syscall: 258\n--1308-- You may be able to write your own handler.\n--1308-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1308-- Nevertheless we consider this a bug. Please report\n--1308-- it at http://valgrind.org/support/bug_reports.html.\n--1308-- WARNING: unhandled riscv64-linux syscall: 258\n--1308-- You may be able to write your own handler.\n--1308-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1308-- Nevertheless we consider this a bug. Please report\n--1308-- it at http://valgrind.org/support/bug_reports.html.\n--1308-- WARNING: unhandled riscv64-linux syscall: 258\n--1308-- You may be able to write your own handler.\n--1308-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1308-- Nevertheless we consider this a bug. Please report\n--1308-- it at http://valgrind.org/support/bug_reports.html.\n--1308-- WARNING: unhandled riscv64-linux syscall: 258\n--1308-- You may be able to write your own handler.\n--1308-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1308-- Nevertheless we consider this a bug. Please report\n--1308-- it at http://valgrind.org/support/bug_reports.html.\ntrurl error: not enough input for a URL\ntrurl error: Try trurl -h for help\n' --- returncode --- expected: 7 got: 7 6: failed ftp.example.com --- stdout --- expected: 'ftp://ftp.example.com/\n' got: 'ftp://ftp.example.com/\n' --- stderr --- expected: '' got: '--1316-- WARNING: unhandled riscv64-linux syscall: 258\n--1316-- You may be able to write your own handler.\n--1316-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1316-- Nevertheless we consider this a bug. Please report\n--1316-- it at http://valgrind.org/support/bug_reports.html.\n--1316-- WARNING: unhandled riscv64-linux syscall: 258\n--1316-- You may be able to write your own handler.\n--1316-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1316-- Nevertheless we consider this a bug. Please report\n--1316-- it at http://valgrind.org/support/bug_reports.html.\n--1316-- WARNING: unhandled riscv64-linux syscall: 258\n--1316-- You may be able to write your own handler.\n--1316-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1316-- Nevertheless we consider this a bug. Please report\n--1316-- it at http://valgrind.org/support/bug_reports.html.\n--1316-- WARNING: unhandled riscv64-linux syscall: 258\n--1316-- You may be able to write your own handler.\n--1316-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1316-- Nevertheless we consider this a bug. Please report\n--1316-- it at http://valgrind.org/support/bug_reports.html.\n--1316-- WARNING: unhandled riscv64-linux syscall: 258\n--1316-- You may be able to write your own handler.\n--1316-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1316-- Nevertheless we consider this a bug. Please report\n--1316-- it at http://valgrind.org/support/bug_reports.html.\n--1316-- WARNING: unhandled riscv64-linux syscall: 258\n--1316-- You may be able to write your own handler.\n--1316-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1316-- Nevertheless we consider this a bug. Please report\n--1316-- it at http://valgrind.org/support/bug_reports.html.\n--1316-- WARNING: unhandled riscv64-linux syscall: 258\n--1316-- You may be able to write your own handler.\n--1316-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1316-- Nevertheless we consider this a bug. Please report\n--1316-- it at http://valgrind.org/support/bug_reports.html.\n--1316-- WARNING: unhandled riscv64-linux syscall: 258\n--1316-- You may be able to write your own handler.\n--1316-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1316-- Nevertheless we consider this a bug. Please report\n--1316-- it at http://valgrind.org/support/bug_reports.html.\n--1316-- WARNING: unhandled riscv64-linux syscall: 258\n--1316-- You may be able to write your own handler.\n--1316-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1316-- Nevertheless we consider this a bug. Please report\n--1316-- it at http://valgrind.org/support/bug_reports.html.\n--1316-- WARNING: unhandled riscv64-linux syscall: 258\n--1316-- You may be able to write your own handler.\n--1316-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1316-- Nevertheless we consider this a bug. Please report\n--1316-- it at http://valgrind.org/support/bug_reports.html.\n--1316-- WARNING: unhandled riscv64-linux syscall: 258\n--1316-- You may be able to write your own handler.\n--1316-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1316-- Nevertheless we consider this a bug. Please report\n--1316-- it at http://valgrind.org/support/bug_reports.html.\n--1316-- WARNING: unhandled riscv64-linux syscall: 258\n--1316-- You may be able to write your own handler.\n--1316-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1316-- Nevertheless we consider this a bug. Please report\n--1316-- it at http://valgrind.org/support/bug_reports.html.\n--1316-- WARNING: unhandled riscv64-linux syscall: 258\n--1316-- You may be able to write your own handler.\n--1316-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1316-- Nevertheless we consider this a bug. Please report\n--1316-- it at http://valgrind.org/support/bug_reports.html.\n--1316-- WARNING: unhandled riscv64-linux syscall: 258\n--1316-- You may be able to write your own handler.\n--1316-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1316-- Nevertheless we consider this a bug. Please report\n--1316-- it at http://valgrind.org/support/bug_reports.html.\n--1316-- WARNING: unhandled riscv64-linux syscall: 258\n--1316-- You may be able to write your own handler.\n--1316-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1316-- Nevertheless we consider this a bug. Please report\n--1316-- it at http://valgrind.org/support/bug_reports.html.\n--1316-- WARNING: unhandled riscv64-linux syscall: 258\n--1316-- You may be able to write your own handler.\n--1316-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1316-- Nevertheless we consider this a bug. Please report\n--1316-- it at http://valgrind.org/support/bug_reports.html.\n--1316-- WARNING: unhandled riscv64-linux syscall: 258\n--1316-- You may be able to write your own handler.\n--1316-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1316-- Nevertheless we consider this a bug. Please report\n--1316-- it at http://valgrind.org/support/bug_reports.html.\n--1316-- WARNING: unhandled riscv64-linux syscall: 258\n--1316-- You may be able to write your own handler.\n--1316-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1316-- Nevertheless we consider this a bug. Please report\n--1316-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 7: failed https://example.com/../moo --- stdout --- expected: 'https://example.com/moo\n' got: 'https://example.com/moo\n' --- stderr --- expected: '' got: '--1324-- WARNING: unhandled riscv64-linux syscall: 258\n--1324-- You may be able to write your own handler.\n--1324-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1324-- Nevertheless we consider this a bug. Please report\n--1324-- it at http://valgrind.org/support/bug_reports.html.\n--1324-- WARNING: unhandled riscv64-linux syscall: 258\n--1324-- You may be able to write your own handler.\n--1324-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1324-- Nevertheless we consider this a bug. Please report\n--1324-- it at http://valgrind.org/support/bug_reports.html.\n--1324-- WARNING: unhandled riscv64-linux syscall: 258\n--1324-- You may be able to write your own handler.\n--1324-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1324-- Nevertheless we consider this a bug. Please report\n--1324-- it at http://valgrind.org/support/bug_reports.html.\n--1324-- WARNING: unhandled riscv64-linux syscall: 258\n--1324-- You may be able to write your own handler.\n--1324-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1324-- Nevertheless we consider this a bug. Please report\n--1324-- it at http://valgrind.org/support/bug_reports.html.\n--1324-- WARNING: unhandled riscv64-linux syscall: 258\n--1324-- You may be able to write your own handler.\n--1324-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1324-- Nevertheless we consider this a bug. Please report\n--1324-- it at http://valgrind.org/support/bug_reports.html.\n--1324-- WARNING: unhandled riscv64-linux syscall: 258\n--1324-- You may be able to write your own handler.\n--1324-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1324-- Nevertheless we consider this a bug. Please report\n--1324-- it at http://valgrind.org/support/bug_reports.html.\n--1324-- WARNING: unhandled riscv64-linux syscall: 258\n--1324-- You may be able to write your own handler.\n--1324-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1324-- Nevertheless we consider this a bug. Please report\n--1324-- it at http://valgrind.org/support/bug_reports.html.\n--1324-- WARNING: unhandled riscv64-linux syscall: 258\n--1324-- You may be able to write your own handler.\n--1324-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1324-- Nevertheless we consider this a bug. Please report\n--1324-- it at http://valgrind.org/support/bug_reports.html.\n--1324-- WARNING: unhandled riscv64-linux syscall: 258\n--1324-- You may be able to write your own handler.\n--1324-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1324-- Nevertheless we consider this a bug. Please report\n--1324-- it at http://valgrind.org/support/bug_reports.html.\n--1324-- WARNING: unhandled riscv64-linux syscall: 258\n--1324-- You may be able to write your own handler.\n--1324-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1324-- Nevertheless we consider this a bug. Please report\n--1324-- it at http://valgrind.org/support/bug_reports.html.\n--1324-- WARNING: unhandled riscv64-linux syscall: 258\n--1324-- You may be able to write your own handler.\n--1324-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1324-- Nevertheless we consider this a bug. Please report\n--1324-- it at http://valgrind.org/support/bug_reports.html.\n--1324-- WARNING: unhandled riscv64-linux syscall: 258\n--1324-- You may be able to write your own handler.\n--1324-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1324-- Nevertheless we consider this a bug. Please report\n--1324-- it at http://valgrind.org/support/bug_reports.html.\n--1324-- WARNING: unhandled riscv64-linux syscall: 258\n--1324-- You may be able to write your own handler.\n--1324-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1324-- Nevertheless we consider this a bug. Please report\n--1324-- it at http://valgrind.org/support/bug_reports.html.\n--1324-- WARNING: unhandled riscv64-linux syscall: 258\n--1324-- You may be able to write your own handler.\n--1324-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1324-- Nevertheless we consider this a bug. Please report\n--1324-- it at http://valgrind.org/support/bug_reports.html.\n--1324-- WARNING: unhandled riscv64-linux syscall: 258\n--1324-- You may be able to write your own handler.\n--1324-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1324-- Nevertheless we consider this a bug. Please report\n--1324-- it at http://valgrind.org/support/bug_reports.html.\n--1324-- WARNING: unhandled riscv64-linux syscall: 258\n--1324-- You may be able to write your own handler.\n--1324-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1324-- Nevertheless we consider this a bug. Please report\n--1324-- it at http://valgrind.org/support/bug_reports.html.\n--1324-- WARNING: unhandled riscv64-linux syscall: 258\n--1324-- You may be able to write your own handler.\n--1324-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1324-- Nevertheless we consider this a bug. Please report\n--1324-- it at http://valgrind.org/support/bug_reports.html.\n--1324-- WARNING: unhandled riscv64-linux syscall: 258\n--1324-- You may be able to write your own handler.\n--1324-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1324-- Nevertheless we consider this a bug. Please report\n--1324-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 8: failed https://example.com/.././moo --- stdout --- expected: 'https://example.com/moo\n' got: 'https://example.com/moo\n' --- stderr --- expected: '' got: '--1332-- WARNING: unhandled riscv64-linux syscall: 258\n--1332-- You may be able to write your own handler.\n--1332-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1332-- Nevertheless we consider this a bug. Please report\n--1332-- it at http://valgrind.org/support/bug_reports.html.\n--1332-- WARNING: unhandled riscv64-linux syscall: 258\n--1332-- You may be able to write your own handler.\n--1332-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1332-- Nevertheless we consider this a bug. Please report\n--1332-- it at http://valgrind.org/support/bug_reports.html.\n--1332-- WARNING: unhandled riscv64-linux syscall: 258\n--1332-- You may be able to write your own handler.\n--1332-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1332-- Nevertheless we consider this a bug. Please report\n--1332-- it at http://valgrind.org/support/bug_reports.html.\n--1332-- WARNING: unhandled riscv64-linux syscall: 258\n--1332-- You may be able to write your own handler.\n--1332-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1332-- Nevertheless we consider this a bug. Please report\n--1332-- it at http://valgrind.org/support/bug_reports.html.\n--1332-- WARNING: unhandled riscv64-linux syscall: 258\n--1332-- You may be able to write your own handler.\n--1332-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1332-- Nevertheless we consider this a bug. Please report\n--1332-- it at http://valgrind.org/support/bug_reports.html.\n--1332-- WARNING: unhandled riscv64-linux syscall: 258\n--1332-- You may be able to write your own handler.\n--1332-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1332-- Nevertheless we consider this a bug. Please report\n--1332-- it at http://valgrind.org/support/bug_reports.html.\n--1332-- WARNING: unhandled riscv64-linux syscall: 258\n--1332-- You may be able to write your own handler.\n--1332-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1332-- Nevertheless we consider this a bug. Please report\n--1332-- it at http://valgrind.org/support/bug_reports.html.\n--1332-- WARNING: unhandled riscv64-linux syscall: 258\n--1332-- You may be able to write your own handler.\n--1332-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1332-- Nevertheless we consider this a bug. Please report\n--1332-- it at http://valgrind.org/support/bug_reports.html.\n--1332-- WARNING: unhandled riscv64-linux syscall: 258\n--1332-- You may be able to write your own handler.\n--1332-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1332-- Nevertheless we consider this a bug. Please report\n--1332-- it at http://valgrind.org/support/bug_reports.html.\n--1332-- WARNING: unhandled riscv64-linux syscall: 258\n--1332-- You may be able to write your own handler.\n--1332-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1332-- Nevertheless we consider this a bug. Please report\n--1332-- it at http://valgrind.org/support/bug_reports.html.\n--1332-- WARNING: unhandled riscv64-linux syscall: 258\n--1332-- You may be able to write your own handler.\n--1332-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1332-- Nevertheless we consider this a bug. Please report\n--1332-- it at http://valgrind.org/support/bug_reports.html.\n--1332-- WARNING: unhandled riscv64-linux syscall: 258\n--1332-- You may be able to write your own handler.\n--1332-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1332-- Nevertheless we consider this a bug. Please report\n--1332-- it at http://valgrind.org/support/bug_reports.html.\n--1332-- WARNING: unhandled riscv64-linux syscall: 258\n--1332-- You may be able to write your own handler.\n--1332-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1332-- Nevertheless we consider this a bug. Please report\n--1332-- it at http://valgrind.org/support/bug_reports.html.\n--1332-- WARNING: unhandled riscv64-linux syscall: 258\n--1332-- You may be able to write your own handler.\n--1332-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1332-- Nevertheless we consider this a bug. Please report\n--1332-- it at http://valgrind.org/support/bug_reports.html.\n--1332-- WARNING: unhandled riscv64-linux syscall: 258\n--1332-- You may be able to write your own handler.\n--1332-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1332-- Nevertheless we consider this a bug. Please report\n--1332-- it at http://valgrind.org/support/bug_reports.html.\n--1332-- WARNING: unhandled riscv64-linux syscall: 258\n--1332-- You may be able to write your own handler.\n--1332-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1332-- Nevertheless we consider this a bug. Please report\n--1332-- it at http://valgrind.org/support/bug_reports.html.\n--1332-- WARNING: unhandled riscv64-linux syscall: 258\n--1332-- You may be able to write your own handler.\n--1332-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1332-- Nevertheless we consider this a bug. Please report\n--1332-- it at http://valgrind.org/support/bug_reports.html.\n--1332-- WARNING: unhandled riscv64-linux syscall: 258\n--1332-- You may be able to write your own handler.\n--1332-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1332-- Nevertheless we consider this a bug. Please report\n--1332-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 9: failed https://example.com/test/../moo --- stdout --- expected: 'https://example.com/moo\n' got: 'https://example.com/moo\n' --- stderr --- expected: '' got: '--1340-- WARNING: unhandled riscv64-linux syscall: 258\n--1340-- You may be able to write your own handler.\n--1340-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1340-- Nevertheless we consider this a bug. Please report\n--1340-- it at http://valgrind.org/support/bug_reports.html.\n--1340-- WARNING: unhandled riscv64-linux syscall: 258\n--1340-- You may be able to write your own handler.\n--1340-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1340-- Nevertheless we consider this a bug. Please report\n--1340-- it at http://valgrind.org/support/bug_reports.html.\n--1340-- WARNING: unhandled riscv64-linux syscall: 258\n--1340-- You may be able to write your own handler.\n--1340-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1340-- Nevertheless we consider this a bug. Please report\n--1340-- it at http://valgrind.org/support/bug_reports.html.\n--1340-- WARNING: unhandled riscv64-linux syscall: 258\n--1340-- You may be able to write your own handler.\n--1340-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1340-- Nevertheless we consider this a bug. Please report\n--1340-- it at http://valgrind.org/support/bug_reports.html.\n--1340-- WARNING: unhandled riscv64-linux syscall: 258\n--1340-- You may be able to write your own handler.\n--1340-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1340-- Nevertheless we consider this a bug. Please report\n--1340-- it at http://valgrind.org/support/bug_reports.html.\n--1340-- WARNING: unhandled riscv64-linux syscall: 258\n--1340-- You may be able to write your own handler.\n--1340-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1340-- Nevertheless we consider this a bug. Please report\n--1340-- it at http://valgrind.org/support/bug_reports.html.\n--1340-- WARNING: unhandled riscv64-linux syscall: 258\n--1340-- You may be able to write your own handler.\n--1340-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1340-- Nevertheless we consider this a bug. Please report\n--1340-- it at http://valgrind.org/support/bug_reports.html.\n--1340-- WARNING: unhandled riscv64-linux syscall: 258\n--1340-- You may be able to write your own handler.\n--1340-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1340-- Nevertheless we consider this a bug. Please report\n--1340-- it at http://valgrind.org/support/bug_reports.html.\n--1340-- WARNING: unhandled riscv64-linux syscall: 258\n--1340-- You may be able to write your own handler.\n--1340-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1340-- Nevertheless we consider this a bug. Please report\n--1340-- it at http://valgrind.org/support/bug_reports.html.\n--1340-- WARNING: unhandled riscv64-linux syscall: 258\n--1340-- You may be able to write your own handler.\n--1340-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1340-- Nevertheless we consider this a bug. Please report\n--1340-- it at http://valgrind.org/support/bug_reports.html.\n--1340-- WARNING: unhandled riscv64-linux syscall: 258\n--1340-- You may be able to write your own handler.\n--1340-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1340-- Nevertheless we consider this a bug. Please report\n--1340-- it at http://valgrind.org/support/bug_reports.html.\n--1340-- WARNING: unhandled riscv64-linux syscall: 258\n--1340-- You may be able to write your own handler.\n--1340-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1340-- Nevertheless we consider this a bug. Please report\n--1340-- it at http://valgrind.org/support/bug_reports.html.\n--1340-- WARNING: unhandled riscv64-linux syscall: 258\n--1340-- You may be able to write your own handler.\n--1340-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1340-- Nevertheless we consider this a bug. Please report\n--1340-- it at http://valgrind.org/support/bug_reports.html.\n--1340-- WARNING: unhandled riscv64-linux syscall: 258\n--1340-- You may be able to write your own handler.\n--1340-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1340-- Nevertheless we consider this a bug. Please report\n--1340-- it at http://valgrind.org/support/bug_reports.html.\n--1340-- WARNING: unhandled riscv64-linux syscall: 258\n--1340-- You may be able to write your own handler.\n--1340-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1340-- Nevertheless we consider this a bug. Please report\n--1340-- it at http://valgrind.org/support/bug_reports.html.\n--1340-- WARNING: unhandled riscv64-linux syscall: 258\n--1340-- You may be able to write your own handler.\n--1340-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1340-- Nevertheless we consider this a bug. Please report\n--1340-- it at http://valgrind.org/support/bug_reports.html.\n--1340-- WARNING: unhandled riscv64-linux syscall: 258\n--1340-- You may be able to write your own handler.\n--1340-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1340-- Nevertheless we consider this a bug. Please report\n--1340-- it at http://valgrind.org/support/bug_reports.html.\n--1340-- WARNING: unhandled riscv64-linux syscall: 258\n--1340-- You may be able to write your own handler.\n--1340-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1340-- Nevertheless we consider this a bug. Please report\n--1340-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 10: failed localhost --append path=moo --- stdout --- expected: 'http://localhost/moo\n' got: 'http://localhost/moo\n' --- stderr --- expected: '' got: '--1348-- WARNING: unhandled riscv64-linux syscall: 258\n--1348-- You may be able to write your own handler.\n--1348-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1348-- Nevertheless we consider this a bug. Please report\n--1348-- it at http://valgrind.org/support/bug_reports.html.\n--1348-- WARNING: unhandled riscv64-linux syscall: 258\n--1348-- You may be able to write your own handler.\n--1348-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1348-- Nevertheless we consider this a bug. Please report\n--1348-- it at http://valgrind.org/support/bug_reports.html.\n--1348-- WARNING: unhandled riscv64-linux syscall: 258\n--1348-- You may be able to write your own handler.\n--1348-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1348-- Nevertheless we consider this a bug. Please report\n--1348-- it at http://valgrind.org/support/bug_reports.html.\n--1348-- WARNING: unhandled riscv64-linux syscall: 258\n--1348-- You may be able to write your own handler.\n--1348-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1348-- Nevertheless we consider this a bug. Please report\n--1348-- it at http://valgrind.org/support/bug_reports.html.\n--1348-- WARNING: unhandled riscv64-linux syscall: 258\n--1348-- You may be able to write your own handler.\n--1348-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1348-- Nevertheless we consider this a bug. Please report\n--1348-- it at http://valgrind.org/support/bug_reports.html.\n--1348-- WARNING: unhandled riscv64-linux syscall: 258\n--1348-- You may be able to write your own handler.\n--1348-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1348-- Nevertheless we consider this a bug. Please report\n--1348-- it at http://valgrind.org/support/bug_reports.html.\n--1348-- WARNING: unhandled riscv64-linux syscall: 258\n--1348-- You may be able to write your own handler.\n--1348-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1348-- Nevertheless we consider this a bug. Please report\n--1348-- it at http://valgrind.org/support/bug_reports.html.\n--1348-- WARNING: unhandled riscv64-linux syscall: 258\n--1348-- You may be able to write your own handler.\n--1348-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1348-- Nevertheless we consider this a bug. Please report\n--1348-- it at http://valgrind.org/support/bug_reports.html.\n--1348-- WARNING: unhandled riscv64-linux syscall: 258\n--1348-- You may be able to write your own handler.\n--1348-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1348-- Nevertheless we consider this a bug. Please report\n--1348-- it at http://valgrind.org/support/bug_reports.html.\n--1348-- WARNING: unhandled riscv64-linux syscall: 258\n--1348-- You may be able to write your own handler.\n--1348-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1348-- Nevertheless we consider this a bug. Please report\n--1348-- it at http://valgrind.org/support/bug_reports.html.\n--1348-- WARNING: unhandled riscv64-linux syscall: 258\n--1348-- You may be able to write your own handler.\n--1348-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1348-- Nevertheless we consider this a bug. Please report\n--1348-- it at http://valgrind.org/support/bug_reports.html.\n--1348-- WARNING: unhandled riscv64-linux syscall: 258\n--1348-- You may be able to write your own handler.\n--1348-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1348-- Nevertheless we consider this a bug. Please report\n--1348-- it at http://valgrind.org/support/bug_reports.html.\n--1348-- WARNING: unhandled riscv64-linux syscall: 258\n--1348-- You may be able to write your own handler.\n--1348-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1348-- Nevertheless we consider this a bug. Please report\n--1348-- it at http://valgrind.org/support/bug_reports.html.\n--1348-- WARNING: unhandled riscv64-linux syscall: 258\n--1348-- You may be able to write your own handler.\n--1348-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1348-- Nevertheless we consider this a bug. Please report\n--1348-- it at http://valgrind.org/support/bug_reports.html.\n--1348-- WARNING: unhandled riscv64-linux syscall: 258\n--1348-- You may be able to write your own handler.\n--1348-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1348-- Nevertheless we consider this a bug. Please report\n--1348-- it at http://valgrind.org/support/bug_reports.html.\n--1348-- WARNING: unhandled riscv64-linux syscall: 258\n--1348-- You may be able to write your own handler.\n--1348-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1348-- Nevertheless we consider this a bug. Please report\n--1348-- it at http://valgrind.org/support/bug_reports.html.\n--1348-- WARNING: unhandled riscv64-linux syscall: 258\n--1348-- You may be able to write your own handler.\n--1348-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1348-- Nevertheless we consider this a bug. Please report\n--1348-- it at http://valgrind.org/support/bug_reports.html.\n--1348-- WARNING: unhandled riscv64-linux syscall: 258\n--1348-- You may be able to write your own handler.\n--1348-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1348-- Nevertheless we consider this a bug. Please report\n--1348-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 11: failed localhost -a path=moo --- stdout --- expected: 'http://localhost/moo\n' got: 'http://localhost/moo\n' --- stderr --- expected: '' got: '--1356-- WARNING: unhandled riscv64-linux syscall: 258\n--1356-- You may be able to write your own handler.\n--1356-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1356-- Nevertheless we consider this a bug. Please report\n--1356-- it at http://valgrind.org/support/bug_reports.html.\n--1356-- WARNING: unhandled riscv64-linux syscall: 258\n--1356-- You may be able to write your own handler.\n--1356-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1356-- Nevertheless we consider this a bug. Please report\n--1356-- it at http://valgrind.org/support/bug_reports.html.\n--1356-- WARNING: unhandled riscv64-linux syscall: 258\n--1356-- You may be able to write your own handler.\n--1356-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1356-- Nevertheless we consider this a bug. Please report\n--1356-- it at http://valgrind.org/support/bug_reports.html.\n--1356-- WARNING: unhandled riscv64-linux syscall: 258\n--1356-- You may be able to write your own handler.\n--1356-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1356-- Nevertheless we consider this a bug. Please report\n--1356-- it at http://valgrind.org/support/bug_reports.html.\n--1356-- WARNING: unhandled riscv64-linux syscall: 258\n--1356-- You may be able to write your own handler.\n--1356-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1356-- Nevertheless we consider this a bug. Please report\n--1356-- it at http://valgrind.org/support/bug_reports.html.\n--1356-- WARNING: unhandled riscv64-linux syscall: 258\n--1356-- You may be able to write your own handler.\n--1356-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1356-- Nevertheless we consider this a bug. Please report\n--1356-- it at http://valgrind.org/support/bug_reports.html.\n--1356-- WARNING: unhandled riscv64-linux syscall: 258\n--1356-- You may be able to write your own handler.\n--1356-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1356-- Nevertheless we consider this a bug. Please report\n--1356-- it at http://valgrind.org/support/bug_reports.html.\n--1356-- WARNING: unhandled riscv64-linux syscall: 258\n--1356-- You may be able to write your own handler.\n--1356-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1356-- Nevertheless we consider this a bug. Please report\n--1356-- it at http://valgrind.org/support/bug_reports.html.\n--1356-- WARNING: unhandled riscv64-linux syscall: 258\n--1356-- You may be able to write your own handler.\n--1356-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1356-- Nevertheless we consider this a bug. Please report\n--1356-- it at http://valgrind.org/support/bug_reports.html.\n--1356-- WARNING: unhandled riscv64-linux syscall: 258\n--1356-- You may be able to write your own handler.\n--1356-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1356-- Nevertheless we consider this a bug. Please report\n--1356-- it at http://valgrind.org/support/bug_reports.html.\n--1356-- WARNING: unhandled riscv64-linux syscall: 258\n--1356-- You may be able to write your own handler.\n--1356-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1356-- Nevertheless we consider this a bug. Please report\n--1356-- it at http://valgrind.org/support/bug_reports.html.\n--1356-- WARNING: unhandled riscv64-linux syscall: 258\n--1356-- You may be able to write your own handler.\n--1356-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1356-- Nevertheless we consider this a bug. Please report\n--1356-- it at http://valgrind.org/support/bug_reports.html.\n--1356-- WARNING: unhandled riscv64-linux syscall: 258\n--1356-- You may be able to write your own handler.\n--1356-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1356-- Nevertheless we consider this a bug. Please report\n--1356-- it at http://valgrind.org/support/bug_reports.html.\n--1356-- WARNING: unhandled riscv64-linux syscall: 258\n--1356-- You may be able to write your own handler.\n--1356-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1356-- Nevertheless we consider this a bug. Please report\n--1356-- it at http://valgrind.org/support/bug_reports.html.\n--1356-- WARNING: unhandled riscv64-linux syscall: 258\n--1356-- You may be able to write your own handler.\n--1356-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1356-- Nevertheless we consider this a bug. Please report\n--1356-- it at http://valgrind.org/support/bug_reports.html.\n--1356-- WARNING: unhandled riscv64-linux syscall: 258\n--1356-- You may be able to write your own handler.\n--1356-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1356-- Nevertheless we consider this a bug. Please report\n--1356-- it at http://valgrind.org/support/bug_reports.html.\n--1356-- WARNING: unhandled riscv64-linux syscall: 258\n--1356-- You may be able to write your own handler.\n--1356-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1356-- Nevertheless we consider this a bug. Please report\n--1356-- it at http://valgrind.org/support/bug_reports.html.\n--1356-- WARNING: unhandled riscv64-linux syscall: 258\n--1356-- You may be able to write your own handler.\n--1356-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1356-- Nevertheless we consider this a bug. Please report\n--1356-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 12: failed --set host=moo --set scheme=http --- stdout --- expected: 'http://moo/\n' got: 'http://moo/\n' --- stderr --- expected: '' got: '--1364-- WARNING: unhandled riscv64-linux syscall: 258\n--1364-- You may be able to write your own handler.\n--1364-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1364-- Nevertheless we consider this a bug. Please report\n--1364-- it at http://valgrind.org/support/bug_reports.html.\n--1364-- WARNING: unhandled riscv64-linux syscall: 258\n--1364-- You may be able to write your own handler.\n--1364-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1364-- Nevertheless we consider this a bug. Please report\n--1364-- it at http://valgrind.org/support/bug_reports.html.\n--1364-- WARNING: unhandled riscv64-linux syscall: 258\n--1364-- You may be able to write your own handler.\n--1364-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1364-- Nevertheless we consider this a bug. Please report\n--1364-- it at http://valgrind.org/support/bug_reports.html.\n--1364-- WARNING: unhandled riscv64-linux syscall: 258\n--1364-- You may be able to write your own handler.\n--1364-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1364-- Nevertheless we consider this a bug. Please report\n--1364-- it at http://valgrind.org/support/bug_reports.html.\n--1364-- WARNING: unhandled riscv64-linux syscall: 258\n--1364-- You may be able to write your own handler.\n--1364-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1364-- Nevertheless we consider this a bug. Please report\n--1364-- it at http://valgrind.org/support/bug_reports.html.\n--1364-- WARNING: unhandled riscv64-linux syscall: 258\n--1364-- You may be able to write your own handler.\n--1364-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1364-- Nevertheless we consider this a bug. Please report\n--1364-- it at http://valgrind.org/support/bug_reports.html.\n--1364-- WARNING: unhandled riscv64-linux syscall: 258\n--1364-- You may be able to write your own handler.\n--1364-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1364-- Nevertheless we consider this a bug. Please report\n--1364-- it at http://valgrind.org/support/bug_reports.html.\n--1364-- WARNING: unhandled riscv64-linux syscall: 258\n--1364-- You may be able to write your own handler.\n--1364-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1364-- Nevertheless we consider this a bug. Please report\n--1364-- it at http://valgrind.org/support/bug_reports.html.\n--1364-- WARNING: unhandled riscv64-linux syscall: 258\n--1364-- You may be able to write your own handler.\n--1364-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1364-- Nevertheless we consider this a bug. Please report\n--1364-- it at http://valgrind.org/support/bug_reports.html.\n--1364-- WARNING: unhandled riscv64-linux syscall: 258\n--1364-- You may be able to write your own handler.\n--1364-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1364-- Nevertheless we consider this a bug. Please report\n--1364-- it at http://valgrind.org/support/bug_reports.html.\n--1364-- WARNING: unhandled riscv64-linux syscall: 258\n--1364-- You may be able to write your own handler.\n--1364-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1364-- Nevertheless we consider this a bug. Please report\n--1364-- it at http://valgrind.org/support/bug_reports.html.\n--1364-- WARNING: unhandled riscv64-linux syscall: 258\n--1364-- You may be able to write your own handler.\n--1364-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1364-- Nevertheless we consider this a bug. Please report\n--1364-- it at http://valgrind.org/support/bug_reports.html.\n--1364-- WARNING: unhandled riscv64-linux syscall: 258\n--1364-- You may be able to write your own handler.\n--1364-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1364-- Nevertheless we consider this a bug. Please report\n--1364-- it at http://valgrind.org/support/bug_reports.html.\n--1364-- WARNING: unhandled riscv64-linux syscall: 258\n--1364-- You may be able to write your own handler.\n--1364-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1364-- Nevertheless we consider this a bug. Please report\n--1364-- it at http://valgrind.org/support/bug_reports.html.\n--1364-- WARNING: unhandled riscv64-linux syscall: 258\n--1364-- You may be able to write your own handler.\n--1364-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1364-- Nevertheless we consider this a bug. Please report\n--1364-- it at http://valgrind.org/support/bug_reports.html.\n--1364-- WARNING: unhandled riscv64-linux syscall: 258\n--1364-- You may be able to write your own handler.\n--1364-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1364-- Nevertheless we consider this a bug. Please report\n--1364-- it at http://valgrind.org/support/bug_reports.html.\n--1364-- WARNING: unhandled riscv64-linux syscall: 258\n--1364-- You may be able to write your own handler.\n--1364-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1364-- Nevertheless we consider this a bug. Please report\n--1364-- it at http://valgrind.org/support/bug_reports.html.\n--1364-- WARNING: unhandled riscv64-linux syscall: 258\n--1364-- You may be able to write your own handler.\n--1364-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1364-- Nevertheless we consider this a bug. Please report\n--1364-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 13: failed -shost=moo -sscheme=http --- stdout --- expected: 'http://moo/\n' got: 'http://moo/\n' --- stderr --- expected: '' got: '--1372-- WARNING: unhandled riscv64-linux syscall: 258\n--1372-- You may be able to write your own handler.\n--1372-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1372-- Nevertheless we consider this a bug. Please report\n--1372-- it at http://valgrind.org/support/bug_reports.html.\n--1372-- WARNING: unhandled riscv64-linux syscall: 258\n--1372-- You may be able to write your own handler.\n--1372-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1372-- Nevertheless we consider this a bug. Please report\n--1372-- it at http://valgrind.org/support/bug_reports.html.\n--1372-- WARNING: unhandled riscv64-linux syscall: 258\n--1372-- You may be able to write your own handler.\n--1372-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1372-- Nevertheless we consider this a bug. Please report\n--1372-- it at http://valgrind.org/support/bug_reports.html.\n--1372-- WARNING: unhandled riscv64-linux syscall: 258\n--1372-- You may be able to write your own handler.\n--1372-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1372-- Nevertheless we consider this a bug. Please report\n--1372-- it at http://valgrind.org/support/bug_reports.html.\n--1372-- WARNING: unhandled riscv64-linux syscall: 258\n--1372-- You may be able to write your own handler.\n--1372-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1372-- Nevertheless we consider this a bug. Please report\n--1372-- it at http://valgrind.org/support/bug_reports.html.\n--1372-- WARNING: unhandled riscv64-linux syscall: 258\n--1372-- You may be able to write your own handler.\n--1372-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1372-- Nevertheless we consider this a bug. Please report\n--1372-- it at http://valgrind.org/support/bug_reports.html.\n--1372-- WARNING: unhandled riscv64-linux syscall: 258\n--1372-- You may be able to write your own handler.\n--1372-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1372-- Nevertheless we consider this a bug. Please report\n--1372-- it at http://valgrind.org/support/bug_reports.html.\n--1372-- WARNING: unhandled riscv64-linux syscall: 258\n--1372-- You may be able to write your own handler.\n--1372-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1372-- Nevertheless we consider this a bug. Please report\n--1372-- it at http://valgrind.org/support/bug_reports.html.\n--1372-- WARNING: unhandled riscv64-linux syscall: 258\n--1372-- You may be able to write your own handler.\n--1372-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1372-- Nevertheless we consider this a bug. Please report\n--1372-- it at http://valgrind.org/support/bug_reports.html.\n--1372-- WARNING: unhandled riscv64-linux syscall: 258\n--1372-- You may be able to write your own handler.\n--1372-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1372-- Nevertheless we consider this a bug. Please report\n--1372-- it at http://valgrind.org/support/bug_reports.html.\n--1372-- WARNING: unhandled riscv64-linux syscall: 258\n--1372-- You may be able to write your own handler.\n--1372-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1372-- Nevertheless we consider this a bug. Please report\n--1372-- it at http://valgrind.org/support/bug_reports.html.\n--1372-- WARNING: unhandled riscv64-linux syscall: 258\n--1372-- You may be able to write your own handler.\n--1372-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1372-- Nevertheless we consider this a bug. Please report\n--1372-- it at http://valgrind.org/support/bug_reports.html.\n--1372-- WARNING: unhandled riscv64-linux syscall: 258\n--1372-- You may be able to write your own handler.\n--1372-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1372-- Nevertheless we consider this a bug. Please report\n--1372-- it at http://valgrind.org/support/bug_reports.html.\n--1372-- WARNING: unhandled riscv64-linux syscall: 258\n--1372-- You may be able to write your own handler.\n--1372-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1372-- Nevertheless we consider this a bug. Please report\n--1372-- it at http://valgrind.org/support/bug_reports.html.\n--1372-- WARNING: unhandled riscv64-linux syscall: 258\n--1372-- You may be able to write your own handler.\n--1372-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1372-- Nevertheless we consider this a bug. Please report\n--1372-- it at http://valgrind.org/support/bug_reports.html.\n--1372-- WARNING: unhandled riscv64-linux syscall: 258\n--1372-- You may be able to write your own handler.\n--1372-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1372-- Nevertheless we consider this a bug. Please report\n--1372-- it at http://valgrind.org/support/bug_reports.html.\n--1372-- WARNING: unhandled riscv64-linux syscall: 258\n--1372-- You may be able to write your own handler.\n--1372-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1372-- Nevertheless we consider this a bug. Please report\n--1372-- it at http://valgrind.org/support/bug_reports.html.\n--1372-- WARNING: unhandled riscv64-linux syscall: 258\n--1372-- You may be able to write your own handler.\n--1372-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1372-- Nevertheless we consider this a bug. Please report\n--1372-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 14: failed --set=host=moo --set=scheme=http --- stdout --- expected: 'http://moo/\n' got: 'http://moo/\n' --- stderr --- expected: '' got: '--1380-- WARNING: unhandled riscv64-linux syscall: 258\n--1380-- You may be able to write your own handler.\n--1380-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1380-- Nevertheless we consider this a bug. Please report\n--1380-- it at http://valgrind.org/support/bug_reports.html.\n--1380-- WARNING: unhandled riscv64-linux syscall: 258\n--1380-- You may be able to write your own handler.\n--1380-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1380-- Nevertheless we consider this a bug. Please report\n--1380-- it at http://valgrind.org/support/bug_reports.html.\n--1380-- WARNING: unhandled riscv64-linux syscall: 258\n--1380-- You may be able to write your own handler.\n--1380-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1380-- Nevertheless we consider this a bug. Please report\n--1380-- it at http://valgrind.org/support/bug_reports.html.\n--1380-- WARNING: unhandled riscv64-linux syscall: 258\n--1380-- You may be able to write your own handler.\n--1380-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1380-- Nevertheless we consider this a bug. Please report\n--1380-- it at http://valgrind.org/support/bug_reports.html.\n--1380-- WARNING: unhandled riscv64-linux syscall: 258\n--1380-- You may be able to write your own handler.\n--1380-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1380-- Nevertheless we consider this a bug. Please report\n--1380-- it at http://valgrind.org/support/bug_reports.html.\n--1380-- WARNING: unhandled riscv64-linux syscall: 258\n--1380-- You may be able to write your own handler.\n--1380-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1380-- Nevertheless we consider this a bug. Please report\n--1380-- it at http://valgrind.org/support/bug_reports.html.\n--1380-- WARNING: unhandled riscv64-linux syscall: 258\n--1380-- You may be able to write your own handler.\n--1380-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1380-- Nevertheless we consider this a bug. Please report\n--1380-- it at http://valgrind.org/support/bug_reports.html.\n--1380-- WARNING: unhandled riscv64-linux syscall: 258\n--1380-- You may be able to write your own handler.\n--1380-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1380-- Nevertheless we consider this a bug. Please report\n--1380-- it at http://valgrind.org/support/bug_reports.html.\n--1380-- WARNING: unhandled riscv64-linux syscall: 258\n--1380-- You may be able to write your own handler.\n--1380-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1380-- Nevertheless we consider this a bug. Please report\n--1380-- it at http://valgrind.org/support/bug_reports.html.\n--1380-- WARNING: unhandled riscv64-linux syscall: 258\n--1380-- You may be able to write your own handler.\n--1380-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1380-- Nevertheless we consider this a bug. Please report\n--1380-- it at http://valgrind.org/support/bug_reports.html.\n--1380-- WARNING: unhandled riscv64-linux syscall: 258\n--1380-- You may be able to write your own handler.\n--1380-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1380-- Nevertheless we consider this a bug. Please report\n--1380-- it at http://valgrind.org/support/bug_reports.html.\n--1380-- WARNING: unhandled riscv64-linux syscall: 258\n--1380-- You may be able to write your own handler.\n--1380-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1380-- Nevertheless we consider this a bug. Please report\n--1380-- it at http://valgrind.org/support/bug_reports.html.\n--1380-- WARNING: unhandled riscv64-linux syscall: 258\n--1380-- You may be able to write your own handler.\n--1380-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1380-- Nevertheless we consider this a bug. Please report\n--1380-- it at http://valgrind.org/support/bug_reports.html.\n--1380-- WARNING: unhandled riscv64-linux syscall: 258\n--1380-- You may be able to write your own handler.\n--1380-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1380-- Nevertheless we consider this a bug. Please report\n--1380-- it at http://valgrind.org/support/bug_reports.html.\n--1380-- WARNING: unhandled riscv64-linux syscall: 258\n--1380-- You may be able to write your own handler.\n--1380-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1380-- Nevertheless we consider this a bug. Please report\n--1380-- it at http://valgrind.org/support/bug_reports.html.\n--1380-- WARNING: unhandled riscv64-linux syscall: 258\n--1380-- You may be able to write your own handler.\n--1380-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1380-- Nevertheless we consider this a bug. Please report\n--1380-- it at http://valgrind.org/support/bug_reports.html.\n--1380-- WARNING: unhandled riscv64-linux syscall: 258\n--1380-- You may be able to write your own handler.\n--1380-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1380-- Nevertheless we consider this a bug. Please report\n--1380-- it at http://valgrind.org/support/bug_reports.html.\n--1380-- WARNING: unhandled riscv64-linux syscall: 258\n--1380-- You may be able to write your own handler.\n--1380-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1380-- Nevertheless we consider this a bug. Please report\n--1380-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 15: failed -s host=moo -s scheme=http --- stdout --- expected: 'http://moo/\n' got: 'http://moo/\n' --- stderr --- expected: '' got: '--1388-- WARNING: unhandled riscv64-linux syscall: 258\n--1388-- You may be able to write your own handler.\n--1388-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1388-- Nevertheless we consider this a bug. Please report\n--1388-- it at http://valgrind.org/support/bug_reports.html.\n--1388-- WARNING: unhandled riscv64-linux syscall: 258\n--1388-- You may be able to write your own handler.\n--1388-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1388-- Nevertheless we consider this a bug. Please report\n--1388-- it at http://valgrind.org/support/bug_reports.html.\n--1388-- WARNING: unhandled riscv64-linux syscall: 258\n--1388-- You may be able to write your own handler.\n--1388-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1388-- Nevertheless we consider this a bug. Please report\n--1388-- it at http://valgrind.org/support/bug_reports.html.\n--1388-- WARNING: unhandled riscv64-linux syscall: 258\n--1388-- You may be able to write your own handler.\n--1388-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1388-- Nevertheless we consider this a bug. Please report\n--1388-- it at http://valgrind.org/support/bug_reports.html.\n--1388-- WARNING: unhandled riscv64-linux syscall: 258\n--1388-- You may be able to write your own handler.\n--1388-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1388-- Nevertheless we consider this a bug. Please report\n--1388-- it at http://valgrind.org/support/bug_reports.html.\n--1388-- WARNING: unhandled riscv64-linux syscall: 258\n--1388-- You may be able to write your own handler.\n--1388-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1388-- Nevertheless we consider this a bug. Please report\n--1388-- it at http://valgrind.org/support/bug_reports.html.\n--1388-- WARNING: unhandled riscv64-linux syscall: 258\n--1388-- You may be able to write your own handler.\n--1388-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1388-- Nevertheless we consider this a bug. Please report\n--1388-- it at http://valgrind.org/support/bug_reports.html.\n--1388-- WARNING: unhandled riscv64-linux syscall: 258\n--1388-- You may be able to write your own handler.\n--1388-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1388-- Nevertheless we consider this a bug. Please report\n--1388-- it at http://valgrind.org/support/bug_reports.html.\n--1388-- WARNING: unhandled riscv64-linux syscall: 258\n--1388-- You may be able to write your own handler.\n--1388-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1388-- Nevertheless we consider this a bug. Please report\n--1388-- it at http://valgrind.org/support/bug_reports.html.\n--1388-- WARNING: unhandled riscv64-linux syscall: 258\n--1388-- You may be able to write your own handler.\n--1388-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1388-- Nevertheless we consider this a bug. Please report\n--1388-- it at http://valgrind.org/support/bug_reports.html.\n--1388-- WARNING: unhandled riscv64-linux syscall: 258\n--1388-- You may be able to write your own handler.\n--1388-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1388-- Nevertheless we consider this a bug. Please report\n--1388-- it at http://valgrind.org/support/bug_reports.html.\n--1388-- WARNING: unhandled riscv64-linux syscall: 258\n--1388-- You may be able to write your own handler.\n--1388-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1388-- Nevertheless we consider this a bug. Please report\n--1388-- it at http://valgrind.org/support/bug_reports.html.\n--1388-- WARNING: unhandled riscv64-linux syscall: 258\n--1388-- You may be able to write your own handler.\n--1388-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1388-- Nevertheless we consider this a bug. Please report\n--1388-- it at http://valgrind.org/support/bug_reports.html.\n--1388-- WARNING: unhandled riscv64-linux syscall: 258\n--1388-- You may be able to write your own handler.\n--1388-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1388-- Nevertheless we consider this a bug. Please report\n--1388-- it at http://valgrind.org/support/bug_reports.html.\n--1388-- WARNING: unhandled riscv64-linux syscall: 258\n--1388-- You may be able to write your own handler.\n--1388-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1388-- Nevertheless we consider this a bug. Please report\n--1388-- it at http://valgrind.org/support/bug_reports.html.\n--1388-- WARNING: unhandled riscv64-linux syscall: 258\n--1388-- You may be able to write your own handler.\n--1388-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1388-- Nevertheless we consider this a bug. Please report\n--1388-- it at http://valgrind.org/support/bug_reports.html.\n--1388-- WARNING: unhandled riscv64-linux syscall: 258\n--1388-- You may be able to write your own handler.\n--1388-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1388-- Nevertheless we consider this a bug. Please report\n--1388-- it at http://valgrind.org/support/bug_reports.html.\n--1388-- WARNING: unhandled riscv64-linux syscall: 258\n--1388-- You may be able to write your own handler.\n--1388-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1388-- Nevertheless we consider this a bug. Please report\n--1388-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 16: failed --set host=moo --set scheme=https --set port=999 --- stdout --- expected: 'https://moo:999/\n' got: 'https://moo:999/\n' --- stderr --- expected: '' got: '--1396-- WARNING: unhandled riscv64-linux syscall: 258\n--1396-- You may be able to write your own handler.\n--1396-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1396-- Nevertheless we consider this a bug. Please report\n--1396-- it at http://valgrind.org/support/bug_reports.html.\n--1396-- WARNING: unhandled riscv64-linux syscall: 258\n--1396-- You may be able to write your own handler.\n--1396-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1396-- Nevertheless we consider this a bug. Please report\n--1396-- it at http://valgrind.org/support/bug_reports.html.\n--1396-- WARNING: unhandled riscv64-linux syscall: 258\n--1396-- You may be able to write your own handler.\n--1396-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1396-- Nevertheless we consider this a bug. Please report\n--1396-- it at http://valgrind.org/support/bug_reports.html.\n--1396-- WARNING: unhandled riscv64-linux syscall: 258\n--1396-- You may be able to write your own handler.\n--1396-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1396-- Nevertheless we consider this a bug. Please report\n--1396-- it at http://valgrind.org/support/bug_reports.html.\n--1396-- WARNING: unhandled riscv64-linux syscall: 258\n--1396-- You may be able to write your own handler.\n--1396-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1396-- Nevertheless we consider this a bug. Please report\n--1396-- it at http://valgrind.org/support/bug_reports.html.\n--1396-- WARNING: unhandled riscv64-linux syscall: 258\n--1396-- You may be able to write your own handler.\n--1396-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1396-- Nevertheless we consider this a bug. Please report\n--1396-- it at http://valgrind.org/support/bug_reports.html.\n--1396-- WARNING: unhandled riscv64-linux syscall: 258\n--1396-- You may be able to write your own handler.\n--1396-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1396-- Nevertheless we consider this a bug. Please report\n--1396-- it at http://valgrind.org/support/bug_reports.html.\n--1396-- WARNING: unhandled riscv64-linux syscall: 258\n--1396-- You may be able to write your own handler.\n--1396-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1396-- Nevertheless we consider this a bug. Please report\n--1396-- it at http://valgrind.org/support/bug_reports.html.\n--1396-- WARNING: unhandled riscv64-linux syscall: 258\n--1396-- You may be able to write your own handler.\n--1396-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1396-- Nevertheless we consider this a bug. Please report\n--1396-- it at http://valgrind.org/support/bug_reports.html.\n--1396-- WARNING: unhandled riscv64-linux syscall: 258\n--1396-- You may be able to write your own handler.\n--1396-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1396-- Nevertheless we consider this a bug. Please report\n--1396-- it at http://valgrind.org/support/bug_reports.html.\n--1396-- WARNING: unhandled riscv64-linux syscall: 258\n--1396-- You may be able to write your own handler.\n--1396-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1396-- Nevertheless we consider this a bug. Please report\n--1396-- it at http://valgrind.org/support/bug_reports.html.\n--1396-- WARNING: unhandled riscv64-linux syscall: 258\n--1396-- You may be able to write your own handler.\n--1396-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1396-- Nevertheless we consider this a bug. Please report\n--1396-- it at http://valgrind.org/support/bug_reports.html.\n--1396-- WARNING: unhandled riscv64-linux syscall: 258\n--1396-- You may be able to write your own handler.\n--1396-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1396-- Nevertheless we consider this a bug. Please report\n--1396-- it at http://valgrind.org/support/bug_reports.html.\n--1396-- WARNING: unhandled riscv64-linux syscall: 258\n--1396-- You may be able to write your own handler.\n--1396-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1396-- Nevertheless we consider this a bug. Please report\n--1396-- it at http://valgrind.org/support/bug_reports.html.\n--1396-- WARNING: unhandled riscv64-linux syscall: 258\n--1396-- You may be able to write your own handler.\n--1396-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1396-- Nevertheless we consider this a bug. Please report\n--1396-- it at http://valgrind.org/support/bug_reports.html.\n--1396-- WARNING: unhandled riscv64-linux syscall: 258\n--1396-- You may be able to write your own handler.\n--1396-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1396-- Nevertheless we consider this a bug. Please report\n--1396-- it at http://valgrind.org/support/bug_reports.html.\n--1396-- WARNING: unhandled riscv64-linux syscall: 258\n--1396-- You may be able to write your own handler.\n--1396-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1396-- Nevertheless we consider this a bug. Please report\n--1396-- it at http://valgrind.org/support/bug_reports.html.\n--1396-- WARNING: unhandled riscv64-linux syscall: 258\n--1396-- You may be able to write your own handler.\n--1396-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1396-- Nevertheless we consider this a bug. Please report\n--1396-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 17: failed --set host=moo --set scheme=ftps --set path=/hello --- stdout --- expected: 'ftps://moo/hello\n' got: 'ftps://moo/hello\n' --- stderr --- expected: '' got: '--1404-- WARNING: unhandled riscv64-linux syscall: 258\n--1404-- You may be able to write your own handler.\n--1404-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1404-- Nevertheless we consider this a bug. Please report\n--1404-- it at http://valgrind.org/support/bug_reports.html.\n--1404-- WARNING: unhandled riscv64-linux syscall: 258\n--1404-- You may be able to write your own handler.\n--1404-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1404-- Nevertheless we consider this a bug. Please report\n--1404-- it at http://valgrind.org/support/bug_reports.html.\n--1404-- WARNING: unhandled riscv64-linux syscall: 258\n--1404-- You may be able to write your own handler.\n--1404-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1404-- Nevertheless we consider this a bug. Please report\n--1404-- it at http://valgrind.org/support/bug_reports.html.\n--1404-- WARNING: unhandled riscv64-linux syscall: 258\n--1404-- You may be able to write your own handler.\n--1404-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1404-- Nevertheless we consider this a bug. Please report\n--1404-- it at http://valgrind.org/support/bug_reports.html.\n--1404-- WARNING: unhandled riscv64-linux syscall: 258\n--1404-- You may be able to write your own handler.\n--1404-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1404-- Nevertheless we consider this a bug. Please report\n--1404-- it at http://valgrind.org/support/bug_reports.html.\n--1404-- WARNING: unhandled riscv64-linux syscall: 258\n--1404-- You may be able to write your own handler.\n--1404-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1404-- Nevertheless we consider this a bug. Please report\n--1404-- it at http://valgrind.org/support/bug_reports.html.\n--1404-- WARNING: unhandled riscv64-linux syscall: 258\n--1404-- You may be able to write your own handler.\n--1404-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1404-- Nevertheless we consider this a bug. Please report\n--1404-- it at http://valgrind.org/support/bug_reports.html.\n--1404-- WARNING: unhandled riscv64-linux syscall: 258\n--1404-- You may be able to write your own handler.\n--1404-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1404-- Nevertheless we consider this a bug. Please report\n--1404-- it at http://valgrind.org/support/bug_reports.html.\n--1404-- WARNING: unhandled riscv64-linux syscall: 258\n--1404-- You may be able to write your own handler.\n--1404-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1404-- Nevertheless we consider this a bug. Please report\n--1404-- it at http://valgrind.org/support/bug_reports.html.\n--1404-- WARNING: unhandled riscv64-linux syscall: 258\n--1404-- You may be able to write your own handler.\n--1404-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1404-- Nevertheless we consider this a bug. Please report\n--1404-- it at http://valgrind.org/support/bug_reports.html.\n--1404-- WARNING: unhandled riscv64-linux syscall: 258\n--1404-- You may be able to write your own handler.\n--1404-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1404-- Nevertheless we consider this a bug. Please report\n--1404-- it at http://valgrind.org/support/bug_reports.html.\n--1404-- WARNING: unhandled riscv64-linux syscall: 258\n--1404-- You may be able to write your own handler.\n--1404-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1404-- Nevertheless we consider this a bug. Please report\n--1404-- it at http://valgrind.org/support/bug_reports.html.\n--1404-- WARNING: unhandled riscv64-linux syscall: 258\n--1404-- You may be able to write your own handler.\n--1404-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1404-- Nevertheless we consider this a bug. Please report\n--1404-- it at http://valgrind.org/support/bug_reports.html.\n--1404-- WARNING: unhandled riscv64-linux syscall: 258\n--1404-- You may be able to write your own handler.\n--1404-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1404-- Nevertheless we consider this a bug. Please report\n--1404-- it at http://valgrind.org/support/bug_reports.html.\n--1404-- WARNING: unhandled riscv64-linux syscall: 258\n--1404-- You may be able to write your own handler.\n--1404-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1404-- Nevertheless we consider this a bug. Please report\n--1404-- it at http://valgrind.org/support/bug_reports.html.\n--1404-- WARNING: unhandled riscv64-linux syscall: 258\n--1404-- You may be able to write your own handler.\n--1404-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1404-- Nevertheless we consider this a bug. Please report\n--1404-- it at http://valgrind.org/support/bug_reports.html.\n--1404-- WARNING: unhandled riscv64-linux syscall: 258\n--1404-- You may be able to write your own handler.\n--1404-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1404-- Nevertheless we consider this a bug. Please report\n--1404-- it at http://valgrind.org/support/bug_reports.html.\n--1404-- WARNING: unhandled riscv64-linux syscall: 258\n--1404-- You may be able to write your own handler.\n--1404-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1404-- Nevertheless we consider this a bug. Please report\n--1404-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 18: failed --url https://curl.se --set host=example.com --- stdout --- expected: 'https://example.com/\n' got: 'https://example.com/\n' --- stderr --- expected: '' got: '--1412-- WARNING: unhandled riscv64-linux syscall: 258\n--1412-- You may be able to write your own handler.\n--1412-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1412-- Nevertheless we consider this a bug. Please report\n--1412-- it at http://valgrind.org/support/bug_reports.html.\n--1412-- WARNING: unhandled riscv64-linux syscall: 258\n--1412-- You may be able to write your own handler.\n--1412-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1412-- Nevertheless we consider this a bug. Please report\n--1412-- it at http://valgrind.org/support/bug_reports.html.\n--1412-- WARNING: unhandled riscv64-linux syscall: 258\n--1412-- You may be able to write your own handler.\n--1412-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1412-- Nevertheless we consider this a bug. Please report\n--1412-- it at http://valgrind.org/support/bug_reports.html.\n--1412-- WARNING: unhandled riscv64-linux syscall: 258\n--1412-- You may be able to write your own handler.\n--1412-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1412-- Nevertheless we consider this a bug. Please report\n--1412-- it at http://valgrind.org/support/bug_reports.html.\n--1412-- WARNING: unhandled riscv64-linux syscall: 258\n--1412-- You may be able to write your own handler.\n--1412-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1412-- Nevertheless we consider this a bug. Please report\n--1412-- it at http://valgrind.org/support/bug_reports.html.\n--1412-- WARNING: unhandled riscv64-linux syscall: 258\n--1412-- You may be able to write your own handler.\n--1412-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1412-- Nevertheless we consider this a bug. Please report\n--1412-- it at http://valgrind.org/support/bug_reports.html.\n--1412-- WARNING: unhandled riscv64-linux syscall: 258\n--1412-- You may be able to write your own handler.\n--1412-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1412-- Nevertheless we consider this a bug. Please report\n--1412-- it at http://valgrind.org/support/bug_reports.html.\n--1412-- WARNING: unhandled riscv64-linux syscall: 258\n--1412-- You may be able to write your own handler.\n--1412-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1412-- Nevertheless we consider this a bug. Please report\n--1412-- it at http://valgrind.org/support/bug_reports.html.\n--1412-- WARNING: unhandled riscv64-linux syscall: 258\n--1412-- You may be able to write your own handler.\n--1412-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1412-- Nevertheless we consider this a bug. Please report\n--1412-- it at http://valgrind.org/support/bug_reports.html.\n--1412-- WARNING: unhandled riscv64-linux syscall: 258\n--1412-- You may be able to write your own handler.\n--1412-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1412-- Nevertheless we consider this a bug. Please report\n--1412-- it at http://valgrind.org/support/bug_reports.html.\n--1412-- WARNING: unhandled riscv64-linux syscall: 258\n--1412-- You may be able to write your own handler.\n--1412-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1412-- Nevertheless we consider this a bug. Please report\n--1412-- it at http://valgrind.org/support/bug_reports.html.\n--1412-- WARNING: unhandled riscv64-linux syscall: 258\n--1412-- You may be able to write your own handler.\n--1412-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1412-- Nevertheless we consider this a bug. Please report\n--1412-- it at http://valgrind.org/support/bug_reports.html.\n--1412-- WARNING: unhandled riscv64-linux syscall: 258\n--1412-- You may be able to write your own handler.\n--1412-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1412-- Nevertheless we consider this a bug. Please report\n--1412-- it at http://valgrind.org/support/bug_reports.html.\n--1412-- WARNING: unhandled riscv64-linux syscall: 258\n--1412-- You may be able to write your own handler.\n--1412-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1412-- Nevertheless we consider this a bug. Please report\n--1412-- it at http://valgrind.org/support/bug_reports.html.\n--1412-- WARNING: unhandled riscv64-linux syscall: 258\n--1412-- You may be able to write your own handler.\n--1412-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1412-- Nevertheless we consider this a bug. Please report\n--1412-- it at http://valgrind.org/support/bug_reports.html.\n--1412-- WARNING: unhandled riscv64-linux syscall: 258\n--1412-- You may be able to write your own handler.\n--1412-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1412-- Nevertheless we consider this a bug. Please report\n--1412-- it at http://valgrind.org/support/bug_reports.html.\n--1412-- WARNING: unhandled riscv64-linux syscall: 258\n--1412-- You may be able to write your own handler.\n--1412-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1412-- Nevertheless we consider this a bug. Please report\n--1412-- it at http://valgrind.org/support/bug_reports.html.\n--1412-- WARNING: unhandled riscv64-linux syscall: 258\n--1412-- You may be able to write your own handler.\n--1412-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1412-- Nevertheless we consider this a bug. Please report\n--1412-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 19: failed --set host=example.com --set scheme=ftp --- stdout --- expected: 'ftp://example.com/\n' got: 'ftp://example.com/\n' --- stderr --- expected: '' got: '--1420-- WARNING: unhandled riscv64-linux syscall: 258\n--1420-- You may be able to write your own handler.\n--1420-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1420-- Nevertheless we consider this a bug. Please report\n--1420-- it at http://valgrind.org/support/bug_reports.html.\n--1420-- WARNING: unhandled riscv64-linux syscall: 258\n--1420-- You may be able to write your own handler.\n--1420-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1420-- Nevertheless we consider this a bug. Please report\n--1420-- it at http://valgrind.org/support/bug_reports.html.\n--1420-- WARNING: unhandled riscv64-linux syscall: 258\n--1420-- You may be able to write your own handler.\n--1420-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1420-- Nevertheless we consider this a bug. Please report\n--1420-- it at http://valgrind.org/support/bug_reports.html.\n--1420-- WARNING: unhandled riscv64-linux syscall: 258\n--1420-- You may be able to write your own handler.\n--1420-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1420-- Nevertheless we consider this a bug. Please report\n--1420-- it at http://valgrind.org/support/bug_reports.html.\n--1420-- WARNING: unhandled riscv64-linux syscall: 258\n--1420-- You may be able to write your own handler.\n--1420-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1420-- Nevertheless we consider this a bug. Please report\n--1420-- it at http://valgrind.org/support/bug_reports.html.\n--1420-- WARNING: unhandled riscv64-linux syscall: 258\n--1420-- You may be able to write your own handler.\n--1420-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1420-- Nevertheless we consider this a bug. Please report\n--1420-- it at http://valgrind.org/support/bug_reports.html.\n--1420-- WARNING: unhandled riscv64-linux syscall: 258\n--1420-- You may be able to write your own handler.\n--1420-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1420-- Nevertheless we consider this a bug. Please report\n--1420-- it at http://valgrind.org/support/bug_reports.html.\n--1420-- WARNING: unhandled riscv64-linux syscall: 258\n--1420-- You may be able to write your own handler.\n--1420-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1420-- Nevertheless we consider this a bug. Please report\n--1420-- it at http://valgrind.org/support/bug_reports.html.\n--1420-- WARNING: unhandled riscv64-linux syscall: 258\n--1420-- You may be able to write your own handler.\n--1420-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1420-- Nevertheless we consider this a bug. Please report\n--1420-- it at http://valgrind.org/support/bug_reports.html.\n--1420-- WARNING: unhandled riscv64-linux syscall: 258\n--1420-- You may be able to write your own handler.\n--1420-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1420-- Nevertheless we consider this a bug. Please report\n--1420-- it at http://valgrind.org/support/bug_reports.html.\n--1420-- WARNING: unhandled riscv64-linux syscall: 258\n--1420-- You may be able to write your own handler.\n--1420-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1420-- Nevertheless we consider this a bug. Please report\n--1420-- it at http://valgrind.org/support/bug_reports.html.\n--1420-- WARNING: unhandled riscv64-linux syscall: 258\n--1420-- You may be able to write your own handler.\n--1420-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1420-- Nevertheless we consider this a bug. Please report\n--1420-- it at http://valgrind.org/support/bug_reports.html.\n--1420-- WARNING: unhandled riscv64-linux syscall: 258\n--1420-- You may be able to write your own handler.\n--1420-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1420-- Nevertheless we consider this a bug. Please report\n--1420-- it at http://valgrind.org/support/bug_reports.html.\n--1420-- WARNING: unhandled riscv64-linux syscall: 258\n--1420-- You may be able to write your own handler.\n--1420-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1420-- Nevertheless we consider this a bug. Please report\n--1420-- it at http://valgrind.org/support/bug_reports.html.\n--1420-- WARNING: unhandled riscv64-linux syscall: 258\n--1420-- You may be able to write your own handler.\n--1420-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1420-- Nevertheless we consider this a bug. Please report\n--1420-- it at http://valgrind.org/support/bug_reports.html.\n--1420-- WARNING: unhandled riscv64-linux syscall: 258\n--1420-- You may be able to write your own handler.\n--1420-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1420-- Nevertheless we consider this a bug. Please report\n--1420-- it at http://valgrind.org/support/bug_reports.html.\n--1420-- WARNING: unhandled riscv64-linux syscall: 258\n--1420-- You may be able to write your own handler.\n--1420-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1420-- Nevertheless we consider this a bug. Please report\n--1420-- it at http://valgrind.org/support/bug_reports.html.\n--1420-- WARNING: unhandled riscv64-linux syscall: 258\n--1420-- You may be able to write your own handler.\n--1420-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1420-- Nevertheless we consider this a bug. Please report\n--1420-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 20: failed --url https://curl.se/we/are.html --redirect here.html --- stdout --- expected: 'https://curl.se/we/here.html\n' got: 'https://curl.se/we/here.html\n' --- stderr --- expected: '' got: '--1428-- WARNING: unhandled riscv64-linux syscall: 258\n--1428-- You may be able to write your own handler.\n--1428-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1428-- Nevertheless we consider this a bug. Please report\n--1428-- it at http://valgrind.org/support/bug_reports.html.\n--1428-- WARNING: unhandled riscv64-linux syscall: 258\n--1428-- You may be able to write your own handler.\n--1428-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1428-- Nevertheless we consider this a bug. Please report\n--1428-- it at http://valgrind.org/support/bug_reports.html.\n--1428-- WARNING: unhandled riscv64-linux syscall: 258\n--1428-- You may be able to write your own handler.\n--1428-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1428-- Nevertheless we consider this a bug. Please report\n--1428-- it at http://valgrind.org/support/bug_reports.html.\n--1428-- WARNING: unhandled riscv64-linux syscall: 258\n--1428-- You may be able to write your own handler.\n--1428-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1428-- Nevertheless we consider this a bug. Please report\n--1428-- it at http://valgrind.org/support/bug_reports.html.\n--1428-- WARNING: unhandled riscv64-linux syscall: 258\n--1428-- You may be able to write your own handler.\n--1428-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1428-- Nevertheless we consider this a bug. Please report\n--1428-- it at http://valgrind.org/support/bug_reports.html.\n--1428-- WARNING: unhandled riscv64-linux syscall: 258\n--1428-- You may be able to write your own handler.\n--1428-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1428-- Nevertheless we consider this a bug. Please report\n--1428-- it at http://valgrind.org/support/bug_reports.html.\n--1428-- WARNING: unhandled riscv64-linux syscall: 258\n--1428-- You may be able to write your own handler.\n--1428-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1428-- Nevertheless we consider this a bug. Please report\n--1428-- it at http://valgrind.org/support/bug_reports.html.\n--1428-- WARNING: unhandled riscv64-linux syscall: 258\n--1428-- You may be able to write your own handler.\n--1428-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1428-- Nevertheless we consider this a bug. Please report\n--1428-- it at http://valgrind.org/support/bug_reports.html.\n--1428-- WARNING: unhandled riscv64-linux syscall: 258\n--1428-- You may be able to write your own handler.\n--1428-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1428-- Nevertheless we consider this a bug. Please report\n--1428-- it at http://valgrind.org/support/bug_reports.html.\n--1428-- WARNING: unhandled riscv64-linux syscall: 258\n--1428-- You may be able to write your own handler.\n--1428-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1428-- Nevertheless we consider this a bug. Please report\n--1428-- it at http://valgrind.org/support/bug_reports.html.\n--1428-- WARNING: unhandled riscv64-linux syscall: 258\n--1428-- You may be able to write your own handler.\n--1428-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1428-- Nevertheless we consider this a bug. Please report\n--1428-- it at http://valgrind.org/support/bug_reports.html.\n--1428-- WARNING: unhandled riscv64-linux syscall: 258\n--1428-- You may be able to write your own handler.\n--1428-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1428-- Nevertheless we consider this a bug. Please report\n--1428-- it at http://valgrind.org/support/bug_reports.html.\n--1428-- WARNING: unhandled riscv64-linux syscall: 258\n--1428-- You may be able to write your own handler.\n--1428-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1428-- Nevertheless we consider this a bug. Please report\n--1428-- it at http://valgrind.org/support/bug_reports.html.\n--1428-- WARNING: unhandled riscv64-linux syscall: 258\n--1428-- You may be able to write your own handler.\n--1428-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1428-- Nevertheless we consider this a bug. Please report\n--1428-- it at http://valgrind.org/support/bug_reports.html.\n--1428-- WARNING: unhandled riscv64-linux syscall: 258\n--1428-- You may be able to write your own handler.\n--1428-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1428-- Nevertheless we consider this a bug. Please report\n--1428-- it at http://valgrind.org/support/bug_reports.html.\n--1428-- WARNING: unhandled riscv64-linux syscall: 258\n--1428-- You may be able to write your own handler.\n--1428-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1428-- Nevertheless we consider this a bug. Please report\n--1428-- it at http://valgrind.org/support/bug_reports.html.\n--1428-- WARNING: unhandled riscv64-linux syscall: 258\n--1428-- You may be able to write your own handler.\n--1428-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1428-- Nevertheless we consider this a bug. Please report\n--1428-- it at http://valgrind.org/support/bug_reports.html.\n--1428-- WARNING: unhandled riscv64-linux syscall: 258\n--1428-- You may be able to write your own handler.\n--1428-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1428-- Nevertheless we consider this a bug. Please report\n--1428-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 21: failed --url https://curl.se/we/../are.html --set port=8080 --- stdout --- expected: 'https://curl.se:8080/are.html\n' got: 'https://curl.se:8080/are.html\n' --- stderr --- expected: '' got: '--1436-- WARNING: unhandled riscv64-linux syscall: 258\n--1436-- You may be able to write your own handler.\n--1436-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1436-- Nevertheless we consider this a bug. Please report\n--1436-- it at http://valgrind.org/support/bug_reports.html.\n--1436-- WARNING: unhandled riscv64-linux syscall: 258\n--1436-- You may be able to write your own handler.\n--1436-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1436-- Nevertheless we consider this a bug. Please report\n--1436-- it at http://valgrind.org/support/bug_reports.html.\n--1436-- WARNING: unhandled riscv64-linux syscall: 258\n--1436-- You may be able to write your own handler.\n--1436-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1436-- Nevertheless we consider this a bug. Please report\n--1436-- it at http://valgrind.org/support/bug_reports.html.\n--1436-- WARNING: unhandled riscv64-linux syscall: 258\n--1436-- You may be able to write your own handler.\n--1436-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1436-- Nevertheless we consider this a bug. Please report\n--1436-- it at http://valgrind.org/support/bug_reports.html.\n--1436-- WARNING: unhandled riscv64-linux syscall: 258\n--1436-- You may be able to write your own handler.\n--1436-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1436-- Nevertheless we consider this a bug. Please report\n--1436-- it at http://valgrind.org/support/bug_reports.html.\n--1436-- WARNING: unhandled riscv64-linux syscall: 258\n--1436-- You may be able to write your own handler.\n--1436-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1436-- Nevertheless we consider this a bug. Please report\n--1436-- it at http://valgrind.org/support/bug_reports.html.\n--1436-- WARNING: unhandled riscv64-linux syscall: 258\n--1436-- You may be able to write your own handler.\n--1436-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1436-- Nevertheless we consider this a bug. Please report\n--1436-- it at http://valgrind.org/support/bug_reports.html.\n--1436-- WARNING: unhandled riscv64-linux syscall: 258\n--1436-- You may be able to write your own handler.\n--1436-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1436-- Nevertheless we consider this a bug. Please report\n--1436-- it at http://valgrind.org/support/bug_reports.html.\n--1436-- WARNING: unhandled riscv64-linux syscall: 258\n--1436-- You may be able to write your own handler.\n--1436-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1436-- Nevertheless we consider this a bug. Please report\n--1436-- it at http://valgrind.org/support/bug_reports.html.\n--1436-- WARNING: unhandled riscv64-linux syscall: 258\n--1436-- You may be able to write your own handler.\n--1436-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1436-- Nevertheless we consider this a bug. Please report\n--1436-- it at http://valgrind.org/support/bug_reports.html.\n--1436-- WARNING: unhandled riscv64-linux syscall: 258\n--1436-- You may be able to write your own handler.\n--1436-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1436-- Nevertheless we consider this a bug. Please report\n--1436-- it at http://valgrind.org/support/bug_reports.html.\n--1436-- WARNING: unhandled riscv64-linux syscall: 258\n--1436-- You may be able to write your own handler.\n--1436-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1436-- Nevertheless we consider this a bug. Please report\n--1436-- it at http://valgrind.org/support/bug_reports.html.\n--1436-- WARNING: unhandled riscv64-linux syscall: 258\n--1436-- You may be able to write your own handler.\n--1436-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1436-- Nevertheless we consider this a bug. Please report\n--1436-- it at http://valgrind.org/support/bug_reports.html.\n--1436-- WARNING: unhandled riscv64-linux syscall: 258\n--1436-- You may be able to write your own handler.\n--1436-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1436-- Nevertheless we consider this a bug. Please report\n--1436-- it at http://valgrind.org/support/bug_reports.html.\n--1436-- WARNING: unhandled riscv64-linux syscall: 258\n--1436-- You may be able to write your own handler.\n--1436-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1436-- Nevertheless we consider this a bug. Please report\n--1436-- it at http://valgrind.org/support/bug_reports.html.\n--1436-- WARNING: unhandled riscv64-linux syscall: 258\n--1436-- You may be able to write your own handler.\n--1436-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1436-- Nevertheless we consider this a bug. Please report\n--1436-- it at http://valgrind.org/support/bug_reports.html.\n--1436-- WARNING: unhandled riscv64-linux syscall: 258\n--1436-- You may be able to write your own handler.\n--1436-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1436-- Nevertheless we consider this a bug. Please report\n--1436-- it at http://valgrind.org/support/bug_reports.html.\n--1436-- WARNING: unhandled riscv64-linux syscall: 258\n--1436-- You may be able to write your own handler.\n--1436-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1436-- Nevertheless we consider this a bug. Please report\n--1436-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 22: failed imap://curl.se:22/ -s port=143 --- stdout --- expected: 'imap://curl.se/\n' got: 'imap://curl.se/\n' --- stderr --- expected: '' got: '--1444-- WARNING: unhandled riscv64-linux syscall: 258\n--1444-- You may be able to write your own handler.\n--1444-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1444-- Nevertheless we consider this a bug. Please report\n--1444-- it at http://valgrind.org/support/bug_reports.html.\n--1444-- WARNING: unhandled riscv64-linux syscall: 258\n--1444-- You may be able to write your own handler.\n--1444-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1444-- Nevertheless we consider this a bug. Please report\n--1444-- it at http://valgrind.org/support/bug_reports.html.\n--1444-- WARNING: unhandled riscv64-linux syscall: 258\n--1444-- You may be able to write your own handler.\n--1444-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1444-- Nevertheless we consider this a bug. Please report\n--1444-- it at http://valgrind.org/support/bug_reports.html.\n--1444-- WARNING: unhandled riscv64-linux syscall: 258\n--1444-- You may be able to write your own handler.\n--1444-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1444-- Nevertheless we consider this a bug. Please report\n--1444-- it at http://valgrind.org/support/bug_reports.html.\n--1444-- WARNING: unhandled riscv64-linux syscall: 258\n--1444-- You may be able to write your own handler.\n--1444-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1444-- Nevertheless we consider this a bug. Please report\n--1444-- it at http://valgrind.org/support/bug_reports.html.\n--1444-- WARNING: unhandled riscv64-linux syscall: 258\n--1444-- You may be able to write your own handler.\n--1444-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1444-- Nevertheless we consider this a bug. Please report\n--1444-- it at http://valgrind.org/support/bug_reports.html.\n--1444-- WARNING: unhandled riscv64-linux syscall: 258\n--1444-- You may be able to write your own handler.\n--1444-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1444-- Nevertheless we consider this a bug. Please report\n--1444-- it at http://valgrind.org/support/bug_reports.html.\n--1444-- WARNING: unhandled riscv64-linux syscall: 258\n--1444-- You may be able to write your own handler.\n--1444-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1444-- Nevertheless we consider this a bug. Please report\n--1444-- it at http://valgrind.org/support/bug_reports.html.\n--1444-- WARNING: unhandled riscv64-linux syscall: 258\n--1444-- You may be able to write your own handler.\n--1444-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1444-- Nevertheless we consider this a bug. Please report\n--1444-- it at http://valgrind.org/support/bug_reports.html.\n--1444-- WARNING: unhandled riscv64-linux syscall: 258\n--1444-- You may be able to write your own handler.\n--1444-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1444-- Nevertheless we consider this a bug. Please report\n--1444-- it at http://valgrind.org/support/bug_reports.html.\n--1444-- WARNING: unhandled riscv64-linux syscall: 258\n--1444-- You may be able to write your own handler.\n--1444-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1444-- Nevertheless we consider this a bug. Please report\n--1444-- it at http://valgrind.org/support/bug_reports.html.\n--1444-- WARNING: unhandled riscv64-linux syscall: 258\n--1444-- You may be able to write your own handler.\n--1444-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1444-- Nevertheless we consider this a bug. Please report\n--1444-- it at http://valgrind.org/support/bug_reports.html.\n--1444-- WARNING: unhandled riscv64-linux syscall: 258\n--1444-- You may be able to write your own handler.\n--1444-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1444-- Nevertheless we consider this a bug. Please report\n--1444-- it at http://valgrind.org/support/bug_reports.html.\n--1444-- WARNING: unhandled riscv64-linux syscall: 258\n--1444-- You may be able to write your own handler.\n--1444-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1444-- Nevertheless we consider this a bug. Please report\n--1444-- it at http://valgrind.org/support/bug_reports.html.\n--1444-- WARNING: unhandled riscv64-linux syscall: 258\n--1444-- You may be able to write your own handler.\n--1444-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1444-- Nevertheless we consider this a bug. Please report\n--1444-- it at http://valgrind.org/support/bug_reports.html.\n--1444-- WARNING: unhandled riscv64-linux syscall: 258\n--1444-- You may be able to write your own handler.\n--1444-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1444-- Nevertheless we consider this a bug. Please report\n--1444-- it at http://valgrind.org/support/bug_reports.html.\n--1444-- WARNING: unhandled riscv64-linux syscall: 258\n--1444-- You may be able to write your own handler.\n--1444-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1444-- Nevertheless we consider this a bug. Please report\n--1444-- it at http://valgrind.org/support/bug_reports.html.\n--1444-- WARNING: unhandled riscv64-linux syscall: 258\n--1444-- You may be able to write your own handler.\n--1444-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1444-- Nevertheless we consider this a bug. Please report\n--1444-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 23: failed --keep-port https://curl.se:22/ -s port=443 --- stdout --- expected: 'https://curl.se:443/\n' got: 'https://curl.se:443/\n' --- stderr --- expected: '' got: '--1452-- WARNING: unhandled riscv64-linux syscall: 258\n--1452-- You may be able to write your own handler.\n--1452-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1452-- Nevertheless we consider this a bug. Please report\n--1452-- it at http://valgrind.org/support/bug_reports.html.\n--1452-- WARNING: unhandled riscv64-linux syscall: 258\n--1452-- You may be able to write your own handler.\n--1452-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1452-- Nevertheless we consider this a bug. Please report\n--1452-- it at http://valgrind.org/support/bug_reports.html.\n--1452-- WARNING: unhandled riscv64-linux syscall: 258\n--1452-- You may be able to write your own handler.\n--1452-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1452-- Nevertheless we consider this a bug. Please report\n--1452-- it at http://valgrind.org/support/bug_reports.html.\n--1452-- WARNING: unhandled riscv64-linux syscall: 258\n--1452-- You may be able to write your own handler.\n--1452-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1452-- Nevertheless we consider this a bug. Please report\n--1452-- it at http://valgrind.org/support/bug_reports.html.\n--1452-- WARNING: unhandled riscv64-linux syscall: 258\n--1452-- You may be able to write your own handler.\n--1452-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1452-- Nevertheless we consider this a bug. Please report\n--1452-- it at http://valgrind.org/support/bug_reports.html.\n--1452-- WARNING: unhandled riscv64-linux syscall: 258\n--1452-- You may be able to write your own handler.\n--1452-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1452-- Nevertheless we consider this a bug. Please report\n--1452-- it at http://valgrind.org/support/bug_reports.html.\n--1452-- WARNING: unhandled riscv64-linux syscall: 258\n--1452-- You may be able to write your own handler.\n--1452-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1452-- Nevertheless we consider this a bug. Please report\n--1452-- it at http://valgrind.org/support/bug_reports.html.\n--1452-- WARNING: unhandled riscv64-linux syscall: 258\n--1452-- You may be able to write your own handler.\n--1452-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1452-- Nevertheless we consider this a bug. Please report\n--1452-- it at http://valgrind.org/support/bug_reports.html.\n--1452-- WARNING: unhandled riscv64-linux syscall: 258\n--1452-- You may be able to write your own handler.\n--1452-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1452-- Nevertheless we consider this a bug. Please report\n--1452-- it at http://valgrind.org/support/bug_reports.html.\n--1452-- WARNING: unhandled riscv64-linux syscall: 258\n--1452-- You may be able to write your own handler.\n--1452-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1452-- Nevertheless we consider this a bug. Please report\n--1452-- it at http://valgrind.org/support/bug_reports.html.\n--1452-- WARNING: unhandled riscv64-linux syscall: 258\n--1452-- You may be able to write your own handler.\n--1452-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1452-- Nevertheless we consider this a bug. Please report\n--1452-- it at http://valgrind.org/support/bug_reports.html.\n--1452-- WARNING: unhandled riscv64-linux syscall: 258\n--1452-- You may be able to write your own handler.\n--1452-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1452-- Nevertheless we consider this a bug. Please report\n--1452-- it at http://valgrind.org/support/bug_reports.html.\n--1452-- WARNING: unhandled riscv64-linux syscall: 258\n--1452-- You may be able to write your own handler.\n--1452-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1452-- Nevertheless we consider this a bug. Please report\n--1452-- it at http://valgrind.org/support/bug_reports.html.\n--1452-- WARNING: unhandled riscv64-linux syscall: 258\n--1452-- You may be able to write your own handler.\n--1452-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1452-- Nevertheless we consider this a bug. Please report\n--1452-- it at http://valgrind.org/support/bug_reports.html.\n--1452-- WARNING: unhandled riscv64-linux syscall: 258\n--1452-- You may be able to write your own handler.\n--1452-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1452-- Nevertheless we consider this a bug. Please report\n--1452-- it at http://valgrind.org/support/bug_reports.html.\n--1452-- WARNING: unhandled riscv64-linux syscall: 258\n--1452-- You may be able to write your own handler.\n--1452-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1452-- Nevertheless we consider this a bug. Please report\n--1452-- it at http://valgrind.org/support/bug_reports.html.\n--1452-- WARNING: unhandled riscv64-linux syscall: 258\n--1452-- You may be able to write your own handler.\n--1452-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1452-- Nevertheless we consider this a bug. Please report\n--1452-- it at http://valgrind.org/support/bug_reports.html.\n--1452-- WARNING: unhandled riscv64-linux syscall: 258\n--1452-- You may be able to write your own handler.\n--1452-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1452-- Nevertheless we consider this a bug. Please report\n--1452-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 24: failed --keep-port https://curl.se:22/ -s port=443 --get '{url}' --- stdout --- expected: 'https://curl.se:443/\n' got: 'https://curl.se:443/\n' --- stderr --- expected: '' got: '--1460-- WARNING: unhandled riscv64-linux syscall: 258\n--1460-- You may be able to write your own handler.\n--1460-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1460-- Nevertheless we consider this a bug. Please report\n--1460-- it at http://valgrind.org/support/bug_reports.html.\n--1460-- WARNING: unhandled riscv64-linux syscall: 258\n--1460-- You may be able to write your own handler.\n--1460-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1460-- Nevertheless we consider this a bug. Please report\n--1460-- it at http://valgrind.org/support/bug_reports.html.\n--1460-- WARNING: unhandled riscv64-linux syscall: 258\n--1460-- You may be able to write your own handler.\n--1460-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1460-- Nevertheless we consider this a bug. Please report\n--1460-- it at http://valgrind.org/support/bug_reports.html.\n--1460-- WARNING: unhandled riscv64-linux syscall: 258\n--1460-- You may be able to write your own handler.\n--1460-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1460-- Nevertheless we consider this a bug. Please report\n--1460-- it at http://valgrind.org/support/bug_reports.html.\n--1460-- WARNING: unhandled riscv64-linux syscall: 258\n--1460-- You may be able to write your own handler.\n--1460-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1460-- Nevertheless we consider this a bug. Please report\n--1460-- it at http://valgrind.org/support/bug_reports.html.\n--1460-- WARNING: unhandled riscv64-linux syscall: 258\n--1460-- You may be able to write your own handler.\n--1460-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1460-- Nevertheless we consider this a bug. Please report\n--1460-- it at http://valgrind.org/support/bug_reports.html.\n--1460-- WARNING: unhandled riscv64-linux syscall: 258\n--1460-- You may be able to write your own handler.\n--1460-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1460-- Nevertheless we consider this a bug. Please report\n--1460-- it at http://valgrind.org/support/bug_reports.html.\n--1460-- WARNING: unhandled riscv64-linux syscall: 258\n--1460-- You may be able to write your own handler.\n--1460-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1460-- Nevertheless we consider this a bug. Please report\n--1460-- it at http://valgrind.org/support/bug_reports.html.\n--1460-- WARNING: unhandled riscv64-linux syscall: 258\n--1460-- You may be able to write your own handler.\n--1460-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1460-- Nevertheless we consider this a bug. Please report\n--1460-- it at http://valgrind.org/support/bug_reports.html.\n--1460-- WARNING: unhandled riscv64-linux syscall: 258\n--1460-- You may be able to write your own handler.\n--1460-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1460-- Nevertheless we consider this a bug. Please report\n--1460-- it at http://valgrind.org/support/bug_reports.html.\n--1460-- WARNING: unhandled riscv64-linux syscall: 258\n--1460-- You may be able to write your own handler.\n--1460-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1460-- Nevertheless we consider this a bug. Please report\n--1460-- it at http://valgrind.org/support/bug_reports.html.\n--1460-- WARNING: unhandled riscv64-linux syscall: 258\n--1460-- You may be able to write your own handler.\n--1460-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1460-- Nevertheless we consider this a bug. Please report\n--1460-- it at http://valgrind.org/support/bug_reports.html.\n--1460-- WARNING: unhandled riscv64-linux syscall: 258\n--1460-- You may be able to write your own handler.\n--1460-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1460-- Nevertheless we consider this a bug. Please report\n--1460-- it at http://valgrind.org/support/bug_reports.html.\n--1460-- WARNING: unhandled riscv64-linux syscall: 258\n--1460-- You may be able to write your own handler.\n--1460-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1460-- Nevertheless we consider this a bug. Please report\n--1460-- it at http://valgrind.org/support/bug_reports.html.\n--1460-- WARNING: unhandled riscv64-linux syscall: 258\n--1460-- You may be able to write your own handler.\n--1460-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1460-- Nevertheless we consider this a bug. Please report\n--1460-- it at http://valgrind.org/support/bug_reports.html.\n--1460-- WARNING: unhandled riscv64-linux syscall: 258\n--1460-- You may be able to write your own handler.\n--1460-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1460-- Nevertheless we consider this a bug. Please report\n--1460-- it at http://valgrind.org/support/bug_reports.html.\n--1460-- WARNING: unhandled riscv64-linux syscall: 258\n--1460-- You may be able to write your own handler.\n--1460-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1460-- Nevertheless we consider this a bug. Please report\n--1460-- it at http://valgrind.org/support/bug_reports.html.\n--1460-- WARNING: unhandled riscv64-linux syscall: 258\n--1460-- You may be able to write your own handler.\n--1460-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1460-- Nevertheless we consider this a bug. Please report\n--1460-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 25: failed --url https://curl.se/we/are.html --get '{path}' --- stdout --- expected: '/we/are.html\n' got: '/we/are.html\n' --- stderr --- expected: '' got: '--1468-- WARNING: unhandled riscv64-linux syscall: 258\n--1468-- You may be able to write your own handler.\n--1468-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1468-- Nevertheless we consider this a bug. Please report\n--1468-- it at http://valgrind.org/support/bug_reports.html.\n--1468-- WARNING: unhandled riscv64-linux syscall: 258\n--1468-- You may be able to write your own handler.\n--1468-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1468-- Nevertheless we consider this a bug. Please report\n--1468-- it at http://valgrind.org/support/bug_reports.html.\n--1468-- WARNING: unhandled riscv64-linux syscall: 258\n--1468-- You may be able to write your own handler.\n--1468-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1468-- Nevertheless we consider this a bug. Please report\n--1468-- it at http://valgrind.org/support/bug_reports.html.\n--1468-- WARNING: unhandled riscv64-linux syscall: 258\n--1468-- You may be able to write your own handler.\n--1468-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1468-- Nevertheless we consider this a bug. Please report\n--1468-- it at http://valgrind.org/support/bug_reports.html.\n--1468-- WARNING: unhandled riscv64-linux syscall: 258\n--1468-- You may be able to write your own handler.\n--1468-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1468-- Nevertheless we consider this a bug. Please report\n--1468-- it at http://valgrind.org/support/bug_reports.html.\n--1468-- WARNING: unhandled riscv64-linux syscall: 258\n--1468-- You may be able to write your own handler.\n--1468-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1468-- Nevertheless we consider this a bug. Please report\n--1468-- it at http://valgrind.org/support/bug_reports.html.\n--1468-- WARNING: unhandled riscv64-linux syscall: 258\n--1468-- You may be able to write your own handler.\n--1468-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1468-- Nevertheless we consider this a bug. Please report\n--1468-- it at http://valgrind.org/support/bug_reports.html.\n--1468-- WARNING: unhandled riscv64-linux syscall: 258\n--1468-- You may be able to write your own handler.\n--1468-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1468-- Nevertheless we consider this a bug. Please report\n--1468-- it at http://valgrind.org/support/bug_reports.html.\n--1468-- WARNING: unhandled riscv64-linux syscall: 258\n--1468-- You may be able to write your own handler.\n--1468-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1468-- Nevertheless we consider this a bug. Please report\n--1468-- it at http://valgrind.org/support/bug_reports.html.\n--1468-- WARNING: unhandled riscv64-linux syscall: 258\n--1468-- You may be able to write your own handler.\n--1468-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1468-- Nevertheless we consider this a bug. Please report\n--1468-- it at http://valgrind.org/support/bug_reports.html.\n--1468-- WARNING: unhandled riscv64-linux syscall: 258\n--1468-- You may be able to write your own handler.\n--1468-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1468-- Nevertheless we consider this a bug. Please report\n--1468-- it at http://valgrind.org/support/bug_reports.html.\n--1468-- WARNING: unhandled riscv64-linux syscall: 258\n--1468-- You may be able to write your own handler.\n--1468-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1468-- Nevertheless we consider this a bug. Please report\n--1468-- it at http://valgrind.org/support/bug_reports.html.\n--1468-- WARNING: unhandled riscv64-linux syscall: 258\n--1468-- You may be able to write your own handler.\n--1468-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1468-- Nevertheless we consider this a bug. Please report\n--1468-- it at http://valgrind.org/support/bug_reports.html.\n--1468-- WARNING: unhandled riscv64-linux syscall: 258\n--1468-- You may be able to write your own handler.\n--1468-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1468-- Nevertheless we consider this a bug. Please report\n--1468-- it at http://valgrind.org/support/bug_reports.html.\n--1468-- WARNING: unhandled riscv64-linux syscall: 258\n--1468-- You may be able to write your own handler.\n--1468-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1468-- Nevertheless we consider this a bug. Please report\n--1468-- it at http://valgrind.org/support/bug_reports.html.\n--1468-- WARNING: unhandled riscv64-linux syscall: 258\n--1468-- You may be able to write your own handler.\n--1468-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1468-- Nevertheless we consider this a bug. Please report\n--1468-- it at http://valgrind.org/support/bug_reports.html.\n--1468-- WARNING: unhandled riscv64-linux syscall: 258\n--1468-- You may be able to write your own handler.\n--1468-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1468-- Nevertheless we consider this a bug. Please report\n--1468-- it at http://valgrind.org/support/bug_reports.html.\n--1468-- WARNING: unhandled riscv64-linux syscall: 258\n--1468-- You may be able to write your own handler.\n--1468-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1468-- Nevertheless we consider this a bug. Please report\n--1468-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 26: failed --url https://curl.se/we/are.html '-g{path}' --- stdout --- expected: '/we/are.html\n' got: '/we/are.html\n' --- stderr --- expected: '' got: '--1476-- WARNING: unhandled riscv64-linux syscall: 258\n--1476-- You may be able to write your own handler.\n--1476-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1476-- Nevertheless we consider this a bug. Please report\n--1476-- it at http://valgrind.org/support/bug_reports.html.\n--1476-- WARNING: unhandled riscv64-linux syscall: 258\n--1476-- You may be able to write your own handler.\n--1476-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1476-- Nevertheless we consider this a bug. Please report\n--1476-- it at http://valgrind.org/support/bug_reports.html.\n--1476-- WARNING: unhandled riscv64-linux syscall: 258\n--1476-- You may be able to write your own handler.\n--1476-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1476-- Nevertheless we consider this a bug. Please report\n--1476-- it at http://valgrind.org/support/bug_reports.html.\n--1476-- WARNING: unhandled riscv64-linux syscall: 258\n--1476-- You may be able to write your own handler.\n--1476-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1476-- Nevertheless we consider this a bug. Please report\n--1476-- it at http://valgrind.org/support/bug_reports.html.\n--1476-- WARNING: unhandled riscv64-linux syscall: 258\n--1476-- You may be able to write your own handler.\n--1476-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1476-- Nevertheless we consider this a bug. Please report\n--1476-- it at http://valgrind.org/support/bug_reports.html.\n--1476-- WARNING: unhandled riscv64-linux syscall: 258\n--1476-- You may be able to write your own handler.\n--1476-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1476-- Nevertheless we consider this a bug. Please report\n--1476-- it at http://valgrind.org/support/bug_reports.html.\n--1476-- WARNING: unhandled riscv64-linux syscall: 258\n--1476-- You may be able to write your own handler.\n--1476-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1476-- Nevertheless we consider this a bug. Please report\n--1476-- it at http://valgrind.org/support/bug_reports.html.\n--1476-- WARNING: unhandled riscv64-linux syscall: 258\n--1476-- You may be able to write your own handler.\n--1476-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1476-- Nevertheless we consider this a bug. Please report\n--1476-- it at http://valgrind.org/support/bug_reports.html.\n--1476-- WARNING: unhandled riscv64-linux syscall: 258\n--1476-- You may be able to write your own handler.\n--1476-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1476-- Nevertheless we consider this a bug. Please report\n--1476-- it at http://valgrind.org/support/bug_reports.html.\n--1476-- WARNING: unhandled riscv64-linux syscall: 258\n--1476-- You may be able to write your own handler.\n--1476-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1476-- Nevertheless we consider this a bug. Please report\n--1476-- it at http://valgrind.org/support/bug_reports.html.\n--1476-- WARNING: unhandled riscv64-linux syscall: 258\n--1476-- You may be able to write your own handler.\n--1476-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1476-- Nevertheless we consider this a bug. Please report\n--1476-- it at http://valgrind.org/support/bug_reports.html.\n--1476-- WARNING: unhandled riscv64-linux syscall: 258\n--1476-- You may be able to write your own handler.\n--1476-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1476-- Nevertheless we consider this a bug. Please report\n--1476-- it at http://valgrind.org/support/bug_reports.html.\n--1476-- WARNING: unhandled riscv64-linux syscall: 258\n--1476-- You may be able to write your own handler.\n--1476-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1476-- Nevertheless we consider this a bug. Please report\n--1476-- it at http://valgrind.org/support/bug_reports.html.\n--1476-- WARNING: unhandled riscv64-linux syscall: 258\n--1476-- You may be able to write your own handler.\n--1476-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1476-- Nevertheless we consider this a bug. Please report\n--1476-- it at http://valgrind.org/support/bug_reports.html.\n--1476-- WARNING: unhandled riscv64-linux syscall: 258\n--1476-- You may be able to write your own handler.\n--1476-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1476-- Nevertheless we consider this a bug. Please report\n--1476-- it at http://valgrind.org/support/bug_reports.html.\n--1476-- WARNING: unhandled riscv64-linux syscall: 258\n--1476-- You may be able to write your own handler.\n--1476-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1476-- Nevertheless we consider this a bug. Please report\n--1476-- it at http://valgrind.org/support/bug_reports.html.\n--1476-- WARNING: unhandled riscv64-linux syscall: 258\n--1476-- You may be able to write your own handler.\n--1476-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1476-- Nevertheless we consider this a bug. Please report\n--1476-- it at http://valgrind.org/support/bug_reports.html.\n--1476-- WARNING: unhandled riscv64-linux syscall: 258\n--1476-- You may be able to write your own handler.\n--1476-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1476-- Nevertheless we consider this a bug. Please report\n--1476-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 27: failed --default-port --url imap://curl.se/we/are.html --get '{port}' --- stdout --- expected: '143\n' got: '143\n' --- stderr --- expected: '' got: '--1484-- WARNING: unhandled riscv64-linux syscall: 258\n--1484-- You may be able to write your own handler.\n--1484-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1484-- Nevertheless we consider this a bug. Please report\n--1484-- it at http://valgrind.org/support/bug_reports.html.\n--1484-- WARNING: unhandled riscv64-linux syscall: 258\n--1484-- You may be able to write your own handler.\n--1484-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1484-- Nevertheless we consider this a bug. Please report\n--1484-- it at http://valgrind.org/support/bug_reports.html.\n--1484-- WARNING: unhandled riscv64-linux syscall: 258\n--1484-- You may be able to write your own handler.\n--1484-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1484-- Nevertheless we consider this a bug. Please report\n--1484-- it at http://valgrind.org/support/bug_reports.html.\n--1484-- WARNING: unhandled riscv64-linux syscall: 258\n--1484-- You may be able to write your own handler.\n--1484-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1484-- Nevertheless we consider this a bug. Please report\n--1484-- it at http://valgrind.org/support/bug_reports.html.\n--1484-- WARNING: unhandled riscv64-linux syscall: 258\n--1484-- You may be able to write your own handler.\n--1484-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1484-- Nevertheless we consider this a bug. Please report\n--1484-- it at http://valgrind.org/support/bug_reports.html.\n--1484-- WARNING: unhandled riscv64-linux syscall: 258\n--1484-- You may be able to write your own handler.\n--1484-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1484-- Nevertheless we consider this a bug. Please report\n--1484-- it at http://valgrind.org/support/bug_reports.html.\n--1484-- WARNING: unhandled riscv64-linux syscall: 258\n--1484-- You may be able to write your own handler.\n--1484-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1484-- Nevertheless we consider this a bug. Please report\n--1484-- it at http://valgrind.org/support/bug_reports.html.\n--1484-- WARNING: unhandled riscv64-linux syscall: 258\n--1484-- You may be able to write your own handler.\n--1484-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1484-- Nevertheless we consider this a bug. Please report\n--1484-- it at http://valgrind.org/support/bug_reports.html.\n--1484-- WARNING: unhandled riscv64-linux syscall: 258\n--1484-- You may be able to write your own handler.\n--1484-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1484-- Nevertheless we consider this a bug. Please report\n--1484-- it at http://valgrind.org/support/bug_reports.html.\n--1484-- WARNING: unhandled riscv64-linux syscall: 258\n--1484-- You may be able to write your own handler.\n--1484-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1484-- Nevertheless we consider this a bug. Please report\n--1484-- it at http://valgrind.org/support/bug_reports.html.\n--1484-- WARNING: unhandled riscv64-linux syscall: 258\n--1484-- You may be able to write your own handler.\n--1484-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1484-- Nevertheless we consider this a bug. Please report\n--1484-- it at http://valgrind.org/support/bug_reports.html.\n--1484-- WARNING: unhandled riscv64-linux syscall: 258\n--1484-- You may be able to write your own handler.\n--1484-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1484-- Nevertheless we consider this a bug. Please report\n--1484-- it at http://valgrind.org/support/bug_reports.html.\n--1484-- WARNING: unhandled riscv64-linux syscall: 258\n--1484-- You may be able to write your own handler.\n--1484-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1484-- Nevertheless we consider this a bug. Please report\n--1484-- it at http://valgrind.org/support/bug_reports.html.\n--1484-- WARNING: unhandled riscv64-linux syscall: 258\n--1484-- You may be able to write your own handler.\n--1484-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1484-- Nevertheless we consider this a bug. Please report\n--1484-- it at http://valgrind.org/support/bug_reports.html.\n--1484-- WARNING: unhandled riscv64-linux syscall: 258\n--1484-- You may be able to write your own handler.\n--1484-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1484-- Nevertheless we consider this a bug. Please report\n--1484-- it at http://valgrind.org/support/bug_reports.html.\n--1484-- WARNING: unhandled riscv64-linux syscall: 258\n--1484-- You may be able to write your own handler.\n--1484-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1484-- Nevertheless we consider this a bug. Please report\n--1484-- it at http://valgrind.org/support/bug_reports.html.\n--1484-- WARNING: unhandled riscv64-linux syscall: 258\n--1484-- You may be able to write your own handler.\n--1484-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1484-- Nevertheless we consider this a bug. Please report\n--1484-- it at http://valgrind.org/support/bug_reports.html.\n--1484-- WARNING: unhandled riscv64-linux syscall: 258\n--1484-- You may be able to write your own handler.\n--1484-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1484-- Nevertheless we consider this a bug. Please report\n--1484-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 28: failed --url https://curl.se/we/are.html --get '{scheme}' --- stdout --- expected: 'https\n' got: 'https\n' --- stderr --- expected: '' got: '--1492-- WARNING: unhandled riscv64-linux syscall: 258\n--1492-- You may be able to write your own handler.\n--1492-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1492-- Nevertheless we consider this a bug. Please report\n--1492-- it at http://valgrind.org/support/bug_reports.html.\n--1492-- WARNING: unhandled riscv64-linux syscall: 258\n--1492-- You may be able to write your own handler.\n--1492-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1492-- Nevertheless we consider this a bug. Please report\n--1492-- it at http://valgrind.org/support/bug_reports.html.\n--1492-- WARNING: unhandled riscv64-linux syscall: 258\n--1492-- You may be able to write your own handler.\n--1492-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1492-- Nevertheless we consider this a bug. Please report\n--1492-- it at http://valgrind.org/support/bug_reports.html.\n--1492-- WARNING: unhandled riscv64-linux syscall: 258\n--1492-- You may be able to write your own handler.\n--1492-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1492-- Nevertheless we consider this a bug. Please report\n--1492-- it at http://valgrind.org/support/bug_reports.html.\n--1492-- WARNING: unhandled riscv64-linux syscall: 258\n--1492-- You may be able to write your own handler.\n--1492-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1492-- Nevertheless we consider this a bug. Please report\n--1492-- it at http://valgrind.org/support/bug_reports.html.\n--1492-- WARNING: unhandled riscv64-linux syscall: 258\n--1492-- You may be able to write your own handler.\n--1492-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1492-- Nevertheless we consider this a bug. Please report\n--1492-- it at http://valgrind.org/support/bug_reports.html.\n--1492-- WARNING: unhandled riscv64-linux syscall: 258\n--1492-- You may be able to write your own handler.\n--1492-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1492-- Nevertheless we consider this a bug. Please report\n--1492-- it at http://valgrind.org/support/bug_reports.html.\n--1492-- WARNING: unhandled riscv64-linux syscall: 258\n--1492-- You may be able to write your own handler.\n--1492-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1492-- Nevertheless we consider this a bug. Please report\n--1492-- it at http://valgrind.org/support/bug_reports.html.\n--1492-- WARNING: unhandled riscv64-linux syscall: 258\n--1492-- You may be able to write your own handler.\n--1492-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1492-- Nevertheless we consider this a bug. Please report\n--1492-- it at http://valgrind.org/support/bug_reports.html.\n--1492-- WARNING: unhandled riscv64-linux syscall: 258\n--1492-- You may be able to write your own handler.\n--1492-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1492-- Nevertheless we consider this a bug. Please report\n--1492-- it at http://valgrind.org/support/bug_reports.html.\n--1492-- WARNING: unhandled riscv64-linux syscall: 258\n--1492-- You may be able to write your own handler.\n--1492-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1492-- Nevertheless we consider this a bug. Please report\n--1492-- it at http://valgrind.org/support/bug_reports.html.\n--1492-- WARNING: unhandled riscv64-linux syscall: 258\n--1492-- You may be able to write your own handler.\n--1492-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1492-- Nevertheless we consider this a bug. Please report\n--1492-- it at http://valgrind.org/support/bug_reports.html.\n--1492-- WARNING: unhandled riscv64-linux syscall: 258\n--1492-- You may be able to write your own handler.\n--1492-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1492-- Nevertheless we consider this a bug. Please report\n--1492-- it at http://valgrind.org/support/bug_reports.html.\n--1492-- WARNING: unhandled riscv64-linux syscall: 258\n--1492-- You may be able to write your own handler.\n--1492-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1492-- Nevertheless we consider this a bug. Please report\n--1492-- it at http://valgrind.org/support/bug_reports.html.\n--1492-- WARNING: unhandled riscv64-linux syscall: 258\n--1492-- You may be able to write your own handler.\n--1492-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1492-- Nevertheless we consider this a bug. Please report\n--1492-- it at http://valgrind.org/support/bug_reports.html.\n--1492-- WARNING: unhandled riscv64-linux syscall: 258\n--1492-- You may be able to write your own handler.\n--1492-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1492-- Nevertheless we consider this a bug. Please report\n--1492-- it at http://valgrind.org/support/bug_reports.html.\n--1492-- WARNING: unhandled riscv64-linux syscall: 258\n--1492-- You may be able to write your own handler.\n--1492-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1492-- Nevertheless we consider this a bug. Please report\n--1492-- it at http://valgrind.org/support/bug_reports.html.\n--1492-- WARNING: unhandled riscv64-linux syscall: 258\n--1492-- You may be able to write your own handler.\n--1492-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1492-- Nevertheless we consider this a bug. Please report\n--1492-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 29: failed --url https://curl.se/we/are.html --get '{:scheme}' --- stdout --- expected: 'https\n' got: 'https\n' --- stderr --- expected: '' got: '--1500-- WARNING: unhandled riscv64-linux syscall: 258\n--1500-- You may be able to write your own handler.\n--1500-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1500-- Nevertheless we consider this a bug. Please report\n--1500-- it at http://valgrind.org/support/bug_reports.html.\n--1500-- WARNING: unhandled riscv64-linux syscall: 258\n--1500-- You may be able to write your own handler.\n--1500-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1500-- Nevertheless we consider this a bug. Please report\n--1500-- it at http://valgrind.org/support/bug_reports.html.\n--1500-- WARNING: unhandled riscv64-linux syscall: 258\n--1500-- You may be able to write your own handler.\n--1500-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1500-- Nevertheless we consider this a bug. Please report\n--1500-- it at http://valgrind.org/support/bug_reports.html.\n--1500-- WARNING: unhandled riscv64-linux syscall: 258\n--1500-- You may be able to write your own handler.\n--1500-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1500-- Nevertheless we consider this a bug. Please report\n--1500-- it at http://valgrind.org/support/bug_reports.html.\n--1500-- WARNING: unhandled riscv64-linux syscall: 258\n--1500-- You may be able to write your own handler.\n--1500-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1500-- Nevertheless we consider this a bug. Please report\n--1500-- it at http://valgrind.org/support/bug_reports.html.\n--1500-- WARNING: unhandled riscv64-linux syscall: 258\n--1500-- You may be able to write your own handler.\n--1500-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1500-- Nevertheless we consider this a bug. Please report\n--1500-- it at http://valgrind.org/support/bug_reports.html.\n--1500-- WARNING: unhandled riscv64-linux syscall: 258\n--1500-- You may be able to write your own handler.\n--1500-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1500-- Nevertheless we consider this a bug. Please report\n--1500-- it at http://valgrind.org/support/bug_reports.html.\n--1500-- WARNING: unhandled riscv64-linux syscall: 258\n--1500-- You may be able to write your own handler.\n--1500-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1500-- Nevertheless we consider this a bug. Please report\n--1500-- it at http://valgrind.org/support/bug_reports.html.\n--1500-- WARNING: unhandled riscv64-linux syscall: 258\n--1500-- You may be able to write your own handler.\n--1500-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1500-- Nevertheless we consider this a bug. Please report\n--1500-- it at http://valgrind.org/support/bug_reports.html.\n--1500-- WARNING: unhandled riscv64-linux syscall: 258\n--1500-- You may be able to write your own handler.\n--1500-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1500-- Nevertheless we consider this a bug. Please report\n--1500-- it at http://valgrind.org/support/bug_reports.html.\n--1500-- WARNING: unhandled riscv64-linux syscall: 258\n--1500-- You may be able to write your own handler.\n--1500-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1500-- Nevertheless we consider this a bug. Please report\n--1500-- it at http://valgrind.org/support/bug_reports.html.\n--1500-- WARNING: unhandled riscv64-linux syscall: 258\n--1500-- You may be able to write your own handler.\n--1500-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1500-- Nevertheless we consider this a bug. Please report\n--1500-- it at http://valgrind.org/support/bug_reports.html.\n--1500-- WARNING: unhandled riscv64-linux syscall: 258\n--1500-- You may be able to write your own handler.\n--1500-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1500-- Nevertheless we consider this a bug. Please report\n--1500-- it at http://valgrind.org/support/bug_reports.html.\n--1500-- WARNING: unhandled riscv64-linux syscall: 258\n--1500-- You may be able to write your own handler.\n--1500-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1500-- Nevertheless we consider this a bug. Please report\n--1500-- it at http://valgrind.org/support/bug_reports.html.\n--1500-- WARNING: unhandled riscv64-linux syscall: 258\n--1500-- You may be able to write your own handler.\n--1500-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1500-- Nevertheless we consider this a bug. Please report\n--1500-- it at http://valgrind.org/support/bug_reports.html.\n--1500-- WARNING: unhandled riscv64-linux syscall: 258\n--1500-- You may be able to write your own handler.\n--1500-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1500-- Nevertheless we consider this a bug. Please report\n--1500-- it at http://valgrind.org/support/bug_reports.html.\n--1500-- WARNING: unhandled riscv64-linux syscall: 258\n--1500-- You may be able to write your own handler.\n--1500-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1500-- Nevertheless we consider this a bug. Please report\n--1500-- it at http://valgrind.org/support/bug_reports.html.\n--1500-- WARNING: unhandled riscv64-linux syscall: 258\n--1500-- You may be able to write your own handler.\n--1500-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1500-- Nevertheless we consider this a bug. Please report\n--1500-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 30: failed --url https://curl.se:55/we/are.html --get '{url:port}' --- stdout --- expected: '55\n' got: '55\n' --- stderr --- expected: '' got: '--1508-- WARNING: unhandled riscv64-linux syscall: 258\n--1508-- You may be able to write your own handler.\n--1508-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1508-- Nevertheless we consider this a bug. Please report\n--1508-- it at http://valgrind.org/support/bug_reports.html.\n--1508-- WARNING: unhandled riscv64-linux syscall: 258\n--1508-- You may be able to write your own handler.\n--1508-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1508-- Nevertheless we consider this a bug. Please report\n--1508-- it at http://valgrind.org/support/bug_reports.html.\n--1508-- WARNING: unhandled riscv64-linux syscall: 258\n--1508-- You may be able to write your own handler.\n--1508-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1508-- Nevertheless we consider this a bug. Please report\n--1508-- it at http://valgrind.org/support/bug_reports.html.\n--1508-- WARNING: unhandled riscv64-linux syscall: 258\n--1508-- You may be able to write your own handler.\n--1508-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1508-- Nevertheless we consider this a bug. Please report\n--1508-- it at http://valgrind.org/support/bug_reports.html.\n--1508-- WARNING: unhandled riscv64-linux syscall: 258\n--1508-- You may be able to write your own handler.\n--1508-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1508-- Nevertheless we consider this a bug. Please report\n--1508-- it at http://valgrind.org/support/bug_reports.html.\n--1508-- WARNING: unhandled riscv64-linux syscall: 258\n--1508-- You may be able to write your own handler.\n--1508-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1508-- Nevertheless we consider this a bug. Please report\n--1508-- it at http://valgrind.org/support/bug_reports.html.\n--1508-- WARNING: unhandled riscv64-linux syscall: 258\n--1508-- You may be able to write your own handler.\n--1508-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1508-- Nevertheless we consider this a bug. Please report\n--1508-- it at http://valgrind.org/support/bug_reports.html.\n--1508-- WARNING: unhandled riscv64-linux syscall: 258\n--1508-- You may be able to write your own handler.\n--1508-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1508-- Nevertheless we consider this a bug. Please report\n--1508-- it at http://valgrind.org/support/bug_reports.html.\n--1508-- WARNING: unhandled riscv64-linux syscall: 258\n--1508-- You may be able to write your own handler.\n--1508-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1508-- Nevertheless we consider this a bug. Please report\n--1508-- it at http://valgrind.org/support/bug_reports.html.\n--1508-- WARNING: unhandled riscv64-linux syscall: 258\n--1508-- You may be able to write your own handler.\n--1508-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1508-- Nevertheless we consider this a bug. Please report\n--1508-- it at http://valgrind.org/support/bug_reports.html.\n--1508-- WARNING: unhandled riscv64-linux syscall: 258\n--1508-- You may be able to write your own handler.\n--1508-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1508-- Nevertheless we consider this a bug. Please report\n--1508-- it at http://valgrind.org/support/bug_reports.html.\n--1508-- WARNING: unhandled riscv64-linux syscall: 258\n--1508-- You may be able to write your own handler.\n--1508-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1508-- Nevertheless we consider this a bug. Please report\n--1508-- it at http://valgrind.org/support/bug_reports.html.\n--1508-- WARNING: unhandled riscv64-linux syscall: 258\n--1508-- You may be able to write your own handler.\n--1508-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1508-- Nevertheless we consider this a bug. Please report\n--1508-- it at http://valgrind.org/support/bug_reports.html.\n--1508-- WARNING: unhandled riscv64-linux syscall: 258\n--1508-- You may be able to write your own handler.\n--1508-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1508-- Nevertheless we consider this a bug. Please report\n--1508-- it at http://valgrind.org/support/bug_reports.html.\n--1508-- WARNING: unhandled riscv64-linux syscall: 258\n--1508-- You may be able to write your own handler.\n--1508-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1508-- Nevertheless we consider this a bug. Please report\n--1508-- it at http://valgrind.org/support/bug_reports.html.\n--1508-- WARNING: unhandled riscv64-linux syscall: 258\n--1508-- You may be able to write your own handler.\n--1508-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1508-- Nevertheless we consider this a bug. Please report\n--1508-- it at http://valgrind.org/support/bug_reports.html.\n--1508-- WARNING: unhandled riscv64-linux syscall: 258\n--1508-- You may be able to write your own handler.\n--1508-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1508-- Nevertheless we consider this a bug. Please report\n--1508-- it at http://valgrind.org/support/bug_reports.html.\n--1508-- WARNING: unhandled riscv64-linux syscall: 258\n--1508-- You may be able to write your own handler.\n--1508-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1508-- Nevertheless we consider this a bug. Please report\n--1508-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 31: failed --url https://curl.se/%2e%61%13 --get '{:path}' --- stdout --- expected: '/.a%13\n' got: '/.a%13\n' --- stderr --- expected: '' got: '--1516-- WARNING: unhandled riscv64-linux syscall: 258\n--1516-- You may be able to write your own handler.\n--1516-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1516-- Nevertheless we consider this a bug. Please report\n--1516-- it at http://valgrind.org/support/bug_reports.html.\n--1516-- WARNING: unhandled riscv64-linux syscall: 258\n--1516-- You may be able to write your own handler.\n--1516-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1516-- Nevertheless we consider this a bug. Please report\n--1516-- it at http://valgrind.org/support/bug_reports.html.\n--1516-- WARNING: unhandled riscv64-linux syscall: 258\n--1516-- You may be able to write your own handler.\n--1516-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1516-- Nevertheless we consider this a bug. Please report\n--1516-- it at http://valgrind.org/support/bug_reports.html.\n--1516-- WARNING: unhandled riscv64-linux syscall: 258\n--1516-- You may be able to write your own handler.\n--1516-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1516-- Nevertheless we consider this a bug. Please report\n--1516-- it at http://valgrind.org/support/bug_reports.html.\n--1516-- WARNING: unhandled riscv64-linux syscall: 258\n--1516-- You may be able to write your own handler.\n--1516-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1516-- Nevertheless we consider this a bug. Please report\n--1516-- it at http://valgrind.org/support/bug_reports.html.\n--1516-- WARNING: unhandled riscv64-linux syscall: 258\n--1516-- You may be able to write your own handler.\n--1516-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1516-- Nevertheless we consider this a bug. Please report\n--1516-- it at http://valgrind.org/support/bug_reports.html.\n--1516-- WARNING: unhandled riscv64-linux syscall: 258\n--1516-- You may be able to write your own handler.\n--1516-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1516-- Nevertheless we consider this a bug. Please report\n--1516-- it at http://valgrind.org/support/bug_reports.html.\n--1516-- WARNING: unhandled riscv64-linux syscall: 258\n--1516-- You may be able to write your own handler.\n--1516-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1516-- Nevertheless we consider this a bug. Please report\n--1516-- it at http://valgrind.org/support/bug_reports.html.\n--1516-- WARNING: unhandled riscv64-linux syscall: 258\n--1516-- You may be able to write your own handler.\n--1516-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1516-- Nevertheless we consider this a bug. Please report\n--1516-- it at http://valgrind.org/support/bug_reports.html.\n--1516-- WARNING: unhandled riscv64-linux syscall: 258\n--1516-- You may be able to write your own handler.\n--1516-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1516-- Nevertheless we consider this a bug. Please report\n--1516-- it at http://valgrind.org/support/bug_reports.html.\n--1516-- WARNING: unhandled riscv64-linux syscall: 258\n--1516-- You may be able to write your own handler.\n--1516-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1516-- Nevertheless we consider this a bug. Please report\n--1516-- it at http://valgrind.org/support/bug_reports.html.\n--1516-- WARNING: unhandled riscv64-linux syscall: 258\n--1516-- You may be able to write your own handler.\n--1516-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1516-- Nevertheless we consider this a bug. Please report\n--1516-- it at http://valgrind.org/support/bug_reports.html.\n--1516-- WARNING: unhandled riscv64-linux syscall: 258\n--1516-- You may be able to write your own handler.\n--1516-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1516-- Nevertheless we consider this a bug. Please report\n--1516-- it at http://valgrind.org/support/bug_reports.html.\n--1516-- WARNING: unhandled riscv64-linux syscall: 258\n--1516-- You may be able to write your own handler.\n--1516-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1516-- Nevertheless we consider this a bug. Please report\n--1516-- it at http://valgrind.org/support/bug_reports.html.\n--1516-- WARNING: unhandled riscv64-linux syscall: 258\n--1516-- You may be able to write your own handler.\n--1516-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1516-- Nevertheless we consider this a bug. Please report\n--1516-- it at http://valgrind.org/support/bug_reports.html.\n--1516-- WARNING: unhandled riscv64-linux syscall: 258\n--1516-- You may be able to write your own handler.\n--1516-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1516-- Nevertheless we consider this a bug. Please report\n--1516-- it at http://valgrind.org/support/bug_reports.html.\n--1516-- WARNING: unhandled riscv64-linux syscall: 258\n--1516-- You may be able to write your own handler.\n--1516-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1516-- Nevertheless we consider this a bug. Please report\n--1516-- it at http://valgrind.org/support/bug_reports.html.\n--1516-- WARNING: unhandled riscv64-linux syscall: 258\n--1516-- You may be able to write your own handler.\n--1516-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1516-- Nevertheless we consider this a bug. Please report\n--1516-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 32: failed --url 'https://curl.se?%2e%61%13' --get '{:query}' --- stdout --- expected: '.a%13\n' got: '.a%13\n' --- stderr --- expected: '' got: '--1524-- WARNING: unhandled riscv64-linux syscall: 258\n--1524-- You may be able to write your own handler.\n--1524-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1524-- Nevertheless we consider this a bug. Please report\n--1524-- it at http://valgrind.org/support/bug_reports.html.\n--1524-- WARNING: unhandled riscv64-linux syscall: 258\n--1524-- You may be able to write your own handler.\n--1524-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1524-- Nevertheless we consider this a bug. Please report\n--1524-- it at http://valgrind.org/support/bug_reports.html.\n--1524-- WARNING: unhandled riscv64-linux syscall: 258\n--1524-- You may be able to write your own handler.\n--1524-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1524-- Nevertheless we consider this a bug. Please report\n--1524-- it at http://valgrind.org/support/bug_reports.html.\n--1524-- WARNING: unhandled riscv64-linux syscall: 258\n--1524-- You may be able to write your own handler.\n--1524-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1524-- Nevertheless we consider this a bug. Please report\n--1524-- it at http://valgrind.org/support/bug_reports.html.\n--1524-- WARNING: unhandled riscv64-linux syscall: 258\n--1524-- You may be able to write your own handler.\n--1524-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1524-- Nevertheless we consider this a bug. Please report\n--1524-- it at http://valgrind.org/support/bug_reports.html.\n--1524-- WARNING: unhandled riscv64-linux syscall: 258\n--1524-- You may be able to write your own handler.\n--1524-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1524-- Nevertheless we consider this a bug. Please report\n--1524-- it at http://valgrind.org/support/bug_reports.html.\n--1524-- WARNING: unhandled riscv64-linux syscall: 258\n--1524-- You may be able to write your own handler.\n--1524-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1524-- Nevertheless we consider this a bug. Please report\n--1524-- it at http://valgrind.org/support/bug_reports.html.\n--1524-- WARNING: unhandled riscv64-linux syscall: 258\n--1524-- You may be able to write your own handler.\n--1524-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1524-- Nevertheless we consider this a bug. Please report\n--1524-- it at http://valgrind.org/support/bug_reports.html.\n--1524-- WARNING: unhandled riscv64-linux syscall: 258\n--1524-- You may be able to write your own handler.\n--1524-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1524-- Nevertheless we consider this a bug. Please report\n--1524-- it at http://valgrind.org/support/bug_reports.html.\n--1524-- WARNING: unhandled riscv64-linux syscall: 258\n--1524-- You may be able to write your own handler.\n--1524-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1524-- Nevertheless we consider this a bug. Please report\n--1524-- it at http://valgrind.org/support/bug_reports.html.\n--1524-- WARNING: unhandled riscv64-linux syscall: 258\n--1524-- You may be able to write your own handler.\n--1524-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1524-- Nevertheless we consider this a bug. Please report\n--1524-- it at http://valgrind.org/support/bug_reports.html.\n--1524-- WARNING: unhandled riscv64-linux syscall: 258\n--1524-- You may be able to write your own handler.\n--1524-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1524-- Nevertheless we consider this a bug. Please report\n--1524-- it at http://valgrind.org/support/bug_reports.html.\n--1524-- WARNING: unhandled riscv64-linux syscall: 258\n--1524-- You may be able to write your own handler.\n--1524-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1524-- Nevertheless we consider this a bug. Please report\n--1524-- it at http://valgrind.org/support/bug_reports.html.\n--1524-- WARNING: unhandled riscv64-linux syscall: 258\n--1524-- You may be able to write your own handler.\n--1524-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1524-- Nevertheless we consider this a bug. Please report\n--1524-- it at http://valgrind.org/support/bug_reports.html.\n--1524-- WARNING: unhandled riscv64-linux syscall: 258\n--1524-- You may be able to write your own handler.\n--1524-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1524-- Nevertheless we consider this a bug. Please report\n--1524-- it at http://valgrind.org/support/bug_reports.html.\n--1524-- WARNING: unhandled riscv64-linux syscall: 258\n--1524-- You may be able to write your own handler.\n--1524-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1524-- Nevertheless we consider this a bug. Please report\n--1524-- it at http://valgrind.org/support/bug_reports.html.\n--1524-- WARNING: unhandled riscv64-linux syscall: 258\n--1524-- You may be able to write your own handler.\n--1524-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1524-- Nevertheless we consider this a bug. Please report\n--1524-- it at http://valgrind.org/support/bug_reports.html.\n--1524-- WARNING: unhandled riscv64-linux syscall: 258\n--1524-- You may be able to write your own handler.\n--1524-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1524-- Nevertheless we consider this a bug. Please report\n--1524-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 33: failed --url 'https://curl.se/#%2e%61%13' --get '{:fragment}' --- stdout --- expected: '.a%13\n' got: '.a%13\n' --- stderr --- expected: '' got: '--1532-- WARNING: unhandled riscv64-linux syscall: 258\n--1532-- You may be able to write your own handler.\n--1532-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1532-- Nevertheless we consider this a bug. Please report\n--1532-- it at http://valgrind.org/support/bug_reports.html.\n--1532-- WARNING: unhandled riscv64-linux syscall: 258\n--1532-- You may be able to write your own handler.\n--1532-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1532-- Nevertheless we consider this a bug. Please report\n--1532-- it at http://valgrind.org/support/bug_reports.html.\n--1532-- WARNING: unhandled riscv64-linux syscall: 258\n--1532-- You may be able to write your own handler.\n--1532-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1532-- Nevertheless we consider this a bug. Please report\n--1532-- it at http://valgrind.org/support/bug_reports.html.\n--1532-- WARNING: unhandled riscv64-linux syscall: 258\n--1532-- You may be able to write your own handler.\n--1532-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1532-- Nevertheless we consider this a bug. Please report\n--1532-- it at http://valgrind.org/support/bug_reports.html.\n--1532-- WARNING: unhandled riscv64-linux syscall: 258\n--1532-- You may be able to write your own handler.\n--1532-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1532-- Nevertheless we consider this a bug. Please report\n--1532-- it at http://valgrind.org/support/bug_reports.html.\n--1532-- WARNING: unhandled riscv64-linux syscall: 258\n--1532-- You may be able to write your own handler.\n--1532-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1532-- Nevertheless we consider this a bug. Please report\n--1532-- it at http://valgrind.org/support/bug_reports.html.\n--1532-- WARNING: unhandled riscv64-linux syscall: 258\n--1532-- You may be able to write your own handler.\n--1532-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1532-- Nevertheless we consider this a bug. Please report\n--1532-- it at http://valgrind.org/support/bug_reports.html.\n--1532-- WARNING: unhandled riscv64-linux syscall: 258\n--1532-- You may be able to write your own handler.\n--1532-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1532-- Nevertheless we consider this a bug. Please report\n--1532-- it at http://valgrind.org/support/bug_reports.html.\n--1532-- WARNING: unhandled riscv64-linux syscall: 258\n--1532-- You may be able to write your own handler.\n--1532-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1532-- Nevertheless we consider this a bug. Please report\n--1532-- it at http://valgrind.org/support/bug_reports.html.\n--1532-- WARNING: unhandled riscv64-linux syscall: 258\n--1532-- You may be able to write your own handler.\n--1532-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1532-- Nevertheless we consider this a bug. Please report\n--1532-- it at http://valgrind.org/support/bug_reports.html.\n--1532-- WARNING: unhandled riscv64-linux syscall: 258\n--1532-- You may be able to write your own handler.\n--1532-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1532-- Nevertheless we consider this a bug. Please report\n--1532-- it at http://valgrind.org/support/bug_reports.html.\n--1532-- WARNING: unhandled riscv64-linux syscall: 258\n--1532-- You may be able to write your own handler.\n--1532-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1532-- Nevertheless we consider this a bug. Please report\n--1532-- it at http://valgrind.org/support/bug_reports.html.\n--1532-- WARNING: unhandled riscv64-linux syscall: 258\n--1532-- You may be able to write your own handler.\n--1532-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1532-- Nevertheless we consider this a bug. Please report\n--1532-- it at http://valgrind.org/support/bug_reports.html.\n--1532-- WARNING: unhandled riscv64-linux syscall: 258\n--1532-- You may be able to write your own handler.\n--1532-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1532-- Nevertheless we consider this a bug. Please report\n--1532-- it at http://valgrind.org/support/bug_reports.html.\n--1532-- WARNING: unhandled riscv64-linux syscall: 258\n--1532-- You may be able to write your own handler.\n--1532-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1532-- Nevertheless we consider this a bug. Please report\n--1532-- it at http://valgrind.org/support/bug_reports.html.\n--1532-- WARNING: unhandled riscv64-linux syscall: 258\n--1532-- You may be able to write your own handler.\n--1532-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1532-- Nevertheless we consider this a bug. Please report\n--1532-- it at http://valgrind.org/support/bug_reports.html.\n--1532-- WARNING: unhandled riscv64-linux syscall: 258\n--1532-- You may be able to write your own handler.\n--1532-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1532-- Nevertheless we consider this a bug. Please report\n--1532-- it at http://valgrind.org/support/bug_reports.html.\n--1532-- WARNING: unhandled riscv64-linux syscall: 258\n--1532-- You may be able to write your own handler.\n--1532-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1532-- Nevertheless we consider this a bug. Please report\n--1532-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 34: failed --url 'https://example.com/#%2e%61%13%Fa' --- stdout --- expected: 'https://example.com/#.a%13%fa\n' got: 'https://example.com/#.a%13%fa\n' --- stderr --- expected: '' got: '--1540-- WARNING: unhandled riscv64-linux syscall: 258\n--1540-- You may be able to write your own handler.\n--1540-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1540-- Nevertheless we consider this a bug. Please report\n--1540-- it at http://valgrind.org/support/bug_reports.html.\n--1540-- WARNING: unhandled riscv64-linux syscall: 258\n--1540-- You may be able to write your own handler.\n--1540-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1540-- Nevertheless we consider this a bug. Please report\n--1540-- it at http://valgrind.org/support/bug_reports.html.\n--1540-- WARNING: unhandled riscv64-linux syscall: 258\n--1540-- You may be able to write your own handler.\n--1540-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1540-- Nevertheless we consider this a bug. Please report\n--1540-- it at http://valgrind.org/support/bug_reports.html.\n--1540-- WARNING: unhandled riscv64-linux syscall: 258\n--1540-- You may be able to write your own handler.\n--1540-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1540-- Nevertheless we consider this a bug. Please report\n--1540-- it at http://valgrind.org/support/bug_reports.html.\n--1540-- WARNING: unhandled riscv64-linux syscall: 258\n--1540-- You may be able to write your own handler.\n--1540-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1540-- Nevertheless we consider this a bug. Please report\n--1540-- it at http://valgrind.org/support/bug_reports.html.\n--1540-- WARNING: unhandled riscv64-linux syscall: 258\n--1540-- You may be able to write your own handler.\n--1540-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1540-- Nevertheless we consider this a bug. Please report\n--1540-- it at http://valgrind.org/support/bug_reports.html.\n--1540-- WARNING: unhandled riscv64-linux syscall: 258\n--1540-- You may be able to write your own handler.\n--1540-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1540-- Nevertheless we consider this a bug. Please report\n--1540-- it at http://valgrind.org/support/bug_reports.html.\n--1540-- WARNING: unhandled riscv64-linux syscall: 258\n--1540-- You may be able to write your own handler.\n--1540-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1540-- Nevertheless we consider this a bug. Please report\n--1540-- it at http://valgrind.org/support/bug_reports.html.\n--1540-- WARNING: unhandled riscv64-linux syscall: 258\n--1540-- You may be able to write your own handler.\n--1540-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1540-- Nevertheless we consider this a bug. Please report\n--1540-- it at http://valgrind.org/support/bug_reports.html.\n--1540-- WARNING: unhandled riscv64-linux syscall: 258\n--1540-- You may be able to write your own handler.\n--1540-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1540-- Nevertheless we consider this a bug. Please report\n--1540-- it at http://valgrind.org/support/bug_reports.html.\n--1540-- WARNING: unhandled riscv64-linux syscall: 258\n--1540-- You may be able to write your own handler.\n--1540-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1540-- Nevertheless we consider this a bug. Please report\n--1540-- it at http://valgrind.org/support/bug_reports.html.\n--1540-- WARNING: unhandled riscv64-linux syscall: 258\n--1540-- You may be able to write your own handler.\n--1540-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1540-- Nevertheless we consider this a bug. Please report\n--1540-- it at http://valgrind.org/support/bug_reports.html.\n--1540-- WARNING: unhandled riscv64-linux syscall: 258\n--1540-- You may be able to write your own handler.\n--1540-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1540-- Nevertheless we consider this a bug. Please report\n--1540-- it at http://valgrind.org/support/bug_reports.html.\n--1540-- WARNING: unhandled riscv64-linux syscall: 258\n--1540-- You may be able to write your own handler.\n--1540-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1540-- Nevertheless we consider this a bug. Please report\n--1540-- it at http://valgrind.org/support/bug_reports.html.\n--1540-- WARNING: unhandled riscv64-linux syscall: 258\n--1540-- You may be able to write your own handler.\n--1540-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1540-- Nevertheless we consider this a bug. Please report\n--1540-- it at http://valgrind.org/support/bug_reports.html.\n--1540-- WARNING: unhandled riscv64-linux syscall: 258\n--1540-- You may be able to write your own handler.\n--1540-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1540-- Nevertheless we consider this a bug. Please report\n--1540-- it at http://valgrind.org/support/bug_reports.html.\n--1540-- WARNING: unhandled riscv64-linux syscall: 258\n--1540-- You may be able to write your own handler.\n--1540-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1540-- Nevertheless we consider this a bug. Please report\n--1540-- it at http://valgrind.org/support/bug_reports.html.\n--1540-- WARNING: unhandled riscv64-linux syscall: 258\n--1540-- You may be able to write your own handler.\n--1540-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1540-- Nevertheless we consider this a bug. Please report\n--1540-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 35: failed --url https://hello@curl.se/we/are.html --get '{user}' --- stdout --- expected: 'hello\n' got: 'hello\n' --- stderr --- expected: '' got: '--1548-- WARNING: unhandled riscv64-linux syscall: 258\n--1548-- You may be able to write your own handler.\n--1548-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1548-- Nevertheless we consider this a bug. Please report\n--1548-- it at http://valgrind.org/support/bug_reports.html.\n--1548-- WARNING: unhandled riscv64-linux syscall: 258\n--1548-- You may be able to write your own handler.\n--1548-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1548-- Nevertheless we consider this a bug. Please report\n--1548-- it at http://valgrind.org/support/bug_reports.html.\n--1548-- WARNING: unhandled riscv64-linux syscall: 258\n--1548-- You may be able to write your own handler.\n--1548-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1548-- Nevertheless we consider this a bug. Please report\n--1548-- it at http://valgrind.org/support/bug_reports.html.\n--1548-- WARNING: unhandled riscv64-linux syscall: 258\n--1548-- You may be able to write your own handler.\n--1548-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1548-- Nevertheless we consider this a bug. Please report\n--1548-- it at http://valgrind.org/support/bug_reports.html.\n--1548-- WARNING: unhandled riscv64-linux syscall: 258\n--1548-- You may be able to write your own handler.\n--1548-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1548-- Nevertheless we consider this a bug. Please report\n--1548-- it at http://valgrind.org/support/bug_reports.html.\n--1548-- WARNING: unhandled riscv64-linux syscall: 258\n--1548-- You may be able to write your own handler.\n--1548-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1548-- Nevertheless we consider this a bug. Please report\n--1548-- it at http://valgrind.org/support/bug_reports.html.\n--1548-- WARNING: unhandled riscv64-linux syscall: 258\n--1548-- You may be able to write your own handler.\n--1548-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1548-- Nevertheless we consider this a bug. Please report\n--1548-- it at http://valgrind.org/support/bug_reports.html.\n--1548-- WARNING: unhandled riscv64-linux syscall: 258\n--1548-- You may be able to write your own handler.\n--1548-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1548-- Nevertheless we consider this a bug. Please report\n--1548-- it at http://valgrind.org/support/bug_reports.html.\n--1548-- WARNING: unhandled riscv64-linux syscall: 258\n--1548-- You may be able to write your own handler.\n--1548-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1548-- Nevertheless we consider this a bug. Please report\n--1548-- it at http://valgrind.org/support/bug_reports.html.\n--1548-- WARNING: unhandled riscv64-linux syscall: 258\n--1548-- You may be able to write your own handler.\n--1548-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1548-- Nevertheless we consider this a bug. Please report\n--1548-- it at http://valgrind.org/support/bug_reports.html.\n--1548-- WARNING: unhandled riscv64-linux syscall: 258\n--1548-- You may be able to write your own handler.\n--1548-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1548-- Nevertheless we consider this a bug. Please report\n--1548-- it at http://valgrind.org/support/bug_reports.html.\n--1548-- WARNING: unhandled riscv64-linux syscall: 258\n--1548-- You may be able to write your own handler.\n--1548-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1548-- Nevertheless we consider this a bug. Please report\n--1548-- it at http://valgrind.org/support/bug_reports.html.\n--1548-- WARNING: unhandled riscv64-linux syscall: 258\n--1548-- You may be able to write your own handler.\n--1548-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1548-- Nevertheless we consider this a bug. Please report\n--1548-- it at http://valgrind.org/support/bug_reports.html.\n--1548-- WARNING: unhandled riscv64-linux syscall: 258\n--1548-- You may be able to write your own handler.\n--1548-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1548-- Nevertheless we consider this a bug. Please report\n--1548-- it at http://valgrind.org/support/bug_reports.html.\n--1548-- WARNING: unhandled riscv64-linux syscall: 258\n--1548-- You may be able to write your own handler.\n--1548-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1548-- Nevertheless we consider this a bug. Please report\n--1548-- it at http://valgrind.org/support/bug_reports.html.\n--1548-- WARNING: unhandled riscv64-linux syscall: 258\n--1548-- You may be able to write your own handler.\n--1548-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1548-- Nevertheless we consider this a bug. Please report\n--1548-- it at http://valgrind.org/support/bug_reports.html.\n--1548-- WARNING: unhandled riscv64-linux syscall: 258\n--1548-- You may be able to write your own handler.\n--1548-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1548-- Nevertheless we consider this a bug. Please report\n--1548-- it at http://valgrind.org/support/bug_reports.html.\n--1548-- WARNING: unhandled riscv64-linux syscall: 258\n--1548-- You may be able to write your own handler.\n--1548-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1548-- Nevertheless we consider this a bug. Please report\n--1548-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 36: failed --url https://hello:secret@curl.se/we/are.html --get '{password}' --- stdout --- expected: 'secret\n' got: 'secret\n' --- stderr --- expected: '' got: '--1556-- WARNING: unhandled riscv64-linux syscall: 258\n--1556-- You may be able to write your own handler.\n--1556-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1556-- Nevertheless we consider this a bug. Please report\n--1556-- it at http://valgrind.org/support/bug_reports.html.\n--1556-- WARNING: unhandled riscv64-linux syscall: 258\n--1556-- You may be able to write your own handler.\n--1556-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1556-- Nevertheless we consider this a bug. Please report\n--1556-- it at http://valgrind.org/support/bug_reports.html.\n--1556-- WARNING: unhandled riscv64-linux syscall: 258\n--1556-- You may be able to write your own handler.\n--1556-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1556-- Nevertheless we consider this a bug. Please report\n--1556-- it at http://valgrind.org/support/bug_reports.html.\n--1556-- WARNING: unhandled riscv64-linux syscall: 258\n--1556-- You may be able to write your own handler.\n--1556-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1556-- Nevertheless we consider this a bug. Please report\n--1556-- it at http://valgrind.org/support/bug_reports.html.\n--1556-- WARNING: unhandled riscv64-linux syscall: 258\n--1556-- You may be able to write your own handler.\n--1556-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1556-- Nevertheless we consider this a bug. Please report\n--1556-- it at http://valgrind.org/support/bug_reports.html.\n--1556-- WARNING: unhandled riscv64-linux syscall: 258\n--1556-- You may be able to write your own handler.\n--1556-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1556-- Nevertheless we consider this a bug. Please report\n--1556-- it at http://valgrind.org/support/bug_reports.html.\n--1556-- WARNING: unhandled riscv64-linux syscall: 258\n--1556-- You may be able to write your own handler.\n--1556-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1556-- Nevertheless we consider this a bug. Please report\n--1556-- it at http://valgrind.org/support/bug_reports.html.\n--1556-- WARNING: unhandled riscv64-linux syscall: 258\n--1556-- You may be able to write your own handler.\n--1556-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1556-- Nevertheless we consider this a bug. Please report\n--1556-- it at http://valgrind.org/support/bug_reports.html.\n--1556-- WARNING: unhandled riscv64-linux syscall: 258\n--1556-- You may be able to write your own handler.\n--1556-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1556-- Nevertheless we consider this a bug. Please report\n--1556-- it at http://valgrind.org/support/bug_reports.html.\n--1556-- WARNING: unhandled riscv64-linux syscall: 258\n--1556-- You may be able to write your own handler.\n--1556-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1556-- Nevertheless we consider this a bug. Please report\n--1556-- it at http://valgrind.org/support/bug_reports.html.\n--1556-- WARNING: unhandled riscv64-linux syscall: 258\n--1556-- You may be able to write your own handler.\n--1556-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1556-- Nevertheless we consider this a bug. Please report\n--1556-- it at http://valgrind.org/support/bug_reports.html.\n--1556-- WARNING: unhandled riscv64-linux syscall: 258\n--1556-- You may be able to write your own handler.\n--1556-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1556-- Nevertheless we consider this a bug. Please report\n--1556-- it at http://valgrind.org/support/bug_reports.html.\n--1556-- WARNING: unhandled riscv64-linux syscall: 258\n--1556-- You may be able to write your own handler.\n--1556-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1556-- Nevertheless we consider this a bug. Please report\n--1556-- it at http://valgrind.org/support/bug_reports.html.\n--1556-- WARNING: unhandled riscv64-linux syscall: 258\n--1556-- You may be able to write your own handler.\n--1556-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1556-- Nevertheless we consider this a bug. Please report\n--1556-- it at http://valgrind.org/support/bug_reports.html.\n--1556-- WARNING: unhandled riscv64-linux syscall: 258\n--1556-- You may be able to write your own handler.\n--1556-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1556-- Nevertheless we consider this a bug. Please report\n--1556-- it at http://valgrind.org/support/bug_reports.html.\n--1556-- WARNING: unhandled riscv64-linux syscall: 258\n--1556-- You may be able to write your own handler.\n--1556-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1556-- Nevertheless we consider this a bug. Please report\n--1556-- it at http://valgrind.org/support/bug_reports.html.\n--1556-- WARNING: unhandled riscv64-linux syscall: 258\n--1556-- You may be able to write your own handler.\n--1556-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1556-- Nevertheless we consider this a bug. Please report\n--1556-- it at http://valgrind.org/support/bug_reports.html.\n--1556-- WARNING: unhandled riscv64-linux syscall: 258\n--1556-- You may be able to write your own handler.\n--1556-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1556-- Nevertheless we consider this a bug. Please report\n--1556-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 37: failed --url 'imap://hello:secret;crazy@curl.se/we/are.html' --get '{options}' --- stdout --- expected: 'crazy\n' got: 'crazy\n' --- stderr --- expected: '' got: '--1564-- WARNING: unhandled riscv64-linux syscall: 258\n--1564-- You may be able to write your own handler.\n--1564-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1564-- Nevertheless we consider this a bug. Please report\n--1564-- it at http://valgrind.org/support/bug_reports.html.\n--1564-- WARNING: unhandled riscv64-linux syscall: 258\n--1564-- You may be able to write your own handler.\n--1564-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1564-- Nevertheless we consider this a bug. Please report\n--1564-- it at http://valgrind.org/support/bug_reports.html.\n--1564-- WARNING: unhandled riscv64-linux syscall: 258\n--1564-- You may be able to write your own handler.\n--1564-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1564-- Nevertheless we consider this a bug. Please report\n--1564-- it at http://valgrind.org/support/bug_reports.html.\n--1564-- WARNING: unhandled riscv64-linux syscall: 258\n--1564-- You may be able to write your own handler.\n--1564-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1564-- Nevertheless we consider this a bug. Please report\n--1564-- it at http://valgrind.org/support/bug_reports.html.\n--1564-- WARNING: unhandled riscv64-linux syscall: 258\n--1564-- You may be able to write your own handler.\n--1564-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1564-- Nevertheless we consider this a bug. Please report\n--1564-- it at http://valgrind.org/support/bug_reports.html.\n--1564-- WARNING: unhandled riscv64-linux syscall: 258\n--1564-- You may be able to write your own handler.\n--1564-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1564-- Nevertheless we consider this a bug. Please report\n--1564-- it at http://valgrind.org/support/bug_reports.html.\n--1564-- WARNING: unhandled riscv64-linux syscall: 258\n--1564-- You may be able to write your own handler.\n--1564-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1564-- Nevertheless we consider this a bug. Please report\n--1564-- it at http://valgrind.org/support/bug_reports.html.\n--1564-- WARNING: unhandled riscv64-linux syscall: 258\n--1564-- You may be able to write your own handler.\n--1564-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1564-- Nevertheless we consider this a bug. Please report\n--1564-- it at http://valgrind.org/support/bug_reports.html.\n--1564-- WARNING: unhandled riscv64-linux syscall: 258\n--1564-- You may be able to write your own handler.\n--1564-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1564-- Nevertheless we consider this a bug. Please report\n--1564-- it at http://valgrind.org/support/bug_reports.html.\n--1564-- WARNING: unhandled riscv64-linux syscall: 258\n--1564-- You may be able to write your own handler.\n--1564-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1564-- Nevertheless we consider this a bug. Please report\n--1564-- it at http://valgrind.org/support/bug_reports.html.\n--1564-- WARNING: unhandled riscv64-linux syscall: 258\n--1564-- You may be able to write your own handler.\n--1564-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1564-- Nevertheless we consider this a bug. Please report\n--1564-- it at http://valgrind.org/support/bug_reports.html.\n--1564-- WARNING: unhandled riscv64-linux syscall: 258\n--1564-- You may be able to write your own handler.\n--1564-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1564-- Nevertheless we consider this a bug. Please report\n--1564-- it at http://valgrind.org/support/bug_reports.html.\n--1564-- WARNING: unhandled riscv64-linux syscall: 258\n--1564-- You may be able to write your own handler.\n--1564-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1564-- Nevertheless we consider this a bug. Please report\n--1564-- it at http://valgrind.org/support/bug_reports.html.\n--1564-- WARNING: unhandled riscv64-linux syscall: 258\n--1564-- You may be able to write your own handler.\n--1564-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1564-- Nevertheless we consider this a bug. Please report\n--1564-- it at http://valgrind.org/support/bug_reports.html.\n--1564-- WARNING: unhandled riscv64-linux syscall: 258\n--1564-- You may be able to write your own handler.\n--1564-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1564-- Nevertheless we consider this a bug. Please report\n--1564-- it at http://valgrind.org/support/bug_reports.html.\n--1564-- WARNING: unhandled riscv64-linux syscall: 258\n--1564-- You may be able to write your own handler.\n--1564-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1564-- Nevertheless we consider this a bug. Please report\n--1564-- it at http://valgrind.org/support/bug_reports.html.\n--1564-- WARNING: unhandled riscv64-linux syscall: 258\n--1564-- You may be able to write your own handler.\n--1564-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1564-- Nevertheless we consider this a bug. Please report\n--1564-- it at http://valgrind.org/support/bug_reports.html.\n--1564-- WARNING: unhandled riscv64-linux syscall: 258\n--1564-- You may be able to write your own handler.\n--1564-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1564-- Nevertheless we consider this a bug. Please report\n--1564-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 38: failed --url https://curl.se/we/are.html --get '{host}' --- stdout --- expected: 'curl.se\n' got: 'curl.se\n' --- stderr --- expected: '' got: '--1572-- WARNING: unhandled riscv64-linux syscall: 258\n--1572-- You may be able to write your own handler.\n--1572-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1572-- Nevertheless we consider this a bug. Please report\n--1572-- it at http://valgrind.org/support/bug_reports.html.\n--1572-- WARNING: unhandled riscv64-linux syscall: 258\n--1572-- You may be able to write your own handler.\n--1572-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1572-- Nevertheless we consider this a bug. Please report\n--1572-- it at http://valgrind.org/support/bug_reports.html.\n--1572-- WARNING: unhandled riscv64-linux syscall: 258\n--1572-- You may be able to write your own handler.\n--1572-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1572-- Nevertheless we consider this a bug. Please report\n--1572-- it at http://valgrind.org/support/bug_reports.html.\n--1572-- WARNING: unhandled riscv64-linux syscall: 258\n--1572-- You may be able to write your own handler.\n--1572-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1572-- Nevertheless we consider this a bug. Please report\n--1572-- it at http://valgrind.org/support/bug_reports.html.\n--1572-- WARNING: unhandled riscv64-linux syscall: 258\n--1572-- You may be able to write your own handler.\n--1572-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1572-- Nevertheless we consider this a bug. Please report\n--1572-- it at http://valgrind.org/support/bug_reports.html.\n--1572-- WARNING: unhandled riscv64-linux syscall: 258\n--1572-- You may be able to write your own handler.\n--1572-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1572-- Nevertheless we consider this a bug. Please report\n--1572-- it at http://valgrind.org/support/bug_reports.html.\n--1572-- WARNING: unhandled riscv64-linux syscall: 258\n--1572-- You may be able to write your own handler.\n--1572-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1572-- Nevertheless we consider this a bug. Please report\n--1572-- it at http://valgrind.org/support/bug_reports.html.\n--1572-- WARNING: unhandled riscv64-linux syscall: 258\n--1572-- You may be able to write your own handler.\n--1572-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1572-- Nevertheless we consider this a bug. Please report\n--1572-- it at http://valgrind.org/support/bug_reports.html.\n--1572-- WARNING: unhandled riscv64-linux syscall: 258\n--1572-- You may be able to write your own handler.\n--1572-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1572-- Nevertheless we consider this a bug. Please report\n--1572-- it at http://valgrind.org/support/bug_reports.html.\n--1572-- WARNING: unhandled riscv64-linux syscall: 258\n--1572-- You may be able to write your own handler.\n--1572-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1572-- Nevertheless we consider this a bug. Please report\n--1572-- it at http://valgrind.org/support/bug_reports.html.\n--1572-- WARNING: unhandled riscv64-linux syscall: 258\n--1572-- You may be able to write your own handler.\n--1572-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1572-- Nevertheless we consider this a bug. Please report\n--1572-- it at http://valgrind.org/support/bug_reports.html.\n--1572-- WARNING: unhandled riscv64-linux syscall: 258\n--1572-- You may be able to write your own handler.\n--1572-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1572-- Nevertheless we consider this a bug. Please report\n--1572-- it at http://valgrind.org/support/bug_reports.html.\n--1572-- WARNING: unhandled riscv64-linux syscall: 258\n--1572-- You may be able to write your own handler.\n--1572-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1572-- Nevertheless we consider this a bug. Please report\n--1572-- it at http://valgrind.org/support/bug_reports.html.\n--1572-- WARNING: unhandled riscv64-linux syscall: 258\n--1572-- You may be able to write your own handler.\n--1572-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1572-- Nevertheless we consider this a bug. Please report\n--1572-- it at http://valgrind.org/support/bug_reports.html.\n--1572-- WARNING: unhandled riscv64-linux syscall: 258\n--1572-- You may be able to write your own handler.\n--1572-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1572-- Nevertheless we consider this a bug. Please report\n--1572-- it at http://valgrind.org/support/bug_reports.html.\n--1572-- WARNING: unhandled riscv64-linux syscall: 258\n--1572-- You may be able to write your own handler.\n--1572-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1572-- Nevertheless we consider this a bug. Please report\n--1572-- it at http://valgrind.org/support/bug_reports.html.\n--1572-- WARNING: unhandled riscv64-linux syscall: 258\n--1572-- You may be able to write your own handler.\n--1572-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1572-- Nevertheless we consider this a bug. Please report\n--1572-- it at http://valgrind.org/support/bug_reports.html.\n--1572-- WARNING: unhandled riscv64-linux syscall: 258\n--1572-- You may be able to write your own handler.\n--1572-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1572-- Nevertheless we consider this a bug. Please report\n--1572-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 39: failed --url https://10.1/we/are.html --get '{host}' --- stdout --- expected: '10.0.0.1\n' got: '10.0.0.1\n' --- stderr --- expected: '' got: '--1580-- WARNING: unhandled riscv64-linux syscall: 258\n--1580-- You may be able to write your own handler.\n--1580-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1580-- Nevertheless we consider this a bug. Please report\n--1580-- it at http://valgrind.org/support/bug_reports.html.\n--1580-- WARNING: unhandled riscv64-linux syscall: 258\n--1580-- You may be able to write your own handler.\n--1580-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1580-- Nevertheless we consider this a bug. Please report\n--1580-- it at http://valgrind.org/support/bug_reports.html.\n--1580-- WARNING: unhandled riscv64-linux syscall: 258\n--1580-- You may be able to write your own handler.\n--1580-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1580-- Nevertheless we consider this a bug. Please report\n--1580-- it at http://valgrind.org/support/bug_reports.html.\n--1580-- WARNING: unhandled riscv64-linux syscall: 258\n--1580-- You may be able to write your own handler.\n--1580-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1580-- Nevertheless we consider this a bug. Please report\n--1580-- it at http://valgrind.org/support/bug_reports.html.\n--1580-- WARNING: unhandled riscv64-linux syscall: 258\n--1580-- You may be able to write your own handler.\n--1580-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1580-- Nevertheless we consider this a bug. Please report\n--1580-- it at http://valgrind.org/support/bug_reports.html.\n--1580-- WARNING: unhandled riscv64-linux syscall: 258\n--1580-- You may be able to write your own handler.\n--1580-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1580-- Nevertheless we consider this a bug. Please report\n--1580-- it at http://valgrind.org/support/bug_reports.html.\n--1580-- WARNING: unhandled riscv64-linux syscall: 258\n--1580-- You may be able to write your own handler.\n--1580-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1580-- Nevertheless we consider this a bug. Please report\n--1580-- it at http://valgrind.org/support/bug_reports.html.\n--1580-- WARNING: unhandled riscv64-linux syscall: 258\n--1580-- You may be able to write your own handler.\n--1580-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1580-- Nevertheless we consider this a bug. Please report\n--1580-- it at http://valgrind.org/support/bug_reports.html.\n--1580-- WARNING: unhandled riscv64-linux syscall: 258\n--1580-- You may be able to write your own handler.\n--1580-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1580-- Nevertheless we consider this a bug. Please report\n--1580-- it at http://valgrind.org/support/bug_reports.html.\n--1580-- WARNING: unhandled riscv64-linux syscall: 258\n--1580-- You may be able to write your own handler.\n--1580-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1580-- Nevertheless we consider this a bug. Please report\n--1580-- it at http://valgrind.org/support/bug_reports.html.\n--1580-- WARNING: unhandled riscv64-linux syscall: 258\n--1580-- You may be able to write your own handler.\n--1580-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1580-- Nevertheless we consider this a bug. Please report\n--1580-- it at http://valgrind.org/support/bug_reports.html.\n--1580-- WARNING: unhandled riscv64-linux syscall: 258\n--1580-- You may be able to write your own handler.\n--1580-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1580-- Nevertheless we consider this a bug. Please report\n--1580-- it at http://valgrind.org/support/bug_reports.html.\n--1580-- WARNING: unhandled riscv64-linux syscall: 258\n--1580-- You may be able to write your own handler.\n--1580-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1580-- Nevertheless we consider this a bug. Please report\n--1580-- it at http://valgrind.org/support/bug_reports.html.\n--1580-- WARNING: unhandled riscv64-linux syscall: 258\n--1580-- You may be able to write your own handler.\n--1580-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1580-- Nevertheless we consider this a bug. Please report\n--1580-- it at http://valgrind.org/support/bug_reports.html.\n--1580-- WARNING: unhandled riscv64-linux syscall: 258\n--1580-- You may be able to write your own handler.\n--1580-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1580-- Nevertheless we consider this a bug. Please report\n--1580-- it at http://valgrind.org/support/bug_reports.html.\n--1580-- WARNING: unhandled riscv64-linux syscall: 258\n--1580-- You may be able to write your own handler.\n--1580-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1580-- Nevertheless we consider this a bug. Please report\n--1580-- it at http://valgrind.org/support/bug_reports.html.\n--1580-- WARNING: unhandled riscv64-linux syscall: 258\n--1580-- You may be able to write your own handler.\n--1580-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1580-- Nevertheless we consider this a bug. Please report\n--1580-- it at http://valgrind.org/support/bug_reports.html.\n--1580-- WARNING: unhandled riscv64-linux syscall: 258\n--1580-- You may be able to write your own handler.\n--1580-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1580-- Nevertheless we consider this a bug. Please report\n--1580-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 40: failed --url 'https://[fe80::0000:20c:29ff:fe9c:409b]:8080/we/are.html' --get '{host}' --- stdout --- expected: '[fe80::20c:29ff:fe9c:409b]\n' got: '[fe80::20c:29ff:fe9c:409b]\n' --- stderr --- expected: '' got: '--1588-- WARNING: unhandled riscv64-linux syscall: 258\n--1588-- You may be able to write your own handler.\n--1588-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1588-- Nevertheless we consider this a bug. Please report\n--1588-- it at http://valgrind.org/support/bug_reports.html.\n--1588-- WARNING: unhandled riscv64-linux syscall: 258\n--1588-- You may be able to write your own handler.\n--1588-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1588-- Nevertheless we consider this a bug. Please report\n--1588-- it at http://valgrind.org/support/bug_reports.html.\n--1588-- WARNING: unhandled riscv64-linux syscall: 258\n--1588-- You may be able to write your own handler.\n--1588-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1588-- Nevertheless we consider this a bug. Please report\n--1588-- it at http://valgrind.org/support/bug_reports.html.\n--1588-- WARNING: unhandled riscv64-linux syscall: 258\n--1588-- You may be able to write your own handler.\n--1588-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1588-- Nevertheless we consider this a bug. Please report\n--1588-- it at http://valgrind.org/support/bug_reports.html.\n--1588-- WARNING: unhandled riscv64-linux syscall: 258\n--1588-- You may be able to write your own handler.\n--1588-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1588-- Nevertheless we consider this a bug. Please report\n--1588-- it at http://valgrind.org/support/bug_reports.html.\n--1588-- WARNING: unhandled riscv64-linux syscall: 258\n--1588-- You may be able to write your own handler.\n--1588-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1588-- Nevertheless we consider this a bug. Please report\n--1588-- it at http://valgrind.org/support/bug_reports.html.\n--1588-- WARNING: unhandled riscv64-linux syscall: 258\n--1588-- You may be able to write your own handler.\n--1588-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1588-- Nevertheless we consider this a bug. Please report\n--1588-- it at http://valgrind.org/support/bug_reports.html.\n--1588-- WARNING: unhandled riscv64-linux syscall: 258\n--1588-- You may be able to write your own handler.\n--1588-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1588-- Nevertheless we consider this a bug. Please report\n--1588-- it at http://valgrind.org/support/bug_reports.html.\n--1588-- WARNING: unhandled riscv64-linux syscall: 258\n--1588-- You may be able to write your own handler.\n--1588-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1588-- Nevertheless we consider this a bug. Please report\n--1588-- it at http://valgrind.org/support/bug_reports.html.\n--1588-- WARNING: unhandled riscv64-linux syscall: 258\n--1588-- You may be able to write your own handler.\n--1588-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1588-- Nevertheless we consider this a bug. Please report\n--1588-- it at http://valgrind.org/support/bug_reports.html.\n--1588-- WARNING: unhandled riscv64-linux syscall: 258\n--1588-- You may be able to write your own handler.\n--1588-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1588-- Nevertheless we consider this a bug. Please report\n--1588-- it at http://valgrind.org/support/bug_reports.html.\n--1588-- WARNING: unhandled riscv64-linux syscall: 258\n--1588-- You may be able to write your own handler.\n--1588-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1588-- Nevertheless we consider this a bug. Please report\n--1588-- it at http://valgrind.org/support/bug_reports.html.\n--1588-- WARNING: unhandled riscv64-linux syscall: 258\n--1588-- You may be able to write your own handler.\n--1588-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1588-- Nevertheless we consider this a bug. Please report\n--1588-- it at http://valgrind.org/support/bug_reports.html.\n--1588-- WARNING: unhandled riscv64-linux syscall: 258\n--1588-- You may be able to write your own handler.\n--1588-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1588-- Nevertheless we consider this a bug. Please report\n--1588-- it at http://valgrind.org/support/bug_reports.html.\n--1588-- WARNING: unhandled riscv64-linux syscall: 258\n--1588-- You may be able to write your own handler.\n--1588-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1588-- Nevertheless we consider this a bug. Please report\n--1588-- it at http://valgrind.org/support/bug_reports.html.\n--1588-- WARNING: unhandled riscv64-linux syscall: 258\n--1588-- You may be able to write your own handler.\n--1588-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1588-- Nevertheless we consider this a bug. Please report\n--1588-- it at http://valgrind.org/support/bug_reports.html.\n--1588-- WARNING: unhandled riscv64-linux syscall: 258\n--1588-- You may be able to write your own handler.\n--1588-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1588-- Nevertheless we consider this a bug. Please report\n--1588-- it at http://valgrind.org/support/bug_reports.html.\n--1588-- WARNING: unhandled riscv64-linux syscall: 258\n--1588-- You may be able to write your own handler.\n--1588-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1588-- Nevertheless we consider this a bug. Please report\n--1588-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 41: failed --url 'https://[fe80::0000:20c:29ff:fe9c:409b%euth0]:8080/we/are.html' --get '{zoneid}' --- stdout --- expected: 'euth0\n' got: 'euth0\n' --- stderr --- expected: '' got: '--1596-- WARNING: unhandled riscv64-linux syscall: 258\n--1596-- You may be able to write your own handler.\n--1596-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1596-- Nevertheless we consider this a bug. Please report\n--1596-- it at http://valgrind.org/support/bug_reports.html.\n--1596-- WARNING: unhandled riscv64-linux syscall: 258\n--1596-- You may be able to write your own handler.\n--1596-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1596-- Nevertheless we consider this a bug. Please report\n--1596-- it at http://valgrind.org/support/bug_reports.html.\n--1596-- WARNING: unhandled riscv64-linux syscall: 258\n--1596-- You may be able to write your own handler.\n--1596-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1596-- Nevertheless we consider this a bug. Please report\n--1596-- it at http://valgrind.org/support/bug_reports.html.\n--1596-- WARNING: unhandled riscv64-linux syscall: 258\n--1596-- You may be able to write your own handler.\n--1596-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1596-- Nevertheless we consider this a bug. Please report\n--1596-- it at http://valgrind.org/support/bug_reports.html.\n--1596-- WARNING: unhandled riscv64-linux syscall: 258\n--1596-- You may be able to write your own handler.\n--1596-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1596-- Nevertheless we consider this a bug. Please report\n--1596-- it at http://valgrind.org/support/bug_reports.html.\n--1596-- WARNING: unhandled riscv64-linux syscall: 258\n--1596-- You may be able to write your own handler.\n--1596-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1596-- Nevertheless we consider this a bug. Please report\n--1596-- it at http://valgrind.org/support/bug_reports.html.\n--1596-- WARNING: unhandled riscv64-linux syscall: 258\n--1596-- You may be able to write your own handler.\n--1596-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1596-- Nevertheless we consider this a bug. Please report\n--1596-- it at http://valgrind.org/support/bug_reports.html.\n--1596-- WARNING: unhandled riscv64-linux syscall: 258\n--1596-- You may be able to write your own handler.\n--1596-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1596-- Nevertheless we consider this a bug. Please report\n--1596-- it at http://valgrind.org/support/bug_reports.html.\n--1596-- WARNING: unhandled riscv64-linux syscall: 258\n--1596-- You may be able to write your own handler.\n--1596-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1596-- Nevertheless we consider this a bug. Please report\n--1596-- it at http://valgrind.org/support/bug_reports.html.\n--1596-- WARNING: unhandled riscv64-linux syscall: 258\n--1596-- You may be able to write your own handler.\n--1596-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1596-- Nevertheless we consider this a bug. Please report\n--1596-- it at http://valgrind.org/support/bug_reports.html.\n--1596-- WARNING: unhandled riscv64-linux syscall: 258\n--1596-- You may be able to write your own handler.\n--1596-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1596-- Nevertheless we consider this a bug. Please report\n--1596-- it at http://valgrind.org/support/bug_reports.html.\n--1596-- WARNING: unhandled riscv64-linux syscall: 258\n--1596-- You may be able to write your own handler.\n--1596-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1596-- Nevertheless we consider this a bug. Please report\n--1596-- it at http://valgrind.org/support/bug_reports.html.\n--1596-- WARNING: unhandled riscv64-linux syscall: 258\n--1596-- You may be able to write your own handler.\n--1596-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1596-- Nevertheless we consider this a bug. Please report\n--1596-- it at http://valgrind.org/support/bug_reports.html.\n--1596-- WARNING: unhandled riscv64-linux syscall: 258\n--1596-- You may be able to write your own handler.\n--1596-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1596-- Nevertheless we consider this a bug. Please report\n--1596-- it at http://valgrind.org/support/bug_reports.html.\n--1596-- WARNING: unhandled riscv64-linux syscall: 258\n--1596-- You may be able to write your own handler.\n--1596-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1596-- Nevertheless we consider this a bug. Please report\n--1596-- it at http://valgrind.org/support/bug_reports.html.\n--1596-- WARNING: unhandled riscv64-linux syscall: 258\n--1596-- You may be able to write your own handler.\n--1596-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1596-- Nevertheless we consider this a bug. Please report\n--1596-- it at http://valgrind.org/support/bug_reports.html.\n--1596-- WARNING: unhandled riscv64-linux syscall: 258\n--1596-- You may be able to write your own handler.\n--1596-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1596-- Nevertheless we consider this a bug. Please report\n--1596-- it at http://valgrind.org/support/bug_reports.html.\n--1596-- WARNING: unhandled riscv64-linux syscall: 258\n--1596-- You may be able to write your own handler.\n--1596-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1596-- Nevertheless we consider this a bug. Please report\n--1596-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 42: failed --url 'https://[fe80::0000:20c:29ff:fe9c:409b%eth0]:8080/we/are.html' --get '{zoneid}' --- stdout --- expected: 'eth0\n' got: 'eth0\n' --- stderr --- expected: '' got: '--1604-- WARNING: unhandled riscv64-linux syscall: 258\n--1604-- You may be able to write your own handler.\n--1604-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1604-- Nevertheless we consider this a bug. Please report\n--1604-- it at http://valgrind.org/support/bug_reports.html.\n--1604-- WARNING: unhandled riscv64-linux syscall: 258\n--1604-- You may be able to write your own handler.\n--1604-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1604-- Nevertheless we consider this a bug. Please report\n--1604-- it at http://valgrind.org/support/bug_reports.html.\n--1604-- WARNING: unhandled riscv64-linux syscall: 258\n--1604-- You may be able to write your own handler.\n--1604-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1604-- Nevertheless we consider this a bug. Please report\n--1604-- it at http://valgrind.org/support/bug_reports.html.\n--1604-- WARNING: unhandled riscv64-linux syscall: 258\n--1604-- You may be able to write your own handler.\n--1604-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1604-- Nevertheless we consider this a bug. Please report\n--1604-- it at http://valgrind.org/support/bug_reports.html.\n--1604-- WARNING: unhandled riscv64-linux syscall: 258\n--1604-- You may be able to write your own handler.\n--1604-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1604-- Nevertheless we consider this a bug. Please report\n--1604-- it at http://valgrind.org/support/bug_reports.html.\n--1604-- WARNING: unhandled riscv64-linux syscall: 258\n--1604-- You may be able to write your own handler.\n--1604-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1604-- Nevertheless we consider this a bug. Please report\n--1604-- it at http://valgrind.org/support/bug_reports.html.\n--1604-- WARNING: unhandled riscv64-linux syscall: 258\n--1604-- You may be able to write your own handler.\n--1604-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1604-- Nevertheless we consider this a bug. Please report\n--1604-- it at http://valgrind.org/support/bug_reports.html.\n--1604-- WARNING: unhandled riscv64-linux syscall: 258\n--1604-- You may be able to write your own handler.\n--1604-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1604-- Nevertheless we consider this a bug. Please report\n--1604-- it at http://valgrind.org/support/bug_reports.html.\n--1604-- WARNING: unhandled riscv64-linux syscall: 258\n--1604-- You may be able to write your own handler.\n--1604-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1604-- Nevertheless we consider this a bug. Please report\n--1604-- it at http://valgrind.org/support/bug_reports.html.\n--1604-- WARNING: unhandled riscv64-linux syscall: 258\n--1604-- You may be able to write your own handler.\n--1604-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1604-- Nevertheless we consider this a bug. Please report\n--1604-- it at http://valgrind.org/support/bug_reports.html.\n--1604-- WARNING: unhandled riscv64-linux syscall: 258\n--1604-- You may be able to write your own handler.\n--1604-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1604-- Nevertheless we consider this a bug. Please report\n--1604-- it at http://valgrind.org/support/bug_reports.html.\n--1604-- WARNING: unhandled riscv64-linux syscall: 258\n--1604-- You may be able to write your own handler.\n--1604-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1604-- Nevertheless we consider this a bug. Please report\n--1604-- it at http://valgrind.org/support/bug_reports.html.\n--1604-- WARNING: unhandled riscv64-linux syscall: 258\n--1604-- You may be able to write your own handler.\n--1604-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1604-- Nevertheless we consider this a bug. Please report\n--1604-- it at http://valgrind.org/support/bug_reports.html.\n--1604-- WARNING: unhandled riscv64-linux syscall: 258\n--1604-- You may be able to write your own handler.\n--1604-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1604-- Nevertheless we consider this a bug. Please report\n--1604-- it at http://valgrind.org/support/bug_reports.html.\n--1604-- WARNING: unhandled riscv64-linux syscall: 258\n--1604-- You may be able to write your own handler.\n--1604-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1604-- Nevertheless we consider this a bug. Please report\n--1604-- it at http://valgrind.org/support/bug_reports.html.\n--1604-- WARNING: unhandled riscv64-linux syscall: 258\n--1604-- You may be able to write your own handler.\n--1604-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1604-- Nevertheless we consider this a bug. Please report\n--1604-- it at http://valgrind.org/support/bug_reports.html.\n--1604-- WARNING: unhandled riscv64-linux syscall: 258\n--1604-- You may be able to write your own handler.\n--1604-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1604-- Nevertheless we consider this a bug. Please report\n--1604-- it at http://valgrind.org/support/bug_reports.html.\n--1604-- WARNING: unhandled riscv64-linux syscall: 258\n--1604-- You may be able to write your own handler.\n--1604-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1604-- Nevertheless we consider this a bug. Please report\n--1604-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 43: failed --url 'https://curl.se/we/are.html?user=many#more' --get '{query}' --- stdout --- expected: 'user=many\n' got: 'user=many\n' --- stderr --- expected: '' got: '--1612-- WARNING: unhandled riscv64-linux syscall: 258\n--1612-- You may be able to write your own handler.\n--1612-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1612-- Nevertheless we consider this a bug. Please report\n--1612-- it at http://valgrind.org/support/bug_reports.html.\n--1612-- WARNING: unhandled riscv64-linux syscall: 258\n--1612-- You may be able to write your own handler.\n--1612-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1612-- Nevertheless we consider this a bug. Please report\n--1612-- it at http://valgrind.org/support/bug_reports.html.\n--1612-- WARNING: unhandled riscv64-linux syscall: 258\n--1612-- You may be able to write your own handler.\n--1612-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1612-- Nevertheless we consider this a bug. Please report\n--1612-- it at http://valgrind.org/support/bug_reports.html.\n--1612-- WARNING: unhandled riscv64-linux syscall: 258\n--1612-- You may be able to write your own handler.\n--1612-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1612-- Nevertheless we consider this a bug. Please report\n--1612-- it at http://valgrind.org/support/bug_reports.html.\n--1612-- WARNING: unhandled riscv64-linux syscall: 258\n--1612-- You may be able to write your own handler.\n--1612-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1612-- Nevertheless we consider this a bug. Please report\n--1612-- it at http://valgrind.org/support/bug_reports.html.\n--1612-- WARNING: unhandled riscv64-linux syscall: 258\n--1612-- You may be able to write your own handler.\n--1612-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1612-- Nevertheless we consider this a bug. Please report\n--1612-- it at http://valgrind.org/support/bug_reports.html.\n--1612-- WARNING: unhandled riscv64-linux syscall: 258\n--1612-- You may be able to write your own handler.\n--1612-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1612-- Nevertheless we consider this a bug. Please report\n--1612-- it at http://valgrind.org/support/bug_reports.html.\n--1612-- WARNING: unhandled riscv64-linux syscall: 258\n--1612-- You may be able to write your own handler.\n--1612-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1612-- Nevertheless we consider this a bug. Please report\n--1612-- it at http://valgrind.org/support/bug_reports.html.\n--1612-- WARNING: unhandled riscv64-linux syscall: 258\n--1612-- You may be able to write your own handler.\n--1612-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1612-- Nevertheless we consider this a bug. Please report\n--1612-- it at http://valgrind.org/support/bug_reports.html.\n--1612-- WARNING: unhandled riscv64-linux syscall: 258\n--1612-- You may be able to write your own handler.\n--1612-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1612-- Nevertheless we consider this a bug. Please report\n--1612-- it at http://valgrind.org/support/bug_reports.html.\n--1612-- WARNING: unhandled riscv64-linux syscall: 258\n--1612-- You may be able to write your own handler.\n--1612-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1612-- Nevertheless we consider this a bug. Please report\n--1612-- it at http://valgrind.org/support/bug_reports.html.\n--1612-- WARNING: unhandled riscv64-linux syscall: 258\n--1612-- You may be able to write your own handler.\n--1612-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1612-- Nevertheless we consider this a bug. Please report\n--1612-- it at http://valgrind.org/support/bug_reports.html.\n--1612-- WARNING: unhandled riscv64-linux syscall: 258\n--1612-- You may be able to write your own handler.\n--1612-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1612-- Nevertheless we consider this a bug. Please report\n--1612-- it at http://valgrind.org/support/bug_reports.html.\n--1612-- WARNING: unhandled riscv64-linux syscall: 258\n--1612-- You may be able to write your own handler.\n--1612-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1612-- Nevertheless we consider this a bug. Please report\n--1612-- it at http://valgrind.org/support/bug_reports.html.\n--1612-- WARNING: unhandled riscv64-linux syscall: 258\n--1612-- You may be able to write your own handler.\n--1612-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1612-- Nevertheless we consider this a bug. Please report\n--1612-- it at http://valgrind.org/support/bug_reports.html.\n--1612-- WARNING: unhandled riscv64-linux syscall: 258\n--1612-- You may be able to write your own handler.\n--1612-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1612-- Nevertheless we consider this a bug. Please report\n--1612-- it at http://valgrind.org/support/bug_reports.html.\n--1612-- WARNING: unhandled riscv64-linux syscall: 258\n--1612-- You may be able to write your own handler.\n--1612-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1612-- Nevertheless we consider this a bug. Please report\n--1612-- it at http://valgrind.org/support/bug_reports.html.\n--1612-- WARNING: unhandled riscv64-linux syscall: 258\n--1612-- You may be able to write your own handler.\n--1612-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1612-- Nevertheless we consider this a bug. Please report\n--1612-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 44: failed --url 'https://curl.se/we/are.html?user=many#more' --get '{fragment}' --- stdout --- expected: 'more\n' got: 'more\n' --- stderr --- expected: '' got: '--1620-- WARNING: unhandled riscv64-linux syscall: 258\n--1620-- You may be able to write your own handler.\n--1620-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1620-- Nevertheless we consider this a bug. Please report\n--1620-- it at http://valgrind.org/support/bug_reports.html.\n--1620-- WARNING: unhandled riscv64-linux syscall: 258\n--1620-- You may be able to write your own handler.\n--1620-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1620-- Nevertheless we consider this a bug. Please report\n--1620-- it at http://valgrind.org/support/bug_reports.html.\n--1620-- WARNING: unhandled riscv64-linux syscall: 258\n--1620-- You may be able to write your own handler.\n--1620-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1620-- Nevertheless we consider this a bug. Please report\n--1620-- it at http://valgrind.org/support/bug_reports.html.\n--1620-- WARNING: unhandled riscv64-linux syscall: 258\n--1620-- You may be able to write your own handler.\n--1620-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1620-- Nevertheless we consider this a bug. Please report\n--1620-- it at http://valgrind.org/support/bug_reports.html.\n--1620-- WARNING: unhandled riscv64-linux syscall: 258\n--1620-- You may be able to write your own handler.\n--1620-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1620-- Nevertheless we consider this a bug. Please report\n--1620-- it at http://valgrind.org/support/bug_reports.html.\n--1620-- WARNING: unhandled riscv64-linux syscall: 258\n--1620-- You may be able to write your own handler.\n--1620-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1620-- Nevertheless we consider this a bug. Please report\n--1620-- it at http://valgrind.org/support/bug_reports.html.\n--1620-- WARNING: unhandled riscv64-linux syscall: 258\n--1620-- You may be able to write your own handler.\n--1620-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1620-- Nevertheless we consider this a bug. Please report\n--1620-- it at http://valgrind.org/support/bug_reports.html.\n--1620-- WARNING: unhandled riscv64-linux syscall: 258\n--1620-- You may be able to write your own handler.\n--1620-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1620-- Nevertheless we consider this a bug. Please report\n--1620-- it at http://valgrind.org/support/bug_reports.html.\n--1620-- WARNING: unhandled riscv64-linux syscall: 258\n--1620-- You may be able to write your own handler.\n--1620-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1620-- Nevertheless we consider this a bug. Please report\n--1620-- it at http://valgrind.org/support/bug_reports.html.\n--1620-- WARNING: unhandled riscv64-linux syscall: 258\n--1620-- You may be able to write your own handler.\n--1620-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1620-- Nevertheless we consider this a bug. Please report\n--1620-- it at http://valgrind.org/support/bug_reports.html.\n--1620-- WARNING: unhandled riscv64-linux syscall: 258\n--1620-- You may be able to write your own handler.\n--1620-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1620-- Nevertheless we consider this a bug. Please report\n--1620-- it at http://valgrind.org/support/bug_reports.html.\n--1620-- WARNING: unhandled riscv64-linux syscall: 258\n--1620-- You may be able to write your own handler.\n--1620-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1620-- Nevertheless we consider this a bug. Please report\n--1620-- it at http://valgrind.org/support/bug_reports.html.\n--1620-- WARNING: unhandled riscv64-linux syscall: 258\n--1620-- You may be able to write your own handler.\n--1620-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1620-- Nevertheless we consider this a bug. Please report\n--1620-- it at http://valgrind.org/support/bug_reports.html.\n--1620-- WARNING: unhandled riscv64-linux syscall: 258\n--1620-- You may be able to write your own handler.\n--1620-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1620-- Nevertheless we consider this a bug. Please report\n--1620-- it at http://valgrind.org/support/bug_reports.html.\n--1620-- WARNING: unhandled riscv64-linux syscall: 258\n--1620-- You may be able to write your own handler.\n--1620-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1620-- Nevertheless we consider this a bug. Please report\n--1620-- it at http://valgrind.org/support/bug_reports.html.\n--1620-- WARNING: unhandled riscv64-linux syscall: 258\n--1620-- You may be able to write your own handler.\n--1620-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1620-- Nevertheless we consider this a bug. Please report\n--1620-- it at http://valgrind.org/support/bug_reports.html.\n--1620-- WARNING: unhandled riscv64-linux syscall: 258\n--1620-- You may be able to write your own handler.\n--1620-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1620-- Nevertheless we consider this a bug. Please report\n--1620-- it at http://valgrind.org/support/bug_reports.html.\n--1620-- WARNING: unhandled riscv64-linux syscall: 258\n--1620-- You may be able to write your own handler.\n--1620-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1620-- Nevertheless we consider this a bug. Please report\n--1620-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 45: failed --url imap://curl.se/we/are.html -g '{default:port}' --- stdout --- expected: '143\n' got: '143\n' --- stderr --- expected: '' got: '--1628-- WARNING: unhandled riscv64-linux syscall: 258\n--1628-- You may be able to write your own handler.\n--1628-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1628-- Nevertheless we consider this a bug. Please report\n--1628-- it at http://valgrind.org/support/bug_reports.html.\n--1628-- WARNING: unhandled riscv64-linux syscall: 258\n--1628-- You may be able to write your own handler.\n--1628-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1628-- Nevertheless we consider this a bug. Please report\n--1628-- it at http://valgrind.org/support/bug_reports.html.\n--1628-- WARNING: unhandled riscv64-linux syscall: 258\n--1628-- You may be able to write your own handler.\n--1628-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1628-- Nevertheless we consider this a bug. Please report\n--1628-- it at http://valgrind.org/support/bug_reports.html.\n--1628-- WARNING: unhandled riscv64-linux syscall: 258\n--1628-- You may be able to write your own handler.\n--1628-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1628-- Nevertheless we consider this a bug. Please report\n--1628-- it at http://valgrind.org/support/bug_reports.html.\n--1628-- WARNING: unhandled riscv64-linux syscall: 258\n--1628-- You may be able to write your own handler.\n--1628-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1628-- Nevertheless we consider this a bug. Please report\n--1628-- it at http://valgrind.org/support/bug_reports.html.\n--1628-- WARNING: unhandled riscv64-linux syscall: 258\n--1628-- You may be able to write your own handler.\n--1628-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1628-- Nevertheless we consider this a bug. Please report\n--1628-- it at http://valgrind.org/support/bug_reports.html.\n--1628-- WARNING: unhandled riscv64-linux syscall: 258\n--1628-- You may be able to write your own handler.\n--1628-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1628-- Nevertheless we consider this a bug. Please report\n--1628-- it at http://valgrind.org/support/bug_reports.html.\n--1628-- WARNING: unhandled riscv64-linux syscall: 258\n--1628-- You may be able to write your own handler.\n--1628-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1628-- Nevertheless we consider this a bug. Please report\n--1628-- it at http://valgrind.org/support/bug_reports.html.\n--1628-- WARNING: unhandled riscv64-linux syscall: 258\n--1628-- You may be able to write your own handler.\n--1628-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1628-- Nevertheless we consider this a bug. Please report\n--1628-- it at http://valgrind.org/support/bug_reports.html.\n--1628-- WARNING: unhandled riscv64-linux syscall: 258\n--1628-- You may be able to write your own handler.\n--1628-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1628-- Nevertheless we consider this a bug. Please report\n--1628-- it at http://valgrind.org/support/bug_reports.html.\n--1628-- WARNING: unhandled riscv64-linux syscall: 258\n--1628-- You may be able to write your own handler.\n--1628-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1628-- Nevertheless we consider this a bug. Please report\n--1628-- it at http://valgrind.org/support/bug_reports.html.\n--1628-- WARNING: unhandled riscv64-linux syscall: 258\n--1628-- You may be able to write your own handler.\n--1628-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1628-- Nevertheless we consider this a bug. Please report\n--1628-- it at http://valgrind.org/support/bug_reports.html.\n--1628-- WARNING: unhandled riscv64-linux syscall: 258\n--1628-- You may be able to write your own handler.\n--1628-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1628-- Nevertheless we consider this a bug. Please report\n--1628-- it at http://valgrind.org/support/bug_reports.html.\n--1628-- WARNING: unhandled riscv64-linux syscall: 258\n--1628-- You may be able to write your own handler.\n--1628-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1628-- Nevertheless we consider this a bug. Please report\n--1628-- it at http://valgrind.org/support/bug_reports.html.\n--1628-- WARNING: unhandled riscv64-linux syscall: 258\n--1628-- You may be able to write your own handler.\n--1628-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1628-- Nevertheless we consider this a bug. Please report\n--1628-- it at http://valgrind.org/support/bug_reports.html.\n--1628-- WARNING: unhandled riscv64-linux syscall: 258\n--1628-- You may be able to write your own handler.\n--1628-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1628-- Nevertheless we consider this a bug. Please report\n--1628-- it at http://valgrind.org/support/bug_reports.html.\n--1628-- WARNING: unhandled riscv64-linux syscall: 258\n--1628-- You may be able to write your own handler.\n--1628-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1628-- Nevertheless we consider this a bug. Please report\n--1628-- it at http://valgrind.org/support/bug_reports.html.\n--1628-- WARNING: unhandled riscv64-linux syscall: 258\n--1628-- You may be able to write your own handler.\n--1628-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1628-- Nevertheless we consider this a bug. Please report\n--1628-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 46: failed --url https://curl.se/hello --append path=you --- stdout --- expected: 'https://curl.se/hello/you\n' got: 'https://curl.se/hello/you\n' --- stderr --- expected: '' got: '--1636-- WARNING: unhandled riscv64-linux syscall: 258\n--1636-- You may be able to write your own handler.\n--1636-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1636-- Nevertheless we consider this a bug. Please report\n--1636-- it at http://valgrind.org/support/bug_reports.html.\n--1636-- WARNING: unhandled riscv64-linux syscall: 258\n--1636-- You may be able to write your own handler.\n--1636-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1636-- Nevertheless we consider this a bug. Please report\n--1636-- it at http://valgrind.org/support/bug_reports.html.\n--1636-- WARNING: unhandled riscv64-linux syscall: 258\n--1636-- You may be able to write your own handler.\n--1636-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1636-- Nevertheless we consider this a bug. Please report\n--1636-- it at http://valgrind.org/support/bug_reports.html.\n--1636-- WARNING: unhandled riscv64-linux syscall: 258\n--1636-- You may be able to write your own handler.\n--1636-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1636-- Nevertheless we consider this a bug. Please report\n--1636-- it at http://valgrind.org/support/bug_reports.html.\n--1636-- WARNING: unhandled riscv64-linux syscall: 258\n--1636-- You may be able to write your own handler.\n--1636-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1636-- Nevertheless we consider this a bug. Please report\n--1636-- it at http://valgrind.org/support/bug_reports.html.\n--1636-- WARNING: unhandled riscv64-linux syscall: 258\n--1636-- You may be able to write your own handler.\n--1636-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1636-- Nevertheless we consider this a bug. Please report\n--1636-- it at http://valgrind.org/support/bug_reports.html.\n--1636-- WARNING: unhandled riscv64-linux syscall: 258\n--1636-- You may be able to write your own handler.\n--1636-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1636-- Nevertheless we consider this a bug. Please report\n--1636-- it at http://valgrind.org/support/bug_reports.html.\n--1636-- WARNING: unhandled riscv64-linux syscall: 258\n--1636-- You may be able to write your own handler.\n--1636-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1636-- Nevertheless we consider this a bug. Please report\n--1636-- it at http://valgrind.org/support/bug_reports.html.\n--1636-- WARNING: unhandled riscv64-linux syscall: 258\n--1636-- You may be able to write your own handler.\n--1636-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1636-- Nevertheless we consider this a bug. Please report\n--1636-- it at http://valgrind.org/support/bug_reports.html.\n--1636-- WARNING: unhandled riscv64-linux syscall: 258\n--1636-- You may be able to write your own handler.\n--1636-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1636-- Nevertheless we consider this a bug. Please report\n--1636-- it at http://valgrind.org/support/bug_reports.html.\n--1636-- WARNING: unhandled riscv64-linux syscall: 258\n--1636-- You may be able to write your own handler.\n--1636-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1636-- Nevertheless we consider this a bug. Please report\n--1636-- it at http://valgrind.org/support/bug_reports.html.\n--1636-- WARNING: unhandled riscv64-linux syscall: 258\n--1636-- You may be able to write your own handler.\n--1636-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1636-- Nevertheless we consider this a bug. Please report\n--1636-- it at http://valgrind.org/support/bug_reports.html.\n--1636-- WARNING: unhandled riscv64-linux syscall: 258\n--1636-- You may be able to write your own handler.\n--1636-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1636-- Nevertheless we consider this a bug. Please report\n--1636-- it at http://valgrind.org/support/bug_reports.html.\n--1636-- WARNING: unhandled riscv64-linux syscall: 258\n--1636-- You may be able to write your own handler.\n--1636-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1636-- Nevertheless we consider this a bug. Please report\n--1636-- it at http://valgrind.org/support/bug_reports.html.\n--1636-- WARNING: unhandled riscv64-linux syscall: 258\n--1636-- You may be able to write your own handler.\n--1636-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1636-- Nevertheless we consider this a bug. Please report\n--1636-- it at http://valgrind.org/support/bug_reports.html.\n--1636-- WARNING: unhandled riscv64-linux syscall: 258\n--1636-- You may be able to write your own handler.\n--1636-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1636-- Nevertheless we consider this a bug. Please report\n--1636-- it at http://valgrind.org/support/bug_reports.html.\n--1636-- WARNING: unhandled riscv64-linux syscall: 258\n--1636-- You may be able to write your own handler.\n--1636-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1636-- Nevertheless we consider this a bug. Please report\n--1636-- it at http://valgrind.org/support/bug_reports.html.\n--1636-- WARNING: unhandled riscv64-linux syscall: 258\n--1636-- You may be able to write your own handler.\n--1636-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1636-- Nevertheless we consider this a bug. Please report\n--1636-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 47: failed --url https://curl.se/hello --append 'path=you index.html' --- stdout --- expected: 'https://curl.se/hello/you%20index.html\n' got: 'https://curl.se/hello/you%20index.html\n' --- stderr --- expected: '' got: '--1644-- WARNING: unhandled riscv64-linux syscall: 258\n--1644-- You may be able to write your own handler.\n--1644-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1644-- Nevertheless we consider this a bug. Please report\n--1644-- it at http://valgrind.org/support/bug_reports.html.\n--1644-- WARNING: unhandled riscv64-linux syscall: 258\n--1644-- You may be able to write your own handler.\n--1644-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1644-- Nevertheless we consider this a bug. Please report\n--1644-- it at http://valgrind.org/support/bug_reports.html.\n--1644-- WARNING: unhandled riscv64-linux syscall: 258\n--1644-- You may be able to write your own handler.\n--1644-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1644-- Nevertheless we consider this a bug. Please report\n--1644-- it at http://valgrind.org/support/bug_reports.html.\n--1644-- WARNING: unhandled riscv64-linux syscall: 258\n--1644-- You may be able to write your own handler.\n--1644-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1644-- Nevertheless we consider this a bug. Please report\n--1644-- it at http://valgrind.org/support/bug_reports.html.\n--1644-- WARNING: unhandled riscv64-linux syscall: 258\n--1644-- You may be able to write your own handler.\n--1644-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1644-- Nevertheless we consider this a bug. Please report\n--1644-- it at http://valgrind.org/support/bug_reports.html.\n--1644-- WARNING: unhandled riscv64-linux syscall: 258\n--1644-- You may be able to write your own handler.\n--1644-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1644-- Nevertheless we consider this a bug. Please report\n--1644-- it at http://valgrind.org/support/bug_reports.html.\n--1644-- WARNING: unhandled riscv64-linux syscall: 258\n--1644-- You may be able to write your own handler.\n--1644-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1644-- Nevertheless we consider this a bug. Please report\n--1644-- it at http://valgrind.org/support/bug_reports.html.\n--1644-- WARNING: unhandled riscv64-linux syscall: 258\n--1644-- You may be able to write your own handler.\n--1644-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1644-- Nevertheless we consider this a bug. Please report\n--1644-- it at http://valgrind.org/support/bug_reports.html.\n--1644-- WARNING: unhandled riscv64-linux syscall: 258\n--1644-- You may be able to write your own handler.\n--1644-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1644-- Nevertheless we consider this a bug. Please report\n--1644-- it at http://valgrind.org/support/bug_reports.html.\n--1644-- WARNING: unhandled riscv64-linux syscall: 258\n--1644-- You may be able to write your own handler.\n--1644-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1644-- Nevertheless we consider this a bug. Please report\n--1644-- it at http://valgrind.org/support/bug_reports.html.\n--1644-- WARNING: unhandled riscv64-linux syscall: 258\n--1644-- You may be able to write your own handler.\n--1644-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1644-- Nevertheless we consider this a bug. Please report\n--1644-- it at http://valgrind.org/support/bug_reports.html.\n--1644-- WARNING: unhandled riscv64-linux syscall: 258\n--1644-- You may be able to write your own handler.\n--1644-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1644-- Nevertheless we consider this a bug. Please report\n--1644-- it at http://valgrind.org/support/bug_reports.html.\n--1644-- WARNING: unhandled riscv64-linux syscall: 258\n--1644-- You may be able to write your own handler.\n--1644-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1644-- Nevertheless we consider this a bug. Please report\n--1644-- it at http://valgrind.org/support/bug_reports.html.\n--1644-- WARNING: unhandled riscv64-linux syscall: 258\n--1644-- You may be able to write your own handler.\n--1644-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1644-- Nevertheless we consider this a bug. Please report\n--1644-- it at http://valgrind.org/support/bug_reports.html.\n--1644-- WARNING: unhandled riscv64-linux syscall: 258\n--1644-- You may be able to write your own handler.\n--1644-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1644-- Nevertheless we consider this a bug. Please report\n--1644-- it at http://valgrind.org/support/bug_reports.html.\n--1644-- WARNING: unhandled riscv64-linux syscall: 258\n--1644-- You may be able to write your own handler.\n--1644-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1644-- Nevertheless we consider this a bug. Please report\n--1644-- it at http://valgrind.org/support/bug_reports.html.\n--1644-- WARNING: unhandled riscv64-linux syscall: 258\n--1644-- You may be able to write your own handler.\n--1644-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1644-- Nevertheless we consider this a bug. Please report\n--1644-- it at http://valgrind.org/support/bug_reports.html.\n--1644-- WARNING: unhandled riscv64-linux syscall: 258\n--1644-- You may be able to write your own handler.\n--1644-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1644-- Nevertheless we consider this a bug. Please report\n--1644-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 48: failed --url 'https://curl.se?name=hello' --append query=search=string --- stdout --- expected: 'https://curl.se/?name=hello&search=string\n' got: 'https://curl.se/?name=hello&search=string\n' --- stderr --- expected: '' got: '--1652-- WARNING: unhandled riscv64-linux syscall: 258\n--1652-- You may be able to write your own handler.\n--1652-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1652-- Nevertheless we consider this a bug. Please report\n--1652-- it at http://valgrind.org/support/bug_reports.html.\n--1652-- WARNING: unhandled riscv64-linux syscall: 258\n--1652-- You may be able to write your own handler.\n--1652-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1652-- Nevertheless we consider this a bug. Please report\n--1652-- it at http://valgrind.org/support/bug_reports.html.\n--1652-- WARNING: unhandled riscv64-linux syscall: 258\n--1652-- You may be able to write your own handler.\n--1652-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1652-- Nevertheless we consider this a bug. Please report\n--1652-- it at http://valgrind.org/support/bug_reports.html.\n--1652-- WARNING: unhandled riscv64-linux syscall: 258\n--1652-- You may be able to write your own handler.\n--1652-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1652-- Nevertheless we consider this a bug. Please report\n--1652-- it at http://valgrind.org/support/bug_reports.html.\n--1652-- WARNING: unhandled riscv64-linux syscall: 258\n--1652-- You may be able to write your own handler.\n--1652-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1652-- Nevertheless we consider this a bug. Please report\n--1652-- it at http://valgrind.org/support/bug_reports.html.\n--1652-- WARNING: unhandled riscv64-linux syscall: 258\n--1652-- You may be able to write your own handler.\n--1652-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1652-- Nevertheless we consider this a bug. Please report\n--1652-- it at http://valgrind.org/support/bug_reports.html.\n--1652-- WARNING: unhandled riscv64-linux syscall: 258\n--1652-- You may be able to write your own handler.\n--1652-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1652-- Nevertheless we consider this a bug. Please report\n--1652-- it at http://valgrind.org/support/bug_reports.html.\n--1652-- WARNING: unhandled riscv64-linux syscall: 258\n--1652-- You may be able to write your own handler.\n--1652-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1652-- Nevertheless we consider this a bug. Please report\n--1652-- it at http://valgrind.org/support/bug_reports.html.\n--1652-- WARNING: unhandled riscv64-linux syscall: 258\n--1652-- You may be able to write your own handler.\n--1652-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1652-- Nevertheless we consider this a bug. Please report\n--1652-- it at http://valgrind.org/support/bug_reports.html.\n--1652-- WARNING: unhandled riscv64-linux syscall: 258\n--1652-- You may be able to write your own handler.\n--1652-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1652-- Nevertheless we consider this a bug. Please report\n--1652-- it at http://valgrind.org/support/bug_reports.html.\n--1652-- WARNING: unhandled riscv64-linux syscall: 258\n--1652-- You may be able to write your own handler.\n--1652-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1652-- Nevertheless we consider this a bug. Please report\n--1652-- it at http://valgrind.org/support/bug_reports.html.\n--1652-- WARNING: unhandled riscv64-linux syscall: 258\n--1652-- You may be able to write your own handler.\n--1652-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1652-- Nevertheless we consider this a bug. Please report\n--1652-- it at http://valgrind.org/support/bug_reports.html.\n--1652-- WARNING: unhandled riscv64-linux syscall: 258\n--1652-- You may be able to write your own handler.\n--1652-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1652-- Nevertheless we consider this a bug. Please report\n--1652-- it at http://valgrind.org/support/bug_reports.html.\n--1652-- WARNING: unhandled riscv64-linux syscall: 258\n--1652-- You may be able to write your own handler.\n--1652-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1652-- Nevertheless we consider this a bug. Please report\n--1652-- it at http://valgrind.org/support/bug_reports.html.\n--1652-- WARNING: unhandled riscv64-linux syscall: 258\n--1652-- You may be able to write your own handler.\n--1652-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1652-- Nevertheless we consider this a bug. Please report\n--1652-- it at http://valgrind.org/support/bug_reports.html.\n--1652-- WARNING: unhandled riscv64-linux syscall: 258\n--1652-- You may be able to write your own handler.\n--1652-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1652-- Nevertheless we consider this a bug. Please report\n--1652-- it at http://valgrind.org/support/bug_reports.html.\n--1652-- WARNING: unhandled riscv64-linux syscall: 258\n--1652-- You may be able to write your own handler.\n--1652-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1652-- Nevertheless we consider this a bug. Please report\n--1652-- it at http://valgrind.org/support/bug_reports.html.\n--1652-- WARNING: unhandled riscv64-linux syscall: 258\n--1652-- You may be able to write your own handler.\n--1652-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1652-- Nevertheless we consider this a bug. Please report\n--1652-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 49: failed --url https://curl.se/hello --set user=:hej: --- stdout --- expected: 'https://%3ahej%3a@curl.se/hello\n' got: 'https://%3ahej%3a@curl.se/hello\n' --- stderr --- expected: '' got: '--1660-- WARNING: unhandled riscv64-linux syscall: 258\n--1660-- You may be able to write your own handler.\n--1660-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1660-- Nevertheless we consider this a bug. Please report\n--1660-- it at http://valgrind.org/support/bug_reports.html.\n--1660-- WARNING: unhandled riscv64-linux syscall: 258\n--1660-- You may be able to write your own handler.\n--1660-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1660-- Nevertheless we consider this a bug. Please report\n--1660-- it at http://valgrind.org/support/bug_reports.html.\n--1660-- WARNING: unhandled riscv64-linux syscall: 258\n--1660-- You may be able to write your own handler.\n--1660-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1660-- Nevertheless we consider this a bug. Please report\n--1660-- it at http://valgrind.org/support/bug_reports.html.\n--1660-- WARNING: unhandled riscv64-linux syscall: 258\n--1660-- You may be able to write your own handler.\n--1660-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1660-- Nevertheless we consider this a bug. Please report\n--1660-- it at http://valgrind.org/support/bug_reports.html.\n--1660-- WARNING: unhandled riscv64-linux syscall: 258\n--1660-- You may be able to write your own handler.\n--1660-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1660-- Nevertheless we consider this a bug. Please report\n--1660-- it at http://valgrind.org/support/bug_reports.html.\n--1660-- WARNING: unhandled riscv64-linux syscall: 258\n--1660-- You may be able to write your own handler.\n--1660-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1660-- Nevertheless we consider this a bug. Please report\n--1660-- it at http://valgrind.org/support/bug_reports.html.\n--1660-- WARNING: unhandled riscv64-linux syscall: 258\n--1660-- You may be able to write your own handler.\n--1660-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1660-- Nevertheless we consider this a bug. Please report\n--1660-- it at http://valgrind.org/support/bug_reports.html.\n--1660-- WARNING: unhandled riscv64-linux syscall: 258\n--1660-- You may be able to write your own handler.\n--1660-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1660-- Nevertheless we consider this a bug. Please report\n--1660-- it at http://valgrind.org/support/bug_reports.html.\n--1660-- WARNING: unhandled riscv64-linux syscall: 258\n--1660-- You may be able to write your own handler.\n--1660-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1660-- Nevertheless we consider this a bug. Please report\n--1660-- it at http://valgrind.org/support/bug_reports.html.\n--1660-- WARNING: unhandled riscv64-linux syscall: 258\n--1660-- You may be able to write your own handler.\n--1660-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1660-- Nevertheless we consider this a bug. Please report\n--1660-- it at http://valgrind.org/support/bug_reports.html.\n--1660-- WARNING: unhandled riscv64-linux syscall: 258\n--1660-- You may be able to write your own handler.\n--1660-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1660-- Nevertheless we consider this a bug. Please report\n--1660-- it at http://valgrind.org/support/bug_reports.html.\n--1660-- WARNING: unhandled riscv64-linux syscall: 258\n--1660-- You may be able to write your own handler.\n--1660-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1660-- Nevertheless we consider this a bug. Please report\n--1660-- it at http://valgrind.org/support/bug_reports.html.\n--1660-- WARNING: unhandled riscv64-linux syscall: 258\n--1660-- You may be able to write your own handler.\n--1660-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1660-- Nevertheless we consider this a bug. Please report\n--1660-- it at http://valgrind.org/support/bug_reports.html.\n--1660-- WARNING: unhandled riscv64-linux syscall: 258\n--1660-- You may be able to write your own handler.\n--1660-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1660-- Nevertheless we consider this a bug. Please report\n--1660-- it at http://valgrind.org/support/bug_reports.html.\n--1660-- WARNING: unhandled riscv64-linux syscall: 258\n--1660-- You may be able to write your own handler.\n--1660-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1660-- Nevertheless we consider this a bug. Please report\n--1660-- it at http://valgrind.org/support/bug_reports.html.\n--1660-- WARNING: unhandled riscv64-linux syscall: 258\n--1660-- You may be able to write your own handler.\n--1660-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1660-- Nevertheless we consider this a bug. Please report\n--1660-- it at http://valgrind.org/support/bug_reports.html.\n--1660-- WARNING: unhandled riscv64-linux syscall: 258\n--1660-- You may be able to write your own handler.\n--1660-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1660-- Nevertheless we consider this a bug. Please report\n--1660-- it at http://valgrind.org/support/bug_reports.html.\n--1660-- WARNING: unhandled riscv64-linux syscall: 258\n--1660-- You may be able to write your own handler.\n--1660-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1660-- Nevertheless we consider this a bug. Please report\n--1660-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 50: failed --url https://curl.se/hello --set user=hej --set password=secret --- stdout --- expected: 'https://hej:secret@curl.se/hello\n' got: 'https://hej:secret@curl.se/hello\n' --- stderr --- expected: '' got: '--1668-- WARNING: unhandled riscv64-linux syscall: 258\n--1668-- You may be able to write your own handler.\n--1668-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1668-- Nevertheless we consider this a bug. Please report\n--1668-- it at http://valgrind.org/support/bug_reports.html.\n--1668-- WARNING: unhandled riscv64-linux syscall: 258\n--1668-- You may be able to write your own handler.\n--1668-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1668-- Nevertheless we consider this a bug. Please report\n--1668-- it at http://valgrind.org/support/bug_reports.html.\n--1668-- WARNING: unhandled riscv64-linux syscall: 258\n--1668-- You may be able to write your own handler.\n--1668-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1668-- Nevertheless we consider this a bug. Please report\n--1668-- it at http://valgrind.org/support/bug_reports.html.\n--1668-- WARNING: unhandled riscv64-linux syscall: 258\n--1668-- You may be able to write your own handler.\n--1668-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1668-- Nevertheless we consider this a bug. Please report\n--1668-- it at http://valgrind.org/support/bug_reports.html.\n--1668-- WARNING: unhandled riscv64-linux syscall: 258\n--1668-- You may be able to write your own handler.\n--1668-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1668-- Nevertheless we consider this a bug. Please report\n--1668-- it at http://valgrind.org/support/bug_reports.html.\n--1668-- WARNING: unhandled riscv64-linux syscall: 258\n--1668-- You may be able to write your own handler.\n--1668-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1668-- Nevertheless we consider this a bug. Please report\n--1668-- it at http://valgrind.org/support/bug_reports.html.\n--1668-- WARNING: unhandled riscv64-linux syscall: 258\n--1668-- You may be able to write your own handler.\n--1668-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1668-- Nevertheless we consider this a bug. Please report\n--1668-- it at http://valgrind.org/support/bug_reports.html.\n--1668-- WARNING: unhandled riscv64-linux syscall: 258\n--1668-- You may be able to write your own handler.\n--1668-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1668-- Nevertheless we consider this a bug. Please report\n--1668-- it at http://valgrind.org/support/bug_reports.html.\n--1668-- WARNING: unhandled riscv64-linux syscall: 258\n--1668-- You may be able to write your own handler.\n--1668-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1668-- Nevertheless we consider this a bug. Please report\n--1668-- it at http://valgrind.org/support/bug_reports.html.\n--1668-- WARNING: unhandled riscv64-linux syscall: 258\n--1668-- You may be able to write your own handler.\n--1668-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1668-- Nevertheless we consider this a bug. Please report\n--1668-- it at http://valgrind.org/support/bug_reports.html.\n--1668-- WARNING: unhandled riscv64-linux syscall: 258\n--1668-- You may be able to write your own handler.\n--1668-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1668-- Nevertheless we consider this a bug. Please report\n--1668-- it at http://valgrind.org/support/bug_reports.html.\n--1668-- WARNING: unhandled riscv64-linux syscall: 258\n--1668-- You may be able to write your own handler.\n--1668-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1668-- Nevertheless we consider this a bug. Please report\n--1668-- it at http://valgrind.org/support/bug_reports.html.\n--1668-- WARNING: unhandled riscv64-linux syscall: 258\n--1668-- You may be able to write your own handler.\n--1668-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1668-- Nevertheless we consider this a bug. Please report\n--1668-- it at http://valgrind.org/support/bug_reports.html.\n--1668-- WARNING: unhandled riscv64-linux syscall: 258\n--1668-- You may be able to write your own handler.\n--1668-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1668-- Nevertheless we consider this a bug. Please report\n--1668-- it at http://valgrind.org/support/bug_reports.html.\n--1668-- WARNING: unhandled riscv64-linux syscall: 258\n--1668-- You may be able to write your own handler.\n--1668-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1668-- Nevertheless we consider this a bug. Please report\n--1668-- it at http://valgrind.org/support/bug_reports.html.\n--1668-- WARNING: unhandled riscv64-linux syscall: 258\n--1668-- You may be able to write your own handler.\n--1668-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1668-- Nevertheless we consider this a bug. Please report\n--1668-- it at http://valgrind.org/support/bug_reports.html.\n--1668-- WARNING: unhandled riscv64-linux syscall: 258\n--1668-- You may be able to write your own handler.\n--1668-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1668-- Nevertheless we consider this a bug. Please report\n--1668-- it at http://valgrind.org/support/bug_reports.html.\n--1668-- WARNING: unhandled riscv64-linux syscall: 258\n--1668-- You may be able to write your own handler.\n--1668-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1668-- Nevertheless we consider this a bug. Please report\n--1668-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 51: failed --url https://curl.se/hello --set query:=user=me --- stdout --- expected: 'https://curl.se/hello?user=me\n' got: 'https://curl.se/hello?user=me\n' --- stderr --- expected: '' got: '--1676-- WARNING: unhandled riscv64-linux syscall: 258\n--1676-- You may be able to write your own handler.\n--1676-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1676-- Nevertheless we consider this a bug. Please report\n--1676-- it at http://valgrind.org/support/bug_reports.html.\n--1676-- WARNING: unhandled riscv64-linux syscall: 258\n--1676-- You may be able to write your own handler.\n--1676-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1676-- Nevertheless we consider this a bug. Please report\n--1676-- it at http://valgrind.org/support/bug_reports.html.\n--1676-- WARNING: unhandled riscv64-linux syscall: 258\n--1676-- You may be able to write your own handler.\n--1676-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1676-- Nevertheless we consider this a bug. Please report\n--1676-- it at http://valgrind.org/support/bug_reports.html.\n--1676-- WARNING: unhandled riscv64-linux syscall: 258\n--1676-- You may be able to write your own handler.\n--1676-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1676-- Nevertheless we consider this a bug. Please report\n--1676-- it at http://valgrind.org/support/bug_reports.html.\n--1676-- WARNING: unhandled riscv64-linux syscall: 258\n--1676-- You may be able to write your own handler.\n--1676-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1676-- Nevertheless we consider this a bug. Please report\n--1676-- it at http://valgrind.org/support/bug_reports.html.\n--1676-- WARNING: unhandled riscv64-linux syscall: 258\n--1676-- You may be able to write your own handler.\n--1676-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1676-- Nevertheless we consider this a bug. Please report\n--1676-- it at http://valgrind.org/support/bug_reports.html.\n--1676-- WARNING: unhandled riscv64-linux syscall: 258\n--1676-- You may be able to write your own handler.\n--1676-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1676-- Nevertheless we consider this a bug. Please report\n--1676-- it at http://valgrind.org/support/bug_reports.html.\n--1676-- WARNING: unhandled riscv64-linux syscall: 258\n--1676-- You may be able to write your own handler.\n--1676-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1676-- Nevertheless we consider this a bug. Please report\n--1676-- it at http://valgrind.org/support/bug_reports.html.\n--1676-- WARNING: unhandled riscv64-linux syscall: 258\n--1676-- You may be able to write your own handler.\n--1676-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1676-- Nevertheless we consider this a bug. Please report\n--1676-- it at http://valgrind.org/support/bug_reports.html.\n--1676-- WARNING: unhandled riscv64-linux syscall: 258\n--1676-- You may be able to write your own handler.\n--1676-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1676-- Nevertheless we consider this a bug. Please report\n--1676-- it at http://valgrind.org/support/bug_reports.html.\n--1676-- WARNING: unhandled riscv64-linux syscall: 258\n--1676-- You may be able to write your own handler.\n--1676-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1676-- Nevertheless we consider this a bug. Please report\n--1676-- it at http://valgrind.org/support/bug_reports.html.\n--1676-- WARNING: unhandled riscv64-linux syscall: 258\n--1676-- You may be able to write your own handler.\n--1676-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1676-- Nevertheless we consider this a bug. Please report\n--1676-- it at http://valgrind.org/support/bug_reports.html.\n--1676-- WARNING: unhandled riscv64-linux syscall: 258\n--1676-- You may be able to write your own handler.\n--1676-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1676-- Nevertheless we consider this a bug. Please report\n--1676-- it at http://valgrind.org/support/bug_reports.html.\n--1676-- WARNING: unhandled riscv64-linux syscall: 258\n--1676-- You may be able to write your own handler.\n--1676-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1676-- Nevertheless we consider this a bug. Please report\n--1676-- it at http://valgrind.org/support/bug_reports.html.\n--1676-- WARNING: unhandled riscv64-linux syscall: 258\n--1676-- You may be able to write your own handler.\n--1676-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1676-- Nevertheless we consider this a bug. Please report\n--1676-- it at http://valgrind.org/support/bug_reports.html.\n--1676-- WARNING: unhandled riscv64-linux syscall: 258\n--1676-- You may be able to write your own handler.\n--1676-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1676-- Nevertheless we consider this a bug. Please report\n--1676-- it at http://valgrind.org/support/bug_reports.html.\n--1676-- WARNING: unhandled riscv64-linux syscall: 258\n--1676-- You may be able to write your own handler.\n--1676-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1676-- Nevertheless we consider this a bug. Please report\n--1676-- it at http://valgrind.org/support/bug_reports.html.\n--1676-- WARNING: unhandled riscv64-linux syscall: 258\n--1676-- You may be able to write your own handler.\n--1676-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1676-- Nevertheless we consider this a bug. Please report\n--1676-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 52: failed --url https://curl.se/hello --set query=user=me --- stdout --- expected: 'https://curl.se/hello?user%3dme\n' got: 'https://curl.se/hello?user%3dme\n' --- stderr --- expected: '' got: '--1684-- WARNING: unhandled riscv64-linux syscall: 258\n--1684-- You may be able to write your own handler.\n--1684-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1684-- Nevertheless we consider this a bug. Please report\n--1684-- it at http://valgrind.org/support/bug_reports.html.\n--1684-- WARNING: unhandled riscv64-linux syscall: 258\n--1684-- You may be able to write your own handler.\n--1684-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1684-- Nevertheless we consider this a bug. Please report\n--1684-- it at http://valgrind.org/support/bug_reports.html.\n--1684-- WARNING: unhandled riscv64-linux syscall: 258\n--1684-- You may be able to write your own handler.\n--1684-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1684-- Nevertheless we consider this a bug. Please report\n--1684-- it at http://valgrind.org/support/bug_reports.html.\n--1684-- WARNING: unhandled riscv64-linux syscall: 258\n--1684-- You may be able to write your own handler.\n--1684-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1684-- Nevertheless we consider this a bug. Please report\n--1684-- it at http://valgrind.org/support/bug_reports.html.\n--1684-- WARNING: unhandled riscv64-linux syscall: 258\n--1684-- You may be able to write your own handler.\n--1684-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1684-- Nevertheless we consider this a bug. Please report\n--1684-- it at http://valgrind.org/support/bug_reports.html.\n--1684-- WARNING: unhandled riscv64-linux syscall: 258\n--1684-- You may be able to write your own handler.\n--1684-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1684-- Nevertheless we consider this a bug. Please report\n--1684-- it at http://valgrind.org/support/bug_reports.html.\n--1684-- WARNING: unhandled riscv64-linux syscall: 258\n--1684-- You may be able to write your own handler.\n--1684-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1684-- Nevertheless we consider this a bug. Please report\n--1684-- it at http://valgrind.org/support/bug_reports.html.\n--1684-- WARNING: unhandled riscv64-linux syscall: 258\n--1684-- You may be able to write your own handler.\n--1684-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1684-- Nevertheless we consider this a bug. Please report\n--1684-- it at http://valgrind.org/support/bug_reports.html.\n--1684-- WARNING: unhandled riscv64-linux syscall: 258\n--1684-- You may be able to write your own handler.\n--1684-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1684-- Nevertheless we consider this a bug. Please report\n--1684-- it at http://valgrind.org/support/bug_reports.html.\n--1684-- WARNING: unhandled riscv64-linux syscall: 258\n--1684-- You may be able to write your own handler.\n--1684-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1684-- Nevertheless we consider this a bug. Please report\n--1684-- it at http://valgrind.org/support/bug_reports.html.\n--1684-- WARNING: unhandled riscv64-linux syscall: 258\n--1684-- You may be able to write your own handler.\n--1684-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1684-- Nevertheless we consider this a bug. Please report\n--1684-- it at http://valgrind.org/support/bug_reports.html.\n--1684-- WARNING: unhandled riscv64-linux syscall: 258\n--1684-- You may be able to write your own handler.\n--1684-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1684-- Nevertheless we consider this a bug. Please report\n--1684-- it at http://valgrind.org/support/bug_reports.html.\n--1684-- WARNING: unhandled riscv64-linux syscall: 258\n--1684-- You may be able to write your own handler.\n--1684-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1684-- Nevertheless we consider this a bug. Please report\n--1684-- it at http://valgrind.org/support/bug_reports.html.\n--1684-- WARNING: unhandled riscv64-linux syscall: 258\n--1684-- You may be able to write your own handler.\n--1684-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1684-- Nevertheless we consider this a bug. Please report\n--1684-- it at http://valgrind.org/support/bug_reports.html.\n--1684-- WARNING: unhandled riscv64-linux syscall: 258\n--1684-- You may be able to write your own handler.\n--1684-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1684-- Nevertheless we consider this a bug. Please report\n--1684-- it at http://valgrind.org/support/bug_reports.html.\n--1684-- WARNING: unhandled riscv64-linux syscall: 258\n--1684-- You may be able to write your own handler.\n--1684-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1684-- Nevertheless we consider this a bug. Please report\n--1684-- it at http://valgrind.org/support/bug_reports.html.\n--1684-- WARNING: unhandled riscv64-linux syscall: 258\n--1684-- You may be able to write your own handler.\n--1684-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1684-- Nevertheless we consider this a bug. Please report\n--1684-- it at http://valgrind.org/support/bug_reports.html.\n--1684-- WARNING: unhandled riscv64-linux syscall: 258\n--1684-- You may be able to write your own handler.\n--1684-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1684-- Nevertheless we consider this a bug. Please report\n--1684-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 53: failed --url https://curl.se/hello --set 'fragment= hello' --- stdout --- expected: 'https://curl.se/hello#%20hello\n' got: 'https://curl.se/hello#%20hello\n' --- stderr --- expected: '' got: '--1692-- WARNING: unhandled riscv64-linux syscall: 258\n--1692-- You may be able to write your own handler.\n--1692-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1692-- Nevertheless we consider this a bug. Please report\n--1692-- it at http://valgrind.org/support/bug_reports.html.\n--1692-- WARNING: unhandled riscv64-linux syscall: 258\n--1692-- You may be able to write your own handler.\n--1692-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1692-- Nevertheless we consider this a bug. Please report\n--1692-- it at http://valgrind.org/support/bug_reports.html.\n--1692-- WARNING: unhandled riscv64-linux syscall: 258\n--1692-- You may be able to write your own handler.\n--1692-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1692-- Nevertheless we consider this a bug. Please report\n--1692-- it at http://valgrind.org/support/bug_reports.html.\n--1692-- WARNING: unhandled riscv64-linux syscall: 258\n--1692-- You may be able to write your own handler.\n--1692-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1692-- Nevertheless we consider this a bug. Please report\n--1692-- it at http://valgrind.org/support/bug_reports.html.\n--1692-- WARNING: unhandled riscv64-linux syscall: 258\n--1692-- You may be able to write your own handler.\n--1692-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1692-- Nevertheless we consider this a bug. Please report\n--1692-- it at http://valgrind.org/support/bug_reports.html.\n--1692-- WARNING: unhandled riscv64-linux syscall: 258\n--1692-- You may be able to write your own handler.\n--1692-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1692-- Nevertheless we consider this a bug. Please report\n--1692-- it at http://valgrind.org/support/bug_reports.html.\n--1692-- WARNING: unhandled riscv64-linux syscall: 258\n--1692-- You may be able to write your own handler.\n--1692-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1692-- Nevertheless we consider this a bug. Please report\n--1692-- it at http://valgrind.org/support/bug_reports.html.\n--1692-- WARNING: unhandled riscv64-linux syscall: 258\n--1692-- You may be able to write your own handler.\n--1692-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1692-- Nevertheless we consider this a bug. Please report\n--1692-- it at http://valgrind.org/support/bug_reports.html.\n--1692-- WARNING: unhandled riscv64-linux syscall: 258\n--1692-- You may be able to write your own handler.\n--1692-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1692-- Nevertheless we consider this a bug. Please report\n--1692-- it at http://valgrind.org/support/bug_reports.html.\n--1692-- WARNING: unhandled riscv64-linux syscall: 258\n--1692-- You may be able to write your own handler.\n--1692-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1692-- Nevertheless we consider this a bug. Please report\n--1692-- it at http://valgrind.org/support/bug_reports.html.\n--1692-- WARNING: unhandled riscv64-linux syscall: 258\n--1692-- You may be able to write your own handler.\n--1692-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1692-- Nevertheless we consider this a bug. Please report\n--1692-- it at http://valgrind.org/support/bug_reports.html.\n--1692-- WARNING: unhandled riscv64-linux syscall: 258\n--1692-- You may be able to write your own handler.\n--1692-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1692-- Nevertheless we consider this a bug. Please report\n--1692-- it at http://valgrind.org/support/bug_reports.html.\n--1692-- WARNING: unhandled riscv64-linux syscall: 258\n--1692-- You may be able to write your own handler.\n--1692-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1692-- Nevertheless we consider this a bug. Please report\n--1692-- it at http://valgrind.org/support/bug_reports.html.\n--1692-- WARNING: unhandled riscv64-linux syscall: 258\n--1692-- You may be able to write your own handler.\n--1692-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1692-- Nevertheless we consider this a bug. Please report\n--1692-- it at http://valgrind.org/support/bug_reports.html.\n--1692-- WARNING: unhandled riscv64-linux syscall: 258\n--1692-- You may be able to write your own handler.\n--1692-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1692-- Nevertheless we consider this a bug. Please report\n--1692-- it at http://valgrind.org/support/bug_reports.html.\n--1692-- WARNING: unhandled riscv64-linux syscall: 258\n--1692-- You may be able to write your own handler.\n--1692-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1692-- Nevertheless we consider this a bug. Please report\n--1692-- it at http://valgrind.org/support/bug_reports.html.\n--1692-- WARNING: unhandled riscv64-linux syscall: 258\n--1692-- You may be able to write your own handler.\n--1692-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1692-- Nevertheless we consider this a bug. Please report\n--1692-- it at http://valgrind.org/support/bug_reports.html.\n--1692-- WARNING: unhandled riscv64-linux syscall: 258\n--1692-- You may be able to write your own handler.\n--1692-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1692-- Nevertheless we consider this a bug. Please report\n--1692-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 54: failed --url https://curl.se/hello --set fragment:=%20hello --- stdout --- expected: 'https://curl.se/hello#%20hello\n' got: 'https://curl.se/hello#%20hello\n' --- stderr --- expected: '' got: '--1700-- WARNING: unhandled riscv64-linux syscall: 258\n--1700-- You may be able to write your own handler.\n--1700-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1700-- Nevertheless we consider this a bug. Please report\n--1700-- it at http://valgrind.org/support/bug_reports.html.\n--1700-- WARNING: unhandled riscv64-linux syscall: 258\n--1700-- You may be able to write your own handler.\n--1700-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1700-- Nevertheless we consider this a bug. Please report\n--1700-- it at http://valgrind.org/support/bug_reports.html.\n--1700-- WARNING: unhandled riscv64-linux syscall: 258\n--1700-- You may be able to write your own handler.\n--1700-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1700-- Nevertheless we consider this a bug. Please report\n--1700-- it at http://valgrind.org/support/bug_reports.html.\n--1700-- WARNING: unhandled riscv64-linux syscall: 258\n--1700-- You may be able to write your own handler.\n--1700-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1700-- Nevertheless we consider this a bug. Please report\n--1700-- it at http://valgrind.org/support/bug_reports.html.\n--1700-- WARNING: unhandled riscv64-linux syscall: 258\n--1700-- You may be able to write your own handler.\n--1700-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1700-- Nevertheless we consider this a bug. Please report\n--1700-- it at http://valgrind.org/support/bug_reports.html.\n--1700-- WARNING: unhandled riscv64-linux syscall: 258\n--1700-- You may be able to write your own handler.\n--1700-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1700-- Nevertheless we consider this a bug. Please report\n--1700-- it at http://valgrind.org/support/bug_reports.html.\n--1700-- WARNING: unhandled riscv64-linux syscall: 258\n--1700-- You may be able to write your own handler.\n--1700-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1700-- Nevertheless we consider this a bug. Please report\n--1700-- it at http://valgrind.org/support/bug_reports.html.\n--1700-- WARNING: unhandled riscv64-linux syscall: 258\n--1700-- You may be able to write your own handler.\n--1700-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1700-- Nevertheless we consider this a bug. Please report\n--1700-- it at http://valgrind.org/support/bug_reports.html.\n--1700-- WARNING: unhandled riscv64-linux syscall: 258\n--1700-- You may be able to write your own handler.\n--1700-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1700-- Nevertheless we consider this a bug. Please report\n--1700-- it at http://valgrind.org/support/bug_reports.html.\n--1700-- WARNING: unhandled riscv64-linux syscall: 258\n--1700-- You may be able to write your own handler.\n--1700-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1700-- Nevertheless we consider this a bug. Please report\n--1700-- it at http://valgrind.org/support/bug_reports.html.\n--1700-- WARNING: unhandled riscv64-linux syscall: 258\n--1700-- You may be able to write your own handler.\n--1700-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1700-- Nevertheless we consider this a bug. Please report\n--1700-- it at http://valgrind.org/support/bug_reports.html.\n--1700-- WARNING: unhandled riscv64-linux syscall: 258\n--1700-- You may be able to write your own handler.\n--1700-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1700-- Nevertheless we consider this a bug. Please report\n--1700-- it at http://valgrind.org/support/bug_reports.html.\n--1700-- WARNING: unhandled riscv64-linux syscall: 258\n--1700-- You may be able to write your own handler.\n--1700-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1700-- Nevertheless we consider this a bug. Please report\n--1700-- it at http://valgrind.org/support/bug_reports.html.\n--1700-- WARNING: unhandled riscv64-linux syscall: 258\n--1700-- You may be able to write your own handler.\n--1700-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1700-- Nevertheless we consider this a bug. Please report\n--1700-- it at http://valgrind.org/support/bug_reports.html.\n--1700-- WARNING: unhandled riscv64-linux syscall: 258\n--1700-- You may be able to write your own handler.\n--1700-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1700-- Nevertheless we consider this a bug. Please report\n--1700-- it at http://valgrind.org/support/bug_reports.html.\n--1700-- WARNING: unhandled riscv64-linux syscall: 258\n--1700-- You may be able to write your own handler.\n--1700-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1700-- Nevertheless we consider this a bug. Please report\n--1700-- it at http://valgrind.org/support/bug_reports.html.\n--1700-- WARNING: unhandled riscv64-linux syscall: 258\n--1700-- You may be able to write your own handler.\n--1700-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1700-- Nevertheless we consider this a bug. Please report\n--1700-- it at http://valgrind.org/support/bug_reports.html.\n--1700-- WARNING: unhandled riscv64-linux syscall: 258\n--1700-- You may be able to write your own handler.\n--1700-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1700-- Nevertheless we consider this a bug. Please report\n--1700-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 55: failed localhost --append query=hello=foo --- stdout --- expected: 'http://localhost/?hello=foo\n' got: 'http://localhost/?hello=foo\n' --- stderr --- expected: '' got: '--1708-- WARNING: unhandled riscv64-linux syscall: 258\n--1708-- You may be able to write your own handler.\n--1708-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1708-- Nevertheless we consider this a bug. Please report\n--1708-- it at http://valgrind.org/support/bug_reports.html.\n--1708-- WARNING: unhandled riscv64-linux syscall: 258\n--1708-- You may be able to write your own handler.\n--1708-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1708-- Nevertheless we consider this a bug. Please report\n--1708-- it at http://valgrind.org/support/bug_reports.html.\n--1708-- WARNING: unhandled riscv64-linux syscall: 258\n--1708-- You may be able to write your own handler.\n--1708-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1708-- Nevertheless we consider this a bug. Please report\n--1708-- it at http://valgrind.org/support/bug_reports.html.\n--1708-- WARNING: unhandled riscv64-linux syscall: 258\n--1708-- You may be able to write your own handler.\n--1708-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1708-- Nevertheless we consider this a bug. Please report\n--1708-- it at http://valgrind.org/support/bug_reports.html.\n--1708-- WARNING: unhandled riscv64-linux syscall: 258\n--1708-- You may be able to write your own handler.\n--1708-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1708-- Nevertheless we consider this a bug. Please report\n--1708-- it at http://valgrind.org/support/bug_reports.html.\n--1708-- WARNING: unhandled riscv64-linux syscall: 258\n--1708-- You may be able to write your own handler.\n--1708-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1708-- Nevertheless we consider this a bug. Please report\n--1708-- it at http://valgrind.org/support/bug_reports.html.\n--1708-- WARNING: unhandled riscv64-linux syscall: 258\n--1708-- You may be able to write your own handler.\n--1708-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1708-- Nevertheless we consider this a bug. Please report\n--1708-- it at http://valgrind.org/support/bug_reports.html.\n--1708-- WARNING: unhandled riscv64-linux syscall: 258\n--1708-- You may be able to write your own handler.\n--1708-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1708-- Nevertheless we consider this a bug. Please report\n--1708-- it at http://valgrind.org/support/bug_reports.html.\n--1708-- WARNING: unhandled riscv64-linux syscall: 258\n--1708-- You may be able to write your own handler.\n--1708-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1708-- Nevertheless we consider this a bug. Please report\n--1708-- it at http://valgrind.org/support/bug_reports.html.\n--1708-- WARNING: unhandled riscv64-linux syscall: 258\n--1708-- You may be able to write your own handler.\n--1708-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1708-- Nevertheless we consider this a bug. Please report\n--1708-- it at http://valgrind.org/support/bug_reports.html.\n--1708-- WARNING: unhandled riscv64-linux syscall: 258\n--1708-- You may be able to write your own handler.\n--1708-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1708-- Nevertheless we consider this a bug. Please report\n--1708-- it at http://valgrind.org/support/bug_reports.html.\n--1708-- WARNING: unhandled riscv64-linux syscall: 258\n--1708-- You may be able to write your own handler.\n--1708-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1708-- Nevertheless we consider this a bug. Please report\n--1708-- it at http://valgrind.org/support/bug_reports.html.\n--1708-- WARNING: unhandled riscv64-linux syscall: 258\n--1708-- You may be able to write your own handler.\n--1708-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1708-- Nevertheless we consider this a bug. Please report\n--1708-- it at http://valgrind.org/support/bug_reports.html.\n--1708-- WARNING: unhandled riscv64-linux syscall: 258\n--1708-- You may be able to write your own handler.\n--1708-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1708-- Nevertheless we consider this a bug. Please report\n--1708-- it at http://valgrind.org/support/bug_reports.html.\n--1708-- WARNING: unhandled riscv64-linux syscall: 258\n--1708-- You may be able to write your own handler.\n--1708-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1708-- Nevertheless we consider this a bug. Please report\n--1708-- it at http://valgrind.org/support/bug_reports.html.\n--1708-- WARNING: unhandled riscv64-linux syscall: 258\n--1708-- You may be able to write your own handler.\n--1708-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1708-- Nevertheless we consider this a bug. Please report\n--1708-- it at http://valgrind.org/support/bug_reports.html.\n--1708-- WARNING: unhandled riscv64-linux syscall: 258\n--1708-- You may be able to write your own handler.\n--1708-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1708-- Nevertheless we consider this a bug. Please report\n--1708-- it at http://valgrind.org/support/bug_reports.html.\n--1708-- WARNING: unhandled riscv64-linux syscall: 258\n--1708-- You may be able to write your own handler.\n--1708-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1708-- Nevertheless we consider this a bug. Please report\n--1708-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 56: failed localhost -a query=hello=foo --- stdout --- expected: 'http://localhost/?hello=foo\n' got: 'http://localhost/?hello=foo\n' --- stderr --- expected: '' got: '--1716-- WARNING: unhandled riscv64-linux syscall: 258\n--1716-- You may be able to write your own handler.\n--1716-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1716-- Nevertheless we consider this a bug. Please report\n--1716-- it at http://valgrind.org/support/bug_reports.html.\n--1716-- WARNING: unhandled riscv64-linux syscall: 258\n--1716-- You may be able to write your own handler.\n--1716-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1716-- Nevertheless we consider this a bug. Please report\n--1716-- it at http://valgrind.org/support/bug_reports.html.\n--1716-- WARNING: unhandled riscv64-linux syscall: 258\n--1716-- You may be able to write your own handler.\n--1716-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1716-- Nevertheless we consider this a bug. Please report\n--1716-- it at http://valgrind.org/support/bug_reports.html.\n--1716-- WARNING: unhandled riscv64-linux syscall: 258\n--1716-- You may be able to write your own handler.\n--1716-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1716-- Nevertheless we consider this a bug. Please report\n--1716-- it at http://valgrind.org/support/bug_reports.html.\n--1716-- WARNING: unhandled riscv64-linux syscall: 258\n--1716-- You may be able to write your own handler.\n--1716-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1716-- Nevertheless we consider this a bug. Please report\n--1716-- it at http://valgrind.org/support/bug_reports.html.\n--1716-- WARNING: unhandled riscv64-linux syscall: 258\n--1716-- You may be able to write your own handler.\n--1716-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1716-- Nevertheless we consider this a bug. Please report\n--1716-- it at http://valgrind.org/support/bug_reports.html.\n--1716-- WARNING: unhandled riscv64-linux syscall: 258\n--1716-- You may be able to write your own handler.\n--1716-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1716-- Nevertheless we consider this a bug. Please report\n--1716-- it at http://valgrind.org/support/bug_reports.html.\n--1716-- WARNING: unhandled riscv64-linux syscall: 258\n--1716-- You may be able to write your own handler.\n--1716-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1716-- Nevertheless we consider this a bug. Please report\n--1716-- it at http://valgrind.org/support/bug_reports.html.\n--1716-- WARNING: unhandled riscv64-linux syscall: 258\n--1716-- You may be able to write your own handler.\n--1716-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1716-- Nevertheless we consider this a bug. Please report\n--1716-- it at http://valgrind.org/support/bug_reports.html.\n--1716-- WARNING: unhandled riscv64-linux syscall: 258\n--1716-- You may be able to write your own handler.\n--1716-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1716-- Nevertheless we consider this a bug. Please report\n--1716-- it at http://valgrind.org/support/bug_reports.html.\n--1716-- WARNING: unhandled riscv64-linux syscall: 258\n--1716-- You may be able to write your own handler.\n--1716-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1716-- Nevertheless we consider this a bug. Please report\n--1716-- it at http://valgrind.org/support/bug_reports.html.\n--1716-- WARNING: unhandled riscv64-linux syscall: 258\n--1716-- You may be able to write your own handler.\n--1716-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1716-- Nevertheless we consider this a bug. Please report\n--1716-- it at http://valgrind.org/support/bug_reports.html.\n--1716-- WARNING: unhandled riscv64-linux syscall: 258\n--1716-- You may be able to write your own handler.\n--1716-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1716-- Nevertheless we consider this a bug. Please report\n--1716-- it at http://valgrind.org/support/bug_reports.html.\n--1716-- WARNING: unhandled riscv64-linux syscall: 258\n--1716-- You may be able to write your own handler.\n--1716-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1716-- Nevertheless we consider this a bug. Please report\n--1716-- it at http://valgrind.org/support/bug_reports.html.\n--1716-- WARNING: unhandled riscv64-linux syscall: 258\n--1716-- You may be able to write your own handler.\n--1716-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1716-- Nevertheless we consider this a bug. Please report\n--1716-- it at http://valgrind.org/support/bug_reports.html.\n--1716-- WARNING: unhandled riscv64-linux syscall: 258\n--1716-- You may be able to write your own handler.\n--1716-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1716-- Nevertheless we consider this a bug. Please report\n--1716-- it at http://valgrind.org/support/bug_reports.html.\n--1716-- WARNING: unhandled riscv64-linux syscall: 258\n--1716-- You may be able to write your own handler.\n--1716-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1716-- Nevertheless we consider this a bug. Please report\n--1716-- it at http://valgrind.org/support/bug_reports.html.\n--1716-- WARNING: unhandled riscv64-linux syscall: 258\n--1716-- You may be able to write your own handler.\n--1716-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1716-- Nevertheless we consider this a bug. Please report\n--1716-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 57: failed 'https://example.com?search=hello&utm_source=tracker' --trim 'query=utm_*' --- stdout --- expected: 'https://example.com/?search=hello\n' got: 'https://example.com/?search=hello\n' --- stderr --- expected: '' got: '--1724-- WARNING: unhandled riscv64-linux syscall: 258\n--1724-- You may be able to write your own handler.\n--1724-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1724-- Nevertheless we consider this a bug. Please report\n--1724-- it at http://valgrind.org/support/bug_reports.html.\n--1724-- WARNING: unhandled riscv64-linux syscall: 258\n--1724-- You may be able to write your own handler.\n--1724-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1724-- Nevertheless we consider this a bug. Please report\n--1724-- it at http://valgrind.org/support/bug_reports.html.\n--1724-- WARNING: unhandled riscv64-linux syscall: 258\n--1724-- You may be able to write your own handler.\n--1724-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1724-- Nevertheless we consider this a bug. Please report\n--1724-- it at http://valgrind.org/support/bug_reports.html.\n--1724-- WARNING: unhandled riscv64-linux syscall: 258\n--1724-- You may be able to write your own handler.\n--1724-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1724-- Nevertheless we consider this a bug. Please report\n--1724-- it at http://valgrind.org/support/bug_reports.html.\n--1724-- WARNING: unhandled riscv64-linux syscall: 258\n--1724-- You may be able to write your own handler.\n--1724-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1724-- Nevertheless we consider this a bug. Please report\n--1724-- it at http://valgrind.org/support/bug_reports.html.\n--1724-- WARNING: unhandled riscv64-linux syscall: 258\n--1724-- You may be able to write your own handler.\n--1724-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1724-- Nevertheless we consider this a bug. Please report\n--1724-- it at http://valgrind.org/support/bug_reports.html.\n--1724-- WARNING: unhandled riscv64-linux syscall: 258\n--1724-- You may be able to write your own handler.\n--1724-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1724-- Nevertheless we consider this a bug. Please report\n--1724-- it at http://valgrind.org/support/bug_reports.html.\n--1724-- WARNING: unhandled riscv64-linux syscall: 258\n--1724-- You may be able to write your own handler.\n--1724-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1724-- Nevertheless we consider this a bug. Please report\n--1724-- it at http://valgrind.org/support/bug_reports.html.\n--1724-- WARNING: unhandled riscv64-linux syscall: 258\n--1724-- You may be able to write your own handler.\n--1724-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1724-- Nevertheless we consider this a bug. Please report\n--1724-- it at http://valgrind.org/support/bug_reports.html.\n--1724-- WARNING: unhandled riscv64-linux syscall: 258\n--1724-- You may be able to write your own handler.\n--1724-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1724-- Nevertheless we consider this a bug. Please report\n--1724-- it at http://valgrind.org/support/bug_reports.html.\n--1724-- WARNING: unhandled riscv64-linux syscall: 258\n--1724-- You may be able to write your own handler.\n--1724-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1724-- Nevertheless we consider this a bug. Please report\n--1724-- it at http://valgrind.org/support/bug_reports.html.\n--1724-- WARNING: unhandled riscv64-linux syscall: 258\n--1724-- You may be able to write your own handler.\n--1724-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1724-- Nevertheless we consider this a bug. Please report\n--1724-- it at http://valgrind.org/support/bug_reports.html.\n--1724-- WARNING: unhandled riscv64-linux syscall: 258\n--1724-- You may be able to write your own handler.\n--1724-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1724-- Nevertheless we consider this a bug. Please report\n--1724-- it at http://valgrind.org/support/bug_reports.html.\n--1724-- WARNING: unhandled riscv64-linux syscall: 258\n--1724-- You may be able to write your own handler.\n--1724-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1724-- Nevertheless we consider this a bug. Please report\n--1724-- it at http://valgrind.org/support/bug_reports.html.\n--1724-- WARNING: unhandled riscv64-linux syscall: 258\n--1724-- You may be able to write your own handler.\n--1724-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1724-- Nevertheless we consider this a bug. Please report\n--1724-- it at http://valgrind.org/support/bug_reports.html.\n--1724-- WARNING: unhandled riscv64-linux syscall: 258\n--1724-- You may be able to write your own handler.\n--1724-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1724-- Nevertheless we consider this a bug. Please report\n--1724-- it at http://valgrind.org/support/bug_reports.html.\n--1724-- WARNING: unhandled riscv64-linux syscall: 258\n--1724-- You may be able to write your own handler.\n--1724-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1724-- Nevertheless we consider this a bug. Please report\n--1724-- it at http://valgrind.org/support/bug_reports.html.\n--1724-- WARNING: unhandled riscv64-linux syscall: 258\n--1724-- You may be able to write your own handler.\n--1724-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1724-- Nevertheless we consider this a bug. Please report\n--1724-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 58: failed 'https://example.com?search=hello&utm_source=tracker' --qtrim 'utm_*' --- stdout --- expected: 'https://example.com/?search=hello\n' got: 'https://example.com/?search=hello\n' --- stderr --- expected: '' got: '--1732-- WARNING: unhandled riscv64-linux syscall: 258\n--1732-- You may be able to write your own handler.\n--1732-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1732-- Nevertheless we consider this a bug. Please report\n--1732-- it at http://valgrind.org/support/bug_reports.html.\n--1732-- WARNING: unhandled riscv64-linux syscall: 258\n--1732-- You may be able to write your own handler.\n--1732-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1732-- Nevertheless we consider this a bug. Please report\n--1732-- it at http://valgrind.org/support/bug_reports.html.\n--1732-- WARNING: unhandled riscv64-linux syscall: 258\n--1732-- You may be able to write your own handler.\n--1732-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1732-- Nevertheless we consider this a bug. Please report\n--1732-- it at http://valgrind.org/support/bug_reports.html.\n--1732-- WARNING: unhandled riscv64-linux syscall: 258\n--1732-- You may be able to write your own handler.\n--1732-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1732-- Nevertheless we consider this a bug. Please report\n--1732-- it at http://valgrind.org/support/bug_reports.html.\n--1732-- WARNING: unhandled riscv64-linux syscall: 258\n--1732-- You may be able to write your own handler.\n--1732-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1732-- Nevertheless we consider this a bug. Please report\n--1732-- it at http://valgrind.org/support/bug_reports.html.\n--1732-- WARNING: unhandled riscv64-linux syscall: 258\n--1732-- You may be able to write your own handler.\n--1732-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1732-- Nevertheless we consider this a bug. Please report\n--1732-- it at http://valgrind.org/support/bug_reports.html.\n--1732-- WARNING: unhandled riscv64-linux syscall: 258\n--1732-- You may be able to write your own handler.\n--1732-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1732-- Nevertheless we consider this a bug. Please report\n--1732-- it at http://valgrind.org/support/bug_reports.html.\n--1732-- WARNING: unhandled riscv64-linux syscall: 258\n--1732-- You may be able to write your own handler.\n--1732-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1732-- Nevertheless we consider this a bug. Please report\n--1732-- it at http://valgrind.org/support/bug_reports.html.\n--1732-- WARNING: unhandled riscv64-linux syscall: 258\n--1732-- You may be able to write your own handler.\n--1732-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1732-- Nevertheless we consider this a bug. Please report\n--1732-- it at http://valgrind.org/support/bug_reports.html.\n--1732-- WARNING: unhandled riscv64-linux syscall: 258\n--1732-- You may be able to write your own handler.\n--1732-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1732-- Nevertheless we consider this a bug. Please report\n--1732-- it at http://valgrind.org/support/bug_reports.html.\n--1732-- WARNING: unhandled riscv64-linux syscall: 258\n--1732-- You may be able to write your own handler.\n--1732-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1732-- Nevertheless we consider this a bug. Please report\n--1732-- it at http://valgrind.org/support/bug_reports.html.\n--1732-- WARNING: unhandled riscv64-linux syscall: 258\n--1732-- You may be able to write your own handler.\n--1732-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1732-- Nevertheless we consider this a bug. Please report\n--1732-- it at http://valgrind.org/support/bug_reports.html.\n--1732-- WARNING: unhandled riscv64-linux syscall: 258\n--1732-- You may be able to write your own handler.\n--1732-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1732-- Nevertheless we consider this a bug. Please report\n--1732-- it at http://valgrind.org/support/bug_reports.html.\n--1732-- WARNING: unhandled riscv64-linux syscall: 258\n--1732-- You may be able to write your own handler.\n--1732-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1732-- Nevertheless we consider this a bug. Please report\n--1732-- it at http://valgrind.org/support/bug_reports.html.\n--1732-- WARNING: unhandled riscv64-linux syscall: 258\n--1732-- You may be able to write your own handler.\n--1732-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1732-- Nevertheless we consider this a bug. Please report\n--1732-- it at http://valgrind.org/support/bug_reports.html.\n--1732-- WARNING: unhandled riscv64-linux syscall: 258\n--1732-- You may be able to write your own handler.\n--1732-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1732-- Nevertheless we consider this a bug. Please report\n--1732-- it at http://valgrind.org/support/bug_reports.html.\n--1732-- WARNING: unhandled riscv64-linux syscall: 258\n--1732-- You may be able to write your own handler.\n--1732-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1732-- Nevertheless we consider this a bug. Please report\n--1732-- it at http://valgrind.org/support/bug_reports.html.\n--1732-- WARNING: unhandled riscv64-linux syscall: 258\n--1732-- You may be able to write your own handler.\n--1732-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1732-- Nevertheless we consider this a bug. Please report\n--1732-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 59: 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: 'https://example.com/?search=hello&more=data\n' --- stderr --- expected: '' got: '--1740-- WARNING: unhandled riscv64-linux syscall: 258\n--1740-- You may be able to write your own handler.\n--1740-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1740-- Nevertheless we consider this a bug. Please report\n--1740-- it at http://valgrind.org/support/bug_reports.html.\n--1740-- WARNING: unhandled riscv64-linux syscall: 258\n--1740-- You may be able to write your own handler.\n--1740-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1740-- Nevertheless we consider this a bug. Please report\n--1740-- it at http://valgrind.org/support/bug_reports.html.\n--1740-- WARNING: unhandled riscv64-linux syscall: 258\n--1740-- You may be able to write your own handler.\n--1740-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1740-- Nevertheless we consider this a bug. Please report\n--1740-- it at http://valgrind.org/support/bug_reports.html.\n--1740-- WARNING: unhandled riscv64-linux syscall: 258\n--1740-- You may be able to write your own handler.\n--1740-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1740-- Nevertheless we consider this a bug. Please report\n--1740-- it at http://valgrind.org/support/bug_reports.html.\n--1740-- WARNING: unhandled riscv64-linux syscall: 258\n--1740-- You may be able to write your own handler.\n--1740-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1740-- Nevertheless we consider this a bug. Please report\n--1740-- it at http://valgrind.org/support/bug_reports.html.\n--1740-- WARNING: unhandled riscv64-linux syscall: 258\n--1740-- You may be able to write your own handler.\n--1740-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1740-- Nevertheless we consider this a bug. Please report\n--1740-- it at http://valgrind.org/support/bug_reports.html.\n--1740-- WARNING: unhandled riscv64-linux syscall: 258\n--1740-- You may be able to write your own handler.\n--1740-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1740-- Nevertheless we consider this a bug. Please report\n--1740-- it at http://valgrind.org/support/bug_reports.html.\n--1740-- WARNING: unhandled riscv64-linux syscall: 258\n--1740-- You may be able to write your own handler.\n--1740-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1740-- Nevertheless we consider this a bug. Please report\n--1740-- it at http://valgrind.org/support/bug_reports.html.\n--1740-- WARNING: unhandled riscv64-linux syscall: 258\n--1740-- You may be able to write your own handler.\n--1740-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1740-- Nevertheless we consider this a bug. Please report\n--1740-- it at http://valgrind.org/support/bug_reports.html.\n--1740-- WARNING: unhandled riscv64-linux syscall: 258\n--1740-- You may be able to write your own handler.\n--1740-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1740-- Nevertheless we consider this a bug. Please report\n--1740-- it at http://valgrind.org/support/bug_reports.html.\n--1740-- WARNING: unhandled riscv64-linux syscall: 258\n--1740-- You may be able to write your own handler.\n--1740-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1740-- Nevertheless we consider this a bug. Please report\n--1740-- it at http://valgrind.org/support/bug_reports.html.\n--1740-- WARNING: unhandled riscv64-linux syscall: 258\n--1740-- You may be able to write your own handler.\n--1740-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1740-- Nevertheless we consider this a bug. Please report\n--1740-- it at http://valgrind.org/support/bug_reports.html.\n--1740-- WARNING: unhandled riscv64-linux syscall: 258\n--1740-- You may be able to write your own handler.\n--1740-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1740-- Nevertheless we consider this a bug. Please report\n--1740-- it at http://valgrind.org/support/bug_reports.html.\n--1740-- WARNING: unhandled riscv64-linux syscall: 258\n--1740-- You may be able to write your own handler.\n--1740-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1740-- Nevertheless we consider this a bug. Please report\n--1740-- it at http://valgrind.org/support/bug_reports.html.\n--1740-- WARNING: unhandled riscv64-linux syscall: 258\n--1740-- You may be able to write your own handler.\n--1740-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1740-- Nevertheless we consider this a bug. Please report\n--1740-- it at http://valgrind.org/support/bug_reports.html.\n--1740-- WARNING: unhandled riscv64-linux syscall: 258\n--1740-- You may be able to write your own handler.\n--1740-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1740-- Nevertheless we consider this a bug. Please report\n--1740-- it at http://valgrind.org/support/bug_reports.html.\n--1740-- WARNING: unhandled riscv64-linux syscall: 258\n--1740-- You may be able to write your own handler.\n--1740-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1740-- Nevertheless we consider this a bug. Please report\n--1740-- it at http://valgrind.org/support/bug_reports.html.\n--1740-- WARNING: unhandled riscv64-linux syscall: 258\n--1740-- You may be able to write your own handler.\n--1740-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1740-- Nevertheless we consider this a bug. Please report\n--1740-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 60: failed 'https://example.com?search=hello&utm_source=tracker&more=data' --qtrim 'utm_*' --- stdout --- expected: 'https://example.com/?search=hello&more=data\n' got: 'https://example.com/?search=hello&more=data\n' --- stderr --- expected: '' got: '--1748-- WARNING: unhandled riscv64-linux syscall: 258\n--1748-- You may be able to write your own handler.\n--1748-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1748-- Nevertheless we consider this a bug. Please report\n--1748-- it at http://valgrind.org/support/bug_reports.html.\n--1748-- WARNING: unhandled riscv64-linux syscall: 258\n--1748-- You may be able to write your own handler.\n--1748-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1748-- Nevertheless we consider this a bug. Please report\n--1748-- it at http://valgrind.org/support/bug_reports.html.\n--1748-- WARNING: unhandled riscv64-linux syscall: 258\n--1748-- You may be able to write your own handler.\n--1748-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1748-- Nevertheless we consider this a bug. Please report\n--1748-- it at http://valgrind.org/support/bug_reports.html.\n--1748-- WARNING: unhandled riscv64-linux syscall: 258\n--1748-- You may be able to write your own handler.\n--1748-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1748-- Nevertheless we consider this a bug. Please report\n--1748-- it at http://valgrind.org/support/bug_reports.html.\n--1748-- WARNING: unhandled riscv64-linux syscall: 258\n--1748-- You may be able to write your own handler.\n--1748-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1748-- Nevertheless we consider this a bug. Please report\n--1748-- it at http://valgrind.org/support/bug_reports.html.\n--1748-- WARNING: unhandled riscv64-linux syscall: 258\n--1748-- You may be able to write your own handler.\n--1748-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1748-- Nevertheless we consider this a bug. Please report\n--1748-- it at http://valgrind.org/support/bug_reports.html.\n--1748-- WARNING: unhandled riscv64-linux syscall: 258\n--1748-- You may be able to write your own handler.\n--1748-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1748-- Nevertheless we consider this a bug. Please report\n--1748-- it at http://valgrind.org/support/bug_reports.html.\n--1748-- WARNING: unhandled riscv64-linux syscall: 258\n--1748-- You may be able to write your own handler.\n--1748-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1748-- Nevertheless we consider this a bug. Please report\n--1748-- it at http://valgrind.org/support/bug_reports.html.\n--1748-- WARNING: unhandled riscv64-linux syscall: 258\n--1748-- You may be able to write your own handler.\n--1748-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1748-- Nevertheless we consider this a bug. Please report\n--1748-- it at http://valgrind.org/support/bug_reports.html.\n--1748-- WARNING: unhandled riscv64-linux syscall: 258\n--1748-- You may be able to write your own handler.\n--1748-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1748-- Nevertheless we consider this a bug. Please report\n--1748-- it at http://valgrind.org/support/bug_reports.html.\n--1748-- WARNING: unhandled riscv64-linux syscall: 258\n--1748-- You may be able to write your own handler.\n--1748-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1748-- Nevertheless we consider this a bug. Please report\n--1748-- it at http://valgrind.org/support/bug_reports.html.\n--1748-- WARNING: unhandled riscv64-linux syscall: 258\n--1748-- You may be able to write your own handler.\n--1748-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1748-- Nevertheless we consider this a bug. Please report\n--1748-- it at http://valgrind.org/support/bug_reports.html.\n--1748-- WARNING: unhandled riscv64-linux syscall: 258\n--1748-- You may be able to write your own handler.\n--1748-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1748-- Nevertheless we consider this a bug. Please report\n--1748-- it at http://valgrind.org/support/bug_reports.html.\n--1748-- WARNING: unhandled riscv64-linux syscall: 258\n--1748-- You may be able to write your own handler.\n--1748-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1748-- Nevertheless we consider this a bug. Please report\n--1748-- it at http://valgrind.org/support/bug_reports.html.\n--1748-- WARNING: unhandled riscv64-linux syscall: 258\n--1748-- You may be able to write your own handler.\n--1748-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1748-- Nevertheless we consider this a bug. Please report\n--1748-- it at http://valgrind.org/support/bug_reports.html.\n--1748-- WARNING: unhandled riscv64-linux syscall: 258\n--1748-- You may be able to write your own handler.\n--1748-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1748-- Nevertheless we consider this a bug. Please report\n--1748-- it at http://valgrind.org/support/bug_reports.html.\n--1748-- WARNING: unhandled riscv64-linux syscall: 258\n--1748-- You may be able to write your own handler.\n--1748-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1748-- Nevertheless we consider this a bug. Please report\n--1748-- it at http://valgrind.org/support/bug_reports.html.\n--1748-- WARNING: unhandled riscv64-linux syscall: 258\n--1748-- You may be able to write your own handler.\n--1748-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1748-- Nevertheless we consider this a bug. Please report\n--1748-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 61: failed 'https://example.com?search=hello&more=data' --qtrim 'utm_*' --- stdout --- expected: 'https://example.com/?search=hello&more=data\n' got: 'https://example.com/?search=hello&more=data\n' --- stderr --- expected: '' got: '--1756-- WARNING: unhandled riscv64-linux syscall: 258\n--1756-- You may be able to write your own handler.\n--1756-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1756-- Nevertheless we consider this a bug. Please report\n--1756-- it at http://valgrind.org/support/bug_reports.html.\n--1756-- WARNING: unhandled riscv64-linux syscall: 258\n--1756-- You may be able to write your own handler.\n--1756-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1756-- Nevertheless we consider this a bug. Please report\n--1756-- it at http://valgrind.org/support/bug_reports.html.\n--1756-- WARNING: unhandled riscv64-linux syscall: 258\n--1756-- You may be able to write your own handler.\n--1756-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1756-- Nevertheless we consider this a bug. Please report\n--1756-- it at http://valgrind.org/support/bug_reports.html.\n--1756-- WARNING: unhandled riscv64-linux syscall: 258\n--1756-- You may be able to write your own handler.\n--1756-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1756-- Nevertheless we consider this a bug. Please report\n--1756-- it at http://valgrind.org/support/bug_reports.html.\n--1756-- WARNING: unhandled riscv64-linux syscall: 258\n--1756-- You may be able to write your own handler.\n--1756-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1756-- Nevertheless we consider this a bug. Please report\n--1756-- it at http://valgrind.org/support/bug_reports.html.\n--1756-- WARNING: unhandled riscv64-linux syscall: 258\n--1756-- You may be able to write your own handler.\n--1756-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1756-- Nevertheless we consider this a bug. Please report\n--1756-- it at http://valgrind.org/support/bug_reports.html.\n--1756-- WARNING: unhandled riscv64-linux syscall: 258\n--1756-- You may be able to write your own handler.\n--1756-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1756-- Nevertheless we consider this a bug. Please report\n--1756-- it at http://valgrind.org/support/bug_reports.html.\n--1756-- WARNING: unhandled riscv64-linux syscall: 258\n--1756-- You may be able to write your own handler.\n--1756-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1756-- Nevertheless we consider this a bug. Please report\n--1756-- it at http://valgrind.org/support/bug_reports.html.\n--1756-- WARNING: unhandled riscv64-linux syscall: 258\n--1756-- You may be able to write your own handler.\n--1756-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1756-- Nevertheless we consider this a bug. Please report\n--1756-- it at http://valgrind.org/support/bug_reports.html.\n--1756-- WARNING: unhandled riscv64-linux syscall: 258\n--1756-- You may be able to write your own handler.\n--1756-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1756-- Nevertheless we consider this a bug. Please report\n--1756-- it at http://valgrind.org/support/bug_reports.html.\n--1756-- WARNING: unhandled riscv64-linux syscall: 258\n--1756-- You may be able to write your own handler.\n--1756-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1756-- Nevertheless we consider this a bug. Please report\n--1756-- it at http://valgrind.org/support/bug_reports.html.\n--1756-- WARNING: unhandled riscv64-linux syscall: 258\n--1756-- You may be able to write your own handler.\n--1756-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1756-- Nevertheless we consider this a bug. Please report\n--1756-- it at http://valgrind.org/support/bug_reports.html.\n--1756-- WARNING: unhandled riscv64-linux syscall: 258\n--1756-- You may be able to write your own handler.\n--1756-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1756-- Nevertheless we consider this a bug. Please report\n--1756-- it at http://valgrind.org/support/bug_reports.html.\n--1756-- WARNING: unhandled riscv64-linux syscall: 258\n--1756-- You may be able to write your own handler.\n--1756-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1756-- Nevertheless we consider this a bug. Please report\n--1756-- it at http://valgrind.org/support/bug_reports.html.\n--1756-- WARNING: unhandled riscv64-linux syscall: 258\n--1756-- You may be able to write your own handler.\n--1756-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1756-- Nevertheless we consider this a bug. Please report\n--1756-- it at http://valgrind.org/support/bug_reports.html.\n--1756-- WARNING: unhandled riscv64-linux syscall: 258\n--1756-- You may be able to write your own handler.\n--1756-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1756-- Nevertheless we consider this a bug. Please report\n--1756-- it at http://valgrind.org/support/bug_reports.html.\n--1756-- WARNING: unhandled riscv64-linux syscall: 258\n--1756-- You may be able to write your own handler.\n--1756-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1756-- Nevertheless we consider this a bug. Please report\n--1756-- it at http://valgrind.org/support/bug_reports.html.\n--1756-- WARNING: unhandled riscv64-linux syscall: 258\n--1756-- You may be able to write your own handler.\n--1756-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1756-- Nevertheless we consider this a bug. Please report\n--1756-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 62: failed 'https://example.com?utm_source=tracker' --trim 'query=utm_*' --- stdout --- expected: 'https://example.com/\n' got: 'https://example.com/\n' --- stderr --- expected: '' got: '--1764-- WARNING: unhandled riscv64-linux syscall: 258\n--1764-- You may be able to write your own handler.\n--1764-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1764-- Nevertheless we consider this a bug. Please report\n--1764-- it at http://valgrind.org/support/bug_reports.html.\n--1764-- WARNING: unhandled riscv64-linux syscall: 258\n--1764-- You may be able to write your own handler.\n--1764-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1764-- Nevertheless we consider this a bug. Please report\n--1764-- it at http://valgrind.org/support/bug_reports.html.\n--1764-- WARNING: unhandled riscv64-linux syscall: 258\n--1764-- You may be able to write your own handler.\n--1764-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1764-- Nevertheless we consider this a bug. Please report\n--1764-- it at http://valgrind.org/support/bug_reports.html.\n--1764-- WARNING: unhandled riscv64-linux syscall: 258\n--1764-- You may be able to write your own handler.\n--1764-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1764-- Nevertheless we consider this a bug. Please report\n--1764-- it at http://valgrind.org/support/bug_reports.html.\n--1764-- WARNING: unhandled riscv64-linux syscall: 258\n--1764-- You may be able to write your own handler.\n--1764-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1764-- Nevertheless we consider this a bug. Please report\n--1764-- it at http://valgrind.org/support/bug_reports.html.\n--1764-- WARNING: unhandled riscv64-linux syscall: 258\n--1764-- You may be able to write your own handler.\n--1764-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1764-- Nevertheless we consider this a bug. Please report\n--1764-- it at http://valgrind.org/support/bug_reports.html.\n--1764-- WARNING: unhandled riscv64-linux syscall: 258\n--1764-- You may be able to write your own handler.\n--1764-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1764-- Nevertheless we consider this a bug. Please report\n--1764-- it at http://valgrind.org/support/bug_reports.html.\n--1764-- WARNING: unhandled riscv64-linux syscall: 258\n--1764-- You may be able to write your own handler.\n--1764-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1764-- Nevertheless we consider this a bug. Please report\n--1764-- it at http://valgrind.org/support/bug_reports.html.\n--1764-- WARNING: unhandled riscv64-linux syscall: 258\n--1764-- You may be able to write your own handler.\n--1764-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1764-- Nevertheless we consider this a bug. Please report\n--1764-- it at http://valgrind.org/support/bug_reports.html.\n--1764-- WARNING: unhandled riscv64-linux syscall: 258\n--1764-- You may be able to write your own handler.\n--1764-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1764-- Nevertheless we consider this a bug. Please report\n--1764-- it at http://valgrind.org/support/bug_reports.html.\n--1764-- WARNING: unhandled riscv64-linux syscall: 258\n--1764-- You may be able to write your own handler.\n--1764-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1764-- Nevertheless we consider this a bug. Please report\n--1764-- it at http://valgrind.org/support/bug_reports.html.\n--1764-- WARNING: unhandled riscv64-linux syscall: 258\n--1764-- You may be able to write your own handler.\n--1764-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1764-- Nevertheless we consider this a bug. Please report\n--1764-- it at http://valgrind.org/support/bug_reports.html.\n--1764-- WARNING: unhandled riscv64-linux syscall: 258\n--1764-- You may be able to write your own handler.\n--1764-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1764-- Nevertheless we consider this a bug. Please report\n--1764-- it at http://valgrind.org/support/bug_reports.html.\n--1764-- WARNING: unhandled riscv64-linux syscall: 258\n--1764-- You may be able to write your own handler.\n--1764-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1764-- Nevertheless we consider this a bug. Please report\n--1764-- it at http://valgrind.org/support/bug_reports.html.\n--1764-- WARNING: unhandled riscv64-linux syscall: 258\n--1764-- You may be able to write your own handler.\n--1764-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1764-- Nevertheless we consider this a bug. Please report\n--1764-- it at http://valgrind.org/support/bug_reports.html.\n--1764-- WARNING: unhandled riscv64-linux syscall: 258\n--1764-- You may be able to write your own handler.\n--1764-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1764-- Nevertheless we consider this a bug. Please report\n--1764-- it at http://valgrind.org/support/bug_reports.html.\n--1764-- WARNING: unhandled riscv64-linux syscall: 258\n--1764-- You may be able to write your own handler.\n--1764-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1764-- Nevertheless we consider this a bug. Please report\n--1764-- it at http://valgrind.org/support/bug_reports.html.\n--1764-- WARNING: unhandled riscv64-linux syscall: 258\n--1764-- You may be able to write your own handler.\n--1764-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1764-- Nevertheless we consider this a bug. Please report\n--1764-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 63: failed 'https://example.com?search=hello&utm_source=tracker&more=data' --qtrim utm_source --- stdout --- expected: 'https://example.com/?search=hello&more=data\n' got: 'https://example.com/?search=hello&more=data\n' --- stderr --- expected: '' got: '--1772-- WARNING: unhandled riscv64-linux syscall: 258\n--1772-- You may be able to write your own handler.\n--1772-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1772-- Nevertheless we consider this a bug. Please report\n--1772-- it at http://valgrind.org/support/bug_reports.html.\n--1772-- WARNING: unhandled riscv64-linux syscall: 258\n--1772-- You may be able to write your own handler.\n--1772-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1772-- Nevertheless we consider this a bug. Please report\n--1772-- it at http://valgrind.org/support/bug_reports.html.\n--1772-- WARNING: unhandled riscv64-linux syscall: 258\n--1772-- You may be able to write your own handler.\n--1772-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1772-- Nevertheless we consider this a bug. Please report\n--1772-- it at http://valgrind.org/support/bug_reports.html.\n--1772-- WARNING: unhandled riscv64-linux syscall: 258\n--1772-- You may be able to write your own handler.\n--1772-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1772-- Nevertheless we consider this a bug. Please report\n--1772-- it at http://valgrind.org/support/bug_reports.html.\n--1772-- WARNING: unhandled riscv64-linux syscall: 258\n--1772-- You may be able to write your own handler.\n--1772-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1772-- Nevertheless we consider this a bug. Please report\n--1772-- it at http://valgrind.org/support/bug_reports.html.\n--1772-- WARNING: unhandled riscv64-linux syscall: 258\n--1772-- You may be able to write your own handler.\n--1772-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1772-- Nevertheless we consider this a bug. Please report\n--1772-- it at http://valgrind.org/support/bug_reports.html.\n--1772-- WARNING: unhandled riscv64-linux syscall: 258\n--1772-- You may be able to write your own handler.\n--1772-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1772-- Nevertheless we consider this a bug. Please report\n--1772-- it at http://valgrind.org/support/bug_reports.html.\n--1772-- WARNING: unhandled riscv64-linux syscall: 258\n--1772-- You may be able to write your own handler.\n--1772-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1772-- Nevertheless we consider this a bug. Please report\n--1772-- it at http://valgrind.org/support/bug_reports.html.\n--1772-- WARNING: unhandled riscv64-linux syscall: 258\n--1772-- You may be able to write your own handler.\n--1772-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1772-- Nevertheless we consider this a bug. Please report\n--1772-- it at http://valgrind.org/support/bug_reports.html.\n--1772-- WARNING: unhandled riscv64-linux syscall: 258\n--1772-- You may be able to write your own handler.\n--1772-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1772-- Nevertheless we consider this a bug. Please report\n--1772-- it at http://valgrind.org/support/bug_reports.html.\n--1772-- WARNING: unhandled riscv64-linux syscall: 258\n--1772-- You may be able to write your own handler.\n--1772-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1772-- Nevertheless we consider this a bug. Please report\n--1772-- it at http://valgrind.org/support/bug_reports.html.\n--1772-- WARNING: unhandled riscv64-linux syscall: 258\n--1772-- You may be able to write your own handler.\n--1772-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1772-- Nevertheless we consider this a bug. Please report\n--1772-- it at http://valgrind.org/support/bug_reports.html.\n--1772-- WARNING: unhandled riscv64-linux syscall: 258\n--1772-- You may be able to write your own handler.\n--1772-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1772-- Nevertheless we consider this a bug. Please report\n--1772-- it at http://valgrind.org/support/bug_reports.html.\n--1772-- WARNING: unhandled riscv64-linux syscall: 258\n--1772-- You may be able to write your own handler.\n--1772-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1772-- Nevertheless we consider this a bug. Please report\n--1772-- it at http://valgrind.org/support/bug_reports.html.\n--1772-- WARNING: unhandled riscv64-linux syscall: 258\n--1772-- You may be able to write your own handler.\n--1772-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1772-- Nevertheless we consider this a bug. Please report\n--1772-- it at http://valgrind.org/support/bug_reports.html.\n--1772-- WARNING: unhandled riscv64-linux syscall: 258\n--1772-- You may be able to write your own handler.\n--1772-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1772-- Nevertheless we consider this a bug. Please report\n--1772-- it at http://valgrind.org/support/bug_reports.html.\n--1772-- WARNING: unhandled riscv64-linux syscall: 258\n--1772-- You may be able to write your own handler.\n--1772-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1772-- Nevertheless we consider this a bug. Please report\n--1772-- it at http://valgrind.org/support/bug_reports.html.\n--1772-- WARNING: unhandled riscv64-linux syscall: 258\n--1772-- You may be able to write your own handler.\n--1772-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1772-- Nevertheless we consider this a bug. Please report\n--1772-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 64: failed 'https://example.com?search=hello&utm_source=tracker&more=data' --qtrim utm_source --qtrim more --qtrim search --- stdout --- expected: 'https://example.com/\n' got: 'https://example.com/\n' --- stderr --- expected: '' got: '--1780-- WARNING: unhandled riscv64-linux syscall: 258\n--1780-- You may be able to write your own handler.\n--1780-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1780-- Nevertheless we consider this a bug. Please report\n--1780-- it at http://valgrind.org/support/bug_reports.html.\n--1780-- WARNING: unhandled riscv64-linux syscall: 258\n--1780-- You may be able to write your own handler.\n--1780-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1780-- Nevertheless we consider this a bug. Please report\n--1780-- it at http://valgrind.org/support/bug_reports.html.\n--1780-- WARNING: unhandled riscv64-linux syscall: 258\n--1780-- You may be able to write your own handler.\n--1780-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1780-- Nevertheless we consider this a bug. Please report\n--1780-- it at http://valgrind.org/support/bug_reports.html.\n--1780-- WARNING: unhandled riscv64-linux syscall: 258\n--1780-- You may be able to write your own handler.\n--1780-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1780-- Nevertheless we consider this a bug. Please report\n--1780-- it at http://valgrind.org/support/bug_reports.html.\n--1780-- WARNING: unhandled riscv64-linux syscall: 258\n--1780-- You may be able to write your own handler.\n--1780-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1780-- Nevertheless we consider this a bug. Please report\n--1780-- it at http://valgrind.org/support/bug_reports.html.\n--1780-- WARNING: unhandled riscv64-linux syscall: 258\n--1780-- You may be able to write your own handler.\n--1780-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1780-- Nevertheless we consider this a bug. Please report\n--1780-- it at http://valgrind.org/support/bug_reports.html.\n--1780-- WARNING: unhandled riscv64-linux syscall: 258\n--1780-- You may be able to write your own handler.\n--1780-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1780-- Nevertheless we consider this a bug. Please report\n--1780-- it at http://valgrind.org/support/bug_reports.html.\n--1780-- WARNING: unhandled riscv64-linux syscall: 258\n--1780-- You may be able to write your own handler.\n--1780-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1780-- Nevertheless we consider this a bug. Please report\n--1780-- it at http://valgrind.org/support/bug_reports.html.\n--1780-- WARNING: unhandled riscv64-linux syscall: 258\n--1780-- You may be able to write your own handler.\n--1780-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1780-- Nevertheless we consider this a bug. Please report\n--1780-- it at http://valgrind.org/support/bug_reports.html.\n--1780-- WARNING: unhandled riscv64-linux syscall: 258\n--1780-- You may be able to write your own handler.\n--1780-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1780-- Nevertheless we consider this a bug. Please report\n--1780-- it at http://valgrind.org/support/bug_reports.html.\n--1780-- WARNING: unhandled riscv64-linux syscall: 258\n--1780-- You may be able to write your own handler.\n--1780-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1780-- Nevertheless we consider this a bug. Please report\n--1780-- it at http://valgrind.org/support/bug_reports.html.\n--1780-- WARNING: unhandled riscv64-linux syscall: 258\n--1780-- You may be able to write your own handler.\n--1780-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1780-- Nevertheless we consider this a bug. Please report\n--1780-- it at http://valgrind.org/support/bug_reports.html.\n--1780-- WARNING: unhandled riscv64-linux syscall: 258\n--1780-- You may be able to write your own handler.\n--1780-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1780-- Nevertheless we consider this a bug. Please report\n--1780-- it at http://valgrind.org/support/bug_reports.html.\n--1780-- WARNING: unhandled riscv64-linux syscall: 258\n--1780-- You may be able to write your own handler.\n--1780-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1780-- Nevertheless we consider this a bug. Please report\n--1780-- it at http://valgrind.org/support/bug_reports.html.\n--1780-- WARNING: unhandled riscv64-linux syscall: 258\n--1780-- You may be able to write your own handler.\n--1780-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1780-- Nevertheless we consider this a bug. Please report\n--1780-- it at http://valgrind.org/support/bug_reports.html.\n--1780-- WARNING: unhandled riscv64-linux syscall: 258\n--1780-- You may be able to write your own handler.\n--1780-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1780-- Nevertheless we consider this a bug. Please report\n--1780-- it at http://valgrind.org/support/bug_reports.html.\n--1780-- WARNING: unhandled riscv64-linux syscall: 258\n--1780-- You may be able to write your own handler.\n--1780-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1780-- Nevertheless we consider this a bug. Please report\n--1780-- it at http://valgrind.org/support/bug_reports.html.\n--1780-- WARNING: unhandled riscv64-linux syscall: 258\n--1780-- You may be able to write your own handler.\n--1780-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1780-- Nevertheless we consider this a bug. Please report\n--1780-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 65: failed --accept-space --url 'gopher://localhost/ with space' --- stdout --- expected: 'gopher://localhost/%20with%20space\n' got: 'gopher://localhost/%20with%20space\n' --- stderr --- expected: '' got: '--1788-- WARNING: unhandled riscv64-linux syscall: 258\n--1788-- You may be able to write your own handler.\n--1788-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1788-- Nevertheless we consider this a bug. Please report\n--1788-- it at http://valgrind.org/support/bug_reports.html.\n--1788-- WARNING: unhandled riscv64-linux syscall: 258\n--1788-- You may be able to write your own handler.\n--1788-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1788-- Nevertheless we consider this a bug. Please report\n--1788-- it at http://valgrind.org/support/bug_reports.html.\n--1788-- WARNING: unhandled riscv64-linux syscall: 258\n--1788-- You may be able to write your own handler.\n--1788-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1788-- Nevertheless we consider this a bug. Please report\n--1788-- it at http://valgrind.org/support/bug_reports.html.\n--1788-- WARNING: unhandled riscv64-linux syscall: 258\n--1788-- You may be able to write your own handler.\n--1788-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1788-- Nevertheless we consider this a bug. Please report\n--1788-- it at http://valgrind.org/support/bug_reports.html.\n--1788-- WARNING: unhandled riscv64-linux syscall: 258\n--1788-- You may be able to write your own handler.\n--1788-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1788-- Nevertheless we consider this a bug. Please report\n--1788-- it at http://valgrind.org/support/bug_reports.html.\n--1788-- WARNING: unhandled riscv64-linux syscall: 258\n--1788-- You may be able to write your own handler.\n--1788-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1788-- Nevertheless we consider this a bug. Please report\n--1788-- it at http://valgrind.org/support/bug_reports.html.\n--1788-- WARNING: unhandled riscv64-linux syscall: 258\n--1788-- You may be able to write your own handler.\n--1788-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1788-- Nevertheless we consider this a bug. Please report\n--1788-- it at http://valgrind.org/support/bug_reports.html.\n--1788-- WARNING: unhandled riscv64-linux syscall: 258\n--1788-- You may be able to write your own handler.\n--1788-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1788-- Nevertheless we consider this a bug. Please report\n--1788-- it at http://valgrind.org/support/bug_reports.html.\n--1788-- WARNING: unhandled riscv64-linux syscall: 258\n--1788-- You may be able to write your own handler.\n--1788-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1788-- Nevertheless we consider this a bug. Please report\n--1788-- it at http://valgrind.org/support/bug_reports.html.\n--1788-- WARNING: unhandled riscv64-linux syscall: 258\n--1788-- You may be able to write your own handler.\n--1788-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1788-- Nevertheless we consider this a bug. Please report\n--1788-- it at http://valgrind.org/support/bug_reports.html.\n--1788-- WARNING: unhandled riscv64-linux syscall: 258\n--1788-- You may be able to write your own handler.\n--1788-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1788-- Nevertheless we consider this a bug. Please report\n--1788-- it at http://valgrind.org/support/bug_reports.html.\n--1788-- WARNING: unhandled riscv64-linux syscall: 258\n--1788-- You may be able to write your own handler.\n--1788-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1788-- Nevertheless we consider this a bug. Please report\n--1788-- it at http://valgrind.org/support/bug_reports.html.\n--1788-- WARNING: unhandled riscv64-linux syscall: 258\n--1788-- You may be able to write your own handler.\n--1788-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1788-- Nevertheless we consider this a bug. Please report\n--1788-- it at http://valgrind.org/support/bug_reports.html.\n--1788-- WARNING: unhandled riscv64-linux syscall: 258\n--1788-- You may be able to write your own handler.\n--1788-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1788-- Nevertheless we consider this a bug. Please report\n--1788-- it at http://valgrind.org/support/bug_reports.html.\n--1788-- WARNING: unhandled riscv64-linux syscall: 258\n--1788-- You may be able to write your own handler.\n--1788-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1788-- Nevertheless we consider this a bug. Please report\n--1788-- it at http://valgrind.org/support/bug_reports.html.\n--1788-- WARNING: unhandled riscv64-linux syscall: 258\n--1788-- You may be able to write your own handler.\n--1788-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1788-- Nevertheless we consider this a bug. Please report\n--1788-- it at http://valgrind.org/support/bug_reports.html.\n--1788-- WARNING: unhandled riscv64-linux syscall: 258\n--1788-- You may be able to write your own handler.\n--1788-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1788-- Nevertheless we consider this a bug. Please report\n--1788-- it at http://valgrind.org/support/bug_reports.html.\n--1788-- WARNING: unhandled riscv64-linux syscall: 258\n--1788-- You may be able to write your own handler.\n--1788-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1788-- Nevertheless we consider this a bug. Please report\n--1788-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 66: failed --accept-space --url 'https://localhost/?with space' --- stdout --- expected: 'https://localhost/?with+space\n' got: 'https://localhost/?with+space\n' --- stderr --- expected: '' got: '--1796-- WARNING: unhandled riscv64-linux syscall: 258\n--1796-- You may be able to write your own handler.\n--1796-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1796-- Nevertheless we consider this a bug. Please report\n--1796-- it at http://valgrind.org/support/bug_reports.html.\n--1796-- WARNING: unhandled riscv64-linux syscall: 258\n--1796-- You may be able to write your own handler.\n--1796-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1796-- Nevertheless we consider this a bug. Please report\n--1796-- it at http://valgrind.org/support/bug_reports.html.\n--1796-- WARNING: unhandled riscv64-linux syscall: 258\n--1796-- You may be able to write your own handler.\n--1796-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1796-- Nevertheless we consider this a bug. Please report\n--1796-- it at http://valgrind.org/support/bug_reports.html.\n--1796-- WARNING: unhandled riscv64-linux syscall: 258\n--1796-- You may be able to write your own handler.\n--1796-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1796-- Nevertheless we consider this a bug. Please report\n--1796-- it at http://valgrind.org/support/bug_reports.html.\n--1796-- WARNING: unhandled riscv64-linux syscall: 258\n--1796-- You may be able to write your own handler.\n--1796-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1796-- Nevertheless we consider this a bug. Please report\n--1796-- it at http://valgrind.org/support/bug_reports.html.\n--1796-- WARNING: unhandled riscv64-linux syscall: 258\n--1796-- You may be able to write your own handler.\n--1796-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1796-- Nevertheless we consider this a bug. Please report\n--1796-- it at http://valgrind.org/support/bug_reports.html.\n--1796-- WARNING: unhandled riscv64-linux syscall: 258\n--1796-- You may be able to write your own handler.\n--1796-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1796-- Nevertheless we consider this a bug. Please report\n--1796-- it at http://valgrind.org/support/bug_reports.html.\n--1796-- WARNING: unhandled riscv64-linux syscall: 258\n--1796-- You may be able to write your own handler.\n--1796-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1796-- Nevertheless we consider this a bug. Please report\n--1796-- it at http://valgrind.org/support/bug_reports.html.\n--1796-- WARNING: unhandled riscv64-linux syscall: 258\n--1796-- You may be able to write your own handler.\n--1796-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1796-- Nevertheless we consider this a bug. Please report\n--1796-- it at http://valgrind.org/support/bug_reports.html.\n--1796-- WARNING: unhandled riscv64-linux syscall: 258\n--1796-- You may be able to write your own handler.\n--1796-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1796-- Nevertheless we consider this a bug. Please report\n--1796-- it at http://valgrind.org/support/bug_reports.html.\n--1796-- WARNING: unhandled riscv64-linux syscall: 258\n--1796-- You may be able to write your own handler.\n--1796-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1796-- Nevertheless we consider this a bug. Please report\n--1796-- it at http://valgrind.org/support/bug_reports.html.\n--1796-- WARNING: unhandled riscv64-linux syscall: 258\n--1796-- You may be able to write your own handler.\n--1796-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1796-- Nevertheless we consider this a bug. Please report\n--1796-- it at http://valgrind.org/support/bug_reports.html.\n--1796-- WARNING: unhandled riscv64-linux syscall: 258\n--1796-- You may be able to write your own handler.\n--1796-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1796-- Nevertheless we consider this a bug. Please report\n--1796-- it at http://valgrind.org/support/bug_reports.html.\n--1796-- WARNING: unhandled riscv64-linux syscall: 258\n--1796-- You may be able to write your own handler.\n--1796-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1796-- Nevertheless we consider this a bug. Please report\n--1796-- it at http://valgrind.org/support/bug_reports.html.\n--1796-- WARNING: unhandled riscv64-linux syscall: 258\n--1796-- You may be able to write your own handler.\n--1796-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1796-- Nevertheless we consider this a bug. Please report\n--1796-- it at http://valgrind.org/support/bug_reports.html.\n--1796-- WARNING: unhandled riscv64-linux syscall: 258\n--1796-- You may be able to write your own handler.\n--1796-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1796-- Nevertheless we consider this a bug. Please report\n--1796-- it at http://valgrind.org/support/bug_reports.html.\n--1796-- WARNING: unhandled riscv64-linux syscall: 258\n--1796-- You may be able to write your own handler.\n--1796-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1796-- Nevertheless we consider this a bug. Please report\n--1796-- it at http://valgrind.org/support/bug_reports.html.\n--1796-- WARNING: unhandled riscv64-linux syscall: 258\n--1796-- You may be able to write your own handler.\n--1796-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1796-- Nevertheless we consider this a bug. Please report\n--1796-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 67: failed https://daniel@curl.se:22/ -s port= -s user= --- stdout --- expected: 'https://curl.se/\n' got: 'https://curl.se/\n' --- stderr --- expected: '' got: '--1804-- WARNING: unhandled riscv64-linux syscall: 258\n--1804-- You may be able to write your own handler.\n--1804-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1804-- Nevertheless we consider this a bug. Please report\n--1804-- it at http://valgrind.org/support/bug_reports.html.\n--1804-- WARNING: unhandled riscv64-linux syscall: 258\n--1804-- You may be able to write your own handler.\n--1804-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1804-- Nevertheless we consider this a bug. Please report\n--1804-- it at http://valgrind.org/support/bug_reports.html.\n--1804-- WARNING: unhandled riscv64-linux syscall: 258\n--1804-- You may be able to write your own handler.\n--1804-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1804-- Nevertheless we consider this a bug. Please report\n--1804-- it at http://valgrind.org/support/bug_reports.html.\n--1804-- WARNING: unhandled riscv64-linux syscall: 258\n--1804-- You may be able to write your own handler.\n--1804-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1804-- Nevertheless we consider this a bug. Please report\n--1804-- it at http://valgrind.org/support/bug_reports.html.\n--1804-- WARNING: unhandled riscv64-linux syscall: 258\n--1804-- You may be able to write your own handler.\n--1804-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1804-- Nevertheless we consider this a bug. Please report\n--1804-- it at http://valgrind.org/support/bug_reports.html.\n--1804-- WARNING: unhandled riscv64-linux syscall: 258\n--1804-- You may be able to write your own handler.\n--1804-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1804-- Nevertheless we consider this a bug. Please report\n--1804-- it at http://valgrind.org/support/bug_reports.html.\n--1804-- WARNING: unhandled riscv64-linux syscall: 258\n--1804-- You may be able to write your own handler.\n--1804-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1804-- Nevertheless we consider this a bug. Please report\n--1804-- it at http://valgrind.org/support/bug_reports.html.\n--1804-- WARNING: unhandled riscv64-linux syscall: 258\n--1804-- You may be able to write your own handler.\n--1804-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1804-- Nevertheless we consider this a bug. Please report\n--1804-- it at http://valgrind.org/support/bug_reports.html.\n--1804-- WARNING: unhandled riscv64-linux syscall: 258\n--1804-- You may be able to write your own handler.\n--1804-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1804-- Nevertheless we consider this a bug. Please report\n--1804-- it at http://valgrind.org/support/bug_reports.html.\n--1804-- WARNING: unhandled riscv64-linux syscall: 258\n--1804-- You may be able to write your own handler.\n--1804-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1804-- Nevertheless we consider this a bug. Please report\n--1804-- it at http://valgrind.org/support/bug_reports.html.\n--1804-- WARNING: unhandled riscv64-linux syscall: 258\n--1804-- You may be able to write your own handler.\n--1804-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1804-- Nevertheless we consider this a bug. Please report\n--1804-- it at http://valgrind.org/support/bug_reports.html.\n--1804-- WARNING: unhandled riscv64-linux syscall: 258\n--1804-- You may be able to write your own handler.\n--1804-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1804-- Nevertheless we consider this a bug. Please report\n--1804-- it at http://valgrind.org/support/bug_reports.html.\n--1804-- WARNING: unhandled riscv64-linux syscall: 258\n--1804-- You may be able to write your own handler.\n--1804-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1804-- Nevertheless we consider this a bug. Please report\n--1804-- it at http://valgrind.org/support/bug_reports.html.\n--1804-- WARNING: unhandled riscv64-linux syscall: 258\n--1804-- You may be able to write your own handler.\n--1804-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1804-- Nevertheless we consider this a bug. Please report\n--1804-- it at http://valgrind.org/support/bug_reports.html.\n--1804-- WARNING: unhandled riscv64-linux syscall: 258\n--1804-- You may be able to write your own handler.\n--1804-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1804-- Nevertheless we consider this a bug. Please report\n--1804-- it at http://valgrind.org/support/bug_reports.html.\n--1804-- WARNING: unhandled riscv64-linux syscall: 258\n--1804-- You may be able to write your own handler.\n--1804-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1804-- Nevertheless we consider this a bug. Please report\n--1804-- it at http://valgrind.org/support/bug_reports.html.\n--1804-- WARNING: unhandled riscv64-linux syscall: 258\n--1804-- You may be able to write your own handler.\n--1804-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1804-- Nevertheless we consider this a bug. Please report\n--1804-- it at http://valgrind.org/support/bug_reports.html.\n--1804-- WARNING: unhandled riscv64-linux syscall: 258\n--1804-- You may be able to write your own handler.\n--1804-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1804-- Nevertheless we consider this a bug. Please report\n--1804-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 68: failed 'https://example.com?moo&search=hello' --qtrim search --- stdout --- expected: 'https://example.com/?moo\n' got: 'https://example.com/?moo\n' --- stderr --- expected: '' got: '--1812-- WARNING: unhandled riscv64-linux syscall: 258\n--1812-- You may be able to write your own handler.\n--1812-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1812-- Nevertheless we consider this a bug. Please report\n--1812-- it at http://valgrind.org/support/bug_reports.html.\n--1812-- WARNING: unhandled riscv64-linux syscall: 258\n--1812-- You may be able to write your own handler.\n--1812-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1812-- Nevertheless we consider this a bug. Please report\n--1812-- it at http://valgrind.org/support/bug_reports.html.\n--1812-- WARNING: unhandled riscv64-linux syscall: 258\n--1812-- You may be able to write your own handler.\n--1812-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1812-- Nevertheless we consider this a bug. Please report\n--1812-- it at http://valgrind.org/support/bug_reports.html.\n--1812-- WARNING: unhandled riscv64-linux syscall: 258\n--1812-- You may be able to write your own handler.\n--1812-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1812-- Nevertheless we consider this a bug. Please report\n--1812-- it at http://valgrind.org/support/bug_reports.html.\n--1812-- WARNING: unhandled riscv64-linux syscall: 258\n--1812-- You may be able to write your own handler.\n--1812-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1812-- Nevertheless we consider this a bug. Please report\n--1812-- it at http://valgrind.org/support/bug_reports.html.\n--1812-- WARNING: unhandled riscv64-linux syscall: 258\n--1812-- You may be able to write your own handler.\n--1812-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1812-- Nevertheless we consider this a bug. Please report\n--1812-- it at http://valgrind.org/support/bug_reports.html.\n--1812-- WARNING: unhandled riscv64-linux syscall: 258\n--1812-- You may be able to write your own handler.\n--1812-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1812-- Nevertheless we consider this a bug. Please report\n--1812-- it at http://valgrind.org/support/bug_reports.html.\n--1812-- WARNING: unhandled riscv64-linux syscall: 258\n--1812-- You may be able to write your own handler.\n--1812-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1812-- Nevertheless we consider this a bug. Please report\n--1812-- it at http://valgrind.org/support/bug_reports.html.\n--1812-- WARNING: unhandled riscv64-linux syscall: 258\n--1812-- You may be able to write your own handler.\n--1812-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1812-- Nevertheless we consider this a bug. Please report\n--1812-- it at http://valgrind.org/support/bug_reports.html.\n--1812-- WARNING: unhandled riscv64-linux syscall: 258\n--1812-- You may be able to write your own handler.\n--1812-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1812-- Nevertheless we consider this a bug. Please report\n--1812-- it at http://valgrind.org/support/bug_reports.html.\n--1812-- WARNING: unhandled riscv64-linux syscall: 258\n--1812-- You may be able to write your own handler.\n--1812-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1812-- Nevertheless we consider this a bug. Please report\n--1812-- it at http://valgrind.org/support/bug_reports.html.\n--1812-- WARNING: unhandled riscv64-linux syscall: 258\n--1812-- You may be able to write your own handler.\n--1812-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1812-- Nevertheless we consider this a bug. Please report\n--1812-- it at http://valgrind.org/support/bug_reports.html.\n--1812-- WARNING: unhandled riscv64-linux syscall: 258\n--1812-- You may be able to write your own handler.\n--1812-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1812-- Nevertheless we consider this a bug. Please report\n--1812-- it at http://valgrind.org/support/bug_reports.html.\n--1812-- WARNING: unhandled riscv64-linux syscall: 258\n--1812-- You may be able to write your own handler.\n--1812-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1812-- Nevertheless we consider this a bug. Please report\n--1812-- it at http://valgrind.org/support/bug_reports.html.\n--1812-- WARNING: unhandled riscv64-linux syscall: 258\n--1812-- You may be able to write your own handler.\n--1812-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1812-- Nevertheless we consider this a bug. Please report\n--1812-- it at http://valgrind.org/support/bug_reports.html.\n--1812-- WARNING: unhandled riscv64-linux syscall: 258\n--1812-- You may be able to write your own handler.\n--1812-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1812-- Nevertheless we consider this a bug. Please report\n--1812-- it at http://valgrind.org/support/bug_reports.html.\n--1812-- WARNING: unhandled riscv64-linux syscall: 258\n--1812-- You may be able to write your own handler.\n--1812-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1812-- Nevertheless we consider this a bug. Please report\n--1812-- it at http://valgrind.org/support/bug_reports.html.\n--1812-- WARNING: unhandled riscv64-linux syscall: 258\n--1812-- You may be able to write your own handler.\n--1812-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1812-- Nevertheless we consider this a bug. Please report\n--1812-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 69: failed 'https://example.com?search=hello&moo' --qtrim search --- stdout --- expected: 'https://example.com/?moo\n' got: 'https://example.com/?moo\n' --- stderr --- expected: '' got: '--1820-- WARNING: unhandled riscv64-linux syscall: 258\n--1820-- You may be able to write your own handler.\n--1820-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1820-- Nevertheless we consider this a bug. Please report\n--1820-- it at http://valgrind.org/support/bug_reports.html.\n--1820-- WARNING: unhandled riscv64-linux syscall: 258\n--1820-- You may be able to write your own handler.\n--1820-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1820-- Nevertheless we consider this a bug. Please report\n--1820-- it at http://valgrind.org/support/bug_reports.html.\n--1820-- WARNING: unhandled riscv64-linux syscall: 258\n--1820-- You may be able to write your own handler.\n--1820-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1820-- Nevertheless we consider this a bug. Please report\n--1820-- it at http://valgrind.org/support/bug_reports.html.\n--1820-- WARNING: unhandled riscv64-linux syscall: 258\n--1820-- You may be able to write your own handler.\n--1820-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1820-- Nevertheless we consider this a bug. Please report\n--1820-- it at http://valgrind.org/support/bug_reports.html.\n--1820-- WARNING: unhandled riscv64-linux syscall: 258\n--1820-- You may be able to write your own handler.\n--1820-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1820-- Nevertheless we consider this a bug. Please report\n--1820-- it at http://valgrind.org/support/bug_reports.html.\n--1820-- WARNING: unhandled riscv64-linux syscall: 258\n--1820-- You may be able to write your own handler.\n--1820-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1820-- Nevertheless we consider this a bug. Please report\n--1820-- it at http://valgrind.org/support/bug_reports.html.\n--1820-- WARNING: unhandled riscv64-linux syscall: 258\n--1820-- You may be able to write your own handler.\n--1820-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1820-- Nevertheless we consider this a bug. Please report\n--1820-- it at http://valgrind.org/support/bug_reports.html.\n--1820-- WARNING: unhandled riscv64-linux syscall: 258\n--1820-- You may be able to write your own handler.\n--1820-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1820-- Nevertheless we consider this a bug. Please report\n--1820-- it at http://valgrind.org/support/bug_reports.html.\n--1820-- WARNING: unhandled riscv64-linux syscall: 258\n--1820-- You may be able to write your own handler.\n--1820-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1820-- Nevertheless we consider this a bug. Please report\n--1820-- it at http://valgrind.org/support/bug_reports.html.\n--1820-- WARNING: unhandled riscv64-linux syscall: 258\n--1820-- You may be able to write your own handler.\n--1820-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1820-- Nevertheless we consider this a bug. Please report\n--1820-- it at http://valgrind.org/support/bug_reports.html.\n--1820-- WARNING: unhandled riscv64-linux syscall: 258\n--1820-- You may be able to write your own handler.\n--1820-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1820-- Nevertheless we consider this a bug. Please report\n--1820-- it at http://valgrind.org/support/bug_reports.html.\n--1820-- WARNING: unhandled riscv64-linux syscall: 258\n--1820-- You may be able to write your own handler.\n--1820-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1820-- Nevertheless we consider this a bug. Please report\n--1820-- it at http://valgrind.org/support/bug_reports.html.\n--1820-- WARNING: unhandled riscv64-linux syscall: 258\n--1820-- You may be able to write your own handler.\n--1820-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1820-- Nevertheless we consider this a bug. Please report\n--1820-- it at http://valgrind.org/support/bug_reports.html.\n--1820-- WARNING: unhandled riscv64-linux syscall: 258\n--1820-- You may be able to write your own handler.\n--1820-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1820-- Nevertheless we consider this a bug. Please report\n--1820-- it at http://valgrind.org/support/bug_reports.html.\n--1820-- WARNING: unhandled riscv64-linux syscall: 258\n--1820-- You may be able to write your own handler.\n--1820-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1820-- Nevertheless we consider this a bug. Please report\n--1820-- it at http://valgrind.org/support/bug_reports.html.\n--1820-- WARNING: unhandled riscv64-linux syscall: 258\n--1820-- You may be able to write your own handler.\n--1820-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1820-- Nevertheless we consider this a bug. Please report\n--1820-- it at http://valgrind.org/support/bug_reports.html.\n--1820-- WARNING: unhandled riscv64-linux syscall: 258\n--1820-- You may be able to write your own handler.\n--1820-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1820-- Nevertheless we consider this a bug. Please report\n--1820-- it at http://valgrind.org/support/bug_reports.html.\n--1820-- WARNING: unhandled riscv64-linux syscall: 258\n--1820-- You may be able to write your own handler.\n--1820-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1820-- Nevertheless we consider this a bug. Please report\n--1820-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 70: failed 'https://example.com?search=hello' --qtrim search --append query=moo --- stdout --- expected: 'https://example.com/?moo\n' got: 'https://example.com/?moo\n' --- stderr --- expected: '' got: '--1828-- WARNING: unhandled riscv64-linux syscall: 258\n--1828-- You may be able to write your own handler.\n--1828-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1828-- Nevertheless we consider this a bug. Please report\n--1828-- it at http://valgrind.org/support/bug_reports.html.\n--1828-- WARNING: unhandled riscv64-linux syscall: 258\n--1828-- You may be able to write your own handler.\n--1828-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1828-- Nevertheless we consider this a bug. Please report\n--1828-- it at http://valgrind.org/support/bug_reports.html.\n--1828-- WARNING: unhandled riscv64-linux syscall: 258\n--1828-- You may be able to write your own handler.\n--1828-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1828-- Nevertheless we consider this a bug. Please report\n--1828-- it at http://valgrind.org/support/bug_reports.html.\n--1828-- WARNING: unhandled riscv64-linux syscall: 258\n--1828-- You may be able to write your own handler.\n--1828-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1828-- Nevertheless we consider this a bug. Please report\n--1828-- it at http://valgrind.org/support/bug_reports.html.\n--1828-- WARNING: unhandled riscv64-linux syscall: 258\n--1828-- You may be able to write your own handler.\n--1828-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1828-- Nevertheless we consider this a bug. Please report\n--1828-- it at http://valgrind.org/support/bug_reports.html.\n--1828-- WARNING: unhandled riscv64-linux syscall: 258\n--1828-- You may be able to write your own handler.\n--1828-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1828-- Nevertheless we consider this a bug. Please report\n--1828-- it at http://valgrind.org/support/bug_reports.html.\n--1828-- WARNING: unhandled riscv64-linux syscall: 258\n--1828-- You may be able to write your own handler.\n--1828-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1828-- Nevertheless we consider this a bug. Please report\n--1828-- it at http://valgrind.org/support/bug_reports.html.\n--1828-- WARNING: unhandled riscv64-linux syscall: 258\n--1828-- You may be able to write your own handler.\n--1828-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1828-- Nevertheless we consider this a bug. Please report\n--1828-- it at http://valgrind.org/support/bug_reports.html.\n--1828-- WARNING: unhandled riscv64-linux syscall: 258\n--1828-- You may be able to write your own handler.\n--1828-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1828-- Nevertheless we consider this a bug. Please report\n--1828-- it at http://valgrind.org/support/bug_reports.html.\n--1828-- WARNING: unhandled riscv64-linux syscall: 258\n--1828-- You may be able to write your own handler.\n--1828-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1828-- Nevertheless we consider this a bug. Please report\n--1828-- it at http://valgrind.org/support/bug_reports.html.\n--1828-- WARNING: unhandled riscv64-linux syscall: 258\n--1828-- You may be able to write your own handler.\n--1828-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1828-- Nevertheless we consider this a bug. Please report\n--1828-- it at http://valgrind.org/support/bug_reports.html.\n--1828-- WARNING: unhandled riscv64-linux syscall: 258\n--1828-- You may be able to write your own handler.\n--1828-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1828-- Nevertheless we consider this a bug. Please report\n--1828-- it at http://valgrind.org/support/bug_reports.html.\n--1828-- WARNING: unhandled riscv64-linux syscall: 258\n--1828-- You may be able to write your own handler.\n--1828-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1828-- Nevertheless we consider this a bug. Please report\n--1828-- it at http://valgrind.org/support/bug_reports.html.\n--1828-- WARNING: unhandled riscv64-linux syscall: 258\n--1828-- You may be able to write your own handler.\n--1828-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1828-- Nevertheless we consider this a bug. Please report\n--1828-- it at http://valgrind.org/support/bug_reports.html.\n--1828-- WARNING: unhandled riscv64-linux syscall: 258\n--1828-- You may be able to write your own handler.\n--1828-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1828-- Nevertheless we consider this a bug. Please report\n--1828-- it at http://valgrind.org/support/bug_reports.html.\n--1828-- WARNING: unhandled riscv64-linux syscall: 258\n--1828-- You may be able to write your own handler.\n--1828-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1828-- Nevertheless we consider this a bug. Please report\n--1828-- it at http://valgrind.org/support/bug_reports.html.\n--1828-- WARNING: unhandled riscv64-linux syscall: 258\n--1828-- You may be able to write your own handler.\n--1828-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1828-- Nevertheless we consider this a bug. Please report\n--1828-- it at http://valgrind.org/support/bug_reports.html.\n--1828-- WARNING: unhandled riscv64-linux syscall: 258\n--1828-- You may be able to write your own handler.\n--1828-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1828-- Nevertheless we consider this a bug. Please report\n--1828-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 71: failed --keep-port https://hello:443/foo --- stdout --- expected: 'https://hello:443/foo\n' got: 'https://hello:443/foo\n' --- stderr --- expected: '' got: '--1836-- WARNING: unhandled riscv64-linux syscall: 258\n--1836-- You may be able to write your own handler.\n--1836-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1836-- Nevertheless we consider this a bug. Please report\n--1836-- it at http://valgrind.org/support/bug_reports.html.\n--1836-- WARNING: unhandled riscv64-linux syscall: 258\n--1836-- You may be able to write your own handler.\n--1836-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1836-- Nevertheless we consider this a bug. Please report\n--1836-- it at http://valgrind.org/support/bug_reports.html.\n--1836-- WARNING: unhandled riscv64-linux syscall: 258\n--1836-- You may be able to write your own handler.\n--1836-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1836-- Nevertheless we consider this a bug. Please report\n--1836-- it at http://valgrind.org/support/bug_reports.html.\n--1836-- WARNING: unhandled riscv64-linux syscall: 258\n--1836-- You may be able to write your own handler.\n--1836-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1836-- Nevertheless we consider this a bug. Please report\n--1836-- it at http://valgrind.org/support/bug_reports.html.\n--1836-- WARNING: unhandled riscv64-linux syscall: 258\n--1836-- You may be able to write your own handler.\n--1836-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1836-- Nevertheless we consider this a bug. Please report\n--1836-- it at http://valgrind.org/support/bug_reports.html.\n--1836-- WARNING: unhandled riscv64-linux syscall: 258\n--1836-- You may be able to write your own handler.\n--1836-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1836-- Nevertheless we consider this a bug. Please report\n--1836-- it at http://valgrind.org/support/bug_reports.html.\n--1836-- WARNING: unhandled riscv64-linux syscall: 258\n--1836-- You may be able to write your own handler.\n--1836-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1836-- Nevertheless we consider this a bug. Please report\n--1836-- it at http://valgrind.org/support/bug_reports.html.\n--1836-- WARNING: unhandled riscv64-linux syscall: 258\n--1836-- You may be able to write your own handler.\n--1836-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1836-- Nevertheless we consider this a bug. Please report\n--1836-- it at http://valgrind.org/support/bug_reports.html.\n--1836-- WARNING: unhandled riscv64-linux syscall: 258\n--1836-- You may be able to write your own handler.\n--1836-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1836-- Nevertheless we consider this a bug. Please report\n--1836-- it at http://valgrind.org/support/bug_reports.html.\n--1836-- WARNING: unhandled riscv64-linux syscall: 258\n--1836-- You may be able to write your own handler.\n--1836-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1836-- Nevertheless we consider this a bug. Please report\n--1836-- it at http://valgrind.org/support/bug_reports.html.\n--1836-- WARNING: unhandled riscv64-linux syscall: 258\n--1836-- You may be able to write your own handler.\n--1836-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1836-- Nevertheless we consider this a bug. Please report\n--1836-- it at http://valgrind.org/support/bug_reports.html.\n--1836-- WARNING: unhandled riscv64-linux syscall: 258\n--1836-- You may be able to write your own handler.\n--1836-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1836-- Nevertheless we consider this a bug. Please report\n--1836-- it at http://valgrind.org/support/bug_reports.html.\n--1836-- WARNING: unhandled riscv64-linux syscall: 258\n--1836-- You may be able to write your own handler.\n--1836-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1836-- Nevertheless we consider this a bug. Please report\n--1836-- it at http://valgrind.org/support/bug_reports.html.\n--1836-- WARNING: unhandled riscv64-linux syscall: 258\n--1836-- You may be able to write your own handler.\n--1836-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1836-- Nevertheless we consider this a bug. Please report\n--1836-- it at http://valgrind.org/support/bug_reports.html.\n--1836-- WARNING: unhandled riscv64-linux syscall: 258\n--1836-- You may be able to write your own handler.\n--1836-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1836-- Nevertheless we consider this a bug. Please report\n--1836-- it at http://valgrind.org/support/bug_reports.html.\n--1836-- WARNING: unhandled riscv64-linux syscall: 258\n--1836-- You may be able to write your own handler.\n--1836-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1836-- Nevertheless we consider this a bug. Please report\n--1836-- it at http://valgrind.org/support/bug_reports.html.\n--1836-- WARNING: unhandled riscv64-linux syscall: 258\n--1836-- You may be able to write your own handler.\n--1836-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1836-- Nevertheless we consider this a bug. Please report\n--1836-- it at http://valgrind.org/support/bug_reports.html.\n--1836-- WARNING: unhandled riscv64-linux syscall: 258\n--1836-- You may be able to write your own handler.\n--1836-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1836-- Nevertheless we consider this a bug. Please report\n--1836-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 72: failed --keep-port ftp://hello:21/foo --- stdout --- expected: 'ftp://hello:21/foo\n' got: 'ftp://hello:21/foo\n' --- stderr --- expected: '' got: '--1844-- WARNING: unhandled riscv64-linux syscall: 258\n--1844-- You may be able to write your own handler.\n--1844-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1844-- Nevertheless we consider this a bug. Please report\n--1844-- it at http://valgrind.org/support/bug_reports.html.\n--1844-- WARNING: unhandled riscv64-linux syscall: 258\n--1844-- You may be able to write your own handler.\n--1844-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1844-- Nevertheless we consider this a bug. Please report\n--1844-- it at http://valgrind.org/support/bug_reports.html.\n--1844-- WARNING: unhandled riscv64-linux syscall: 258\n--1844-- You may be able to write your own handler.\n--1844-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1844-- Nevertheless we consider this a bug. Please report\n--1844-- it at http://valgrind.org/support/bug_reports.html.\n--1844-- WARNING: unhandled riscv64-linux syscall: 258\n--1844-- You may be able to write your own handler.\n--1844-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1844-- Nevertheless we consider this a bug. Please report\n--1844-- it at http://valgrind.org/support/bug_reports.html.\n--1844-- WARNING: unhandled riscv64-linux syscall: 258\n--1844-- You may be able to write your own handler.\n--1844-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1844-- Nevertheless we consider this a bug. Please report\n--1844-- it at http://valgrind.org/support/bug_reports.html.\n--1844-- WARNING: unhandled riscv64-linux syscall: 258\n--1844-- You may be able to write your own handler.\n--1844-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1844-- Nevertheless we consider this a bug. Please report\n--1844-- it at http://valgrind.org/support/bug_reports.html.\n--1844-- WARNING: unhandled riscv64-linux syscall: 258\n--1844-- You may be able to write your own handler.\n--1844-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1844-- Nevertheless we consider this a bug. Please report\n--1844-- it at http://valgrind.org/support/bug_reports.html.\n--1844-- WARNING: unhandled riscv64-linux syscall: 258\n--1844-- You may be able to write your own handler.\n--1844-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1844-- Nevertheless we consider this a bug. Please report\n--1844-- it at http://valgrind.org/support/bug_reports.html.\n--1844-- WARNING: unhandled riscv64-linux syscall: 258\n--1844-- You may be able to write your own handler.\n--1844-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1844-- Nevertheless we consider this a bug. Please report\n--1844-- it at http://valgrind.org/support/bug_reports.html.\n--1844-- WARNING: unhandled riscv64-linux syscall: 258\n--1844-- You may be able to write your own handler.\n--1844-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1844-- Nevertheless we consider this a bug. Please report\n--1844-- it at http://valgrind.org/support/bug_reports.html.\n--1844-- WARNING: unhandled riscv64-linux syscall: 258\n--1844-- You may be able to write your own handler.\n--1844-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1844-- Nevertheless we consider this a bug. Please report\n--1844-- it at http://valgrind.org/support/bug_reports.html.\n--1844-- WARNING: unhandled riscv64-linux syscall: 258\n--1844-- You may be able to write your own handler.\n--1844-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1844-- Nevertheless we consider this a bug. Please report\n--1844-- it at http://valgrind.org/support/bug_reports.html.\n--1844-- WARNING: unhandled riscv64-linux syscall: 258\n--1844-- You may be able to write your own handler.\n--1844-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1844-- Nevertheless we consider this a bug. Please report\n--1844-- it at http://valgrind.org/support/bug_reports.html.\n--1844-- WARNING: unhandled riscv64-linux syscall: 258\n--1844-- You may be able to write your own handler.\n--1844-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1844-- Nevertheless we consider this a bug. Please report\n--1844-- it at http://valgrind.org/support/bug_reports.html.\n--1844-- WARNING: unhandled riscv64-linux syscall: 258\n--1844-- You may be able to write your own handler.\n--1844-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1844-- Nevertheless we consider this a bug. Please report\n--1844-- it at http://valgrind.org/support/bug_reports.html.\n--1844-- WARNING: unhandled riscv64-linux syscall: 258\n--1844-- You may be able to write your own handler.\n--1844-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1844-- Nevertheless we consider this a bug. Please report\n--1844-- it at http://valgrind.org/support/bug_reports.html.\n--1844-- WARNING: unhandled riscv64-linux syscall: 258\n--1844-- You may be able to write your own handler.\n--1844-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1844-- Nevertheless we consider this a bug. Please report\n--1844-- it at http://valgrind.org/support/bug_reports.html.\n--1844-- WARNING: unhandled riscv64-linux syscall: 258\n--1844-- You may be able to write your own handler.\n--1844-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1844-- Nevertheless we consider this a bug. Please report\n--1844-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 73: failed https://hello:443/foo -s scheme=ftp --- stdout --- expected: 'ftp://hello:443/foo\n' got: 'ftp://hello:443/foo\n' --- stderr --- expected: '' got: '--1852-- WARNING: unhandled riscv64-linux syscall: 258\n--1852-- You may be able to write your own handler.\n--1852-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1852-- Nevertheless we consider this a bug. Please report\n--1852-- it at http://valgrind.org/support/bug_reports.html.\n--1852-- WARNING: unhandled riscv64-linux syscall: 258\n--1852-- You may be able to write your own handler.\n--1852-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1852-- Nevertheless we consider this a bug. Please report\n--1852-- it at http://valgrind.org/support/bug_reports.html.\n--1852-- WARNING: unhandled riscv64-linux syscall: 258\n--1852-- You may be able to write your own handler.\n--1852-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1852-- Nevertheless we consider this a bug. Please report\n--1852-- it at http://valgrind.org/support/bug_reports.html.\n--1852-- WARNING: unhandled riscv64-linux syscall: 258\n--1852-- You may be able to write your own handler.\n--1852-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1852-- Nevertheless we consider this a bug. Please report\n--1852-- it at http://valgrind.org/support/bug_reports.html.\n--1852-- WARNING: unhandled riscv64-linux syscall: 258\n--1852-- You may be able to write your own handler.\n--1852-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1852-- Nevertheless we consider this a bug. Please report\n--1852-- it at http://valgrind.org/support/bug_reports.html.\n--1852-- WARNING: unhandled riscv64-linux syscall: 258\n--1852-- You may be able to write your own handler.\n--1852-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1852-- Nevertheless we consider this a bug. Please report\n--1852-- it at http://valgrind.org/support/bug_reports.html.\n--1852-- WARNING: unhandled riscv64-linux syscall: 258\n--1852-- You may be able to write your own handler.\n--1852-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1852-- Nevertheless we consider this a bug. Please report\n--1852-- it at http://valgrind.org/support/bug_reports.html.\n--1852-- WARNING: unhandled riscv64-linux syscall: 258\n--1852-- You may be able to write your own handler.\n--1852-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1852-- Nevertheless we consider this a bug. Please report\n--1852-- it at http://valgrind.org/support/bug_reports.html.\n--1852-- WARNING: unhandled riscv64-linux syscall: 258\n--1852-- You may be able to write your own handler.\n--1852-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1852-- Nevertheless we consider this a bug. Please report\n--1852-- it at http://valgrind.org/support/bug_reports.html.\n--1852-- WARNING: unhandled riscv64-linux syscall: 258\n--1852-- You may be able to write your own handler.\n--1852-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1852-- Nevertheless we consider this a bug. Please report\n--1852-- it at http://valgrind.org/support/bug_reports.html.\n--1852-- WARNING: unhandled riscv64-linux syscall: 258\n--1852-- You may be able to write your own handler.\n--1852-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1852-- Nevertheless we consider this a bug. Please report\n--1852-- it at http://valgrind.org/support/bug_reports.html.\n--1852-- WARNING: unhandled riscv64-linux syscall: 258\n--1852-- You may be able to write your own handler.\n--1852-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1852-- Nevertheless we consider this a bug. Please report\n--1852-- it at http://valgrind.org/support/bug_reports.html.\n--1852-- WARNING: unhandled riscv64-linux syscall: 258\n--1852-- You may be able to write your own handler.\n--1852-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1852-- Nevertheless we consider this a bug. Please report\n--1852-- it at http://valgrind.org/support/bug_reports.html.\n--1852-- WARNING: unhandled riscv64-linux syscall: 258\n--1852-- You may be able to write your own handler.\n--1852-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1852-- Nevertheless we consider this a bug. Please report\n--1852-- it at http://valgrind.org/support/bug_reports.html.\n--1852-- WARNING: unhandled riscv64-linux syscall: 258\n--1852-- You may be able to write your own handler.\n--1852-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1852-- Nevertheless we consider this a bug. Please report\n--1852-- it at http://valgrind.org/support/bug_reports.html.\n--1852-- WARNING: unhandled riscv64-linux syscall: 258\n--1852-- You may be able to write your own handler.\n--1852-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1852-- Nevertheless we consider this a bug. Please report\n--1852-- it at http://valgrind.org/support/bug_reports.html.\n--1852-- WARNING: unhandled riscv64-linux syscall: 258\n--1852-- You may be able to write your own handler.\n--1852-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1852-- Nevertheless we consider this a bug. Please report\n--1852-- it at http://valgrind.org/support/bug_reports.html.\n--1852-- WARNING: unhandled riscv64-linux syscall: 258\n--1852-- You may be able to write your own handler.\n--1852-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1852-- Nevertheless we consider this a bug. Please report\n--1852-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 74: failed --keep-port ftp://hello:443/foo -s scheme=https --- stdout --- expected: 'https://hello:443/foo\n' got: 'https://hello:443/foo\n' --- stderr --- expected: '' got: '--1860-- WARNING: unhandled riscv64-linux syscall: 258\n--1860-- You may be able to write your own handler.\n--1860-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1860-- Nevertheless we consider this a bug. Please report\n--1860-- it at http://valgrind.org/support/bug_reports.html.\n--1860-- WARNING: unhandled riscv64-linux syscall: 258\n--1860-- You may be able to write your own handler.\n--1860-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1860-- Nevertheless we consider this a bug. Please report\n--1860-- it at http://valgrind.org/support/bug_reports.html.\n--1860-- WARNING: unhandled riscv64-linux syscall: 258\n--1860-- You may be able to write your own handler.\n--1860-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1860-- Nevertheless we consider this a bug. Please report\n--1860-- it at http://valgrind.org/support/bug_reports.html.\n--1860-- WARNING: unhandled riscv64-linux syscall: 258\n--1860-- You may be able to write your own handler.\n--1860-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1860-- Nevertheless we consider this a bug. Please report\n--1860-- it at http://valgrind.org/support/bug_reports.html.\n--1860-- WARNING: unhandled riscv64-linux syscall: 258\n--1860-- You may be able to write your own handler.\n--1860-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1860-- Nevertheless we consider this a bug. Please report\n--1860-- it at http://valgrind.org/support/bug_reports.html.\n--1860-- WARNING: unhandled riscv64-linux syscall: 258\n--1860-- You may be able to write your own handler.\n--1860-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1860-- Nevertheless we consider this a bug. Please report\n--1860-- it at http://valgrind.org/support/bug_reports.html.\n--1860-- WARNING: unhandled riscv64-linux syscall: 258\n--1860-- You may be able to write your own handler.\n--1860-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1860-- Nevertheless we consider this a bug. Please report\n--1860-- it at http://valgrind.org/support/bug_reports.html.\n--1860-- WARNING: unhandled riscv64-linux syscall: 258\n--1860-- You may be able to write your own handler.\n--1860-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1860-- Nevertheless we consider this a bug. Please report\n--1860-- it at http://valgrind.org/support/bug_reports.html.\n--1860-- WARNING: unhandled riscv64-linux syscall: 258\n--1860-- You may be able to write your own handler.\n--1860-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1860-- Nevertheless we consider this a bug. Please report\n--1860-- it at http://valgrind.org/support/bug_reports.html.\n--1860-- WARNING: unhandled riscv64-linux syscall: 258\n--1860-- You may be able to write your own handler.\n--1860-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1860-- Nevertheless we consider this a bug. Please report\n--1860-- it at http://valgrind.org/support/bug_reports.html.\n--1860-- WARNING: unhandled riscv64-linux syscall: 258\n--1860-- You may be able to write your own handler.\n--1860-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1860-- Nevertheless we consider this a bug. Please report\n--1860-- it at http://valgrind.org/support/bug_reports.html.\n--1860-- WARNING: unhandled riscv64-linux syscall: 258\n--1860-- You may be able to write your own handler.\n--1860-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1860-- Nevertheless we consider this a bug. Please report\n--1860-- it at http://valgrind.org/support/bug_reports.html.\n--1860-- WARNING: unhandled riscv64-linux syscall: 258\n--1860-- You may be able to write your own handler.\n--1860-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1860-- Nevertheless we consider this a bug. Please report\n--1860-- it at http://valgrind.org/support/bug_reports.html.\n--1860-- WARNING: unhandled riscv64-linux syscall: 258\n--1860-- You may be able to write your own handler.\n--1860-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1860-- Nevertheless we consider this a bug. Please report\n--1860-- it at http://valgrind.org/support/bug_reports.html.\n--1860-- WARNING: unhandled riscv64-linux syscall: 258\n--1860-- You may be able to write your own handler.\n--1860-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1860-- Nevertheless we consider this a bug. Please report\n--1860-- it at http://valgrind.org/support/bug_reports.html.\n--1860-- WARNING: unhandled riscv64-linux syscall: 258\n--1860-- You may be able to write your own handler.\n--1860-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1860-- Nevertheless we consider this a bug. Please report\n--1860-- it at http://valgrind.org/support/bug_reports.html.\n--1860-- WARNING: unhandled riscv64-linux syscall: 258\n--1860-- You may be able to write your own handler.\n--1860-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1860-- Nevertheless we consider this a bug. Please report\n--1860-- it at http://valgrind.org/support/bug_reports.html.\n--1860-- WARNING: unhandled riscv64-linux syscall: 258\n--1860-- You may be able to write your own handler.\n--1860-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1860-- Nevertheless we consider this a bug. Please report\n--1860-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 75: failed 'https://example.com?utm_source=tra%20cker&address%20=home&here=now&thisthen' -g '{query:utm_source}' --- stdout --- expected: 'tra cker\n' got: 'tra cker\n' --- stderr --- expected: '' got: '--1868-- WARNING: unhandled riscv64-linux syscall: 258\n--1868-- You may be able to write your own handler.\n--1868-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1868-- Nevertheless we consider this a bug. Please report\n--1868-- it at http://valgrind.org/support/bug_reports.html.\n--1868-- WARNING: unhandled riscv64-linux syscall: 258\n--1868-- You may be able to write your own handler.\n--1868-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1868-- Nevertheless we consider this a bug. Please report\n--1868-- it at http://valgrind.org/support/bug_reports.html.\n--1868-- WARNING: unhandled riscv64-linux syscall: 258\n--1868-- You may be able to write your own handler.\n--1868-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1868-- Nevertheless we consider this a bug. Please report\n--1868-- it at http://valgrind.org/support/bug_reports.html.\n--1868-- WARNING: unhandled riscv64-linux syscall: 258\n--1868-- You may be able to write your own handler.\n--1868-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1868-- Nevertheless we consider this a bug. Please report\n--1868-- it at http://valgrind.org/support/bug_reports.html.\n--1868-- WARNING: unhandled riscv64-linux syscall: 258\n--1868-- You may be able to write your own handler.\n--1868-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1868-- Nevertheless we consider this a bug. Please report\n--1868-- it at http://valgrind.org/support/bug_reports.html.\n--1868-- WARNING: unhandled riscv64-linux syscall: 258\n--1868-- You may be able to write your own handler.\n--1868-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1868-- Nevertheless we consider this a bug. Please report\n--1868-- it at http://valgrind.org/support/bug_reports.html.\n--1868-- WARNING: unhandled riscv64-linux syscall: 258\n--1868-- You may be able to write your own handler.\n--1868-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1868-- Nevertheless we consider this a bug. Please report\n--1868-- it at http://valgrind.org/support/bug_reports.html.\n--1868-- WARNING: unhandled riscv64-linux syscall: 258\n--1868-- You may be able to write your own handler.\n--1868-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1868-- Nevertheless we consider this a bug. Please report\n--1868-- it at http://valgrind.org/support/bug_reports.html.\n--1868-- WARNING: unhandled riscv64-linux syscall: 258\n--1868-- You may be able to write your own handler.\n--1868-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1868-- Nevertheless we consider this a bug. Please report\n--1868-- it at http://valgrind.org/support/bug_reports.html.\n--1868-- WARNING: unhandled riscv64-linux syscall: 258\n--1868-- You may be able to write your own handler.\n--1868-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1868-- Nevertheless we consider this a bug. Please report\n--1868-- it at http://valgrind.org/support/bug_reports.html.\n--1868-- WARNING: unhandled riscv64-linux syscall: 258\n--1868-- You may be able to write your own handler.\n--1868-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1868-- Nevertheless we consider this a bug. Please report\n--1868-- it at http://valgrind.org/support/bug_reports.html.\n--1868-- WARNING: unhandled riscv64-linux syscall: 258\n--1868-- You may be able to write your own handler.\n--1868-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1868-- Nevertheless we consider this a bug. Please report\n--1868-- it at http://valgrind.org/support/bug_reports.html.\n--1868-- WARNING: unhandled riscv64-linux syscall: 258\n--1868-- You may be able to write your own handler.\n--1868-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1868-- Nevertheless we consider this a bug. Please report\n--1868-- it at http://valgrind.org/support/bug_reports.html.\n--1868-- WARNING: unhandled riscv64-linux syscall: 258\n--1868-- You may be able to write your own handler.\n--1868-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1868-- Nevertheless we consider this a bug. Please report\n--1868-- it at http://valgrind.org/support/bug_reports.html.\n--1868-- WARNING: unhandled riscv64-linux syscall: 258\n--1868-- You may be able to write your own handler.\n--1868-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1868-- Nevertheless we consider this a bug. Please report\n--1868-- it at http://valgrind.org/support/bug_reports.html.\n--1868-- WARNING: unhandled riscv64-linux syscall: 258\n--1868-- You may be able to write your own handler.\n--1868-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1868-- Nevertheless we consider this a bug. Please report\n--1868-- it at http://valgrind.org/support/bug_reports.html.\n--1868-- WARNING: unhandled riscv64-linux syscall: 258\n--1868-- You may be able to write your own handler.\n--1868-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1868-- Nevertheless we consider this a bug. Please report\n--1868-- it at http://valgrind.org/support/bug_reports.html.\n--1868-- WARNING: unhandled riscv64-linux syscall: 258\n--1868-- You may be able to write your own handler.\n--1868-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1868-- Nevertheless we consider this a bug. Please report\n--1868-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 76: failed 'https://example.com?utm_source=tra%20cker&address%20=home&here=now&thisthen' -g '{:query:utm_source}' --- stdout --- expected: 'tra+cker\n' got: 'tra+cker\n' --- stderr --- expected: '' got: '--1876-- WARNING: unhandled riscv64-linux syscall: 258\n--1876-- You may be able to write your own handler.\n--1876-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1876-- Nevertheless we consider this a bug. Please report\n--1876-- it at http://valgrind.org/support/bug_reports.html.\n--1876-- WARNING: unhandled riscv64-linux syscall: 258\n--1876-- You may be able to write your own handler.\n--1876-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1876-- Nevertheless we consider this a bug. Please report\n--1876-- it at http://valgrind.org/support/bug_reports.html.\n--1876-- WARNING: unhandled riscv64-linux syscall: 258\n--1876-- You may be able to write your own handler.\n--1876-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1876-- Nevertheless we consider this a bug. Please report\n--1876-- it at http://valgrind.org/support/bug_reports.html.\n--1876-- WARNING: unhandled riscv64-linux syscall: 258\n--1876-- You may be able to write your own handler.\n--1876-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1876-- Nevertheless we consider this a bug. Please report\n--1876-- it at http://valgrind.org/support/bug_reports.html.\n--1876-- WARNING: unhandled riscv64-linux syscall: 258\n--1876-- You may be able to write your own handler.\n--1876-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1876-- Nevertheless we consider this a bug. Please report\n--1876-- it at http://valgrind.org/support/bug_reports.html.\n--1876-- WARNING: unhandled riscv64-linux syscall: 258\n--1876-- You may be able to write your own handler.\n--1876-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1876-- Nevertheless we consider this a bug. Please report\n--1876-- it at http://valgrind.org/support/bug_reports.html.\n--1876-- WARNING: unhandled riscv64-linux syscall: 258\n--1876-- You may be able to write your own handler.\n--1876-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1876-- Nevertheless we consider this a bug. Please report\n--1876-- it at http://valgrind.org/support/bug_reports.html.\n--1876-- WARNING: unhandled riscv64-linux syscall: 258\n--1876-- You may be able to write your own handler.\n--1876-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1876-- Nevertheless we consider this a bug. Please report\n--1876-- it at http://valgrind.org/support/bug_reports.html.\n--1876-- WARNING: unhandled riscv64-linux syscall: 258\n--1876-- You may be able to write your own handler.\n--1876-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1876-- Nevertheless we consider this a bug. Please report\n--1876-- it at http://valgrind.org/support/bug_reports.html.\n--1876-- WARNING: unhandled riscv64-linux syscall: 258\n--1876-- You may be able to write your own handler.\n--1876-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1876-- Nevertheless we consider this a bug. Please report\n--1876-- it at http://valgrind.org/support/bug_reports.html.\n--1876-- WARNING: unhandled riscv64-linux syscall: 258\n--1876-- You may be able to write your own handler.\n--1876-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1876-- Nevertheless we consider this a bug. Please report\n--1876-- it at http://valgrind.org/support/bug_reports.html.\n--1876-- WARNING: unhandled riscv64-linux syscall: 258\n--1876-- You may be able to write your own handler.\n--1876-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1876-- Nevertheless we consider this a bug. Please report\n--1876-- it at http://valgrind.org/support/bug_reports.html.\n--1876-- WARNING: unhandled riscv64-linux syscall: 258\n--1876-- You may be able to write your own handler.\n--1876-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1876-- Nevertheless we consider this a bug. Please report\n--1876-- it at http://valgrind.org/support/bug_reports.html.\n--1876-- WARNING: unhandled riscv64-linux syscall: 258\n--1876-- You may be able to write your own handler.\n--1876-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1876-- Nevertheless we consider this a bug. Please report\n--1876-- it at http://valgrind.org/support/bug_reports.html.\n--1876-- WARNING: unhandled riscv64-linux syscall: 258\n--1876-- You may be able to write your own handler.\n--1876-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1876-- Nevertheless we consider this a bug. Please report\n--1876-- it at http://valgrind.org/support/bug_reports.html.\n--1876-- WARNING: unhandled riscv64-linux syscall: 258\n--1876-- You may be able to write your own handler.\n--1876-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1876-- Nevertheless we consider this a bug. Please report\n--1876-- it at http://valgrind.org/support/bug_reports.html.\n--1876-- WARNING: unhandled riscv64-linux syscall: 258\n--1876-- You may be able to write your own handler.\n--1876-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1876-- Nevertheless we consider this a bug. Please report\n--1876-- it at http://valgrind.org/support/bug_reports.html.\n--1876-- WARNING: unhandled riscv64-linux syscall: 258\n--1876-- You may be able to write your own handler.\n--1876-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1876-- Nevertheless we consider this a bug. Please report\n--1876-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 77: failed 'https://example.com?utm_source=tra%20cker&address%20=home&here=now&thisthen' -g '{:query:utm_}' --- stdout --- expected: '\n' got: '\n' --- stderr --- expected: '' got: '--1884-- WARNING: unhandled riscv64-linux syscall: 258\n--1884-- You may be able to write your own handler.\n--1884-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1884-- Nevertheless we consider this a bug. Please report\n--1884-- it at http://valgrind.org/support/bug_reports.html.\n--1884-- WARNING: unhandled riscv64-linux syscall: 258\n--1884-- You may be able to write your own handler.\n--1884-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1884-- Nevertheless we consider this a bug. Please report\n--1884-- it at http://valgrind.org/support/bug_reports.html.\n--1884-- WARNING: unhandled riscv64-linux syscall: 258\n--1884-- You may be able to write your own handler.\n--1884-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1884-- Nevertheless we consider this a bug. Please report\n--1884-- it at http://valgrind.org/support/bug_reports.html.\n--1884-- WARNING: unhandled riscv64-linux syscall: 258\n--1884-- You may be able to write your own handler.\n--1884-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1884-- Nevertheless we consider this a bug. Please report\n--1884-- it at http://valgrind.org/support/bug_reports.html.\n--1884-- WARNING: unhandled riscv64-linux syscall: 258\n--1884-- You may be able to write your own handler.\n--1884-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1884-- Nevertheless we consider this a bug. Please report\n--1884-- it at http://valgrind.org/support/bug_reports.html.\n--1884-- WARNING: unhandled riscv64-linux syscall: 258\n--1884-- You may be able to write your own handler.\n--1884-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1884-- Nevertheless we consider this a bug. Please report\n--1884-- it at http://valgrind.org/support/bug_reports.html.\n--1884-- WARNING: unhandled riscv64-linux syscall: 258\n--1884-- You may be able to write your own handler.\n--1884-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1884-- Nevertheless we consider this a bug. Please report\n--1884-- it at http://valgrind.org/support/bug_reports.html.\n--1884-- WARNING: unhandled riscv64-linux syscall: 258\n--1884-- You may be able to write your own handler.\n--1884-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1884-- Nevertheless we consider this a bug. Please report\n--1884-- it at http://valgrind.org/support/bug_reports.html.\n--1884-- WARNING: unhandled riscv64-linux syscall: 258\n--1884-- You may be able to write your own handler.\n--1884-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1884-- Nevertheless we consider this a bug. Please report\n--1884-- it at http://valgrind.org/support/bug_reports.html.\n--1884-- WARNING: unhandled riscv64-linux syscall: 258\n--1884-- You may be able to write your own handler.\n--1884-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1884-- Nevertheless we consider this a bug. Please report\n--1884-- it at http://valgrind.org/support/bug_reports.html.\n--1884-- WARNING: unhandled riscv64-linux syscall: 258\n--1884-- You may be able to write your own handler.\n--1884-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1884-- Nevertheless we consider this a bug. Please report\n--1884-- it at http://valgrind.org/support/bug_reports.html.\n--1884-- WARNING: unhandled riscv64-linux syscall: 258\n--1884-- You may be able to write your own handler.\n--1884-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1884-- Nevertheless we consider this a bug. Please report\n--1884-- it at http://valgrind.org/support/bug_reports.html.\n--1884-- WARNING: unhandled riscv64-linux syscall: 258\n--1884-- You may be able to write your own handler.\n--1884-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1884-- Nevertheless we consider this a bug. Please report\n--1884-- it at http://valgrind.org/support/bug_reports.html.\n--1884-- WARNING: unhandled riscv64-linux syscall: 258\n--1884-- You may be able to write your own handler.\n--1884-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1884-- Nevertheless we consider this a bug. Please report\n--1884-- it at http://valgrind.org/support/bug_reports.html.\n--1884-- WARNING: unhandled riscv64-linux syscall: 258\n--1884-- You may be able to write your own handler.\n--1884-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1884-- Nevertheless we consider this a bug. Please report\n--1884-- it at http://valgrind.org/support/bug_reports.html.\n--1884-- WARNING: unhandled riscv64-linux syscall: 258\n--1884-- You may be able to write your own handler.\n--1884-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1884-- Nevertheless we consider this a bug. Please report\n--1884-- it at http://valgrind.org/support/bug_reports.html.\n--1884-- WARNING: unhandled riscv64-linux syscall: 258\n--1884-- You may be able to write your own handler.\n--1884-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1884-- Nevertheless we consider this a bug. Please report\n--1884-- it at http://valgrind.org/support/bug_reports.html.\n--1884-- WARNING: unhandled riscv64-linux syscall: 258\n--1884-- You may be able to write your own handler.\n--1884-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1884-- Nevertheless we consider this a bug. Please report\n--1884-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 78: failed 'https://example.com?utm_source=tra%20cker&address%20=home&here=now&thisthen' -g '{:query:UTM_SOURCE}' --- stdout --- expected: '\n' got: '\n' --- stderr --- expected: '' got: '--1892-- WARNING: unhandled riscv64-linux syscall: 258\n--1892-- You may be able to write your own handler.\n--1892-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1892-- Nevertheless we consider this a bug. Please report\n--1892-- it at http://valgrind.org/support/bug_reports.html.\n--1892-- WARNING: unhandled riscv64-linux syscall: 258\n--1892-- You may be able to write your own handler.\n--1892-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1892-- Nevertheless we consider this a bug. Please report\n--1892-- it at http://valgrind.org/support/bug_reports.html.\n--1892-- WARNING: unhandled riscv64-linux syscall: 258\n--1892-- You may be able to write your own handler.\n--1892-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1892-- Nevertheless we consider this a bug. Please report\n--1892-- it at http://valgrind.org/support/bug_reports.html.\n--1892-- WARNING: unhandled riscv64-linux syscall: 258\n--1892-- You may be able to write your own handler.\n--1892-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1892-- Nevertheless we consider this a bug. Please report\n--1892-- it at http://valgrind.org/support/bug_reports.html.\n--1892-- WARNING: unhandled riscv64-linux syscall: 258\n--1892-- You may be able to write your own handler.\n--1892-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1892-- Nevertheless we consider this a bug. Please report\n--1892-- it at http://valgrind.org/support/bug_reports.html.\n--1892-- WARNING: unhandled riscv64-linux syscall: 258\n--1892-- You may be able to write your own handler.\n--1892-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1892-- Nevertheless we consider this a bug. Please report\n--1892-- it at http://valgrind.org/support/bug_reports.html.\n--1892-- WARNING: unhandled riscv64-linux syscall: 258\n--1892-- You may be able to write your own handler.\n--1892-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1892-- Nevertheless we consider this a bug. Please report\n--1892-- it at http://valgrind.org/support/bug_reports.html.\n--1892-- WARNING: unhandled riscv64-linux syscall: 258\n--1892-- You may be able to write your own handler.\n--1892-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1892-- Nevertheless we consider this a bug. Please report\n--1892-- it at http://valgrind.org/support/bug_reports.html.\n--1892-- WARNING: unhandled riscv64-linux syscall: 258\n--1892-- You may be able to write your own handler.\n--1892-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1892-- Nevertheless we consider this a bug. Please report\n--1892-- it at http://valgrind.org/support/bug_reports.html.\n--1892-- WARNING: unhandled riscv64-linux syscall: 258\n--1892-- You may be able to write your own handler.\n--1892-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1892-- Nevertheless we consider this a bug. Please report\n--1892-- it at http://valgrind.org/support/bug_reports.html.\n--1892-- WARNING: unhandled riscv64-linux syscall: 258\n--1892-- You may be able to write your own handler.\n--1892-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1892-- Nevertheless we consider this a bug. Please report\n--1892-- it at http://valgrind.org/support/bug_reports.html.\n--1892-- WARNING: unhandled riscv64-linux syscall: 258\n--1892-- You may be able to write your own handler.\n--1892-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1892-- Nevertheless we consider this a bug. Please report\n--1892-- it at http://valgrind.org/support/bug_reports.html.\n--1892-- WARNING: unhandled riscv64-linux syscall: 258\n--1892-- You may be able to write your own handler.\n--1892-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1892-- Nevertheless we consider this a bug. Please report\n--1892-- it at http://valgrind.org/support/bug_reports.html.\n--1892-- WARNING: unhandled riscv64-linux syscall: 258\n--1892-- You may be able to write your own handler.\n--1892-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1892-- Nevertheless we consider this a bug. Please report\n--1892-- it at http://valgrind.org/support/bug_reports.html.\n--1892-- WARNING: unhandled riscv64-linux syscall: 258\n--1892-- You may be able to write your own handler.\n--1892-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1892-- Nevertheless we consider this a bug. Please report\n--1892-- it at http://valgrind.org/support/bug_reports.html.\n--1892-- WARNING: unhandled riscv64-linux syscall: 258\n--1892-- You may be able to write your own handler.\n--1892-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1892-- Nevertheless we consider this a bug. Please report\n--1892-- it at http://valgrind.org/support/bug_reports.html.\n--1892-- WARNING: unhandled riscv64-linux syscall: 258\n--1892-- You may be able to write your own handler.\n--1892-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1892-- Nevertheless we consider this a bug. Please report\n--1892-- it at http://valgrind.org/support/bug_reports.html.\n--1892-- WARNING: unhandled riscv64-linux syscall: 258\n--1892-- You may be able to write your own handler.\n--1892-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1892-- Nevertheless we consider this a bug. Please report\n--1892-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 79: failed 'https://example.com?utm_source=tracker&monkey=123' --sort-query --- stdout --- expected: 'https://example.com/?monkey=123&utm_source=tracker\n' got: 'https://example.com/?monkey=123&utm_source=tracker\n' --- stderr --- expected: '' got: '--1900-- WARNING: unhandled riscv64-linux syscall: 258\n--1900-- You may be able to write your own handler.\n--1900-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1900-- Nevertheless we consider this a bug. Please report\n--1900-- it at http://valgrind.org/support/bug_reports.html.\n--1900-- WARNING: unhandled riscv64-linux syscall: 258\n--1900-- You may be able to write your own handler.\n--1900-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1900-- Nevertheless we consider this a bug. Please report\n--1900-- it at http://valgrind.org/support/bug_reports.html.\n--1900-- WARNING: unhandled riscv64-linux syscall: 258\n--1900-- You may be able to write your own handler.\n--1900-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1900-- Nevertheless we consider this a bug. Please report\n--1900-- it at http://valgrind.org/support/bug_reports.html.\n--1900-- WARNING: unhandled riscv64-linux syscall: 258\n--1900-- You may be able to write your own handler.\n--1900-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1900-- Nevertheless we consider this a bug. Please report\n--1900-- it at http://valgrind.org/support/bug_reports.html.\n--1900-- WARNING: unhandled riscv64-linux syscall: 258\n--1900-- You may be able to write your own handler.\n--1900-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1900-- Nevertheless we consider this a bug. Please report\n--1900-- it at http://valgrind.org/support/bug_reports.html.\n--1900-- WARNING: unhandled riscv64-linux syscall: 258\n--1900-- You may be able to write your own handler.\n--1900-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1900-- Nevertheless we consider this a bug. Please report\n--1900-- it at http://valgrind.org/support/bug_reports.html.\n--1900-- WARNING: unhandled riscv64-linux syscall: 258\n--1900-- You may be able to write your own handler.\n--1900-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1900-- Nevertheless we consider this a bug. Please report\n--1900-- it at http://valgrind.org/support/bug_reports.html.\n--1900-- WARNING: unhandled riscv64-linux syscall: 258\n--1900-- You may be able to write your own handler.\n--1900-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1900-- Nevertheless we consider this a bug. Please report\n--1900-- it at http://valgrind.org/support/bug_reports.html.\n--1900-- WARNING: unhandled riscv64-linux syscall: 258\n--1900-- You may be able to write your own handler.\n--1900-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1900-- Nevertheless we consider this a bug. Please report\n--1900-- it at http://valgrind.org/support/bug_reports.html.\n--1900-- WARNING: unhandled riscv64-linux syscall: 258\n--1900-- You may be able to write your own handler.\n--1900-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1900-- Nevertheless we consider this a bug. Please report\n--1900-- it at http://valgrind.org/support/bug_reports.html.\n--1900-- WARNING: unhandled riscv64-linux syscall: 258\n--1900-- You may be able to write your own handler.\n--1900-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1900-- Nevertheless we consider this a bug. Please report\n--1900-- it at http://valgrind.org/support/bug_reports.html.\n--1900-- WARNING: unhandled riscv64-linux syscall: 258\n--1900-- You may be able to write your own handler.\n--1900-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1900-- Nevertheless we consider this a bug. Please report\n--1900-- it at http://valgrind.org/support/bug_reports.html.\n--1900-- WARNING: unhandled riscv64-linux syscall: 258\n--1900-- You may be able to write your own handler.\n--1900-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1900-- Nevertheless we consider this a bug. Please report\n--1900-- it at http://valgrind.org/support/bug_reports.html.\n--1900-- WARNING: unhandled riscv64-linux syscall: 258\n--1900-- You may be able to write your own handler.\n--1900-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1900-- Nevertheless we consider this a bug. Please report\n--1900-- it at http://valgrind.org/support/bug_reports.html.\n--1900-- WARNING: unhandled riscv64-linux syscall: 258\n--1900-- You may be able to write your own handler.\n--1900-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1900-- Nevertheless we consider this a bug. Please report\n--1900-- it at http://valgrind.org/support/bug_reports.html.\n--1900-- WARNING: unhandled riscv64-linux syscall: 258\n--1900-- You may be able to write your own handler.\n--1900-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1900-- Nevertheless we consider this a bug. Please report\n--1900-- it at http://valgrind.org/support/bug_reports.html.\n--1900-- WARNING: unhandled riscv64-linux syscall: 258\n--1900-- You may be able to write your own handler.\n--1900-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1900-- Nevertheless we consider this a bug. Please report\n--1900-- it at http://valgrind.org/support/bug_reports.html.\n--1900-- WARNING: unhandled riscv64-linux syscall: 258\n--1900-- You may be able to write your own handler.\n--1900-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1900-- Nevertheless we consider this a bug. Please report\n--1900-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 80: failed 'https://example.com?a=b&c=d&' --sort-query --- stdout --- expected: 'https://example.com/?a=b&c=d\n' got: 'https://example.com/?a=b&c=d\n' --- stderr --- expected: '' got: '--1908-- WARNING: unhandled riscv64-linux syscall: 258\n--1908-- You may be able to write your own handler.\n--1908-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1908-- Nevertheless we consider this a bug. Please report\n--1908-- it at http://valgrind.org/support/bug_reports.html.\n--1908-- WARNING: unhandled riscv64-linux syscall: 258\n--1908-- You may be able to write your own handler.\n--1908-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1908-- Nevertheless we consider this a bug. Please report\n--1908-- it at http://valgrind.org/support/bug_reports.html.\n--1908-- WARNING: unhandled riscv64-linux syscall: 258\n--1908-- You may be able to write your own handler.\n--1908-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1908-- Nevertheless we consider this a bug. Please report\n--1908-- it at http://valgrind.org/support/bug_reports.html.\n--1908-- WARNING: unhandled riscv64-linux syscall: 258\n--1908-- You may be able to write your own handler.\n--1908-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1908-- Nevertheless we consider this a bug. Please report\n--1908-- it at http://valgrind.org/support/bug_reports.html.\n--1908-- WARNING: unhandled riscv64-linux syscall: 258\n--1908-- You may be able to write your own handler.\n--1908-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1908-- Nevertheless we consider this a bug. Please report\n--1908-- it at http://valgrind.org/support/bug_reports.html.\n--1908-- WARNING: unhandled riscv64-linux syscall: 258\n--1908-- You may be able to write your own handler.\n--1908-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1908-- Nevertheless we consider this a bug. Please report\n--1908-- it at http://valgrind.org/support/bug_reports.html.\n--1908-- WARNING: unhandled riscv64-linux syscall: 258\n--1908-- You may be able to write your own handler.\n--1908-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1908-- Nevertheless we consider this a bug. Please report\n--1908-- it at http://valgrind.org/support/bug_reports.html.\n--1908-- WARNING: unhandled riscv64-linux syscall: 258\n--1908-- You may be able to write your own handler.\n--1908-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1908-- Nevertheless we consider this a bug. Please report\n--1908-- it at http://valgrind.org/support/bug_reports.html.\n--1908-- WARNING: unhandled riscv64-linux syscall: 258\n--1908-- You may be able to write your own handler.\n--1908-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1908-- Nevertheless we consider this a bug. Please report\n--1908-- it at http://valgrind.org/support/bug_reports.html.\n--1908-- WARNING: unhandled riscv64-linux syscall: 258\n--1908-- You may be able to write your own handler.\n--1908-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1908-- Nevertheless we consider this a bug. Please report\n--1908-- it at http://valgrind.org/support/bug_reports.html.\n--1908-- WARNING: unhandled riscv64-linux syscall: 258\n--1908-- You may be able to write your own handler.\n--1908-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1908-- Nevertheless we consider this a bug. Please report\n--1908-- it at http://valgrind.org/support/bug_reports.html.\n--1908-- WARNING: unhandled riscv64-linux syscall: 258\n--1908-- You may be able to write your own handler.\n--1908-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1908-- Nevertheless we consider this a bug. Please report\n--1908-- it at http://valgrind.org/support/bug_reports.html.\n--1908-- WARNING: unhandled riscv64-linux syscall: 258\n--1908-- You may be able to write your own handler.\n--1908-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1908-- Nevertheless we consider this a bug. Please report\n--1908-- it at http://valgrind.org/support/bug_reports.html.\n--1908-- WARNING: unhandled riscv64-linux syscall: 258\n--1908-- You may be able to write your own handler.\n--1908-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1908-- Nevertheless we consider this a bug. Please report\n--1908-- it at http://valgrind.org/support/bug_reports.html.\n--1908-- WARNING: unhandled riscv64-linux syscall: 258\n--1908-- You may be able to write your own handler.\n--1908-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1908-- Nevertheless we consider this a bug. Please report\n--1908-- it at http://valgrind.org/support/bug_reports.html.\n--1908-- WARNING: unhandled riscv64-linux syscall: 258\n--1908-- You may be able to write your own handler.\n--1908-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1908-- Nevertheless we consider this a bug. Please report\n--1908-- it at http://valgrind.org/support/bug_reports.html.\n--1908-- WARNING: unhandled riscv64-linux syscall: 258\n--1908-- You may be able to write your own handler.\n--1908-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1908-- Nevertheless we consider this a bug. Please report\n--1908-- it at http://valgrind.org/support/bug_reports.html.\n--1908-- WARNING: unhandled riscv64-linux syscall: 258\n--1908-- You may be able to write your own handler.\n--1908-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1908-- Nevertheless we consider this a bug. Please report\n--1908-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 81: failed 'https://example.com?a=b&c=d&' --sort-query --trim query=a --- stdout --- expected: 'https://example.com/?c=d\n' got: 'https://example.com/?c=d\n' --- stderr --- expected: '' got: '--1916-- WARNING: unhandled riscv64-linux syscall: 258\n--1916-- You may be able to write your own handler.\n--1916-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1916-- Nevertheless we consider this a bug. Please report\n--1916-- it at http://valgrind.org/support/bug_reports.html.\n--1916-- WARNING: unhandled riscv64-linux syscall: 258\n--1916-- You may be able to write your own handler.\n--1916-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1916-- Nevertheless we consider this a bug. Please report\n--1916-- it at http://valgrind.org/support/bug_reports.html.\n--1916-- WARNING: unhandled riscv64-linux syscall: 258\n--1916-- You may be able to write your own handler.\n--1916-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1916-- Nevertheless we consider this a bug. Please report\n--1916-- it at http://valgrind.org/support/bug_reports.html.\n--1916-- WARNING: unhandled riscv64-linux syscall: 258\n--1916-- You may be able to write your own handler.\n--1916-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1916-- Nevertheless we consider this a bug. Please report\n--1916-- it at http://valgrind.org/support/bug_reports.html.\n--1916-- WARNING: unhandled riscv64-linux syscall: 258\n--1916-- You may be able to write your own handler.\n--1916-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1916-- Nevertheless we consider this a bug. Please report\n--1916-- it at http://valgrind.org/support/bug_reports.html.\n--1916-- WARNING: unhandled riscv64-linux syscall: 258\n--1916-- You may be able to write your own handler.\n--1916-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1916-- Nevertheless we consider this a bug. Please report\n--1916-- it at http://valgrind.org/support/bug_reports.html.\n--1916-- WARNING: unhandled riscv64-linux syscall: 258\n--1916-- You may be able to write your own handler.\n--1916-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1916-- Nevertheless we consider this a bug. Please report\n--1916-- it at http://valgrind.org/support/bug_reports.html.\n--1916-- WARNING: unhandled riscv64-linux syscall: 258\n--1916-- You may be able to write your own handler.\n--1916-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1916-- Nevertheless we consider this a bug. Please report\n--1916-- it at http://valgrind.org/support/bug_reports.html.\n--1916-- WARNING: unhandled riscv64-linux syscall: 258\n--1916-- You may be able to write your own handler.\n--1916-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1916-- Nevertheless we consider this a bug. Please report\n--1916-- it at http://valgrind.org/support/bug_reports.html.\n--1916-- WARNING: unhandled riscv64-linux syscall: 258\n--1916-- You may be able to write your own handler.\n--1916-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1916-- Nevertheless we consider this a bug. Please report\n--1916-- it at http://valgrind.org/support/bug_reports.html.\n--1916-- WARNING: unhandled riscv64-linux syscall: 258\n--1916-- You may be able to write your own handler.\n--1916-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1916-- Nevertheless we consider this a bug. Please report\n--1916-- it at http://valgrind.org/support/bug_reports.html.\n--1916-- WARNING: unhandled riscv64-linux syscall: 258\n--1916-- You may be able to write your own handler.\n--1916-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1916-- Nevertheless we consider this a bug. Please report\n--1916-- it at http://valgrind.org/support/bug_reports.html.\n--1916-- WARNING: unhandled riscv64-linux syscall: 258\n--1916-- You may be able to write your own handler.\n--1916-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1916-- Nevertheless we consider this a bug. Please report\n--1916-- it at http://valgrind.org/support/bug_reports.html.\n--1916-- WARNING: unhandled riscv64-linux syscall: 258\n--1916-- You may be able to write your own handler.\n--1916-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1916-- Nevertheless we consider this a bug. Please report\n--1916-- it at http://valgrind.org/support/bug_reports.html.\n--1916-- WARNING: unhandled riscv64-linux syscall: 258\n--1916-- You may be able to write your own handler.\n--1916-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1916-- Nevertheless we consider this a bug. Please report\n--1916-- it at http://valgrind.org/support/bug_reports.html.\n--1916-- WARNING: unhandled riscv64-linux syscall: 258\n--1916-- You may be able to write your own handler.\n--1916-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1916-- Nevertheless we consider this a bug. Please report\n--1916-- it at http://valgrind.org/support/bug_reports.html.\n--1916-- WARNING: unhandled riscv64-linux syscall: 258\n--1916-- You may be able to write your own handler.\n--1916-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1916-- Nevertheless we consider this a bug. Please report\n--1916-- it at http://valgrind.org/support/bug_reports.html.\n--1916-- WARNING: unhandled riscv64-linux syscall: 258\n--1916-- You may be able to write your own handler.\n--1916-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1916-- Nevertheless we consider this a bug. Please report\n--1916-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 82: failed example.com:29 --set port= --- stdout --- expected: 'http://example.com/\n' got: 'http://example.com/\n' --- stderr --- expected: '' got: '--1924-- WARNING: unhandled riscv64-linux syscall: 258\n--1924-- You may be able to write your own handler.\n--1924-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1924-- Nevertheless we consider this a bug. Please report\n--1924-- it at http://valgrind.org/support/bug_reports.html.\n--1924-- WARNING: unhandled riscv64-linux syscall: 258\n--1924-- You may be able to write your own handler.\n--1924-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1924-- Nevertheless we consider this a bug. Please report\n--1924-- it at http://valgrind.org/support/bug_reports.html.\n--1924-- WARNING: unhandled riscv64-linux syscall: 258\n--1924-- You may be able to write your own handler.\n--1924-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1924-- Nevertheless we consider this a bug. Please report\n--1924-- it at http://valgrind.org/support/bug_reports.html.\n--1924-- WARNING: unhandled riscv64-linux syscall: 258\n--1924-- You may be able to write your own handler.\n--1924-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1924-- Nevertheless we consider this a bug. Please report\n--1924-- it at http://valgrind.org/support/bug_reports.html.\n--1924-- WARNING: unhandled riscv64-linux syscall: 258\n--1924-- You may be able to write your own handler.\n--1924-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1924-- Nevertheless we consider this a bug. Please report\n--1924-- it at http://valgrind.org/support/bug_reports.html.\n--1924-- WARNING: unhandled riscv64-linux syscall: 258\n--1924-- You may be able to write your own handler.\n--1924-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1924-- Nevertheless we consider this a bug. Please report\n--1924-- it at http://valgrind.org/support/bug_reports.html.\n--1924-- WARNING: unhandled riscv64-linux syscall: 258\n--1924-- You may be able to write your own handler.\n--1924-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1924-- Nevertheless we consider this a bug. Please report\n--1924-- it at http://valgrind.org/support/bug_reports.html.\n--1924-- WARNING: unhandled riscv64-linux syscall: 258\n--1924-- You may be able to write your own handler.\n--1924-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1924-- Nevertheless we consider this a bug. Please report\n--1924-- it at http://valgrind.org/support/bug_reports.html.\n--1924-- WARNING: unhandled riscv64-linux syscall: 258\n--1924-- You may be able to write your own handler.\n--1924-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1924-- Nevertheless we consider this a bug. Please report\n--1924-- it at http://valgrind.org/support/bug_reports.html.\n--1924-- WARNING: unhandled riscv64-linux syscall: 258\n--1924-- You may be able to write your own handler.\n--1924-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1924-- Nevertheless we consider this a bug. Please report\n--1924-- it at http://valgrind.org/support/bug_reports.html.\n--1924-- WARNING: unhandled riscv64-linux syscall: 258\n--1924-- You may be able to write your own handler.\n--1924-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1924-- Nevertheless we consider this a bug. Please report\n--1924-- it at http://valgrind.org/support/bug_reports.html.\n--1924-- WARNING: unhandled riscv64-linux syscall: 258\n--1924-- You may be able to write your own handler.\n--1924-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1924-- Nevertheless we consider this a bug. Please report\n--1924-- it at http://valgrind.org/support/bug_reports.html.\n--1924-- WARNING: unhandled riscv64-linux syscall: 258\n--1924-- You may be able to write your own handler.\n--1924-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1924-- Nevertheless we consider this a bug. Please report\n--1924-- it at http://valgrind.org/support/bug_reports.html.\n--1924-- WARNING: unhandled riscv64-linux syscall: 258\n--1924-- You may be able to write your own handler.\n--1924-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1924-- Nevertheless we consider this a bug. Please report\n--1924-- it at http://valgrind.org/support/bug_reports.html.\n--1924-- WARNING: unhandled riscv64-linux syscall: 258\n--1924-- You may be able to write your own handler.\n--1924-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1924-- Nevertheless we consider this a bug. Please report\n--1924-- it at http://valgrind.org/support/bug_reports.html.\n--1924-- WARNING: unhandled riscv64-linux syscall: 258\n--1924-- You may be able to write your own handler.\n--1924-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1924-- Nevertheless we consider this a bug. Please report\n--1924-- it at http://valgrind.org/support/bug_reports.html.\n--1924-- WARNING: unhandled riscv64-linux syscall: 258\n--1924-- You may be able to write your own handler.\n--1924-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1924-- Nevertheless we consider this a bug. Please report\n--1924-- it at http://valgrind.org/support/bug_reports.html.\n--1924-- WARNING: unhandled riscv64-linux syscall: 258\n--1924-- You may be able to write your own handler.\n--1924-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1924-- Nevertheless we consider this a bug. Please report\n--1924-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 83: failed --url HTTPS://example.com --- stdout --- expected: 'https://example.com/\n' got: 'https://example.com/\n' --- stderr --- expected: '' got: '--1932-- WARNING: unhandled riscv64-linux syscall: 258\n--1932-- You may be able to write your own handler.\n--1932-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1932-- Nevertheless we consider this a bug. Please report\n--1932-- it at http://valgrind.org/support/bug_reports.html.\n--1932-- WARNING: unhandled riscv64-linux syscall: 258\n--1932-- You may be able to write your own handler.\n--1932-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1932-- Nevertheless we consider this a bug. Please report\n--1932-- it at http://valgrind.org/support/bug_reports.html.\n--1932-- WARNING: unhandled riscv64-linux syscall: 258\n--1932-- You may be able to write your own handler.\n--1932-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1932-- Nevertheless we consider this a bug. Please report\n--1932-- it at http://valgrind.org/support/bug_reports.html.\n--1932-- WARNING: unhandled riscv64-linux syscall: 258\n--1932-- You may be able to write your own handler.\n--1932-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1932-- Nevertheless we consider this a bug. Please report\n--1932-- it at http://valgrind.org/support/bug_reports.html.\n--1932-- WARNING: unhandled riscv64-linux syscall: 258\n--1932-- You may be able to write your own handler.\n--1932-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1932-- Nevertheless we consider this a bug. Please report\n--1932-- it at http://valgrind.org/support/bug_reports.html.\n--1932-- WARNING: unhandled riscv64-linux syscall: 258\n--1932-- You may be able to write your own handler.\n--1932-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1932-- Nevertheless we consider this a bug. Please report\n--1932-- it at http://valgrind.org/support/bug_reports.html.\n--1932-- WARNING: unhandled riscv64-linux syscall: 258\n--1932-- You may be able to write your own handler.\n--1932-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1932-- Nevertheless we consider this a bug. Please report\n--1932-- it at http://valgrind.org/support/bug_reports.html.\n--1932-- WARNING: unhandled riscv64-linux syscall: 258\n--1932-- You may be able to write your own handler.\n--1932-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1932-- Nevertheless we consider this a bug. Please report\n--1932-- it at http://valgrind.org/support/bug_reports.html.\n--1932-- WARNING: unhandled riscv64-linux syscall: 258\n--1932-- You may be able to write your own handler.\n--1932-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1932-- Nevertheless we consider this a bug. Please report\n--1932-- it at http://valgrind.org/support/bug_reports.html.\n--1932-- WARNING: unhandled riscv64-linux syscall: 258\n--1932-- You may be able to write your own handler.\n--1932-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1932-- Nevertheless we consider this a bug. Please report\n--1932-- it at http://valgrind.org/support/bug_reports.html.\n--1932-- WARNING: unhandled riscv64-linux syscall: 258\n--1932-- You may be able to write your own handler.\n--1932-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1932-- Nevertheless we consider this a bug. Please report\n--1932-- it at http://valgrind.org/support/bug_reports.html.\n--1932-- WARNING: unhandled riscv64-linux syscall: 258\n--1932-- You may be able to write your own handler.\n--1932-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1932-- Nevertheless we consider this a bug. Please report\n--1932-- it at http://valgrind.org/support/bug_reports.html.\n--1932-- WARNING: unhandled riscv64-linux syscall: 258\n--1932-- You may be able to write your own handler.\n--1932-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1932-- Nevertheless we consider this a bug. Please report\n--1932-- it at http://valgrind.org/support/bug_reports.html.\n--1932-- WARNING: unhandled riscv64-linux syscall: 258\n--1932-- You may be able to write your own handler.\n--1932-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1932-- Nevertheless we consider this a bug. Please report\n--1932-- it at http://valgrind.org/support/bug_reports.html.\n--1932-- WARNING: unhandled riscv64-linux syscall: 258\n--1932-- You may be able to write your own handler.\n--1932-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1932-- Nevertheless we consider this a bug. Please report\n--1932-- it at http://valgrind.org/support/bug_reports.html.\n--1932-- WARNING: unhandled riscv64-linux syscall: 258\n--1932-- You may be able to write your own handler.\n--1932-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1932-- Nevertheless we consider this a bug. Please report\n--1932-- it at http://valgrind.org/support/bug_reports.html.\n--1932-- WARNING: unhandled riscv64-linux syscall: 258\n--1932-- You may be able to write your own handler.\n--1932-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1932-- Nevertheless we consider this a bug. Please report\n--1932-- it at http://valgrind.org/support/bug_reports.html.\n--1932-- WARNING: unhandled riscv64-linux syscall: 258\n--1932-- You may be able to write your own handler.\n--1932-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1932-- Nevertheless we consider this a bug. Please report\n--1932-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 84: failed --url https://EXAMPLE.com --- stdout --- expected: 'https://EXAMPLE.com/\n' got: 'https://EXAMPLE.com/\n' --- stderr --- expected: '' got: '--1940-- WARNING: unhandled riscv64-linux syscall: 258\n--1940-- You may be able to write your own handler.\n--1940-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1940-- Nevertheless we consider this a bug. Please report\n--1940-- it at http://valgrind.org/support/bug_reports.html.\n--1940-- WARNING: unhandled riscv64-linux syscall: 258\n--1940-- You may be able to write your own handler.\n--1940-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1940-- Nevertheless we consider this a bug. Please report\n--1940-- it at http://valgrind.org/support/bug_reports.html.\n--1940-- WARNING: unhandled riscv64-linux syscall: 258\n--1940-- You may be able to write your own handler.\n--1940-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1940-- Nevertheless we consider this a bug. Please report\n--1940-- it at http://valgrind.org/support/bug_reports.html.\n--1940-- WARNING: unhandled riscv64-linux syscall: 258\n--1940-- You may be able to write your own handler.\n--1940-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1940-- Nevertheless we consider this a bug. Please report\n--1940-- it at http://valgrind.org/support/bug_reports.html.\n--1940-- WARNING: unhandled riscv64-linux syscall: 258\n--1940-- You may be able to write your own handler.\n--1940-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1940-- Nevertheless we consider this a bug. Please report\n--1940-- it at http://valgrind.org/support/bug_reports.html.\n--1940-- WARNING: unhandled riscv64-linux syscall: 258\n--1940-- You may be able to write your own handler.\n--1940-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1940-- Nevertheless we consider this a bug. Please report\n--1940-- it at http://valgrind.org/support/bug_reports.html.\n--1940-- WARNING: unhandled riscv64-linux syscall: 258\n--1940-- You may be able to write your own handler.\n--1940-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1940-- Nevertheless we consider this a bug. Please report\n--1940-- it at http://valgrind.org/support/bug_reports.html.\n--1940-- WARNING: unhandled riscv64-linux syscall: 258\n--1940-- You may be able to write your own handler.\n--1940-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1940-- Nevertheless we consider this a bug. Please report\n--1940-- it at http://valgrind.org/support/bug_reports.html.\n--1940-- WARNING: unhandled riscv64-linux syscall: 258\n--1940-- You may be able to write your own handler.\n--1940-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1940-- Nevertheless we consider this a bug. Please report\n--1940-- it at http://valgrind.org/support/bug_reports.html.\n--1940-- WARNING: unhandled riscv64-linux syscall: 258\n--1940-- You may be able to write your own handler.\n--1940-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1940-- Nevertheless we consider this a bug. Please report\n--1940-- it at http://valgrind.org/support/bug_reports.html.\n--1940-- WARNING: unhandled riscv64-linux syscall: 258\n--1940-- You may be able to write your own handler.\n--1940-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1940-- Nevertheless we consider this a bug. Please report\n--1940-- it at http://valgrind.org/support/bug_reports.html.\n--1940-- WARNING: unhandled riscv64-linux syscall: 258\n--1940-- You may be able to write your own handler.\n--1940-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1940-- Nevertheless we consider this a bug. Please report\n--1940-- it at http://valgrind.org/support/bug_reports.html.\n--1940-- WARNING: unhandled riscv64-linux syscall: 258\n--1940-- You may be able to write your own handler.\n--1940-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1940-- Nevertheless we consider this a bug. Please report\n--1940-- it at http://valgrind.org/support/bug_reports.html.\n--1940-- WARNING: unhandled riscv64-linux syscall: 258\n--1940-- You may be able to write your own handler.\n--1940-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1940-- Nevertheless we consider this a bug. Please report\n--1940-- it at http://valgrind.org/support/bug_reports.html.\n--1940-- WARNING: unhandled riscv64-linux syscall: 258\n--1940-- You may be able to write your own handler.\n--1940-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1940-- Nevertheless we consider this a bug. Please report\n--1940-- it at http://valgrind.org/support/bug_reports.html.\n--1940-- WARNING: unhandled riscv64-linux syscall: 258\n--1940-- You may be able to write your own handler.\n--1940-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1940-- Nevertheless we consider this a bug. Please report\n--1940-- it at http://valgrind.org/support/bug_reports.html.\n--1940-- WARNING: unhandled riscv64-linux syscall: 258\n--1940-- You may be able to write your own handler.\n--1940-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1940-- Nevertheless we consider this a bug. Please report\n--1940-- it at http://valgrind.org/support/bug_reports.html.\n--1940-- WARNING: unhandled riscv64-linux syscall: 258\n--1940-- You may be able to write your own handler.\n--1940-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1940-- Nevertheless we consider this a bug. Please report\n--1940-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 85: failed --url https://example.com/FOO/BAR --- stdout --- expected: 'https://example.com/FOO/BAR\n' got: 'https://example.com/FOO/BAR\n' --- stderr --- expected: '' got: '--1948-- WARNING: unhandled riscv64-linux syscall: 258\n--1948-- You may be able to write your own handler.\n--1948-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1948-- Nevertheless we consider this a bug. Please report\n--1948-- it at http://valgrind.org/support/bug_reports.html.\n--1948-- WARNING: unhandled riscv64-linux syscall: 258\n--1948-- You may be able to write your own handler.\n--1948-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1948-- Nevertheless we consider this a bug. Please report\n--1948-- it at http://valgrind.org/support/bug_reports.html.\n--1948-- WARNING: unhandled riscv64-linux syscall: 258\n--1948-- You may be able to write your own handler.\n--1948-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1948-- Nevertheless we consider this a bug. Please report\n--1948-- it at http://valgrind.org/support/bug_reports.html.\n--1948-- WARNING: unhandled riscv64-linux syscall: 258\n--1948-- You may be able to write your own handler.\n--1948-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1948-- Nevertheless we consider this a bug. Please report\n--1948-- it at http://valgrind.org/support/bug_reports.html.\n--1948-- WARNING: unhandled riscv64-linux syscall: 258\n--1948-- You may be able to write your own handler.\n--1948-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1948-- Nevertheless we consider this a bug. Please report\n--1948-- it at http://valgrind.org/support/bug_reports.html.\n--1948-- WARNING: unhandled riscv64-linux syscall: 258\n--1948-- You may be able to write your own handler.\n--1948-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1948-- Nevertheless we consider this a bug. Please report\n--1948-- it at http://valgrind.org/support/bug_reports.html.\n--1948-- WARNING: unhandled riscv64-linux syscall: 258\n--1948-- You may be able to write your own handler.\n--1948-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1948-- Nevertheless we consider this a bug. Please report\n--1948-- it at http://valgrind.org/support/bug_reports.html.\n--1948-- WARNING: unhandled riscv64-linux syscall: 258\n--1948-- You may be able to write your own handler.\n--1948-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1948-- Nevertheless we consider this a bug. Please report\n--1948-- it at http://valgrind.org/support/bug_reports.html.\n--1948-- WARNING: unhandled riscv64-linux syscall: 258\n--1948-- You may be able to write your own handler.\n--1948-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1948-- Nevertheless we consider this a bug. Please report\n--1948-- it at http://valgrind.org/support/bug_reports.html.\n--1948-- WARNING: unhandled riscv64-linux syscall: 258\n--1948-- You may be able to write your own handler.\n--1948-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1948-- Nevertheless we consider this a bug. Please report\n--1948-- it at http://valgrind.org/support/bug_reports.html.\n--1948-- WARNING: unhandled riscv64-linux syscall: 258\n--1948-- You may be able to write your own handler.\n--1948-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1948-- Nevertheless we consider this a bug. Please report\n--1948-- it at http://valgrind.org/support/bug_reports.html.\n--1948-- WARNING: unhandled riscv64-linux syscall: 258\n--1948-- You may be able to write your own handler.\n--1948-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1948-- Nevertheless we consider this a bug. Please report\n--1948-- it at http://valgrind.org/support/bug_reports.html.\n--1948-- WARNING: unhandled riscv64-linux syscall: 258\n--1948-- You may be able to write your own handler.\n--1948-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1948-- Nevertheless we consider this a bug. Please report\n--1948-- it at http://valgrind.org/support/bug_reports.html.\n--1948-- WARNING: unhandled riscv64-linux syscall: 258\n--1948-- You may be able to write your own handler.\n--1948-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1948-- Nevertheless we consider this a bug. Please report\n--1948-- it at http://valgrind.org/support/bug_reports.html.\n--1948-- WARNING: unhandled riscv64-linux syscall: 258\n--1948-- You may be able to write your own handler.\n--1948-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1948-- Nevertheless we consider this a bug. Please report\n--1948-- it at http://valgrind.org/support/bug_reports.html.\n--1948-- WARNING: unhandled riscv64-linux syscall: 258\n--1948-- You may be able to write your own handler.\n--1948-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1948-- Nevertheless we consider this a bug. Please report\n--1948-- it at http://valgrind.org/support/bug_reports.html.\n--1948-- WARNING: unhandled riscv64-linux syscall: 258\n--1948-- You may be able to write your own handler.\n--1948-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1948-- Nevertheless we consider this a bug. Please report\n--1948-- it at http://valgrind.org/support/bug_reports.html.\n--1948-- WARNING: unhandled riscv64-linux syscall: 258\n--1948-- You may be able to write your own handler.\n--1948-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1948-- Nevertheless we consider this a bug. Please report\n--1948-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 86: failed --url '[2001:0db8:0000:0000:0000:ff00:0042:8329]' --- stdout --- expected: 'http://[2001:db8::ff00:42:8329]/\n' got: 'http://[2001:db8::ff00:42:8329]/\n' --- stderr --- expected: '' got: '--1956-- WARNING: unhandled riscv64-linux syscall: 258\n--1956-- You may be able to write your own handler.\n--1956-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1956-- Nevertheless we consider this a bug. Please report\n--1956-- it at http://valgrind.org/support/bug_reports.html.\n--1956-- WARNING: unhandled riscv64-linux syscall: 258\n--1956-- You may be able to write your own handler.\n--1956-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1956-- Nevertheless we consider this a bug. Please report\n--1956-- it at http://valgrind.org/support/bug_reports.html.\n--1956-- WARNING: unhandled riscv64-linux syscall: 258\n--1956-- You may be able to write your own handler.\n--1956-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1956-- Nevertheless we consider this a bug. Please report\n--1956-- it at http://valgrind.org/support/bug_reports.html.\n--1956-- WARNING: unhandled riscv64-linux syscall: 258\n--1956-- You may be able to write your own handler.\n--1956-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1956-- Nevertheless we consider this a bug. Please report\n--1956-- it at http://valgrind.org/support/bug_reports.html.\n--1956-- WARNING: unhandled riscv64-linux syscall: 258\n--1956-- You may be able to write your own handler.\n--1956-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1956-- Nevertheless we consider this a bug. Please report\n--1956-- it at http://valgrind.org/support/bug_reports.html.\n--1956-- WARNING: unhandled riscv64-linux syscall: 258\n--1956-- You may be able to write your own handler.\n--1956-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1956-- Nevertheless we consider this a bug. Please report\n--1956-- it at http://valgrind.org/support/bug_reports.html.\n--1956-- WARNING: unhandled riscv64-linux syscall: 258\n--1956-- You may be able to write your own handler.\n--1956-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1956-- Nevertheless we consider this a bug. Please report\n--1956-- it at http://valgrind.org/support/bug_reports.html.\n--1956-- WARNING: unhandled riscv64-linux syscall: 258\n--1956-- You may be able to write your own handler.\n--1956-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1956-- Nevertheless we consider this a bug. Please report\n--1956-- it at http://valgrind.org/support/bug_reports.html.\n--1956-- WARNING: unhandled riscv64-linux syscall: 258\n--1956-- You may be able to write your own handler.\n--1956-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1956-- Nevertheless we consider this a bug. Please report\n--1956-- it at http://valgrind.org/support/bug_reports.html.\n--1956-- WARNING: unhandled riscv64-linux syscall: 258\n--1956-- You may be able to write your own handler.\n--1956-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1956-- Nevertheless we consider this a bug. Please report\n--1956-- it at http://valgrind.org/support/bug_reports.html.\n--1956-- WARNING: unhandled riscv64-linux syscall: 258\n--1956-- You may be able to write your own handler.\n--1956-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1956-- Nevertheless we consider this a bug. Please report\n--1956-- it at http://valgrind.org/support/bug_reports.html.\n--1956-- WARNING: unhandled riscv64-linux syscall: 258\n--1956-- You may be able to write your own handler.\n--1956-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1956-- Nevertheless we consider this a bug. Please report\n--1956-- it at http://valgrind.org/support/bug_reports.html.\n--1956-- WARNING: unhandled riscv64-linux syscall: 258\n--1956-- You may be able to write your own handler.\n--1956-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1956-- Nevertheless we consider this a bug. Please report\n--1956-- it at http://valgrind.org/support/bug_reports.html.\n--1956-- WARNING: unhandled riscv64-linux syscall: 258\n--1956-- You may be able to write your own handler.\n--1956-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1956-- Nevertheless we consider this a bug. Please report\n--1956-- it at http://valgrind.org/support/bug_reports.html.\n--1956-- WARNING: unhandled riscv64-linux syscall: 258\n--1956-- You may be able to write your own handler.\n--1956-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1956-- Nevertheless we consider this a bug. Please report\n--1956-- it at http://valgrind.org/support/bug_reports.html.\n--1956-- WARNING: unhandled riscv64-linux syscall: 258\n--1956-- You may be able to write your own handler.\n--1956-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1956-- Nevertheless we consider this a bug. Please report\n--1956-- it at http://valgrind.org/support/bug_reports.html.\n--1956-- WARNING: unhandled riscv64-linux syscall: 258\n--1956-- You may be able to write your own handler.\n--1956-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1956-- Nevertheless we consider this a bug. Please report\n--1956-- it at http://valgrind.org/support/bug_reports.html.\n--1956-- WARNING: unhandled riscv64-linux syscall: 258\n--1956-- You may be able to write your own handler.\n--1956-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1956-- Nevertheless we consider this a bug. Please report\n--1956-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 87: failed 'https://example.com?utm=tra%20cker:address%20=home:here=now:thisthen' --sort-query --query-separator : --- stdout --- expected: 'https://example.com/?address+=home:here=now:thisthen:utm=tra+cker\n' got: 'https://example.com/?address+=home:here=now:thisthen:utm=tra+cker\n' --- stderr --- expected: '' got: '--1964-- WARNING: unhandled riscv64-linux syscall: 258\n--1964-- You may be able to write your own handler.\n--1964-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1964-- Nevertheless we consider this a bug. Please report\n--1964-- it at http://valgrind.org/support/bug_reports.html.\n--1964-- WARNING: unhandled riscv64-linux syscall: 258\n--1964-- You may be able to write your own handler.\n--1964-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1964-- Nevertheless we consider this a bug. Please report\n--1964-- it at http://valgrind.org/support/bug_reports.html.\n--1964-- WARNING: unhandled riscv64-linux syscall: 258\n--1964-- You may be able to write your own handler.\n--1964-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1964-- Nevertheless we consider this a bug. Please report\n--1964-- it at http://valgrind.org/support/bug_reports.html.\n--1964-- WARNING: unhandled riscv64-linux syscall: 258\n--1964-- You may be able to write your own handler.\n--1964-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1964-- Nevertheless we consider this a bug. Please report\n--1964-- it at http://valgrind.org/support/bug_reports.html.\n--1964-- WARNING: unhandled riscv64-linux syscall: 258\n--1964-- You may be able to write your own handler.\n--1964-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1964-- Nevertheless we consider this a bug. Please report\n--1964-- it at http://valgrind.org/support/bug_reports.html.\n--1964-- WARNING: unhandled riscv64-linux syscall: 258\n--1964-- You may be able to write your own handler.\n--1964-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1964-- Nevertheless we consider this a bug. Please report\n--1964-- it at http://valgrind.org/support/bug_reports.html.\n--1964-- WARNING: unhandled riscv64-linux syscall: 258\n--1964-- You may be able to write your own handler.\n--1964-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1964-- Nevertheless we consider this a bug. Please report\n--1964-- it at http://valgrind.org/support/bug_reports.html.\n--1964-- WARNING: unhandled riscv64-linux syscall: 258\n--1964-- You may be able to write your own handler.\n--1964-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1964-- Nevertheless we consider this a bug. Please report\n--1964-- it at http://valgrind.org/support/bug_reports.html.\n--1964-- WARNING: unhandled riscv64-linux syscall: 258\n--1964-- You may be able to write your own handler.\n--1964-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1964-- Nevertheless we consider this a bug. Please report\n--1964-- it at http://valgrind.org/support/bug_reports.html.\n--1964-- WARNING: unhandled riscv64-linux syscall: 258\n--1964-- You may be able to write your own handler.\n--1964-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1964-- Nevertheless we consider this a bug. Please report\n--1964-- it at http://valgrind.org/support/bug_reports.html.\n--1964-- WARNING: unhandled riscv64-linux syscall: 258\n--1964-- You may be able to write your own handler.\n--1964-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1964-- Nevertheless we consider this a bug. Please report\n--1964-- it at http://valgrind.org/support/bug_reports.html.\n--1964-- WARNING: unhandled riscv64-linux syscall: 258\n--1964-- You may be able to write your own handler.\n--1964-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1964-- Nevertheless we consider this a bug. Please report\n--1964-- it at http://valgrind.org/support/bug_reports.html.\n--1964-- WARNING: unhandled riscv64-linux syscall: 258\n--1964-- You may be able to write your own handler.\n--1964-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1964-- Nevertheless we consider this a bug. Please report\n--1964-- it at http://valgrind.org/support/bug_reports.html.\n--1964-- WARNING: unhandled riscv64-linux syscall: 258\n--1964-- You may be able to write your own handler.\n--1964-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1964-- Nevertheless we consider this a bug. Please report\n--1964-- it at http://valgrind.org/support/bug_reports.html.\n--1964-- WARNING: unhandled riscv64-linux syscall: 258\n--1964-- You may be able to write your own handler.\n--1964-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1964-- Nevertheless we consider this a bug. Please report\n--1964-- it at http://valgrind.org/support/bug_reports.html.\n--1964-- WARNING: unhandled riscv64-linux syscall: 258\n--1964-- You may be able to write your own handler.\n--1964-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1964-- Nevertheless we consider this a bug. Please report\n--1964-- it at http://valgrind.org/support/bug_reports.html.\n--1964-- WARNING: unhandled riscv64-linux syscall: 258\n--1964-- You may be able to write your own handler.\n--1964-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1964-- Nevertheless we consider this a bug. Please report\n--1964-- it at http://valgrind.org/support/bug_reports.html.\n--1964-- WARNING: unhandled riscv64-linux syscall: 258\n--1964-- You may be able to write your own handler.\n--1964-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1964-- Nevertheless we consider this a bug. Please report\n--1964-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 88: failed 'foo?a=bCd=eCe=f' --query-separator C --trim query=d --- stdout --- expected: 'http://foo/?a=bCe=f\n' got: 'http://foo/?a=bCe=f\n' --- stderr --- expected: '' got: '--1972-- WARNING: unhandled riscv64-linux syscall: 258\n--1972-- You may be able to write your own handler.\n--1972-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1972-- Nevertheless we consider this a bug. Please report\n--1972-- it at http://valgrind.org/support/bug_reports.html.\n--1972-- WARNING: unhandled riscv64-linux syscall: 258\n--1972-- You may be able to write your own handler.\n--1972-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1972-- Nevertheless we consider this a bug. Please report\n--1972-- it at http://valgrind.org/support/bug_reports.html.\n--1972-- WARNING: unhandled riscv64-linux syscall: 258\n--1972-- You may be able to write your own handler.\n--1972-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1972-- Nevertheless we consider this a bug. Please report\n--1972-- it at http://valgrind.org/support/bug_reports.html.\n--1972-- WARNING: unhandled riscv64-linux syscall: 258\n--1972-- You may be able to write your own handler.\n--1972-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1972-- Nevertheless we consider this a bug. Please report\n--1972-- it at http://valgrind.org/support/bug_reports.html.\n--1972-- WARNING: unhandled riscv64-linux syscall: 258\n--1972-- You may be able to write your own handler.\n--1972-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1972-- Nevertheless we consider this a bug. Please report\n--1972-- it at http://valgrind.org/support/bug_reports.html.\n--1972-- WARNING: unhandled riscv64-linux syscall: 258\n--1972-- You may be able to write your own handler.\n--1972-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1972-- Nevertheless we consider this a bug. Please report\n--1972-- it at http://valgrind.org/support/bug_reports.html.\n--1972-- WARNING: unhandled riscv64-linux syscall: 258\n--1972-- You may be able to write your own handler.\n--1972-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1972-- Nevertheless we consider this a bug. Please report\n--1972-- it at http://valgrind.org/support/bug_reports.html.\n--1972-- WARNING: unhandled riscv64-linux syscall: 258\n--1972-- You may be able to write your own handler.\n--1972-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1972-- Nevertheless we consider this a bug. Please report\n--1972-- it at http://valgrind.org/support/bug_reports.html.\n--1972-- WARNING: unhandled riscv64-linux syscall: 258\n--1972-- You may be able to write your own handler.\n--1972-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1972-- Nevertheless we consider this a bug. Please report\n--1972-- it at http://valgrind.org/support/bug_reports.html.\n--1972-- WARNING: unhandled riscv64-linux syscall: 258\n--1972-- You may be able to write your own handler.\n--1972-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1972-- Nevertheless we consider this a bug. Please report\n--1972-- it at http://valgrind.org/support/bug_reports.html.\n--1972-- WARNING: unhandled riscv64-linux syscall: 258\n--1972-- You may be able to write your own handler.\n--1972-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1972-- Nevertheless we consider this a bug. Please report\n--1972-- it at http://valgrind.org/support/bug_reports.html.\n--1972-- WARNING: unhandled riscv64-linux syscall: 258\n--1972-- You may be able to write your own handler.\n--1972-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1972-- Nevertheless we consider this a bug. Please report\n--1972-- it at http://valgrind.org/support/bug_reports.html.\n--1972-- WARNING: unhandled riscv64-linux syscall: 258\n--1972-- You may be able to write your own handler.\n--1972-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1972-- Nevertheless we consider this a bug. Please report\n--1972-- it at http://valgrind.org/support/bug_reports.html.\n--1972-- WARNING: unhandled riscv64-linux syscall: 258\n--1972-- You may be able to write your own handler.\n--1972-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1972-- Nevertheless we consider this a bug. Please report\n--1972-- it at http://valgrind.org/support/bug_reports.html.\n--1972-- WARNING: unhandled riscv64-linux syscall: 258\n--1972-- You may be able to write your own handler.\n--1972-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1972-- Nevertheless we consider this a bug. Please report\n--1972-- it at http://valgrind.org/support/bug_reports.html.\n--1972-- WARNING: unhandled riscv64-linux syscall: 258\n--1972-- You may be able to write your own handler.\n--1972-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1972-- Nevertheless we consider this a bug. Please report\n--1972-- it at http://valgrind.org/support/bug_reports.html.\n--1972-- WARNING: unhandled riscv64-linux syscall: 258\n--1972-- You may be able to write your own handler.\n--1972-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1972-- Nevertheless we consider this a bug. Please report\n--1972-- it at http://valgrind.org/support/bug_reports.html.\n--1972-- WARNING: unhandled riscv64-linux syscall: 258\n--1972-- You may be able to write your own handler.\n--1972-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1972-- Nevertheless we consider this a bug. Please report\n--1972-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 89: failed localhost -g '{scheme} {host' --- stderr --- expected: '' got: '--1980-- WARNING: unhandled riscv64-linux syscall: 258\n--1980-- You may be able to write your own handler.\n--1980-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1980-- Nevertheless we consider this a bug. Please report\n--1980-- it at http://valgrind.org/support/bug_reports.html.\n--1980-- WARNING: unhandled riscv64-linux syscall: 258\n--1980-- You may be able to write your own handler.\n--1980-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1980-- Nevertheless we consider this a bug. Please report\n--1980-- it at http://valgrind.org/support/bug_reports.html.\n--1980-- WARNING: unhandled riscv64-linux syscall: 258\n--1980-- You may be able to write your own handler.\n--1980-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1980-- Nevertheless we consider this a bug. Please report\n--1980-- it at http://valgrind.org/support/bug_reports.html.\n--1980-- WARNING: unhandled riscv64-linux syscall: 258\n--1980-- You may be able to write your own handler.\n--1980-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1980-- Nevertheless we consider this a bug. Please report\n--1980-- it at http://valgrind.org/support/bug_reports.html.\n--1980-- WARNING: unhandled riscv64-linux syscall: 258\n--1980-- You may be able to write your own handler.\n--1980-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1980-- Nevertheless we consider this a bug. Please report\n--1980-- it at http://valgrind.org/support/bug_reports.html.\n--1980-- WARNING: unhandled riscv64-linux syscall: 258\n--1980-- You may be able to write your own handler.\n--1980-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1980-- Nevertheless we consider this a bug. Please report\n--1980-- it at http://valgrind.org/support/bug_reports.html.\n--1980-- WARNING: unhandled riscv64-linux syscall: 258\n--1980-- You may be able to write your own handler.\n--1980-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1980-- Nevertheless we consider this a bug. Please report\n--1980-- it at http://valgrind.org/support/bug_reports.html.\n--1980-- WARNING: unhandled riscv64-linux syscall: 258\n--1980-- You may be able to write your own handler.\n--1980-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1980-- Nevertheless we consider this a bug. Please report\n--1980-- it at http://valgrind.org/support/bug_reports.html.\n--1980-- WARNING: unhandled riscv64-linux syscall: 258\n--1980-- You may be able to write your own handler.\n--1980-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1980-- Nevertheless we consider this a bug. Please report\n--1980-- it at http://valgrind.org/support/bug_reports.html.\n--1980-- WARNING: unhandled riscv64-linux syscall: 258\n--1980-- You may be able to write your own handler.\n--1980-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1980-- Nevertheless we consider this a bug. Please report\n--1980-- it at http://valgrind.org/support/bug_reports.html.\n--1980-- WARNING: unhandled riscv64-linux syscall: 258\n--1980-- You may be able to write your own handler.\n--1980-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1980-- Nevertheless we consider this a bug. Please report\n--1980-- it at http://valgrind.org/support/bug_reports.html.\n--1980-- WARNING: unhandled riscv64-linux syscall: 258\n--1980-- You may be able to write your own handler.\n--1980-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1980-- Nevertheless we consider this a bug. Please report\n--1980-- it at http://valgrind.org/support/bug_reports.html.\n--1980-- WARNING: unhandled riscv64-linux syscall: 258\n--1980-- You may be able to write your own handler.\n--1980-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1980-- Nevertheless we consider this a bug. Please report\n--1980-- it at http://valgrind.org/support/bug_reports.html.\n--1980-- WARNING: unhandled riscv64-linux syscall: 258\n--1980-- You may be able to write your own handler.\n--1980-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1980-- Nevertheless we consider this a bug. Please report\n--1980-- it at http://valgrind.org/support/bug_reports.html.\n--1980-- WARNING: unhandled riscv64-linux syscall: 258\n--1980-- You may be able to write your own handler.\n--1980-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1980-- Nevertheless we consider this a bug. Please report\n--1980-- it at http://valgrind.org/support/bug_reports.html.\n--1980-- WARNING: unhandled riscv64-linux syscall: 258\n--1980-- You may be able to write your own handler.\n--1980-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1980-- Nevertheless we consider this a bug. Please report\n--1980-- it at http://valgrind.org/support/bug_reports.html.\n--1980-- WARNING: unhandled riscv64-linux syscall: 258\n--1980-- You may be able to write your own handler.\n--1980-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1980-- Nevertheless we consider this a bug. Please report\n--1980-- it at http://valgrind.org/support/bug_reports.html.\n--1980-- WARNING: unhandled riscv64-linux syscall: 258\n--1980-- You may be able to write your own handler.\n--1980-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1980-- Nevertheless we consider this a bug. Please report\n--1980-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 --- stdout --- expected: 'http {host\n' got: 'http {host\n' 90: failed localhost -g '[scheme] [host' --- stderr --- expected: '' got: '--1988-- WARNING: unhandled riscv64-linux syscall: 258\n--1988-- You may be able to write your own handler.\n--1988-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1988-- Nevertheless we consider this a bug. Please report\n--1988-- it at http://valgrind.org/support/bug_reports.html.\n--1988-- WARNING: unhandled riscv64-linux syscall: 258\n--1988-- You may be able to write your own handler.\n--1988-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1988-- Nevertheless we consider this a bug. Please report\n--1988-- it at http://valgrind.org/support/bug_reports.html.\n--1988-- WARNING: unhandled riscv64-linux syscall: 258\n--1988-- You may be able to write your own handler.\n--1988-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1988-- Nevertheless we consider this a bug. Please report\n--1988-- it at http://valgrind.org/support/bug_reports.html.\n--1988-- WARNING: unhandled riscv64-linux syscall: 258\n--1988-- You may be able to write your own handler.\n--1988-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1988-- Nevertheless we consider this a bug. Please report\n--1988-- it at http://valgrind.org/support/bug_reports.html.\n--1988-- WARNING: unhandled riscv64-linux syscall: 258\n--1988-- You may be able to write your own handler.\n--1988-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1988-- Nevertheless we consider this a bug. Please report\n--1988-- it at http://valgrind.org/support/bug_reports.html.\n--1988-- WARNING: unhandled riscv64-linux syscall: 258\n--1988-- You may be able to write your own handler.\n--1988-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1988-- Nevertheless we consider this a bug. Please report\n--1988-- it at http://valgrind.org/support/bug_reports.html.\n--1988-- WARNING: unhandled riscv64-linux syscall: 258\n--1988-- You may be able to write your own handler.\n--1988-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1988-- Nevertheless we consider this a bug. Please report\n--1988-- it at http://valgrind.org/support/bug_reports.html.\n--1988-- WARNING: unhandled riscv64-linux syscall: 258\n--1988-- You may be able to write your own handler.\n--1988-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1988-- Nevertheless we consider this a bug. Please report\n--1988-- it at http://valgrind.org/support/bug_reports.html.\n--1988-- WARNING: unhandled riscv64-linux syscall: 258\n--1988-- You may be able to write your own handler.\n--1988-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1988-- Nevertheless we consider this a bug. Please report\n--1988-- it at http://valgrind.org/support/bug_reports.html.\n--1988-- WARNING: unhandled riscv64-linux syscall: 258\n--1988-- You may be able to write your own handler.\n--1988-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1988-- Nevertheless we consider this a bug. Please report\n--1988-- it at http://valgrind.org/support/bug_reports.html.\n--1988-- WARNING: unhandled riscv64-linux syscall: 258\n--1988-- You may be able to write your own handler.\n--1988-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1988-- Nevertheless we consider this a bug. Please report\n--1988-- it at http://valgrind.org/support/bug_reports.html.\n--1988-- WARNING: unhandled riscv64-linux syscall: 258\n--1988-- You may be able to write your own handler.\n--1988-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1988-- Nevertheless we consider this a bug. Please report\n--1988-- it at http://valgrind.org/support/bug_reports.html.\n--1988-- WARNING: unhandled riscv64-linux syscall: 258\n--1988-- You may be able to write your own handler.\n--1988-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1988-- Nevertheless we consider this a bug. Please report\n--1988-- it at http://valgrind.org/support/bug_reports.html.\n--1988-- WARNING: unhandled riscv64-linux syscall: 258\n--1988-- You may be able to write your own handler.\n--1988-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1988-- Nevertheless we consider this a bug. Please report\n--1988-- it at http://valgrind.org/support/bug_reports.html.\n--1988-- WARNING: unhandled riscv64-linux syscall: 258\n--1988-- You may be able to write your own handler.\n--1988-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1988-- Nevertheless we consider this a bug. Please report\n--1988-- it at http://valgrind.org/support/bug_reports.html.\n--1988-- WARNING: unhandled riscv64-linux syscall: 258\n--1988-- You may be able to write your own handler.\n--1988-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1988-- Nevertheless we consider this a bug. Please report\n--1988-- it at http://valgrind.org/support/bug_reports.html.\n--1988-- WARNING: unhandled riscv64-linux syscall: 258\n--1988-- You may be able to write your own handler.\n--1988-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1988-- Nevertheless we consider this a bug. Please report\n--1988-- it at http://valgrind.org/support/bug_reports.html.\n--1988-- WARNING: unhandled riscv64-linux syscall: 258\n--1988-- You may be able to write your own handler.\n--1988-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1988-- Nevertheless we consider this a bug. Please report\n--1988-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 --- stdout --- expected: 'http [host\n' got: 'http [host\n' 91: failed localhost -g '\{{scheme}\[' --- stderr --- expected: '' got: '--1996-- WARNING: unhandled riscv64-linux syscall: 258\n--1996-- You may be able to write your own handler.\n--1996-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1996-- Nevertheless we consider this a bug. Please report\n--1996-- it at http://valgrind.org/support/bug_reports.html.\n--1996-- WARNING: unhandled riscv64-linux syscall: 258\n--1996-- You may be able to write your own handler.\n--1996-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1996-- Nevertheless we consider this a bug. Please report\n--1996-- it at http://valgrind.org/support/bug_reports.html.\n--1996-- WARNING: unhandled riscv64-linux syscall: 258\n--1996-- You may be able to write your own handler.\n--1996-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1996-- Nevertheless we consider this a bug. Please report\n--1996-- it at http://valgrind.org/support/bug_reports.html.\n--1996-- WARNING: unhandled riscv64-linux syscall: 258\n--1996-- You may be able to write your own handler.\n--1996-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1996-- Nevertheless we consider this a bug. Please report\n--1996-- it at http://valgrind.org/support/bug_reports.html.\n--1996-- WARNING: unhandled riscv64-linux syscall: 258\n--1996-- You may be able to write your own handler.\n--1996-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1996-- Nevertheless we consider this a bug. Please report\n--1996-- it at http://valgrind.org/support/bug_reports.html.\n--1996-- WARNING: unhandled riscv64-linux syscall: 258\n--1996-- You may be able to write your own handler.\n--1996-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1996-- Nevertheless we consider this a bug. Please report\n--1996-- it at http://valgrind.org/support/bug_reports.html.\n--1996-- WARNING: unhandled riscv64-linux syscall: 258\n--1996-- You may be able to write your own handler.\n--1996-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1996-- Nevertheless we consider this a bug. Please report\n--1996-- it at http://valgrind.org/support/bug_reports.html.\n--1996-- WARNING: unhandled riscv64-linux syscall: 258\n--1996-- You may be able to write your own handler.\n--1996-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1996-- Nevertheless we consider this a bug. Please report\n--1996-- it at http://valgrind.org/support/bug_reports.html.\n--1996-- WARNING: unhandled riscv64-linux syscall: 258\n--1996-- You may be able to write your own handler.\n--1996-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1996-- Nevertheless we consider this a bug. Please report\n--1996-- it at http://valgrind.org/support/bug_reports.html.\n--1996-- WARNING: unhandled riscv64-linux syscall: 258\n--1996-- You may be able to write your own handler.\n--1996-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1996-- Nevertheless we consider this a bug. Please report\n--1996-- it at http://valgrind.org/support/bug_reports.html.\n--1996-- WARNING: unhandled riscv64-linux syscall: 258\n--1996-- You may be able to write your own handler.\n--1996-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1996-- Nevertheless we consider this a bug. Please report\n--1996-- it at http://valgrind.org/support/bug_reports.html.\n--1996-- WARNING: unhandled riscv64-linux syscall: 258\n--1996-- You may be able to write your own handler.\n--1996-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1996-- Nevertheless we consider this a bug. Please report\n--1996-- it at http://valgrind.org/support/bug_reports.html.\n--1996-- WARNING: unhandled riscv64-linux syscall: 258\n--1996-- You may be able to write your own handler.\n--1996-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1996-- Nevertheless we consider this a bug. Please report\n--1996-- it at http://valgrind.org/support/bug_reports.html.\n--1996-- WARNING: unhandled riscv64-linux syscall: 258\n--1996-- You may be able to write your own handler.\n--1996-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1996-- Nevertheless we consider this a bug. Please report\n--1996-- it at http://valgrind.org/support/bug_reports.html.\n--1996-- WARNING: unhandled riscv64-linux syscall: 258\n--1996-- You may be able to write your own handler.\n--1996-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1996-- Nevertheless we consider this a bug. Please report\n--1996-- it at http://valgrind.org/support/bug_reports.html.\n--1996-- WARNING: unhandled riscv64-linux syscall: 258\n--1996-- You may be able to write your own handler.\n--1996-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1996-- Nevertheless we consider this a bug. Please report\n--1996-- it at http://valgrind.org/support/bug_reports.html.\n--1996-- WARNING: unhandled riscv64-linux syscall: 258\n--1996-- You may be able to write your own handler.\n--1996-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1996-- Nevertheless we consider this a bug. Please report\n--1996-- it at http://valgrind.org/support/bug_reports.html.\n--1996-- WARNING: unhandled riscv64-linux syscall: 258\n--1996-- You may be able to write your own handler.\n--1996-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1996-- Nevertheless we consider this a bug. Please report\n--1996-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 --- stdout --- expected: '{http[\n' got: '{http[\n' 92: failed localhost -g '\\[' --- stderr --- expected: '' got: '--2004-- WARNING: unhandled riscv64-linux syscall: 258\n--2004-- You may be able to write your own handler.\n--2004-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2004-- Nevertheless we consider this a bug. Please report\n--2004-- it at http://valgrind.org/support/bug_reports.html.\n--2004-- WARNING: unhandled riscv64-linux syscall: 258\n--2004-- You may be able to write your own handler.\n--2004-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2004-- Nevertheless we consider this a bug. Please report\n--2004-- it at http://valgrind.org/support/bug_reports.html.\n--2004-- WARNING: unhandled riscv64-linux syscall: 258\n--2004-- You may be able to write your own handler.\n--2004-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2004-- Nevertheless we consider this a bug. Please report\n--2004-- it at http://valgrind.org/support/bug_reports.html.\n--2004-- WARNING: unhandled riscv64-linux syscall: 258\n--2004-- You may be able to write your own handler.\n--2004-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2004-- Nevertheless we consider this a bug. Please report\n--2004-- it at http://valgrind.org/support/bug_reports.html.\n--2004-- WARNING: unhandled riscv64-linux syscall: 258\n--2004-- You may be able to write your own handler.\n--2004-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2004-- Nevertheless we consider this a bug. Please report\n--2004-- it at http://valgrind.org/support/bug_reports.html.\n--2004-- WARNING: unhandled riscv64-linux syscall: 258\n--2004-- You may be able to write your own handler.\n--2004-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2004-- Nevertheless we consider this a bug. Please report\n--2004-- it at http://valgrind.org/support/bug_reports.html.\n--2004-- WARNING: unhandled riscv64-linux syscall: 258\n--2004-- You may be able to write your own handler.\n--2004-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2004-- Nevertheless we consider this a bug. Please report\n--2004-- it at http://valgrind.org/support/bug_reports.html.\n--2004-- WARNING: unhandled riscv64-linux syscall: 258\n--2004-- You may be able to write your own handler.\n--2004-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2004-- Nevertheless we consider this a bug. Please report\n--2004-- it at http://valgrind.org/support/bug_reports.html.\n--2004-- WARNING: unhandled riscv64-linux syscall: 258\n--2004-- You may be able to write your own handler.\n--2004-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2004-- Nevertheless we consider this a bug. Please report\n--2004-- it at http://valgrind.org/support/bug_reports.html.\n--2004-- WARNING: unhandled riscv64-linux syscall: 258\n--2004-- You may be able to write your own handler.\n--2004-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2004-- Nevertheless we consider this a bug. Please report\n--2004-- it at http://valgrind.org/support/bug_reports.html.\n--2004-- WARNING: unhandled riscv64-linux syscall: 258\n--2004-- You may be able to write your own handler.\n--2004-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2004-- Nevertheless we consider this a bug. Please report\n--2004-- it at http://valgrind.org/support/bug_reports.html.\n--2004-- WARNING: unhandled riscv64-linux syscall: 258\n--2004-- You may be able to write your own handler.\n--2004-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2004-- Nevertheless we consider this a bug. Please report\n--2004-- it at http://valgrind.org/support/bug_reports.html.\n--2004-- WARNING: unhandled riscv64-linux syscall: 258\n--2004-- You may be able to write your own handler.\n--2004-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2004-- Nevertheless we consider this a bug. Please report\n--2004-- it at http://valgrind.org/support/bug_reports.html.\n--2004-- WARNING: unhandled riscv64-linux syscall: 258\n--2004-- You may be able to write your own handler.\n--2004-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2004-- Nevertheless we consider this a bug. Please report\n--2004-- it at http://valgrind.org/support/bug_reports.html.\n--2004-- WARNING: unhandled riscv64-linux syscall: 258\n--2004-- You may be able to write your own handler.\n--2004-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2004-- Nevertheless we consider this a bug. Please report\n--2004-- it at http://valgrind.org/support/bug_reports.html.\n--2004-- WARNING: unhandled riscv64-linux syscall: 258\n--2004-- You may be able to write your own handler.\n--2004-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2004-- Nevertheless we consider this a bug. Please report\n--2004-- it at http://valgrind.org/support/bug_reports.html.\n--2004-- WARNING: unhandled riscv64-linux syscall: 258\n--2004-- You may be able to write your own handler.\n--2004-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2004-- Nevertheless we consider this a bug. Please report\n--2004-- it at http://valgrind.org/support/bug_reports.html.\n--2004-- WARNING: unhandled riscv64-linux syscall: 258\n--2004-- You may be able to write your own handler.\n--2004-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2004-- Nevertheless we consider this a bug. Please report\n--2004-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 --- stdout --- expected: '\\[\n' got: '\\[\n' 93: failed 'https://u:s@foo?moo' -g '[scheme][user][password][query]' --- stderr --- expected: '' got: '--2012-- WARNING: unhandled riscv64-linux syscall: 258\n--2012-- You may be able to write your own handler.\n--2012-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2012-- Nevertheless we consider this a bug. Please report\n--2012-- it at http://valgrind.org/support/bug_reports.html.\n--2012-- WARNING: unhandled riscv64-linux syscall: 258\n--2012-- You may be able to write your own handler.\n--2012-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2012-- Nevertheless we consider this a bug. Please report\n--2012-- it at http://valgrind.org/support/bug_reports.html.\n--2012-- WARNING: unhandled riscv64-linux syscall: 258\n--2012-- You may be able to write your own handler.\n--2012-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2012-- Nevertheless we consider this a bug. Please report\n--2012-- it at http://valgrind.org/support/bug_reports.html.\n--2012-- WARNING: unhandled riscv64-linux syscall: 258\n--2012-- You may be able to write your own handler.\n--2012-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2012-- Nevertheless we consider this a bug. Please report\n--2012-- it at http://valgrind.org/support/bug_reports.html.\n--2012-- WARNING: unhandled riscv64-linux syscall: 258\n--2012-- You may be able to write your own handler.\n--2012-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2012-- Nevertheless we consider this a bug. Please report\n--2012-- it at http://valgrind.org/support/bug_reports.html.\n--2012-- WARNING: unhandled riscv64-linux syscall: 258\n--2012-- You may be able to write your own handler.\n--2012-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2012-- Nevertheless we consider this a bug. Please report\n--2012-- it at http://valgrind.org/support/bug_reports.html.\n--2012-- WARNING: unhandled riscv64-linux syscall: 258\n--2012-- You may be able to write your own handler.\n--2012-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2012-- Nevertheless we consider this a bug. Please report\n--2012-- it at http://valgrind.org/support/bug_reports.html.\n--2012-- WARNING: unhandled riscv64-linux syscall: 258\n--2012-- You may be able to write your own handler.\n--2012-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2012-- Nevertheless we consider this a bug. Please report\n--2012-- it at http://valgrind.org/support/bug_reports.html.\n--2012-- WARNING: unhandled riscv64-linux syscall: 258\n--2012-- You may be able to write your own handler.\n--2012-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2012-- Nevertheless we consider this a bug. Please report\n--2012-- it at http://valgrind.org/support/bug_reports.html.\n--2012-- WARNING: unhandled riscv64-linux syscall: 258\n--2012-- You may be able to write your own handler.\n--2012-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2012-- Nevertheless we consider this a bug. Please report\n--2012-- it at http://valgrind.org/support/bug_reports.html.\n--2012-- WARNING: unhandled riscv64-linux syscall: 258\n--2012-- You may be able to write your own handler.\n--2012-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2012-- Nevertheless we consider this a bug. Please report\n--2012-- it at http://valgrind.org/support/bug_reports.html.\n--2012-- WARNING: unhandled riscv64-linux syscall: 258\n--2012-- You may be able to write your own handler.\n--2012-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2012-- Nevertheless we consider this a bug. Please report\n--2012-- it at http://valgrind.org/support/bug_reports.html.\n--2012-- WARNING: unhandled riscv64-linux syscall: 258\n--2012-- You may be able to write your own handler.\n--2012-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2012-- Nevertheless we consider this a bug. Please report\n--2012-- it at http://valgrind.org/support/bug_reports.html.\n--2012-- WARNING: unhandled riscv64-linux syscall: 258\n--2012-- You may be able to write your own handler.\n--2012-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2012-- Nevertheless we consider this a bug. Please report\n--2012-- it at http://valgrind.org/support/bug_reports.html.\n--2012-- WARNING: unhandled riscv64-linux syscall: 258\n--2012-- You may be able to write your own handler.\n--2012-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2012-- Nevertheless we consider this a bug. Please report\n--2012-- it at http://valgrind.org/support/bug_reports.html.\n--2012-- WARNING: unhandled riscv64-linux syscall: 258\n--2012-- You may be able to write your own handler.\n--2012-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2012-- Nevertheless we consider this a bug. Please report\n--2012-- it at http://valgrind.org/support/bug_reports.html.\n--2012-- WARNING: unhandled riscv64-linux syscall: 258\n--2012-- You may be able to write your own handler.\n--2012-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2012-- Nevertheless we consider this a bug. Please report\n--2012-- it at http://valgrind.org/support/bug_reports.html.\n--2012-- WARNING: unhandled riscv64-linux syscall: 258\n--2012-- You may be able to write your own handler.\n--2012-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2012-- Nevertheless we consider this a bug. Please report\n--2012-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 --- stdout --- expected: 'httpsusmoo\n' got: 'httpsusmoo\n' 94: failed 'hej?a=b&a=c&a=d&b=a' -g '{query-all:a}' --- stderr --- expected: '' got: '--2020-- WARNING: unhandled riscv64-linux syscall: 258\n--2020-- You may be able to write your own handler.\n--2020-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2020-- Nevertheless we consider this a bug. Please report\n--2020-- it at http://valgrind.org/support/bug_reports.html.\n--2020-- WARNING: unhandled riscv64-linux syscall: 258\n--2020-- You may be able to write your own handler.\n--2020-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2020-- Nevertheless we consider this a bug. Please report\n--2020-- it at http://valgrind.org/support/bug_reports.html.\n--2020-- WARNING: unhandled riscv64-linux syscall: 258\n--2020-- You may be able to write your own handler.\n--2020-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2020-- Nevertheless we consider this a bug. Please report\n--2020-- it at http://valgrind.org/support/bug_reports.html.\n--2020-- WARNING: unhandled riscv64-linux syscall: 258\n--2020-- You may be able to write your own handler.\n--2020-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2020-- Nevertheless we consider this a bug. Please report\n--2020-- it at http://valgrind.org/support/bug_reports.html.\n--2020-- WARNING: unhandled riscv64-linux syscall: 258\n--2020-- You may be able to write your own handler.\n--2020-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2020-- Nevertheless we consider this a bug. Please report\n--2020-- it at http://valgrind.org/support/bug_reports.html.\n--2020-- WARNING: unhandled riscv64-linux syscall: 258\n--2020-- You may be able to write your own handler.\n--2020-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2020-- Nevertheless we consider this a bug. Please report\n--2020-- it at http://valgrind.org/support/bug_reports.html.\n--2020-- WARNING: unhandled riscv64-linux syscall: 258\n--2020-- You may be able to write your own handler.\n--2020-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2020-- Nevertheless we consider this a bug. Please report\n--2020-- it at http://valgrind.org/support/bug_reports.html.\n--2020-- WARNING: unhandled riscv64-linux syscall: 258\n--2020-- You may be able to write your own handler.\n--2020-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2020-- Nevertheless we consider this a bug. Please report\n--2020-- it at http://valgrind.org/support/bug_reports.html.\n--2020-- WARNING: unhandled riscv64-linux syscall: 258\n--2020-- You may be able to write your own handler.\n--2020-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2020-- Nevertheless we consider this a bug. Please report\n--2020-- it at http://valgrind.org/support/bug_reports.html.\n--2020-- WARNING: unhandled riscv64-linux syscall: 258\n--2020-- You may be able to write your own handler.\n--2020-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2020-- Nevertheless we consider this a bug. Please report\n--2020-- it at http://valgrind.org/support/bug_reports.html.\n--2020-- WARNING: unhandled riscv64-linux syscall: 258\n--2020-- You may be able to write your own handler.\n--2020-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2020-- Nevertheless we consider this a bug. Please report\n--2020-- it at http://valgrind.org/support/bug_reports.html.\n--2020-- WARNING: unhandled riscv64-linux syscall: 258\n--2020-- You may be able to write your own handler.\n--2020-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2020-- Nevertheless we consider this a bug. Please report\n--2020-- it at http://valgrind.org/support/bug_reports.html.\n--2020-- WARNING: unhandled riscv64-linux syscall: 258\n--2020-- You may be able to write your own handler.\n--2020-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2020-- Nevertheless we consider this a bug. Please report\n--2020-- it at http://valgrind.org/support/bug_reports.html.\n--2020-- WARNING: unhandled riscv64-linux syscall: 258\n--2020-- You may be able to write your own handler.\n--2020-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2020-- Nevertheless we consider this a bug. Please report\n--2020-- it at http://valgrind.org/support/bug_reports.html.\n--2020-- WARNING: unhandled riscv64-linux syscall: 258\n--2020-- You may be able to write your own handler.\n--2020-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2020-- Nevertheless we consider this a bug. Please report\n--2020-- it at http://valgrind.org/support/bug_reports.html.\n--2020-- WARNING: unhandled riscv64-linux syscall: 258\n--2020-- You may be able to write your own handler.\n--2020-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2020-- Nevertheless we consider this a bug. Please report\n--2020-- it at http://valgrind.org/support/bug_reports.html.\n--2020-- WARNING: unhandled riscv64-linux syscall: 258\n--2020-- You may be able to write your own handler.\n--2020-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2020-- Nevertheless we consider this a bug. Please report\n--2020-- it at http://valgrind.org/support/bug_reports.html.\n--2020-- WARNING: unhandled riscv64-linux syscall: 258\n--2020-- You may be able to write your own handler.\n--2020-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2020-- Nevertheless we consider this a bug. Please report\n--2020-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 --- stdout --- expected: 'b c d\n' got: 'b c d\n' 95: failed 'https://curl.se?name=mr%00smith' --get '{query:name}' --- stderr --- expected: '' got: '--2028-- WARNING: unhandled riscv64-linux syscall: 258\n--2028-- You may be able to write your own handler.\n--2028-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2028-- Nevertheless we consider this a bug. Please report\n--2028-- it at http://valgrind.org/support/bug_reports.html.\n--2028-- WARNING: unhandled riscv64-linux syscall: 258\n--2028-- You may be able to write your own handler.\n--2028-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2028-- Nevertheless we consider this a bug. Please report\n--2028-- it at http://valgrind.org/support/bug_reports.html.\n--2028-- WARNING: unhandled riscv64-linux syscall: 258\n--2028-- You may be able to write your own handler.\n--2028-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2028-- Nevertheless we consider this a bug. Please report\n--2028-- it at http://valgrind.org/support/bug_reports.html.\n--2028-- WARNING: unhandled riscv64-linux syscall: 258\n--2028-- You may be able to write your own handler.\n--2028-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2028-- Nevertheless we consider this a bug. Please report\n--2028-- it at http://valgrind.org/support/bug_reports.html.\n--2028-- WARNING: unhandled riscv64-linux syscall: 258\n--2028-- You may be able to write your own handler.\n--2028-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2028-- Nevertheless we consider this a bug. Please report\n--2028-- it at http://valgrind.org/support/bug_reports.html.\n--2028-- WARNING: unhandled riscv64-linux syscall: 258\n--2028-- You may be able to write your own handler.\n--2028-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2028-- Nevertheless we consider this a bug. Please report\n--2028-- it at http://valgrind.org/support/bug_reports.html.\n--2028-- WARNING: unhandled riscv64-linux syscall: 258\n--2028-- You may be able to write your own handler.\n--2028-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2028-- Nevertheless we consider this a bug. Please report\n--2028-- it at http://valgrind.org/support/bug_reports.html.\n--2028-- WARNING: unhandled riscv64-linux syscall: 258\n--2028-- You may be able to write your own handler.\n--2028-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2028-- Nevertheless we consider this a bug. Please report\n--2028-- it at http://valgrind.org/support/bug_reports.html.\n--2028-- WARNING: unhandled riscv64-linux syscall: 258\n--2028-- You may be able to write your own handler.\n--2028-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2028-- Nevertheless we consider this a bug. Please report\n--2028-- it at http://valgrind.org/support/bug_reports.html.\n--2028-- WARNING: unhandled riscv64-linux syscall: 258\n--2028-- You may be able to write your own handler.\n--2028-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2028-- Nevertheless we consider this a bug. Please report\n--2028-- it at http://valgrind.org/support/bug_reports.html.\n--2028-- WARNING: unhandled riscv64-linux syscall: 258\n--2028-- You may be able to write your own handler.\n--2028-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2028-- Nevertheless we consider this a bug. Please report\n--2028-- it at http://valgrind.org/support/bug_reports.html.\n--2028-- WARNING: unhandled riscv64-linux syscall: 258\n--2028-- You may be able to write your own handler.\n--2028-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2028-- Nevertheless we consider this a bug. Please report\n--2028-- it at http://valgrind.org/support/bug_reports.html.\n--2028-- WARNING: unhandled riscv64-linux syscall: 258\n--2028-- You may be able to write your own handler.\n--2028-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2028-- Nevertheless we consider this a bug. Please report\n--2028-- it at http://valgrind.org/support/bug_reports.html.\n--2028-- WARNING: unhandled riscv64-linux syscall: 258\n--2028-- You may be able to write your own handler.\n--2028-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2028-- Nevertheless we consider this a bug. Please report\n--2028-- it at http://valgrind.org/support/bug_reports.html.\n--2028-- WARNING: unhandled riscv64-linux syscall: 258\n--2028-- You may be able to write your own handler.\n--2028-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2028-- Nevertheless we consider this a bug. Please report\n--2028-- it at http://valgrind.org/support/bug_reports.html.\n--2028-- WARNING: unhandled riscv64-linux syscall: 258\n--2028-- You may be able to write your own handler.\n--2028-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2028-- Nevertheless we consider this a bug. Please report\n--2028-- it at http://valgrind.org/support/bug_reports.html.\n--2028-- WARNING: unhandled riscv64-linux syscall: 258\n--2028-- You may be able to write your own handler.\n--2028-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2028-- Nevertheless we consider this a bug. Please report\n--2028-- it at http://valgrind.org/support/bug_reports.html.\n--2028-- WARNING: unhandled riscv64-linux syscall: 258\n--2028-- You may be able to write your own handler.\n--2028-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2028-- Nevertheless we consider this a bug. Please report\n--2028-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 --- stdout --- expected: 'mr.smith\n' got: 'mr.smith\n' 96: failed --keep-port https://curl.se --iterate 'port=80 81 443' --- stderr --- expected: '' got: '--2036-- WARNING: unhandled riscv64-linux syscall: 258\n--2036-- You may be able to write your own handler.\n--2036-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2036-- Nevertheless we consider this a bug. Please report\n--2036-- it at http://valgrind.org/support/bug_reports.html.\n--2036-- WARNING: unhandled riscv64-linux syscall: 258\n--2036-- You may be able to write your own handler.\n--2036-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2036-- Nevertheless we consider this a bug. Please report\n--2036-- it at http://valgrind.org/support/bug_reports.html.\n--2036-- WARNING: unhandled riscv64-linux syscall: 258\n--2036-- You may be able to write your own handler.\n--2036-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2036-- Nevertheless we consider this a bug. Please report\n--2036-- it at http://valgrind.org/support/bug_reports.html.\n--2036-- WARNING: unhandled riscv64-linux syscall: 258\n--2036-- You may be able to write your own handler.\n--2036-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2036-- Nevertheless we consider this a bug. Please report\n--2036-- it at http://valgrind.org/support/bug_reports.html.\n--2036-- WARNING: unhandled riscv64-linux syscall: 258\n--2036-- You may be able to write your own handler.\n--2036-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2036-- Nevertheless we consider this a bug. Please report\n--2036-- it at http://valgrind.org/support/bug_reports.html.\n--2036-- WARNING: unhandled riscv64-linux syscall: 258\n--2036-- You may be able to write your own handler.\n--2036-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2036-- Nevertheless we consider this a bug. Please report\n--2036-- it at http://valgrind.org/support/bug_reports.html.\n--2036-- WARNING: unhandled riscv64-linux syscall: 258\n--2036-- You may be able to write your own handler.\n--2036-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2036-- Nevertheless we consider this a bug. Please report\n--2036-- it at http://valgrind.org/support/bug_reports.html.\n--2036-- WARNING: unhandled riscv64-linux syscall: 258\n--2036-- You may be able to write your own handler.\n--2036-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2036-- Nevertheless we consider this a bug. Please report\n--2036-- it at http://valgrind.org/support/bug_reports.html.\n--2036-- WARNING: unhandled riscv64-linux syscall: 258\n--2036-- You may be able to write your own handler.\n--2036-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2036-- Nevertheless we consider this a bug. Please report\n--2036-- it at http://valgrind.org/support/bug_reports.html.\n--2036-- WARNING: unhandled riscv64-linux syscall: 258\n--2036-- You may be able to write your own handler.\n--2036-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2036-- Nevertheless we consider this a bug. Please report\n--2036-- it at http://valgrind.org/support/bug_reports.html.\n--2036-- WARNING: unhandled riscv64-linux syscall: 258\n--2036-- You may be able to write your own handler.\n--2036-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2036-- Nevertheless we consider this a bug. Please report\n--2036-- it at http://valgrind.org/support/bug_reports.html.\n--2036-- WARNING: unhandled riscv64-linux syscall: 258\n--2036-- You may be able to write your own handler.\n--2036-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2036-- Nevertheless we consider this a bug. Please report\n--2036-- it at http://valgrind.org/support/bug_reports.html.\n--2036-- WARNING: unhandled riscv64-linux syscall: 258\n--2036-- You may be able to write your own handler.\n--2036-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2036-- Nevertheless we consider this a bug. Please report\n--2036-- it at http://valgrind.org/support/bug_reports.html.\n--2036-- WARNING: unhandled riscv64-linux syscall: 258\n--2036-- You may be able to write your own handler.\n--2036-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2036-- Nevertheless we consider this a bug. Please report\n--2036-- it at http://valgrind.org/support/bug_reports.html.\n--2036-- WARNING: unhandled riscv64-linux syscall: 258\n--2036-- You may be able to write your own handler.\n--2036-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2036-- Nevertheless we consider this a bug. Please report\n--2036-- it at http://valgrind.org/support/bug_reports.html.\n--2036-- WARNING: unhandled riscv64-linux syscall: 258\n--2036-- You may be able to write your own handler.\n--2036-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2036-- Nevertheless we consider this a bug. Please report\n--2036-- it at http://valgrind.org/support/bug_reports.html.\n--2036-- WARNING: unhandled riscv64-linux syscall: 258\n--2036-- You may be able to write your own handler.\n--2036-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2036-- Nevertheless we consider this a bug. Please report\n--2036-- it at http://valgrind.org/support/bug_reports.html.\n--2036-- WARNING: unhandled riscv64-linux syscall: 258\n--2036-- You may be able to write your own handler.\n--2036-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2036-- Nevertheless we consider this a bug. Please report\n--2036-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 --- stdout --- expected: 'https://curl.se:80/\nhttps://curl.se:81/\nhttps://curl.se:443/\n' got: 'https://curl.se:80/\nhttps://curl.se:81/\nhttps://curl.se:443/\n' 97: failed https://curl.se --iterate 'port=81 443' --iterate 'scheme=sftp moo' --- stderr --- expected: '' got: '--2044-- WARNING: unhandled riscv64-linux syscall: 258\n--2044-- You may be able to write your own handler.\n--2044-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2044-- Nevertheless we consider this a bug. Please report\n--2044-- it at http://valgrind.org/support/bug_reports.html.\n--2044-- WARNING: unhandled riscv64-linux syscall: 258\n--2044-- You may be able to write your own handler.\n--2044-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2044-- Nevertheless we consider this a bug. Please report\n--2044-- it at http://valgrind.org/support/bug_reports.html.\n--2044-- WARNING: unhandled riscv64-linux syscall: 258\n--2044-- You may be able to write your own handler.\n--2044-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2044-- Nevertheless we consider this a bug. Please report\n--2044-- it at http://valgrind.org/support/bug_reports.html.\n--2044-- WARNING: unhandled riscv64-linux syscall: 258\n--2044-- You may be able to write your own handler.\n--2044-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2044-- Nevertheless we consider this a bug. Please report\n--2044-- it at http://valgrind.org/support/bug_reports.html.\n--2044-- WARNING: unhandled riscv64-linux syscall: 258\n--2044-- You may be able to write your own handler.\n--2044-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2044-- Nevertheless we consider this a bug. Please report\n--2044-- it at http://valgrind.org/support/bug_reports.html.\n--2044-- WARNING: unhandled riscv64-linux syscall: 258\n--2044-- You may be able to write your own handler.\n--2044-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2044-- Nevertheless we consider this a bug. Please report\n--2044-- it at http://valgrind.org/support/bug_reports.html.\n--2044-- WARNING: unhandled riscv64-linux syscall: 258\n--2044-- You may be able to write your own handler.\n--2044-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2044-- Nevertheless we consider this a bug. Please report\n--2044-- it at http://valgrind.org/support/bug_reports.html.\n--2044-- WARNING: unhandled riscv64-linux syscall: 258\n--2044-- You may be able to write your own handler.\n--2044-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2044-- Nevertheless we consider this a bug. Please report\n--2044-- it at http://valgrind.org/support/bug_reports.html.\n--2044-- WARNING: unhandled riscv64-linux syscall: 258\n--2044-- You may be able to write your own handler.\n--2044-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2044-- Nevertheless we consider this a bug. Please report\n--2044-- it at http://valgrind.org/support/bug_reports.html.\n--2044-- WARNING: unhandled riscv64-linux syscall: 258\n--2044-- You may be able to write your own handler.\n--2044-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2044-- Nevertheless we consider this a bug. Please report\n--2044-- it at http://valgrind.org/support/bug_reports.html.\n--2044-- WARNING: unhandled riscv64-linux syscall: 258\n--2044-- You may be able to write your own handler.\n--2044-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2044-- Nevertheless we consider this a bug. Please report\n--2044-- it at http://valgrind.org/support/bug_reports.html.\n--2044-- WARNING: unhandled riscv64-linux syscall: 258\n--2044-- You may be able to write your own handler.\n--2044-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2044-- Nevertheless we consider this a bug. Please report\n--2044-- it at http://valgrind.org/support/bug_reports.html.\n--2044-- WARNING: unhandled riscv64-linux syscall: 258\n--2044-- You may be able to write your own handler.\n--2044-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2044-- Nevertheless we consider this a bug. Please report\n--2044-- it at http://valgrind.org/support/bug_reports.html.\n--2044-- WARNING: unhandled riscv64-linux syscall: 258\n--2044-- You may be able to write your own handler.\n--2044-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2044-- Nevertheless we consider this a bug. Please report\n--2044-- it at http://valgrind.org/support/bug_reports.html.\n--2044-- WARNING: unhandled riscv64-linux syscall: 258\n--2044-- You may be able to write your own handler.\n--2044-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2044-- Nevertheless we consider this a bug. Please report\n--2044-- it at http://valgrind.org/support/bug_reports.html.\n--2044-- WARNING: unhandled riscv64-linux syscall: 258\n--2044-- You may be able to write your own handler.\n--2044-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2044-- Nevertheless we consider this a bug. Please report\n--2044-- it at http://valgrind.org/support/bug_reports.html.\n--2044-- WARNING: unhandled riscv64-linux syscall: 258\n--2044-- You may be able to write your own handler.\n--2044-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2044-- Nevertheless we consider this a bug. Please report\n--2044-- it at http://valgrind.org/support/bug_reports.html.\n--2044-- WARNING: unhandled riscv64-linux syscall: 258\n--2044-- You may be able to write your own handler.\n--2044-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2044-- Nevertheless we consider this a bug. Please report\n--2044-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 --- stdout --- expected: 'sftp://curl.se:81/\nmoo://curl.se:81/\nsftp://curl.se:443/\nmoo://curl.se:443/\n' got: 'sftp://curl.se:81/\nmoo://curl.se:81/\nsftp://curl.se:443/\nmoo://curl.se:443/\n' 98: 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: '--2052-- WARNING: unhandled riscv64-linux syscall: 258\n--2052-- You may be able to write your own handler.\n--2052-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2052-- Nevertheless we consider this a bug. Please report\n--2052-- it at http://valgrind.org/support/bug_reports.html.\n--2052-- WARNING: unhandled riscv64-linux syscall: 258\n--2052-- You may be able to write your own handler.\n--2052-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2052-- Nevertheless we consider this a bug. Please report\n--2052-- it at http://valgrind.org/support/bug_reports.html.\n--2052-- WARNING: unhandled riscv64-linux syscall: 258\n--2052-- You may be able to write your own handler.\n--2052-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2052-- Nevertheless we consider this a bug. Please report\n--2052-- it at http://valgrind.org/support/bug_reports.html.\n--2052-- WARNING: unhandled riscv64-linux syscall: 258\n--2052-- You may be able to write your own handler.\n--2052-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2052-- Nevertheless we consider this a bug. Please report\n--2052-- it at http://valgrind.org/support/bug_reports.html.\n--2052-- WARNING: unhandled riscv64-linux syscall: 258\n--2052-- You may be able to write your own handler.\n--2052-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2052-- Nevertheless we consider this a bug. Please report\n--2052-- it at http://valgrind.org/support/bug_reports.html.\n--2052-- WARNING: unhandled riscv64-linux syscall: 258\n--2052-- You may be able to write your own handler.\n--2052-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2052-- Nevertheless we consider this a bug. Please report\n--2052-- it at http://valgrind.org/support/bug_reports.html.\n--2052-- WARNING: unhandled riscv64-linux syscall: 258\n--2052-- You may be able to write your own handler.\n--2052-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2052-- Nevertheless we consider this a bug. Please report\n--2052-- it at http://valgrind.org/support/bug_reports.html.\n--2052-- WARNING: unhandled riscv64-linux syscall: 258\n--2052-- You may be able to write your own handler.\n--2052-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2052-- Nevertheless we consider this a bug. Please report\n--2052-- it at http://valgrind.org/support/bug_reports.html.\n--2052-- WARNING: unhandled riscv64-linux syscall: 258\n--2052-- You may be able to write your own handler.\n--2052-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2052-- Nevertheless we consider this a bug. Please report\n--2052-- it at http://valgrind.org/support/bug_reports.html.\n--2052-- WARNING: unhandled riscv64-linux syscall: 258\n--2052-- You may be able to write your own handler.\n--2052-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2052-- Nevertheless we consider this a bug. Please report\n--2052-- it at http://valgrind.org/support/bug_reports.html.\n--2052-- WARNING: unhandled riscv64-linux syscall: 258\n--2052-- You may be able to write your own handler.\n--2052-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2052-- Nevertheless we consider this a bug. Please report\n--2052-- it at http://valgrind.org/support/bug_reports.html.\n--2052-- WARNING: unhandled riscv64-linux syscall: 258\n--2052-- You may be able to write your own handler.\n--2052-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2052-- Nevertheless we consider this a bug. Please report\n--2052-- it at http://valgrind.org/support/bug_reports.html.\n--2052-- WARNING: unhandled riscv64-linux syscall: 258\n--2052-- You may be able to write your own handler.\n--2052-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2052-- Nevertheless we consider this a bug. Please report\n--2052-- it at http://valgrind.org/support/bug_reports.html.\n--2052-- WARNING: unhandled riscv64-linux syscall: 258\n--2052-- You may be able to write your own handler.\n--2052-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2052-- Nevertheless we consider this a bug. Please report\n--2052-- it at http://valgrind.org/support/bug_reports.html.\n--2052-- WARNING: unhandled riscv64-linux syscall: 258\n--2052-- You may be able to write your own handler.\n--2052-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2052-- Nevertheless we consider this a bug. Please report\n--2052-- it at http://valgrind.org/support/bug_reports.html.\n--2052-- WARNING: unhandled riscv64-linux syscall: 258\n--2052-- You may be able to write your own handler.\n--2052-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2052-- Nevertheless we consider this a bug. Please report\n--2052-- it at http://valgrind.org/support/bug_reports.html.\n--2052-- WARNING: unhandled riscv64-linux syscall: 258\n--2052-- You may be able to write your own handler.\n--2052-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2052-- Nevertheless we consider this a bug. Please report\n--2052-- it at http://valgrind.org/support/bug_reports.html.\n--2052-- WARNING: unhandled riscv64-linux syscall: 258\n--2052-- You may be able to write your own handler.\n--2052-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2052-- Nevertheless we consider this a bug. Please report\n--2052-- it at http://valgrind.org/support/bug_reports.html.\ntrurl error: duplicate component for iterate: port\ntrurl error: Try trurl -h for help\n' --- returncode --- expected: 11 got: 11 --- stdout --- expected: '' got: '' 99: failed https://curl.se -s host=localhost --iterate 'port=22 23' --- stderr --- expected: '' got: '--2060-- WARNING: unhandled riscv64-linux syscall: 258\n--2060-- You may be able to write your own handler.\n--2060-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2060-- Nevertheless we consider this a bug. Please report\n--2060-- it at http://valgrind.org/support/bug_reports.html.\n--2060-- WARNING: unhandled riscv64-linux syscall: 258\n--2060-- You may be able to write your own handler.\n--2060-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2060-- Nevertheless we consider this a bug. Please report\n--2060-- it at http://valgrind.org/support/bug_reports.html.\n--2060-- WARNING: unhandled riscv64-linux syscall: 258\n--2060-- You may be able to write your own handler.\n--2060-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2060-- Nevertheless we consider this a bug. Please report\n--2060-- it at http://valgrind.org/support/bug_reports.html.\n--2060-- WARNING: unhandled riscv64-linux syscall: 258\n--2060-- You may be able to write your own handler.\n--2060-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2060-- Nevertheless we consider this a bug. Please report\n--2060-- it at http://valgrind.org/support/bug_reports.html.\n--2060-- WARNING: unhandled riscv64-linux syscall: 258\n--2060-- You may be able to write your own handler.\n--2060-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2060-- Nevertheless we consider this a bug. Please report\n--2060-- it at http://valgrind.org/support/bug_reports.html.\n--2060-- WARNING: unhandled riscv64-linux syscall: 258\n--2060-- You may be able to write your own handler.\n--2060-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2060-- Nevertheless we consider this a bug. Please report\n--2060-- it at http://valgrind.org/support/bug_reports.html.\n--2060-- WARNING: unhandled riscv64-linux syscall: 258\n--2060-- You may be able to write your own handler.\n--2060-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2060-- Nevertheless we consider this a bug. Please report\n--2060-- it at http://valgrind.org/support/bug_reports.html.\n--2060-- WARNING: unhandled riscv64-linux syscall: 258\n--2060-- You may be able to write your own handler.\n--2060-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2060-- Nevertheless we consider this a bug. Please report\n--2060-- it at http://valgrind.org/support/bug_reports.html.\n--2060-- WARNING: unhandled riscv64-linux syscall: 258\n--2060-- You may be able to write your own handler.\n--2060-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2060-- Nevertheless we consider this a bug. Please report\n--2060-- it at http://valgrind.org/support/bug_reports.html.\n--2060-- WARNING: unhandled riscv64-linux syscall: 258\n--2060-- You may be able to write your own handler.\n--2060-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2060-- Nevertheless we consider this a bug. Please report\n--2060-- it at http://valgrind.org/support/bug_reports.html.\n--2060-- WARNING: unhandled riscv64-linux syscall: 258\n--2060-- You may be able to write your own handler.\n--2060-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2060-- Nevertheless we consider this a bug. Please report\n--2060-- it at http://valgrind.org/support/bug_reports.html.\n--2060-- WARNING: unhandled riscv64-linux syscall: 258\n--2060-- You may be able to write your own handler.\n--2060-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2060-- Nevertheless we consider this a bug. Please report\n--2060-- it at http://valgrind.org/support/bug_reports.html.\n--2060-- WARNING: unhandled riscv64-linux syscall: 258\n--2060-- You may be able to write your own handler.\n--2060-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2060-- Nevertheless we consider this a bug. Please report\n--2060-- it at http://valgrind.org/support/bug_reports.html.\n--2060-- WARNING: unhandled riscv64-linux syscall: 258\n--2060-- You may be able to write your own handler.\n--2060-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2060-- Nevertheless we consider this a bug. Please report\n--2060-- it at http://valgrind.org/support/bug_reports.html.\n--2060-- WARNING: unhandled riscv64-linux syscall: 258\n--2060-- You may be able to write your own handler.\n--2060-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2060-- Nevertheless we consider this a bug. Please report\n--2060-- it at http://valgrind.org/support/bug_reports.html.\n--2060-- WARNING: unhandled riscv64-linux syscall: 258\n--2060-- You may be able to write your own handler.\n--2060-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2060-- Nevertheless we consider this a bug. Please report\n--2060-- it at http://valgrind.org/support/bug_reports.html.\n--2060-- WARNING: unhandled riscv64-linux syscall: 258\n--2060-- You may be able to write your own handler.\n--2060-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2060-- Nevertheless we consider this a bug. Please report\n--2060-- it at http://valgrind.org/support/bug_reports.html.\n--2060-- WARNING: unhandled riscv64-linux syscall: 258\n--2060-- You may be able to write your own handler.\n--2060-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2060-- Nevertheless we consider this a bug. Please report\n--2060-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 --- stdout --- expected: 'https://localhost:22/\nhttps://localhost:23/\n' got: 'https://localhost:22/\nhttps://localhost:23/\n' 100: failed hello@localhost --iterate 'host=one two' -g '{host} {user}' --- stderr --- expected: '' got: '--2068-- WARNING: unhandled riscv64-linux syscall: 258\n--2068-- You may be able to write your own handler.\n--2068-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2068-- Nevertheless we consider this a bug. Please report\n--2068-- it at http://valgrind.org/support/bug_reports.html.\n--2068-- WARNING: unhandled riscv64-linux syscall: 258\n--2068-- You may be able to write your own handler.\n--2068-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2068-- Nevertheless we consider this a bug. Please report\n--2068-- it at http://valgrind.org/support/bug_reports.html.\n--2068-- WARNING: unhandled riscv64-linux syscall: 258\n--2068-- You may be able to write your own handler.\n--2068-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2068-- Nevertheless we consider this a bug. Please report\n--2068-- it at http://valgrind.org/support/bug_reports.html.\n--2068-- WARNING: unhandled riscv64-linux syscall: 258\n--2068-- You may be able to write your own handler.\n--2068-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2068-- Nevertheless we consider this a bug. Please report\n--2068-- it at http://valgrind.org/support/bug_reports.html.\n--2068-- WARNING: unhandled riscv64-linux syscall: 258\n--2068-- You may be able to write your own handler.\n--2068-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2068-- Nevertheless we consider this a bug. Please report\n--2068-- it at http://valgrind.org/support/bug_reports.html.\n--2068-- WARNING: unhandled riscv64-linux syscall: 258\n--2068-- You may be able to write your own handler.\n--2068-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2068-- Nevertheless we consider this a bug. Please report\n--2068-- it at http://valgrind.org/support/bug_reports.html.\n--2068-- WARNING: unhandled riscv64-linux syscall: 258\n--2068-- You may be able to write your own handler.\n--2068-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2068-- Nevertheless we consider this a bug. Please report\n--2068-- it at http://valgrind.org/support/bug_reports.html.\n--2068-- WARNING: unhandled riscv64-linux syscall: 258\n--2068-- You may be able to write your own handler.\n--2068-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2068-- Nevertheless we consider this a bug. Please report\n--2068-- it at http://valgrind.org/support/bug_reports.html.\n--2068-- WARNING: unhandled riscv64-linux syscall: 258\n--2068-- You may be able to write your own handler.\n--2068-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2068-- Nevertheless we consider this a bug. Please report\n--2068-- it at http://valgrind.org/support/bug_reports.html.\n--2068-- WARNING: unhandled riscv64-linux syscall: 258\n--2068-- You may be able to write your own handler.\n--2068-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2068-- Nevertheless we consider this a bug. Please report\n--2068-- it at http://valgrind.org/support/bug_reports.html.\n--2068-- WARNING: unhandled riscv64-linux syscall: 258\n--2068-- You may be able to write your own handler.\n--2068-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2068-- Nevertheless we consider this a bug. Please report\n--2068-- it at http://valgrind.org/support/bug_reports.html.\n--2068-- WARNING: unhandled riscv64-linux syscall: 258\n--2068-- You may be able to write your own handler.\n--2068-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2068-- Nevertheless we consider this a bug. Please report\n--2068-- it at http://valgrind.org/support/bug_reports.html.\n--2068-- WARNING: unhandled riscv64-linux syscall: 258\n--2068-- You may be able to write your own handler.\n--2068-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2068-- Nevertheless we consider this a bug. Please report\n--2068-- it at http://valgrind.org/support/bug_reports.html.\n--2068-- WARNING: unhandled riscv64-linux syscall: 258\n--2068-- You may be able to write your own handler.\n--2068-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2068-- Nevertheless we consider this a bug. Please report\n--2068-- it at http://valgrind.org/support/bug_reports.html.\n--2068-- WARNING: unhandled riscv64-linux syscall: 258\n--2068-- You may be able to write your own handler.\n--2068-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2068-- Nevertheless we consider this a bug. Please report\n--2068-- it at http://valgrind.org/support/bug_reports.html.\n--2068-- WARNING: unhandled riscv64-linux syscall: 258\n--2068-- You may be able to write your own handler.\n--2068-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2068-- Nevertheless we consider this a bug. Please report\n--2068-- it at http://valgrind.org/support/bug_reports.html.\n--2068-- WARNING: unhandled riscv64-linux syscall: 258\n--2068-- You may be able to write your own handler.\n--2068-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2068-- Nevertheless we consider this a bug. Please report\n--2068-- it at http://valgrind.org/support/bug_reports.html.\n--2068-- WARNING: unhandled riscv64-linux syscall: 258\n--2068-- You may be able to write your own handler.\n--2068-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2068-- Nevertheless we consider this a bug. Please report\n--2068-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 --- stdout --- expected: 'one hello\ntwo hello\n' got: 'one hello\ntwo hello\n' 101: failed 'https://example.com?utm=tra%20cker&address%20=home&here=now&thisthen' --json --- stderr --- expected: '' got: '--2076-- WARNING: unhandled riscv64-linux syscall: 258\n--2076-- You may be able to write your own handler.\n--2076-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2076-- Nevertheless we consider this a bug. Please report\n--2076-- it at http://valgrind.org/support/bug_reports.html.\n--2076-- WARNING: unhandled riscv64-linux syscall: 258\n--2076-- You may be able to write your own handler.\n--2076-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2076-- Nevertheless we consider this a bug. Please report\n--2076-- it at http://valgrind.org/support/bug_reports.html.\n--2076-- WARNING: unhandled riscv64-linux syscall: 258\n--2076-- You may be able to write your own handler.\n--2076-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2076-- Nevertheless we consider this a bug. Please report\n--2076-- it at http://valgrind.org/support/bug_reports.html.\n--2076-- WARNING: unhandled riscv64-linux syscall: 258\n--2076-- You may be able to write your own handler.\n--2076-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2076-- Nevertheless we consider this a bug. Please report\n--2076-- it at http://valgrind.org/support/bug_reports.html.\n--2076-- WARNING: unhandled riscv64-linux syscall: 258\n--2076-- You may be able to write your own handler.\n--2076-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2076-- Nevertheless we consider this a bug. Please report\n--2076-- it at http://valgrind.org/support/bug_reports.html.\n--2076-- WARNING: unhandled riscv64-linux syscall: 258\n--2076-- You may be able to write your own handler.\n--2076-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2076-- Nevertheless we consider this a bug. Please report\n--2076-- it at http://valgrind.org/support/bug_reports.html.\n--2076-- WARNING: unhandled riscv64-linux syscall: 258\n--2076-- You may be able to write your own handler.\n--2076-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2076-- Nevertheless we consider this a bug. Please report\n--2076-- it at http://valgrind.org/support/bug_reports.html.\n--2076-- WARNING: unhandled riscv64-linux syscall: 258\n--2076-- You may be able to write your own handler.\n--2076-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2076-- Nevertheless we consider this a bug. Please report\n--2076-- it at http://valgrind.org/support/bug_reports.html.\n--2076-- WARNING: unhandled riscv64-linux syscall: 258\n--2076-- You may be able to write your own handler.\n--2076-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2076-- Nevertheless we consider this a bug. Please report\n--2076-- it at http://valgrind.org/support/bug_reports.html.\n--2076-- WARNING: unhandled riscv64-linux syscall: 258\n--2076-- You may be able to write your own handler.\n--2076-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2076-- Nevertheless we consider this a bug. Please report\n--2076-- it at http://valgrind.org/support/bug_reports.html.\n--2076-- WARNING: unhandled riscv64-linux syscall: 258\n--2076-- You may be able to write your own handler.\n--2076-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2076-- Nevertheless we consider this a bug. Please report\n--2076-- it at http://valgrind.org/support/bug_reports.html.\n--2076-- WARNING: unhandled riscv64-linux syscall: 258\n--2076-- You may be able to write your own handler.\n--2076-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2076-- Nevertheless we consider this a bug. Please report\n--2076-- it at http://valgrind.org/support/bug_reports.html.\n--2076-- WARNING: unhandled riscv64-linux syscall: 258\n--2076-- You may be able to write your own handler.\n--2076-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2076-- Nevertheless we consider this a bug. Please report\n--2076-- it at http://valgrind.org/support/bug_reports.html.\n--2076-- WARNING: unhandled riscv64-linux syscall: 258\n--2076-- You may be able to write your own handler.\n--2076-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2076-- Nevertheless we consider this a bug. Please report\n--2076-- it at http://valgrind.org/support/bug_reports.html.\n--2076-- WARNING: unhandled riscv64-linux syscall: 258\n--2076-- You may be able to write your own handler.\n--2076-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2076-- Nevertheless we consider this a bug. Please report\n--2076-- it at http://valgrind.org/support/bug_reports.html.\n--2076-- WARNING: unhandled riscv64-linux syscall: 258\n--2076-- You may be able to write your own handler.\n--2076-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2076-- Nevertheless we consider this a bug. Please report\n--2076-- it at http://valgrind.org/support/bug_reports.html.\n--2076-- WARNING: unhandled riscv64-linux syscall: 258\n--2076-- You may be able to write your own handler.\n--2076-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2076-- Nevertheless we consider this a bug. Please report\n--2076-- it at http://valgrind.org/support/bug_reports.html.\n--2076-- WARNING: unhandled riscv64-linux syscall: 258\n--2076-- You may be able to write your own handler.\n--2076-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2076-- Nevertheless we consider this a bug. Please report\n--2076-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 --- stdout --- expected: [{'url': 'https://example.com/?utm=tra+cker&address+=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: [{'url': 'https://example.com/?utm=tra+cker&address+=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': ''}]}] 102: failed 'ftp://smith:secret@example.com:33/path?search=me#where' --json --- stderr --- expected: '' got: '--2084-- WARNING: unhandled riscv64-linux syscall: 258\n--2084-- You may be able to write your own handler.\n--2084-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2084-- Nevertheless we consider this a bug. Please report\n--2084-- it at http://valgrind.org/support/bug_reports.html.\n--2084-- WARNING: unhandled riscv64-linux syscall: 258\n--2084-- You may be able to write your own handler.\n--2084-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2084-- Nevertheless we consider this a bug. Please report\n--2084-- it at http://valgrind.org/support/bug_reports.html.\n--2084-- WARNING: unhandled riscv64-linux syscall: 258\n--2084-- You may be able to write your own handler.\n--2084-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2084-- Nevertheless we consider this a bug. Please report\n--2084-- it at http://valgrind.org/support/bug_reports.html.\n--2084-- WARNING: unhandled riscv64-linux syscall: 258\n--2084-- You may be able to write your own handler.\n--2084-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2084-- Nevertheless we consider this a bug. Please report\n--2084-- it at http://valgrind.org/support/bug_reports.html.\n--2084-- WARNING: unhandled riscv64-linux syscall: 258\n--2084-- You may be able to write your own handler.\n--2084-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2084-- Nevertheless we consider this a bug. Please report\n--2084-- it at http://valgrind.org/support/bug_reports.html.\n--2084-- WARNING: unhandled riscv64-linux syscall: 258\n--2084-- You may be able to write your own handler.\n--2084-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2084-- Nevertheless we consider this a bug. Please report\n--2084-- it at http://valgrind.org/support/bug_reports.html.\n--2084-- WARNING: unhandled riscv64-linux syscall: 258\n--2084-- You may be able to write your own handler.\n--2084-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2084-- Nevertheless we consider this a bug. Please report\n--2084-- it at http://valgrind.org/support/bug_reports.html.\n--2084-- WARNING: unhandled riscv64-linux syscall: 258\n--2084-- You may be able to write your own handler.\n--2084-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2084-- Nevertheless we consider this a bug. Please report\n--2084-- it at http://valgrind.org/support/bug_reports.html.\n--2084-- WARNING: unhandled riscv64-linux syscall: 258\n--2084-- You may be able to write your own handler.\n--2084-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2084-- Nevertheless we consider this a bug. Please report\n--2084-- it at http://valgrind.org/support/bug_reports.html.\n--2084-- WARNING: unhandled riscv64-linux syscall: 258\n--2084-- You may be able to write your own handler.\n--2084-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2084-- Nevertheless we consider this a bug. Please report\n--2084-- it at http://valgrind.org/support/bug_reports.html.\n--2084-- WARNING: unhandled riscv64-linux syscall: 258\n--2084-- You may be able to write your own handler.\n--2084-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2084-- Nevertheless we consider this a bug. Please report\n--2084-- it at http://valgrind.org/support/bug_reports.html.\n--2084-- WARNING: unhandled riscv64-linux syscall: 258\n--2084-- You may be able to write your own handler.\n--2084-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2084-- Nevertheless we consider this a bug. Please report\n--2084-- it at http://valgrind.org/support/bug_reports.html.\n--2084-- WARNING: unhandled riscv64-linux syscall: 258\n--2084-- You may be able to write your own handler.\n--2084-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2084-- Nevertheless we consider this a bug. Please report\n--2084-- it at http://valgrind.org/support/bug_reports.html.\n--2084-- WARNING: unhandled riscv64-linux syscall: 258\n--2084-- You may be able to write your own handler.\n--2084-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2084-- Nevertheless we consider this a bug. Please report\n--2084-- it at http://valgrind.org/support/bug_reports.html.\n--2084-- WARNING: unhandled riscv64-linux syscall: 258\n--2084-- You may be able to write your own handler.\n--2084-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2084-- Nevertheless we consider this a bug. Please report\n--2084-- it at http://valgrind.org/support/bug_reports.html.\n--2084-- WARNING: unhandled riscv64-linux syscall: 258\n--2084-- You may be able to write your own handler.\n--2084-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2084-- Nevertheless we consider this a bug. Please report\n--2084-- it at http://valgrind.org/support/bug_reports.html.\n--2084-- WARNING: unhandled riscv64-linux syscall: 258\n--2084-- You may be able to write your own handler.\n--2084-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2084-- Nevertheless we consider this a bug. Please report\n--2084-- it at http://valgrind.org/support/bug_reports.html.\n--2084-- WARNING: unhandled riscv64-linux syscall: 258\n--2084-- You may be able to write your own handler.\n--2084-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2084-- Nevertheless we consider this a bug. Please report\n--2084-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 --- 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: [{'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'}]}] 103: failed example.com --json --- stderr --- expected: '' got: '--2092-- WARNING: unhandled riscv64-linux syscall: 258\n--2092-- You may be able to write your own handler.\n--2092-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2092-- Nevertheless we consider this a bug. Please report\n--2092-- it at http://valgrind.org/support/bug_reports.html.\n--2092-- WARNING: unhandled riscv64-linux syscall: 258\n--2092-- You may be able to write your own handler.\n--2092-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2092-- Nevertheless we consider this a bug. Please report\n--2092-- it at http://valgrind.org/support/bug_reports.html.\n--2092-- WARNING: unhandled riscv64-linux syscall: 258\n--2092-- You may be able to write your own handler.\n--2092-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2092-- Nevertheless we consider this a bug. Please report\n--2092-- it at http://valgrind.org/support/bug_reports.html.\n--2092-- WARNING: unhandled riscv64-linux syscall: 258\n--2092-- You may be able to write your own handler.\n--2092-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2092-- Nevertheless we consider this a bug. Please report\n--2092-- it at http://valgrind.org/support/bug_reports.html.\n--2092-- WARNING: unhandled riscv64-linux syscall: 258\n--2092-- You may be able to write your own handler.\n--2092-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2092-- Nevertheless we consider this a bug. Please report\n--2092-- it at http://valgrind.org/support/bug_reports.html.\n--2092-- WARNING: unhandled riscv64-linux syscall: 258\n--2092-- You may be able to write your own handler.\n--2092-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2092-- Nevertheless we consider this a bug. Please report\n--2092-- it at http://valgrind.org/support/bug_reports.html.\n--2092-- WARNING: unhandled riscv64-linux syscall: 258\n--2092-- You may be able to write your own handler.\n--2092-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2092-- Nevertheless we consider this a bug. Please report\n--2092-- it at http://valgrind.org/support/bug_reports.html.\n--2092-- WARNING: unhandled riscv64-linux syscall: 258\n--2092-- You may be able to write your own handler.\n--2092-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2092-- Nevertheless we consider this a bug. Please report\n--2092-- it at http://valgrind.org/support/bug_reports.html.\n--2092-- WARNING: unhandled riscv64-linux syscall: 258\n--2092-- You may be able to write your own handler.\n--2092-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2092-- Nevertheless we consider this a bug. Please report\n--2092-- it at http://valgrind.org/support/bug_reports.html.\n--2092-- WARNING: unhandled riscv64-linux syscall: 258\n--2092-- You may be able to write your own handler.\n--2092-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2092-- Nevertheless we consider this a bug. Please report\n--2092-- it at http://valgrind.org/support/bug_reports.html.\n--2092-- WARNING: unhandled riscv64-linux syscall: 258\n--2092-- You may be able to write your own handler.\n--2092-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2092-- Nevertheless we consider this a bug. Please report\n--2092-- it at http://valgrind.org/support/bug_reports.html.\n--2092-- WARNING: unhandled riscv64-linux syscall: 258\n--2092-- You may be able to write your own handler.\n--2092-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2092-- Nevertheless we consider this a bug. Please report\n--2092-- it at http://valgrind.org/support/bug_reports.html.\n--2092-- WARNING: unhandled riscv64-linux syscall: 258\n--2092-- You may be able to write your own handler.\n--2092-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2092-- Nevertheless we consider this a bug. Please report\n--2092-- it at http://valgrind.org/support/bug_reports.html.\n--2092-- WARNING: unhandled riscv64-linux syscall: 258\n--2092-- You may be able to write your own handler.\n--2092-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2092-- Nevertheless we consider this a bug. Please report\n--2092-- it at http://valgrind.org/support/bug_reports.html.\n--2092-- WARNING: unhandled riscv64-linux syscall: 258\n--2092-- You may be able to write your own handler.\n--2092-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2092-- Nevertheless we consider this a bug. Please report\n--2092-- it at http://valgrind.org/support/bug_reports.html.\n--2092-- WARNING: unhandled riscv64-linux syscall: 258\n--2092-- You may be able to write your own handler.\n--2092-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2092-- Nevertheless we consider this a bug. Please report\n--2092-- it at http://valgrind.org/support/bug_reports.html.\n--2092-- WARNING: unhandled riscv64-linux syscall: 258\n--2092-- You may be able to write your own handler.\n--2092-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2092-- Nevertheless we consider this a bug. Please report\n--2092-- it at http://valgrind.org/support/bug_reports.html.\n--2092-- WARNING: unhandled riscv64-linux syscall: 258\n--2092-- You may be able to write your own handler.\n--2092-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2092-- Nevertheless we consider this a bug. Please report\n--2092-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 --- stdout --- expected: [{'url': 'http://example.com/', 'parts': {'scheme': 'http', 'host': 'example.com', 'path': '/'}}] got: [{'url': 'http://example.com/', 'parts': {'scheme': 'http', 'host': 'example.com', 'path': '/'}}] 104: failed example.com other.com --json --- stderr --- expected: '' got: '--2100-- WARNING: unhandled riscv64-linux syscall: 258\n--2100-- You may be able to write your own handler.\n--2100-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2100-- Nevertheless we consider this a bug. Please report\n--2100-- it at http://valgrind.org/support/bug_reports.html.\n--2100-- WARNING: unhandled riscv64-linux syscall: 258\n--2100-- You may be able to write your own handler.\n--2100-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2100-- Nevertheless we consider this a bug. Please report\n--2100-- it at http://valgrind.org/support/bug_reports.html.\n--2100-- WARNING: unhandled riscv64-linux syscall: 258\n--2100-- You may be able to write your own handler.\n--2100-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2100-- Nevertheless we consider this a bug. Please report\n--2100-- it at http://valgrind.org/support/bug_reports.html.\n--2100-- WARNING: unhandled riscv64-linux syscall: 258\n--2100-- You may be able to write your own handler.\n--2100-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2100-- Nevertheless we consider this a bug. Please report\n--2100-- it at http://valgrind.org/support/bug_reports.html.\n--2100-- WARNING: unhandled riscv64-linux syscall: 258\n--2100-- You may be able to write your own handler.\n--2100-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2100-- Nevertheless we consider this a bug. Please report\n--2100-- it at http://valgrind.org/support/bug_reports.html.\n--2100-- WARNING: unhandled riscv64-linux syscall: 258\n--2100-- You may be able to write your own handler.\n--2100-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2100-- Nevertheless we consider this a bug. Please report\n--2100-- it at http://valgrind.org/support/bug_reports.html.\n--2100-- WARNING: unhandled riscv64-linux syscall: 258\n--2100-- You may be able to write your own handler.\n--2100-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2100-- Nevertheless we consider this a bug. Please report\n--2100-- it at http://valgrind.org/support/bug_reports.html.\n--2100-- WARNING: unhandled riscv64-linux syscall: 258\n--2100-- You may be able to write your own handler.\n--2100-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2100-- Nevertheless we consider this a bug. Please report\n--2100-- it at http://valgrind.org/support/bug_reports.html.\n--2100-- WARNING: unhandled riscv64-linux syscall: 258\n--2100-- You may be able to write your own handler.\n--2100-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2100-- Nevertheless we consider this a bug. Please report\n--2100-- it at http://valgrind.org/support/bug_reports.html.\n--2100-- WARNING: unhandled riscv64-linux syscall: 258\n--2100-- You may be able to write your own handler.\n--2100-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2100-- Nevertheless we consider this a bug. Please report\n--2100-- it at http://valgrind.org/support/bug_reports.html.\n--2100-- WARNING: unhandled riscv64-linux syscall: 258\n--2100-- You may be able to write your own handler.\n--2100-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2100-- Nevertheless we consider this a bug. Please report\n--2100-- it at http://valgrind.org/support/bug_reports.html.\n--2100-- WARNING: unhandled riscv64-linux syscall: 258\n--2100-- You may be able to write your own handler.\n--2100-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2100-- Nevertheless we consider this a bug. Please report\n--2100-- it at http://valgrind.org/support/bug_reports.html.\n--2100-- WARNING: unhandled riscv64-linux syscall: 258\n--2100-- You may be able to write your own handler.\n--2100-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2100-- Nevertheless we consider this a bug. Please report\n--2100-- it at http://valgrind.org/support/bug_reports.html.\n--2100-- WARNING: unhandled riscv64-linux syscall: 258\n--2100-- You may be able to write your own handler.\n--2100-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2100-- Nevertheless we consider this a bug. Please report\n--2100-- it at http://valgrind.org/support/bug_reports.html.\n--2100-- WARNING: unhandled riscv64-linux syscall: 258\n--2100-- You may be able to write your own handler.\n--2100-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2100-- Nevertheless we consider this a bug. Please report\n--2100-- it at http://valgrind.org/support/bug_reports.html.\n--2100-- WARNING: unhandled riscv64-linux syscall: 258\n--2100-- You may be able to write your own handler.\n--2100-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2100-- Nevertheless we consider this a bug. Please report\n--2100-- it at http://valgrind.org/support/bug_reports.html.\n--2100-- WARNING: unhandled riscv64-linux syscall: 258\n--2100-- You may be able to write your own handler.\n--2100-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2100-- Nevertheless we consider this a bug. Please report\n--2100-- it at http://valgrind.org/support/bug_reports.html.\n--2100-- WARNING: unhandled riscv64-linux syscall: 258\n--2100-- You may be able to write your own handler.\n--2100-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2100-- Nevertheless we consider this a bug. Please report\n--2100-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 --- 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: [{'url': 'http://example.com/', 'parts': {'scheme': 'http', 'host': 'example.com', 'path': '/'}}, {'url': 'http://other.com/', 'parts': {'scheme': 'http', 'host': 'other.com', 'path': '/'}}] 105: failed localhost --iterate 'host=one two' --json --- stderr --- expected: '' got: '--2108-- WARNING: unhandled riscv64-linux syscall: 258\n--2108-- You may be able to write your own handler.\n--2108-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2108-- Nevertheless we consider this a bug. Please report\n--2108-- it at http://valgrind.org/support/bug_reports.html.\n--2108-- WARNING: unhandled riscv64-linux syscall: 258\n--2108-- You may be able to write your own handler.\n--2108-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2108-- Nevertheless we consider this a bug. Please report\n--2108-- it at http://valgrind.org/support/bug_reports.html.\n--2108-- WARNING: unhandled riscv64-linux syscall: 258\n--2108-- You may be able to write your own handler.\n--2108-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2108-- Nevertheless we consider this a bug. Please report\n--2108-- it at http://valgrind.org/support/bug_reports.html.\n--2108-- WARNING: unhandled riscv64-linux syscall: 258\n--2108-- You may be able to write your own handler.\n--2108-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2108-- Nevertheless we consider this a bug. Please report\n--2108-- it at http://valgrind.org/support/bug_reports.html.\n--2108-- WARNING: unhandled riscv64-linux syscall: 258\n--2108-- You may be able to write your own handler.\n--2108-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2108-- Nevertheless we consider this a bug. Please report\n--2108-- it at http://valgrind.org/support/bug_reports.html.\n--2108-- WARNING: unhandled riscv64-linux syscall: 258\n--2108-- You may be able to write your own handler.\n--2108-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2108-- Nevertheless we consider this a bug. Please report\n--2108-- it at http://valgrind.org/support/bug_reports.html.\n--2108-- WARNING: unhandled riscv64-linux syscall: 258\n--2108-- You may be able to write your own handler.\n--2108-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2108-- Nevertheless we consider this a bug. Please report\n--2108-- it at http://valgrind.org/support/bug_reports.html.\n--2108-- WARNING: unhandled riscv64-linux syscall: 258\n--2108-- You may be able to write your own handler.\n--2108-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2108-- Nevertheless we consider this a bug. Please report\n--2108-- it at http://valgrind.org/support/bug_reports.html.\n--2108-- WARNING: unhandled riscv64-linux syscall: 258\n--2108-- You may be able to write your own handler.\n--2108-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2108-- Nevertheless we consider this a bug. Please report\n--2108-- it at http://valgrind.org/support/bug_reports.html.\n--2108-- WARNING: unhandled riscv64-linux syscall: 258\n--2108-- You may be able to write your own handler.\n--2108-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2108-- Nevertheless we consider this a bug. Please report\n--2108-- it at http://valgrind.org/support/bug_reports.html.\n--2108-- WARNING: unhandled riscv64-linux syscall: 258\n--2108-- You may be able to write your own handler.\n--2108-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2108-- Nevertheless we consider this a bug. Please report\n--2108-- it at http://valgrind.org/support/bug_reports.html.\n--2108-- WARNING: unhandled riscv64-linux syscall: 258\n--2108-- You may be able to write your own handler.\n--2108-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2108-- Nevertheless we consider this a bug. Please report\n--2108-- it at http://valgrind.org/support/bug_reports.html.\n--2108-- WARNING: unhandled riscv64-linux syscall: 258\n--2108-- You may be able to write your own handler.\n--2108-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2108-- Nevertheless we consider this a bug. Please report\n--2108-- it at http://valgrind.org/support/bug_reports.html.\n--2108-- WARNING: unhandled riscv64-linux syscall: 258\n--2108-- You may be able to write your own handler.\n--2108-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2108-- Nevertheless we consider this a bug. Please report\n--2108-- it at http://valgrind.org/support/bug_reports.html.\n--2108-- WARNING: unhandled riscv64-linux syscall: 258\n--2108-- You may be able to write your own handler.\n--2108-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2108-- Nevertheless we consider this a bug. Please report\n--2108-- it at http://valgrind.org/support/bug_reports.html.\n--2108-- WARNING: unhandled riscv64-linux syscall: 258\n--2108-- You may be able to write your own handler.\n--2108-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2108-- Nevertheless we consider this a bug. Please report\n--2108-- it at http://valgrind.org/support/bug_reports.html.\n--2108-- WARNING: unhandled riscv64-linux syscall: 258\n--2108-- You may be able to write your own handler.\n--2108-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2108-- Nevertheless we consider this a bug. Please report\n--2108-- it at http://valgrind.org/support/bug_reports.html.\n--2108-- WARNING: unhandled riscv64-linux syscall: 258\n--2108-- You may be able to write your own handler.\n--2108-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2108-- Nevertheless we consider this a bug. Please report\n--2108-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 --- stdout --- expected: [{'url': 'http://one/', 'parts': {'scheme': 'http', 'host': 'one', 'path': '/'}}, {'url': 'http://two/', 'parts': {'scheme': 'http', 'host': 'two', 'path': '/'}}] got: [{'url': 'http://one/', 'parts': {'scheme': 'http', 'host': 'one', 'path': '/'}}, {'url': 'http://two/', 'parts': {'scheme': 'http', 'host': 'two', 'path': '/'}}] 106: failed --json -s scheme=irc -s host=curl.se --- stdout --- expected: [{'url': 'irc://curl.se/', 'parts': {'scheme': 'irc', 'host': 'curl.se', 'path': '/'}}] got: [{'url': 'irc://curl.se/', 'parts': {'scheme': 'irc', 'host': 'curl.se', 'path': '/'}}] --- returncode --- expected: 0 got: 0 --- stderr --- expected: '' got: '--2116-- WARNING: unhandled riscv64-linux syscall: 258\n--2116-- You may be able to write your own handler.\n--2116-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2116-- Nevertheless we consider this a bug. Please report\n--2116-- it at http://valgrind.org/support/bug_reports.html.\n--2116-- WARNING: unhandled riscv64-linux syscall: 258\n--2116-- You may be able to write your own handler.\n--2116-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2116-- Nevertheless we consider this a bug. Please report\n--2116-- it at http://valgrind.org/support/bug_reports.html.\n--2116-- WARNING: unhandled riscv64-linux syscall: 258\n--2116-- You may be able to write your own handler.\n--2116-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2116-- Nevertheless we consider this a bug. Please report\n--2116-- it at http://valgrind.org/support/bug_reports.html.\n--2116-- WARNING: unhandled riscv64-linux syscall: 258\n--2116-- You may be able to write your own handler.\n--2116-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2116-- Nevertheless we consider this a bug. Please report\n--2116-- it at http://valgrind.org/support/bug_reports.html.\n--2116-- WARNING: unhandled riscv64-linux syscall: 258\n--2116-- You may be able to write your own handler.\n--2116-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2116-- Nevertheless we consider this a bug. Please report\n--2116-- it at http://valgrind.org/support/bug_reports.html.\n--2116-- WARNING: unhandled riscv64-linux syscall: 258\n--2116-- You may be able to write your own handler.\n--2116-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2116-- Nevertheless we consider this a bug. Please report\n--2116-- it at http://valgrind.org/support/bug_reports.html.\n--2116-- WARNING: unhandled riscv64-linux syscall: 258\n--2116-- You may be able to write your own handler.\n--2116-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2116-- Nevertheless we consider this a bug. Please report\n--2116-- it at http://valgrind.org/support/bug_reports.html.\n--2116-- WARNING: unhandled riscv64-linux syscall: 258\n--2116-- You may be able to write your own handler.\n--2116-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2116-- Nevertheless we consider this a bug. Please report\n--2116-- it at http://valgrind.org/support/bug_reports.html.\n--2116-- WARNING: unhandled riscv64-linux syscall: 258\n--2116-- You may be able to write your own handler.\n--2116-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2116-- Nevertheless we consider this a bug. Please report\n--2116-- it at http://valgrind.org/support/bug_reports.html.\n--2116-- WARNING: unhandled riscv64-linux syscall: 258\n--2116-- You may be able to write your own handler.\n--2116-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2116-- Nevertheless we consider this a bug. Please report\n--2116-- it at http://valgrind.org/support/bug_reports.html.\n--2116-- WARNING: unhandled riscv64-linux syscall: 258\n--2116-- You may be able to write your own handler.\n--2116-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2116-- Nevertheless we consider this a bug. Please report\n--2116-- it at http://valgrind.org/support/bug_reports.html.\n--2116-- WARNING: unhandled riscv64-linux syscall: 258\n--2116-- You may be able to write your own handler.\n--2116-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2116-- Nevertheless we consider this a bug. Please report\n--2116-- it at http://valgrind.org/support/bug_reports.html.\n--2116-- WARNING: unhandled riscv64-linux syscall: 258\n--2116-- You may be able to write your own handler.\n--2116-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2116-- Nevertheless we consider this a bug. Please report\n--2116-- it at http://valgrind.org/support/bug_reports.html.\n--2116-- WARNING: unhandled riscv64-linux syscall: 258\n--2116-- You may be able to write your own handler.\n--2116-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2116-- Nevertheless we consider this a bug. Please report\n--2116-- it at http://valgrind.org/support/bug_reports.html.\n--2116-- WARNING: unhandled riscv64-linux syscall: 258\n--2116-- You may be able to write your own handler.\n--2116-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2116-- Nevertheless we consider this a bug. Please report\n--2116-- it at http://valgrind.org/support/bug_reports.html.\n--2116-- WARNING: unhandled riscv64-linux syscall: 258\n--2116-- You may be able to write your own handler.\n--2116-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2116-- Nevertheless we consider this a bug. Please report\n--2116-- it at http://valgrind.org/support/bug_reports.html.\n--2116-- WARNING: unhandled riscv64-linux syscall: 258\n--2116-- You may be able to write your own handler.\n--2116-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2116-- Nevertheless we consider this a bug. Please report\n--2116-- it at http://valgrind.org/support/bug_reports.html.\n--2116-- WARNING: unhandled riscv64-linux syscall: 258\n--2116-- You may be able to write your own handler.\n--2116-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2116-- Nevertheless we consider this a bug. Please report\n--2116-- it at http://valgrind.org/support/bug_reports.html.\n' 107: failed --json -s host=curl.se --- stdout --- expected: [] got: [] --- returncode --- expected: 7 got: 7 --- stderr --- expected: 'trurl error: not enough input for a URL\ntrurl error: Try trurl -h for help\n' got: '--2124-- WARNING: unhandled riscv64-linux syscall: 258\n--2124-- You may be able to write your own handler.\n--2124-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2124-- Nevertheless we consider this a bug. Please report\n--2124-- it at http://valgrind.org/support/bug_reports.html.\n--2124-- WARNING: unhandled riscv64-linux syscall: 258\n--2124-- You may be able to write your own handler.\n--2124-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2124-- Nevertheless we consider this a bug. Please report\n--2124-- it at http://valgrind.org/support/bug_reports.html.\n--2124-- WARNING: unhandled riscv64-linux syscall: 258\n--2124-- You may be able to write your own handler.\n--2124-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2124-- Nevertheless we consider this a bug. Please report\n--2124-- it at http://valgrind.org/support/bug_reports.html.\n--2124-- WARNING: unhandled riscv64-linux syscall: 258\n--2124-- You may be able to write your own handler.\n--2124-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2124-- Nevertheless we consider this a bug. Please report\n--2124-- it at http://valgrind.org/support/bug_reports.html.\n--2124-- WARNING: unhandled riscv64-linux syscall: 258\n--2124-- You may be able to write your own handler.\n--2124-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2124-- Nevertheless we consider this a bug. Please report\n--2124-- it at http://valgrind.org/support/bug_reports.html.\n--2124-- WARNING: unhandled riscv64-linux syscall: 258\n--2124-- You may be able to write your own handler.\n--2124-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2124-- Nevertheless we consider this a bug. Please report\n--2124-- it at http://valgrind.org/support/bug_reports.html.\n--2124-- WARNING: unhandled riscv64-linux syscall: 258\n--2124-- You may be able to write your own handler.\n--2124-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2124-- Nevertheless we consider this a bug. Please report\n--2124-- it at http://valgrind.org/support/bug_reports.html.\n--2124-- WARNING: unhandled riscv64-linux syscall: 258\n--2124-- You may be able to write your own handler.\n--2124-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2124-- Nevertheless we consider this a bug. Please report\n--2124-- it at http://valgrind.org/support/bug_reports.html.\n--2124-- WARNING: unhandled riscv64-linux syscall: 258\n--2124-- You may be able to write your own handler.\n--2124-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2124-- Nevertheless we consider this a bug. Please report\n--2124-- it at http://valgrind.org/support/bug_reports.html.\n--2124-- WARNING: unhandled riscv64-linux syscall: 258\n--2124-- You may be able to write your own handler.\n--2124-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2124-- Nevertheless we consider this a bug. Please report\n--2124-- it at http://valgrind.org/support/bug_reports.html.\n--2124-- WARNING: unhandled riscv64-linux syscall: 258\n--2124-- You may be able to write your own handler.\n--2124-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2124-- Nevertheless we consider this a bug. Please report\n--2124-- it at http://valgrind.org/support/bug_reports.html.\n--2124-- WARNING: unhandled riscv64-linux syscall: 258\n--2124-- You may be able to write your own handler.\n--2124-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2124-- Nevertheless we consider this a bug. Please report\n--2124-- it at http://valgrind.org/support/bug_reports.html.\n--2124-- WARNING: unhandled riscv64-linux syscall: 258\n--2124-- You may be able to write your own handler.\n--2124-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2124-- Nevertheless we consider this a bug. Please report\n--2124-- it at http://valgrind.org/support/bug_reports.html.\n--2124-- WARNING: unhandled riscv64-linux syscall: 258\n--2124-- You may be able to write your own handler.\n--2124-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2124-- Nevertheless we consider this a bug. Please report\n--2124-- it at http://valgrind.org/support/bug_reports.html.\n--2124-- WARNING: unhandled riscv64-linux syscall: 258\n--2124-- You may be able to write your own handler.\n--2124-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2124-- Nevertheless we consider this a bug. Please report\n--2124-- it at http://valgrind.org/support/bug_reports.html.\n--2124-- WARNING: unhandled riscv64-linux syscall: 258\n--2124-- You may be able to write your own handler.\n--2124-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2124-- Nevertheless we consider this a bug. Please report\n--2124-- it at http://valgrind.org/support/bug_reports.html.\n--2124-- WARNING: unhandled riscv64-linux syscall: 258\n--2124-- You may be able to write your own handler.\n--2124-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2124-- Nevertheless we consider this a bug. Please report\n--2124-- it at http://valgrind.org/support/bug_reports.html.\n--2124-- WARNING: unhandled riscv64-linux syscall: 258\n--2124-- You may be able to write your own handler.\n--2124-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2124-- Nevertheless we consider this a bug. Please report\n--2124-- it at http://valgrind.org/support/bug_reports.html.\ntrurl error: not enough input for a URL\ntrurl error: Try trurl -h for help\n' 109: failed -s scheme=imap --- stdout --- expected: '' got: '' --- returncode --- expected: 7 got: 7 --- stderr --- expected: 'trurl error: not enough input for a URL\ntrurl error: Try trurl -h for help\n' got: '--2140-- WARNING: unhandled riscv64-linux syscall: 258\n--2140-- You may be able to write your own handler.\n--2140-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2140-- Nevertheless we consider this a bug. Please report\n--2140-- it at http://valgrind.org/support/bug_reports.html.\n--2140-- WARNING: unhandled riscv64-linux syscall: 258\n--2140-- You may be able to write your own handler.\n--2140-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2140-- Nevertheless we consider this a bug. Please report\n--2140-- it at http://valgrind.org/support/bug_reports.html.\n--2140-- WARNING: unhandled riscv64-linux syscall: 258\n--2140-- You may be able to write your own handler.\n--2140-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2140-- Nevertheless we consider this a bug. Please report\n--2140-- it at http://valgrind.org/support/bug_reports.html.\n--2140-- WARNING: unhandled riscv64-linux syscall: 258\n--2140-- You may be able to write your own handler.\n--2140-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2140-- Nevertheless we consider this a bug. Please report\n--2140-- it at http://valgrind.org/support/bug_reports.html.\n--2140-- WARNING: unhandled riscv64-linux syscall: 258\n--2140-- You may be able to write your own handler.\n--2140-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2140-- Nevertheless we consider this a bug. Please report\n--2140-- it at http://valgrind.org/support/bug_reports.html.\n--2140-- WARNING: unhandled riscv64-linux syscall: 258\n--2140-- You may be able to write your own handler.\n--2140-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2140-- Nevertheless we consider this a bug. Please report\n--2140-- it at http://valgrind.org/support/bug_reports.html.\n--2140-- WARNING: unhandled riscv64-linux syscall: 258\n--2140-- You may be able to write your own handler.\n--2140-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2140-- Nevertheless we consider this a bug. Please report\n--2140-- it at http://valgrind.org/support/bug_reports.html.\n--2140-- WARNING: unhandled riscv64-linux syscall: 258\n--2140-- You may be able to write your own handler.\n--2140-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2140-- Nevertheless we consider this a bug. Please report\n--2140-- it at http://valgrind.org/support/bug_reports.html.\n--2140-- WARNING: unhandled riscv64-linux syscall: 258\n--2140-- You may be able to write your own handler.\n--2140-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2140-- Nevertheless we consider this a bug. Please report\n--2140-- it at http://valgrind.org/support/bug_reports.html.\n--2140-- WARNING: unhandled riscv64-linux syscall: 258\n--2140-- You may be able to write your own handler.\n--2140-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2140-- Nevertheless we consider this a bug. Please report\n--2140-- it at http://valgrind.org/support/bug_reports.html.\n--2140-- WARNING: unhandled riscv64-linux syscall: 258\n--2140-- You may be able to write your own handler.\n--2140-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2140-- Nevertheless we consider this a bug. Please report\n--2140-- it at http://valgrind.org/support/bug_reports.html.\n--2140-- WARNING: unhandled riscv64-linux syscall: 258\n--2140-- You may be able to write your own handler.\n--2140-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2140-- Nevertheless we consider this a bug. Please report\n--2140-- it at http://valgrind.org/support/bug_reports.html.\n--2140-- WARNING: unhandled riscv64-linux syscall: 258\n--2140-- You may be able to write your own handler.\n--2140-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2140-- Nevertheless we consider this a bug. Please report\n--2140-- it at http://valgrind.org/support/bug_reports.html.\n--2140-- WARNING: unhandled riscv64-linux syscall: 258\n--2140-- You may be able to write your own handler.\n--2140-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2140-- Nevertheless we consider this a bug. Please report\n--2140-- it at http://valgrind.org/support/bug_reports.html.\n--2140-- WARNING: unhandled riscv64-linux syscall: 258\n--2140-- You may be able to write your own handler.\n--2140-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2140-- Nevertheless we consider this a bug. Please report\n--2140-- it at http://valgrind.org/support/bug_reports.html.\n--2140-- WARNING: unhandled riscv64-linux syscall: 258\n--2140-- You may be able to write your own handler.\n--2140-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2140-- Nevertheless we consider this a bug. Please report\n--2140-- it at http://valgrind.org/support/bug_reports.html.\n--2140-- WARNING: unhandled riscv64-linux syscall: 258\n--2140-- You may be able to write your own handler.\n--2140-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2140-- Nevertheless we consider this a bug. Please report\n--2140-- it at http://valgrind.org/support/bug_reports.html.\n--2140-- WARNING: unhandled riscv64-linux syscall: 258\n--2140-- You may be able to write your own handler.\n--2140-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2140-- Nevertheless we consider this a bug. Please report\n--2140-- it at http://valgrind.org/support/bug_reports.html.\ntrurl error: not enough input for a URL\ntrurl error: Try trurl -h for help\n' 110: failed -g '{query:}' 'http://localhost/?=bar' --- stdout --- expected: 'bar\n' got: 'bar\n' --- returncode --- expected: 0 got: 0 --- stderr --- expected: '' got: '--2148-- WARNING: unhandled riscv64-linux syscall: 258\n--2148-- You may be able to write your own handler.\n--2148-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2148-- Nevertheless we consider this a bug. Please report\n--2148-- it at http://valgrind.org/support/bug_reports.html.\n--2148-- WARNING: unhandled riscv64-linux syscall: 258\n--2148-- You may be able to write your own handler.\n--2148-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2148-- Nevertheless we consider this a bug. Please report\n--2148-- it at http://valgrind.org/support/bug_reports.html.\n--2148-- WARNING: unhandled riscv64-linux syscall: 258\n--2148-- You may be able to write your own handler.\n--2148-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2148-- Nevertheless we consider this a bug. Please report\n--2148-- it at http://valgrind.org/support/bug_reports.html.\n--2148-- WARNING: unhandled riscv64-linux syscall: 258\n--2148-- You may be able to write your own handler.\n--2148-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2148-- Nevertheless we consider this a bug. Please report\n--2148-- it at http://valgrind.org/support/bug_reports.html.\n--2148-- WARNING: unhandled riscv64-linux syscall: 258\n--2148-- You may be able to write your own handler.\n--2148-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2148-- Nevertheless we consider this a bug. Please report\n--2148-- it at http://valgrind.org/support/bug_reports.html.\n--2148-- WARNING: unhandled riscv64-linux syscall: 258\n--2148-- You may be able to write your own handler.\n--2148-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2148-- Nevertheless we consider this a bug. Please report\n--2148-- it at http://valgrind.org/support/bug_reports.html.\n--2148-- WARNING: unhandled riscv64-linux syscall: 258\n--2148-- You may be able to write your own handler.\n--2148-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2148-- Nevertheless we consider this a bug. Please report\n--2148-- it at http://valgrind.org/support/bug_reports.html.\n--2148-- WARNING: unhandled riscv64-linux syscall: 258\n--2148-- You may be able to write your own handler.\n--2148-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2148-- Nevertheless we consider this a bug. Please report\n--2148-- it at http://valgrind.org/support/bug_reports.html.\n--2148-- WARNING: unhandled riscv64-linux syscall: 258\n--2148-- You may be able to write your own handler.\n--2148-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2148-- Nevertheless we consider this a bug. Please report\n--2148-- it at http://valgrind.org/support/bug_reports.html.\n--2148-- WARNING: unhandled riscv64-linux syscall: 258\n--2148-- You may be able to write your own handler.\n--2148-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2148-- Nevertheless we consider this a bug. Please report\n--2148-- it at http://valgrind.org/support/bug_reports.html.\n--2148-- WARNING: unhandled riscv64-linux syscall: 258\n--2148-- You may be able to write your own handler.\n--2148-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2148-- Nevertheless we consider this a bug. Please report\n--2148-- it at http://valgrind.org/support/bug_reports.html.\n--2148-- WARNING: unhandled riscv64-linux syscall: 258\n--2148-- You may be able to write your own handler.\n--2148-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2148-- Nevertheless we consider this a bug. Please report\n--2148-- it at http://valgrind.org/support/bug_reports.html.\n--2148-- WARNING: unhandled riscv64-linux syscall: 258\n--2148-- You may be able to write your own handler.\n--2148-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2148-- Nevertheless we consider this a bug. Please report\n--2148-- it at http://valgrind.org/support/bug_reports.html.\n--2148-- WARNING: unhandled riscv64-linux syscall: 258\n--2148-- You may be able to write your own handler.\n--2148-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2148-- Nevertheless we consider this a bug. Please report\n--2148-- it at http://valgrind.org/support/bug_reports.html.\n--2148-- WARNING: unhandled riscv64-linux syscall: 258\n--2148-- You may be able to write your own handler.\n--2148-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2148-- Nevertheless we consider this a bug. Please report\n--2148-- it at http://valgrind.org/support/bug_reports.html.\n--2148-- WARNING: unhandled riscv64-linux syscall: 258\n--2148-- You may be able to write your own handler.\n--2148-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2148-- Nevertheless we consider this a bug. Please report\n--2148-- it at http://valgrind.org/support/bug_reports.html.\n--2148-- WARNING: unhandled riscv64-linux syscall: 258\n--2148-- You may be able to write your own handler.\n--2148-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2148-- Nevertheless we consider this a bug. Please report\n--2148-- it at http://valgrind.org/support/bug_reports.html.\n--2148-- WARNING: unhandled riscv64-linux syscall: 258\n--2148-- You may be able to write your own handler.\n--2148-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2148-- Nevertheless we consider this a bug. Please report\n--2148-- it at http://valgrind.org/support/bug_reports.html.\n' 111: failed --json 'https://curl.se/?&&&' --- stdout --- expected: [{'url': 'https://curl.se/?&&&', 'parts': {'scheme': 'https', 'host': 'curl.se', 'path': '/', 'query': '&&&'}, 'params': []}] got: [{'url': 'https://curl.se/?&&&', 'parts': {'scheme': 'https', 'host': 'curl.se', 'path': '/', 'query': '&&&'}, 'params': []}] --- returncode --- expected: 0 got: 0 --- stderr --- expected: '' got: '--2156-- WARNING: unhandled riscv64-linux syscall: 258\n--2156-- You may be able to write your own handler.\n--2156-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2156-- Nevertheless we consider this a bug. Please report\n--2156-- it at http://valgrind.org/support/bug_reports.html.\n--2156-- WARNING: unhandled riscv64-linux syscall: 258\n--2156-- You may be able to write your own handler.\n--2156-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2156-- Nevertheless we consider this a bug. Please report\n--2156-- it at http://valgrind.org/support/bug_reports.html.\n--2156-- WARNING: unhandled riscv64-linux syscall: 258\n--2156-- You may be able to write your own handler.\n--2156-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2156-- Nevertheless we consider this a bug. Please report\n--2156-- it at http://valgrind.org/support/bug_reports.html.\n--2156-- WARNING: unhandled riscv64-linux syscall: 258\n--2156-- You may be able to write your own handler.\n--2156-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2156-- Nevertheless we consider this a bug. Please report\n--2156-- it at http://valgrind.org/support/bug_reports.html.\n--2156-- WARNING: unhandled riscv64-linux syscall: 258\n--2156-- You may be able to write your own handler.\n--2156-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2156-- Nevertheless we consider this a bug. Please report\n--2156-- it at http://valgrind.org/support/bug_reports.html.\n--2156-- WARNING: unhandled riscv64-linux syscall: 258\n--2156-- You may be able to write your own handler.\n--2156-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2156-- Nevertheless we consider this a bug. Please report\n--2156-- it at http://valgrind.org/support/bug_reports.html.\n--2156-- WARNING: unhandled riscv64-linux syscall: 258\n--2156-- You may be able to write your own handler.\n--2156-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2156-- Nevertheless we consider this a bug. Please report\n--2156-- it at http://valgrind.org/support/bug_reports.html.\n--2156-- WARNING: unhandled riscv64-linux syscall: 258\n--2156-- You may be able to write your own handler.\n--2156-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2156-- Nevertheless we consider this a bug. Please report\n--2156-- it at http://valgrind.org/support/bug_reports.html.\n--2156-- WARNING: unhandled riscv64-linux syscall: 258\n--2156-- You may be able to write your own handler.\n--2156-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2156-- Nevertheless we consider this a bug. Please report\n--2156-- it at http://valgrind.org/support/bug_reports.html.\n--2156-- WARNING: unhandled riscv64-linux syscall: 258\n--2156-- You may be able to write your own handler.\n--2156-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2156-- Nevertheless we consider this a bug. Please report\n--2156-- it at http://valgrind.org/support/bug_reports.html.\n--2156-- WARNING: unhandled riscv64-linux syscall: 258\n--2156-- You may be able to write your own handler.\n--2156-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2156-- Nevertheless we consider this a bug. Please report\n--2156-- it at http://valgrind.org/support/bug_reports.html.\n--2156-- WARNING: unhandled riscv64-linux syscall: 258\n--2156-- You may be able to write your own handler.\n--2156-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2156-- Nevertheless we consider this a bug. Please report\n--2156-- it at http://valgrind.org/support/bug_reports.html.\n--2156-- WARNING: unhandled riscv64-linux syscall: 258\n--2156-- You may be able to write your own handler.\n--2156-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2156-- Nevertheless we consider this a bug. Please report\n--2156-- it at http://valgrind.org/support/bug_reports.html.\n--2156-- WARNING: unhandled riscv64-linux syscall: 258\n--2156-- You may be able to write your own handler.\n--2156-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2156-- Nevertheless we consider this a bug. Please report\n--2156-- it at http://valgrind.org/support/bug_reports.html.\n--2156-- WARNING: unhandled riscv64-linux syscall: 258\n--2156-- You may be able to write your own handler.\n--2156-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2156-- Nevertheless we consider this a bug. Please report\n--2156-- it at http://valgrind.org/support/bug_reports.html.\n--2156-- WARNING: unhandled riscv64-linux syscall: 258\n--2156-- You may be able to write your own handler.\n--2156-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2156-- Nevertheless we consider this a bug. Please report\n--2156-- it at http://valgrind.org/support/bug_reports.html.\n--2156-- WARNING: unhandled riscv64-linux syscall: 258\n--2156-- You may be able to write your own handler.\n--2156-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2156-- Nevertheless we consider this a bug. Please report\n--2156-- it at http://valgrind.org/support/bug_reports.html.\n--2156-- WARNING: unhandled riscv64-linux syscall: 258\n--2156-- You may be able to write your own handler.\n--2156-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2156-- Nevertheless we consider this a bug. Please report\n--2156-- it at http://valgrind.org/support/bug_reports.html.\n' 112: 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: [{'url': 'http://localhost/?bar=ar', 'parts': {'scheme': 'http', 'host': 'localhost', 'path': '/', 'query': 'bar=ar'}, 'params': [{'key': 'bar', 'value': 'ar'}]}] --- returncode --- expected: 0 got: 0 --- stderr --- expected: '' got: '--2164-- WARNING: unhandled riscv64-linux syscall: 258\n--2164-- You may be able to write your own handler.\n--2164-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2164-- Nevertheless we consider this a bug. Please report\n--2164-- it at http://valgrind.org/support/bug_reports.html.\n--2164-- WARNING: unhandled riscv64-linux syscall: 258\n--2164-- You may be able to write your own handler.\n--2164-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2164-- Nevertheless we consider this a bug. Please report\n--2164-- it at http://valgrind.org/support/bug_reports.html.\n--2164-- WARNING: unhandled riscv64-linux syscall: 258\n--2164-- You may be able to write your own handler.\n--2164-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2164-- Nevertheless we consider this a bug. Please report\n--2164-- it at http://valgrind.org/support/bug_reports.html.\n--2164-- WARNING: unhandled riscv64-linux syscall: 258\n--2164-- You may be able to write your own handler.\n--2164-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2164-- Nevertheless we consider this a bug. Please report\n--2164-- it at http://valgrind.org/support/bug_reports.html.\n--2164-- WARNING: unhandled riscv64-linux syscall: 258\n--2164-- You may be able to write your own handler.\n--2164-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2164-- Nevertheless we consider this a bug. Please report\n--2164-- it at http://valgrind.org/support/bug_reports.html.\n--2164-- WARNING: unhandled riscv64-linux syscall: 258\n--2164-- You may be able to write your own handler.\n--2164-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2164-- Nevertheless we consider this a bug. Please report\n--2164-- it at http://valgrind.org/support/bug_reports.html.\n--2164-- WARNING: unhandled riscv64-linux syscall: 258\n--2164-- You may be able to write your own handler.\n--2164-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2164-- Nevertheless we consider this a bug. Please report\n--2164-- it at http://valgrind.org/support/bug_reports.html.\n--2164-- WARNING: unhandled riscv64-linux syscall: 258\n--2164-- You may be able to write your own handler.\n--2164-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2164-- Nevertheless we consider this a bug. Please report\n--2164-- it at http://valgrind.org/support/bug_reports.html.\n--2164-- WARNING: unhandled riscv64-linux syscall: 258\n--2164-- You may be able to write your own handler.\n--2164-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2164-- Nevertheless we consider this a bug. Please report\n--2164-- it at http://valgrind.org/support/bug_reports.html.\n--2164-- WARNING: unhandled riscv64-linux syscall: 258\n--2164-- You may be able to write your own handler.\n--2164-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2164-- Nevertheless we consider this a bug. Please report\n--2164-- it at http://valgrind.org/support/bug_reports.html.\n--2164-- WARNING: unhandled riscv64-linux syscall: 258\n--2164-- You may be able to write your own handler.\n--2164-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2164-- Nevertheless we consider this a bug. Please report\n--2164-- it at http://valgrind.org/support/bug_reports.html.\n--2164-- WARNING: unhandled riscv64-linux syscall: 258\n--2164-- You may be able to write your own handler.\n--2164-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2164-- Nevertheless we consider this a bug. Please report\n--2164-- it at http://valgrind.org/support/bug_reports.html.\n--2164-- WARNING: unhandled riscv64-linux syscall: 258\n--2164-- You may be able to write your own handler.\n--2164-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2164-- Nevertheless we consider this a bug. Please report\n--2164-- it at http://valgrind.org/support/bug_reports.html.\n--2164-- WARNING: unhandled riscv64-linux syscall: 258\n--2164-- You may be able to write your own handler.\n--2164-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2164-- Nevertheless we consider this a bug. Please report\n--2164-- it at http://valgrind.org/support/bug_reports.html.\n--2164-- WARNING: unhandled riscv64-linux syscall: 258\n--2164-- You may be able to write your own handler.\n--2164-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2164-- Nevertheless we consider this a bug. Please report\n--2164-- it at http://valgrind.org/support/bug_reports.html.\n--2164-- WARNING: unhandled riscv64-linux syscall: 258\n--2164-- You may be able to write your own handler.\n--2164-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2164-- Nevertheless we consider this a bug. Please report\n--2164-- it at http://valgrind.org/support/bug_reports.html.\n--2164-- WARNING: unhandled riscv64-linux syscall: 258\n--2164-- You may be able to write your own handler.\n--2164-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2164-- Nevertheless we consider this a bug. Please report\n--2164-- it at http://valgrind.org/support/bug_reports.html.\n--2164-- WARNING: unhandled riscv64-linux syscall: 258\n--2164-- You may be able to write your own handler.\n--2164-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2164-- Nevertheless we consider this a bug. Please report\n--2164-- it at http://valgrind.org/support/bug_reports.html.\n' 113: 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: [{'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': ''}]}] --- returncode --- expected: 0 got: 0 --- stderr --- expected: '' got: '--2172-- WARNING: unhandled riscv64-linux syscall: 258\n--2172-- You may be able to write your own handler.\n--2172-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2172-- Nevertheless we consider this a bug. Please report\n--2172-- it at http://valgrind.org/support/bug_reports.html.\n--2172-- WARNING: unhandled riscv64-linux syscall: 258\n--2172-- You may be able to write your own handler.\n--2172-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2172-- Nevertheless we consider this a bug. Please report\n--2172-- it at http://valgrind.org/support/bug_reports.html.\n--2172-- WARNING: unhandled riscv64-linux syscall: 258\n--2172-- You may be able to write your own handler.\n--2172-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2172-- Nevertheless we consider this a bug. Please report\n--2172-- it at http://valgrind.org/support/bug_reports.html.\n--2172-- WARNING: unhandled riscv64-linux syscall: 258\n--2172-- You may be able to write your own handler.\n--2172-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2172-- Nevertheless we consider this a bug. Please report\n--2172-- it at http://valgrind.org/support/bug_reports.html.\n--2172-- WARNING: unhandled riscv64-linux syscall: 258\n--2172-- You may be able to write your own handler.\n--2172-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2172-- Nevertheless we consider this a bug. Please report\n--2172-- it at http://valgrind.org/support/bug_reports.html.\n--2172-- WARNING: unhandled riscv64-linux syscall: 258\n--2172-- You may be able to write your own handler.\n--2172-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2172-- Nevertheless we consider this a bug. Please report\n--2172-- it at http://valgrind.org/support/bug_reports.html.\n--2172-- WARNING: unhandled riscv64-linux syscall: 258\n--2172-- You may be able to write your own handler.\n--2172-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2172-- Nevertheless we consider this a bug. Please report\n--2172-- it at http://valgrind.org/support/bug_reports.html.\n--2172-- WARNING: unhandled riscv64-linux syscall: 258\n--2172-- You may be able to write your own handler.\n--2172-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2172-- Nevertheless we consider this a bug. Please report\n--2172-- it at http://valgrind.org/support/bug_reports.html.\n--2172-- WARNING: unhandled riscv64-linux syscall: 258\n--2172-- You may be able to write your own handler.\n--2172-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2172-- Nevertheless we consider this a bug. Please report\n--2172-- it at http://valgrind.org/support/bug_reports.html.\n--2172-- WARNING: unhandled riscv64-linux syscall: 258\n--2172-- You may be able to write your own handler.\n--2172-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2172-- Nevertheless we consider this a bug. Please report\n--2172-- it at http://valgrind.org/support/bug_reports.html.\n--2172-- WARNING: unhandled riscv64-linux syscall: 258\n--2172-- You may be able to write your own handler.\n--2172-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2172-- Nevertheless we consider this a bug. Please report\n--2172-- it at http://valgrind.org/support/bug_reports.html.\n--2172-- WARNING: unhandled riscv64-linux syscall: 258\n--2172-- You may be able to write your own handler.\n--2172-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2172-- Nevertheless we consider this a bug. Please report\n--2172-- it at http://valgrind.org/support/bug_reports.html.\n--2172-- WARNING: unhandled riscv64-linux syscall: 258\n--2172-- You may be able to write your own handler.\n--2172-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2172-- Nevertheless we consider this a bug. Please report\n--2172-- it at http://valgrind.org/support/bug_reports.html.\n--2172-- WARNING: unhandled riscv64-linux syscall: 258\n--2172-- You may be able to write your own handler.\n--2172-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2172-- Nevertheless we consider this a bug. Please report\n--2172-- it at http://valgrind.org/support/bug_reports.html.\n--2172-- WARNING: unhandled riscv64-linux syscall: 258\n--2172-- You may be able to write your own handler.\n--2172-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2172-- Nevertheless we consider this a bug. Please report\n--2172-- it at http://valgrind.org/support/bug_reports.html.\n--2172-- WARNING: unhandled riscv64-linux syscall: 258\n--2172-- You may be able to write your own handler.\n--2172-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2172-- Nevertheless we consider this a bug. Please report\n--2172-- it at http://valgrind.org/support/bug_reports.html.\n--2172-- WARNING: unhandled riscv64-linux syscall: 258\n--2172-- You may be able to write your own handler.\n--2172-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2172-- Nevertheless we consider this a bug. Please report\n--2172-- it at http://valgrind.org/support/bug_reports.html.\n--2172-- WARNING: unhandled riscv64-linux syscall: 258\n--2172-- You may be able to write your own handler.\n--2172-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2172-- Nevertheless we consider this a bug. Please report\n--2172-- it at http://valgrind.org/support/bug_reports.html.\n' 114: failed 'https://räksmörgås.se' -g '{default:puny:url}' --- stderr --- expected: '' got: '--2181-- WARNING: unhandled riscv64-linux syscall: 258\n--2181-- You may be able to write your own handler.\n--2181-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2181-- Nevertheless we consider this a bug. Please report\n--2181-- it at http://valgrind.org/support/bug_reports.html.\n--2181-- WARNING: unhandled riscv64-linux syscall: 258\n--2181-- You may be able to write your own handler.\n--2181-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2181-- Nevertheless we consider this a bug. Please report\n--2181-- it at http://valgrind.org/support/bug_reports.html.\n--2181-- WARNING: unhandled riscv64-linux syscall: 258\n--2181-- You may be able to write your own handler.\n--2181-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2181-- Nevertheless we consider this a bug. Please report\n--2181-- it at http://valgrind.org/support/bug_reports.html.\n--2181-- WARNING: unhandled riscv64-linux syscall: 258\n--2181-- You may be able to write your own handler.\n--2181-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2181-- Nevertheless we consider this a bug. Please report\n--2181-- it at http://valgrind.org/support/bug_reports.html.\n--2181-- WARNING: unhandled riscv64-linux syscall: 258\n--2181-- You may be able to write your own handler.\n--2181-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2181-- Nevertheless we consider this a bug. Please report\n--2181-- it at http://valgrind.org/support/bug_reports.html.\n--2181-- WARNING: unhandled riscv64-linux syscall: 258\n--2181-- You may be able to write your own handler.\n--2181-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2181-- Nevertheless we consider this a bug. Please report\n--2181-- it at http://valgrind.org/support/bug_reports.html.\n--2181-- WARNING: unhandled riscv64-linux syscall: 258\n--2181-- You may be able to write your own handler.\n--2181-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2181-- Nevertheless we consider this a bug. Please report\n--2181-- it at http://valgrind.org/support/bug_reports.html.\n--2181-- WARNING: unhandled riscv64-linux syscall: 258\n--2181-- You may be able to write your own handler.\n--2181-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2181-- Nevertheless we consider this a bug. Please report\n--2181-- it at http://valgrind.org/support/bug_reports.html.\n--2181-- WARNING: unhandled riscv64-linux syscall: 258\n--2181-- You may be able to write your own handler.\n--2181-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2181-- Nevertheless we consider this a bug. Please report\n--2181-- it at http://valgrind.org/support/bug_reports.html.\n--2181-- WARNING: unhandled riscv64-linux syscall: 258\n--2181-- You may be able to write your own handler.\n--2181-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2181-- Nevertheless we consider this a bug. Please report\n--2181-- it at http://valgrind.org/support/bug_reports.html.\n--2181-- WARNING: unhandled riscv64-linux syscall: 258\n--2181-- You may be able to write your own handler.\n--2181-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2181-- Nevertheless we consider this a bug. Please report\n--2181-- it at http://valgrind.org/support/bug_reports.html.\n--2181-- WARNING: unhandled riscv64-linux syscall: 258\n--2181-- You may be able to write your own handler.\n--2181-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2181-- Nevertheless we consider this a bug. Please report\n--2181-- it at http://valgrind.org/support/bug_reports.html.\n--2181-- WARNING: unhandled riscv64-linux syscall: 258\n--2181-- You may be able to write your own handler.\n--2181-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2181-- Nevertheless we consider this a bug. Please report\n--2181-- it at http://valgrind.org/support/bug_reports.html.\n--2181-- WARNING: unhandled riscv64-linux syscall: 258\n--2181-- You may be able to write your own handler.\n--2181-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2181-- Nevertheless we consider this a bug. Please report\n--2181-- it at http://valgrind.org/support/bug_reports.html.\n--2181-- WARNING: unhandled riscv64-linux syscall: 258\n--2181-- You may be able to write your own handler.\n--2181-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2181-- Nevertheless we consider this a bug. Please report\n--2181-- it at http://valgrind.org/support/bug_reports.html.\n--2181-- WARNING: unhandled riscv64-linux syscall: 258\n--2181-- You may be able to write your own handler.\n--2181-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2181-- Nevertheless we consider this a bug. Please report\n--2181-- it at http://valgrind.org/support/bug_reports.html.\n--2181-- WARNING: unhandled riscv64-linux syscall: 258\n--2181-- You may be able to write your own handler.\n--2181-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2181-- Nevertheless we consider this a bug. Please report\n--2181-- it at http://valgrind.org/support/bug_reports.html.\n--2181-- WARNING: unhandled riscv64-linux syscall: 258\n--2181-- You may be able to write your own handler.\n--2181-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2181-- Nevertheless we consider this a bug. Please report\n--2181-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 --- stdout --- expected: 'https://xn--rksmrgs-5wao1o.se:443/\n' got: 'https://xn--rksmrgs-5wao1o.se:443/\n' 115: failed 'https://räksmörgås.se' -g '{puny:url}' --- stderr --- expected: '' got: '--2194-- WARNING: unhandled riscv64-linux syscall: 258\n--2194-- You may be able to write your own handler.\n--2194-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2194-- Nevertheless we consider this a bug. Please report\n--2194-- it at http://valgrind.org/support/bug_reports.html.\n--2194-- WARNING: unhandled riscv64-linux syscall: 258\n--2194-- You may be able to write your own handler.\n--2194-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2194-- Nevertheless we consider this a bug. Please report\n--2194-- it at http://valgrind.org/support/bug_reports.html.\n--2194-- WARNING: unhandled riscv64-linux syscall: 258\n--2194-- You may be able to write your own handler.\n--2194-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2194-- Nevertheless we consider this a bug. Please report\n--2194-- it at http://valgrind.org/support/bug_reports.html.\n--2194-- WARNING: unhandled riscv64-linux syscall: 258\n--2194-- You may be able to write your own handler.\n--2194-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2194-- Nevertheless we consider this a bug. Please report\n--2194-- it at http://valgrind.org/support/bug_reports.html.\n--2194-- WARNING: unhandled riscv64-linux syscall: 258\n--2194-- You may be able to write your own handler.\n--2194-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2194-- Nevertheless we consider this a bug. Please report\n--2194-- it at http://valgrind.org/support/bug_reports.html.\n--2194-- WARNING: unhandled riscv64-linux syscall: 258\n--2194-- You may be able to write your own handler.\n--2194-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2194-- Nevertheless we consider this a bug. Please report\n--2194-- it at http://valgrind.org/support/bug_reports.html.\n--2194-- WARNING: unhandled riscv64-linux syscall: 258\n--2194-- You may be able to write your own handler.\n--2194-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2194-- Nevertheless we consider this a bug. Please report\n--2194-- it at http://valgrind.org/support/bug_reports.html.\n--2194-- WARNING: unhandled riscv64-linux syscall: 258\n--2194-- You may be able to write your own handler.\n--2194-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2194-- Nevertheless we consider this a bug. Please report\n--2194-- it at http://valgrind.org/support/bug_reports.html.\n--2194-- WARNING: unhandled riscv64-linux syscall: 258\n--2194-- You may be able to write your own handler.\n--2194-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2194-- Nevertheless we consider this a bug. Please report\n--2194-- it at http://valgrind.org/support/bug_reports.html.\n--2194-- WARNING: unhandled riscv64-linux syscall: 258\n--2194-- You may be able to write your own handler.\n--2194-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2194-- Nevertheless we consider this a bug. Please report\n--2194-- it at http://valgrind.org/support/bug_reports.html.\n--2194-- WARNING: unhandled riscv64-linux syscall: 258\n--2194-- You may be able to write your own handler.\n--2194-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2194-- Nevertheless we consider this a bug. Please report\n--2194-- it at http://valgrind.org/support/bug_reports.html.\n--2194-- WARNING: unhandled riscv64-linux syscall: 258\n--2194-- You may be able to write your own handler.\n--2194-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2194-- Nevertheless we consider this a bug. Please report\n--2194-- it at http://valgrind.org/support/bug_reports.html.\n--2194-- WARNING: unhandled riscv64-linux syscall: 258\n--2194-- You may be able to write your own handler.\n--2194-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2194-- Nevertheless we consider this a bug. Please report\n--2194-- it at http://valgrind.org/support/bug_reports.html.\n--2194-- WARNING: unhandled riscv64-linux syscall: 258\n--2194-- You may be able to write your own handler.\n--2194-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2194-- Nevertheless we consider this a bug. Please report\n--2194-- it at http://valgrind.org/support/bug_reports.html.\n--2194-- WARNING: unhandled riscv64-linux syscall: 258\n--2194-- You may be able to write your own handler.\n--2194-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2194-- Nevertheless we consider this a bug. Please report\n--2194-- it at http://valgrind.org/support/bug_reports.html.\n--2194-- WARNING: unhandled riscv64-linux syscall: 258\n--2194-- You may be able to write your own handler.\n--2194-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2194-- Nevertheless we consider this a bug. Please report\n--2194-- it at http://valgrind.org/support/bug_reports.html.\n--2194-- WARNING: unhandled riscv64-linux syscall: 258\n--2194-- You may be able to write your own handler.\n--2194-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2194-- Nevertheless we consider this a bug. Please report\n--2194-- it at http://valgrind.org/support/bug_reports.html.\n--2194-- WARNING: unhandled riscv64-linux syscall: 258\n--2194-- You may be able to write your own handler.\n--2194-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2194-- Nevertheless we consider this a bug. Please report\n--2194-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 --- stdout --- expected: 'https://xn--rksmrgs-5wao1o.se/\n' got: 'https://xn--rksmrgs-5wao1o.se/\n' 116: failed 'https://räksmörgås.se' -g '{puny:host}' --- stderr --- expected: '' got: '--2205-- WARNING: unhandled riscv64-linux syscall: 258\n--2205-- You may be able to write your own handler.\n--2205-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2205-- Nevertheless we consider this a bug. Please report\n--2205-- it at http://valgrind.org/support/bug_reports.html.\n--2205-- WARNING: unhandled riscv64-linux syscall: 258\n--2205-- You may be able to write your own handler.\n--2205-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2205-- Nevertheless we consider this a bug. Please report\n--2205-- it at http://valgrind.org/support/bug_reports.html.\n--2205-- WARNING: unhandled riscv64-linux syscall: 258\n--2205-- You may be able to write your own handler.\n--2205-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2205-- Nevertheless we consider this a bug. Please report\n--2205-- it at http://valgrind.org/support/bug_reports.html.\n--2205-- WARNING: unhandled riscv64-linux syscall: 258\n--2205-- You may be able to write your own handler.\n--2205-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2205-- Nevertheless we consider this a bug. Please report\n--2205-- it at http://valgrind.org/support/bug_reports.html.\n--2205-- WARNING: unhandled riscv64-linux syscall: 258\n--2205-- You may be able to write your own handler.\n--2205-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2205-- Nevertheless we consider this a bug. Please report\n--2205-- it at http://valgrind.org/support/bug_reports.html.\n--2205-- WARNING: unhandled riscv64-linux syscall: 258\n--2205-- You may be able to write your own handler.\n--2205-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2205-- Nevertheless we consider this a bug. Please report\n--2205-- it at http://valgrind.org/support/bug_reports.html.\n--2205-- WARNING: unhandled riscv64-linux syscall: 258\n--2205-- You may be able to write your own handler.\n--2205-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2205-- Nevertheless we consider this a bug. Please report\n--2205-- it at http://valgrind.org/support/bug_reports.html.\n--2205-- WARNING: unhandled riscv64-linux syscall: 258\n--2205-- You may be able to write your own handler.\n--2205-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2205-- Nevertheless we consider this a bug. Please report\n--2205-- it at http://valgrind.org/support/bug_reports.html.\n--2205-- WARNING: unhandled riscv64-linux syscall: 258\n--2205-- You may be able to write your own handler.\n--2205-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2205-- Nevertheless we consider this a bug. Please report\n--2205-- it at http://valgrind.org/support/bug_reports.html.\n--2205-- WARNING: unhandled riscv64-linux syscall: 258\n--2205-- You may be able to write your own handler.\n--2205-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2205-- Nevertheless we consider this a bug. Please report\n--2205-- it at http://valgrind.org/support/bug_reports.html.\n--2205-- WARNING: unhandled riscv64-linux syscall: 258\n--2205-- You may be able to write your own handler.\n--2205-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2205-- Nevertheless we consider this a bug. Please report\n--2205-- it at http://valgrind.org/support/bug_reports.html.\n--2205-- WARNING: unhandled riscv64-linux syscall: 258\n--2205-- You may be able to write your own handler.\n--2205-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2205-- Nevertheless we consider this a bug. Please report\n--2205-- it at http://valgrind.org/support/bug_reports.html.\n--2205-- WARNING: unhandled riscv64-linux syscall: 258\n--2205-- You may be able to write your own handler.\n--2205-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2205-- Nevertheless we consider this a bug. Please report\n--2205-- it at http://valgrind.org/support/bug_reports.html.\n--2205-- WARNING: unhandled riscv64-linux syscall: 258\n--2205-- You may be able to write your own handler.\n--2205-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2205-- Nevertheless we consider this a bug. Please report\n--2205-- it at http://valgrind.org/support/bug_reports.html.\n--2205-- WARNING: unhandled riscv64-linux syscall: 258\n--2205-- You may be able to write your own handler.\n--2205-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2205-- Nevertheless we consider this a bug. Please report\n--2205-- it at http://valgrind.org/support/bug_reports.html.\n--2205-- WARNING: unhandled riscv64-linux syscall: 258\n--2205-- You may be able to write your own handler.\n--2205-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2205-- Nevertheless we consider this a bug. Please report\n--2205-- it at http://valgrind.org/support/bug_reports.html.\n--2205-- WARNING: unhandled riscv64-linux syscall: 258\n--2205-- You may be able to write your own handler.\n--2205-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2205-- Nevertheless we consider this a bug. Please report\n--2205-- it at http://valgrind.org/support/bug_reports.html.\n--2205-- WARNING: unhandled riscv64-linux syscall: 258\n--2205-- You may be able to write your own handler.\n--2205-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2205-- Nevertheless we consider this a bug. Please report\n--2205-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 --- stdout --- expected: 'xn--rksmrgs-5wao1o.se\n' got: 'xn--rksmrgs-5wao1o.se\n' 120: failed localhost -s host=foo --iterate 'host=bar baz' --- stdout --- expected: '' got: '' --- returncode --- expected: 11 got: 11 --- stderr --- expected: 'trurl error: duplicate --iterate and --set for component host\ntrurl error: Try trurl -h for help\n' got: '--2239-- WARNING: unhandled riscv64-linux syscall: 258\n--2239-- You may be able to write your own handler.\n--2239-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2239-- Nevertheless we consider this a bug. Please report\n--2239-- it at http://valgrind.org/support/bug_reports.html.\n--2239-- WARNING: unhandled riscv64-linux syscall: 258\n--2239-- You may be able to write your own handler.\n--2239-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2239-- Nevertheless we consider this a bug. Please report\n--2239-- it at http://valgrind.org/support/bug_reports.html.\n--2239-- WARNING: unhandled riscv64-linux syscall: 258\n--2239-- You may be able to write your own handler.\n--2239-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2239-- Nevertheless we consider this a bug. Please report\n--2239-- it at http://valgrind.org/support/bug_reports.html.\n--2239-- WARNING: unhandled riscv64-linux syscall: 258\n--2239-- You may be able to write your own handler.\n--2239-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2239-- Nevertheless we consider this a bug. Please report\n--2239-- it at http://valgrind.org/support/bug_reports.html.\n--2239-- WARNING: unhandled riscv64-linux syscall: 258\n--2239-- You may be able to write your own handler.\n--2239-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2239-- Nevertheless we consider this a bug. Please report\n--2239-- it at http://valgrind.org/support/bug_reports.html.\n--2239-- WARNING: unhandled riscv64-linux syscall: 258\n--2239-- You may be able to write your own handler.\n--2239-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2239-- Nevertheless we consider this a bug. Please report\n--2239-- it at http://valgrind.org/support/bug_reports.html.\n--2239-- WARNING: unhandled riscv64-linux syscall: 258\n--2239-- You may be able to write your own handler.\n--2239-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2239-- Nevertheless we consider this a bug. Please report\n--2239-- it at http://valgrind.org/support/bug_reports.html.\n--2239-- WARNING: unhandled riscv64-linux syscall: 258\n--2239-- You may be able to write your own handler.\n--2239-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2239-- Nevertheless we consider this a bug. Please report\n--2239-- it at http://valgrind.org/support/bug_reports.html.\n--2239-- WARNING: unhandled riscv64-linux syscall: 258\n--2239-- You may be able to write your own handler.\n--2239-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2239-- Nevertheless we consider this a bug. Please report\n--2239-- it at http://valgrind.org/support/bug_reports.html.\n--2239-- WARNING: unhandled riscv64-linux syscall: 258\n--2239-- You may be able to write your own handler.\n--2239-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2239-- Nevertheless we consider this a bug. Please report\n--2239-- it at http://valgrind.org/support/bug_reports.html.\n--2239-- WARNING: unhandled riscv64-linux syscall: 258\n--2239-- You may be able to write your own handler.\n--2239-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2239-- Nevertheless we consider this a bug. Please report\n--2239-- it at http://valgrind.org/support/bug_reports.html.\n--2239-- WARNING: unhandled riscv64-linux syscall: 258\n--2239-- You may be able to write your own handler.\n--2239-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2239-- Nevertheless we consider this a bug. Please report\n--2239-- it at http://valgrind.org/support/bug_reports.html.\n--2239-- WARNING: unhandled riscv64-linux syscall: 258\n--2239-- You may be able to write your own handler.\n--2239-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2239-- Nevertheless we consider this a bug. Please report\n--2239-- it at http://valgrind.org/support/bug_reports.html.\n--2239-- WARNING: unhandled riscv64-linux syscall: 258\n--2239-- You may be able to write your own handler.\n--2239-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2239-- Nevertheless we consider this a bug. Please report\n--2239-- it at http://valgrind.org/support/bug_reports.html.\n--2239-- WARNING: unhandled riscv64-linux syscall: 258\n--2239-- You may be able to write your own handler.\n--2239-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2239-- Nevertheless we consider this a bug. Please report\n--2239-- it at http://valgrind.org/support/bug_reports.html.\n--2239-- WARNING: unhandled riscv64-linux syscall: 258\n--2239-- You may be able to write your own handler.\n--2239-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2239-- Nevertheless we consider this a bug. Please report\n--2239-- it at http://valgrind.org/support/bug_reports.html.\n--2239-- WARNING: unhandled riscv64-linux syscall: 258\n--2239-- You may be able to write your own handler.\n--2239-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2239-- Nevertheless we consider this a bug. Please report\n--2239-- it at http://valgrind.org/support/bug_reports.html.\n--2239-- WARNING: unhandled riscv64-linux syscall: 258\n--2239-- You may be able to write your own handler.\n--2239-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2239-- Nevertheless we consider this a bug. Please report\n--2239-- it at http://valgrind.org/support/bug_reports.html.\ntrurl error: duplicate --iterate and --set for component host\ntrurl error: Try trurl -h for help\n' 122: failed --verify --no-guess-scheme hello --- stdout --- expected: '' got: '' --- returncode --- expected: 9 got: 9 --- stderr --- expected: 'trurl error: Bad scheme [hello]\ntrurl error: Try trurl -h for help\n' got: '--2255-- WARNING: unhandled riscv64-linux syscall: 258\n--2255-- You may be able to write your own handler.\n--2255-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2255-- Nevertheless we consider this a bug. Please report\n--2255-- it at http://valgrind.org/support/bug_reports.html.\n--2255-- WARNING: unhandled riscv64-linux syscall: 258\n--2255-- You may be able to write your own handler.\n--2255-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2255-- Nevertheless we consider this a bug. Please report\n--2255-- it at http://valgrind.org/support/bug_reports.html.\n--2255-- WARNING: unhandled riscv64-linux syscall: 258\n--2255-- You may be able to write your own handler.\n--2255-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2255-- Nevertheless we consider this a bug. Please report\n--2255-- it at http://valgrind.org/support/bug_reports.html.\n--2255-- WARNING: unhandled riscv64-linux syscall: 258\n--2255-- You may be able to write your own handler.\n--2255-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2255-- Nevertheless we consider this a bug. Please report\n--2255-- it at http://valgrind.org/support/bug_reports.html.\n--2255-- WARNING: unhandled riscv64-linux syscall: 258\n--2255-- You may be able to write your own handler.\n--2255-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2255-- Nevertheless we consider this a bug. Please report\n--2255-- it at http://valgrind.org/support/bug_reports.html.\n--2255-- WARNING: unhandled riscv64-linux syscall: 258\n--2255-- You may be able to write your own handler.\n--2255-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2255-- Nevertheless we consider this a bug. Please report\n--2255-- it at http://valgrind.org/support/bug_reports.html.\n--2255-- WARNING: unhandled riscv64-linux syscall: 258\n--2255-- You may be able to write your own handler.\n--2255-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2255-- Nevertheless we consider this a bug. Please report\n--2255-- it at http://valgrind.org/support/bug_reports.html.\n--2255-- WARNING: unhandled riscv64-linux syscall: 258\n--2255-- You may be able to write your own handler.\n--2255-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2255-- Nevertheless we consider this a bug. Please report\n--2255-- it at http://valgrind.org/support/bug_reports.html.\n--2255-- WARNING: unhandled riscv64-linux syscall: 258\n--2255-- You may be able to write your own handler.\n--2255-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2255-- Nevertheless we consider this a bug. Please report\n--2255-- it at http://valgrind.org/support/bug_reports.html.\n--2255-- WARNING: unhandled riscv64-linux syscall: 258\n--2255-- You may be able to write your own handler.\n--2255-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2255-- Nevertheless we consider this a bug. Please report\n--2255-- it at http://valgrind.org/support/bug_reports.html.\n--2255-- WARNING: unhandled riscv64-linux syscall: 258\n--2255-- You may be able to write your own handler.\n--2255-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2255-- Nevertheless we consider this a bug. Please report\n--2255-- it at http://valgrind.org/support/bug_reports.html.\n--2255-- WARNING: unhandled riscv64-linux syscall: 258\n--2255-- You may be able to write your own handler.\n--2255-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2255-- Nevertheless we consider this a bug. Please report\n--2255-- it at http://valgrind.org/support/bug_reports.html.\n--2255-- WARNING: unhandled riscv64-linux syscall: 258\n--2255-- You may be able to write your own handler.\n--2255-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2255-- Nevertheless we consider this a bug. Please report\n--2255-- it at http://valgrind.org/support/bug_reports.html.\n--2255-- WARNING: unhandled riscv64-linux syscall: 258\n--2255-- You may be able to write your own handler.\n--2255-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2255-- Nevertheless we consider this a bug. Please report\n--2255-- it at http://valgrind.org/support/bug_reports.html.\n--2255-- WARNING: unhandled riscv64-linux syscall: 258\n--2255-- You may be able to write your own handler.\n--2255-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2255-- Nevertheless we consider this a bug. Please report\n--2255-- it at http://valgrind.org/support/bug_reports.html.\n--2255-- WARNING: unhandled riscv64-linux syscall: 258\n--2255-- You may be able to write your own handler.\n--2255-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2255-- Nevertheless we consider this a bug. Please report\n--2255-- it at http://valgrind.org/support/bug_reports.html.\n--2255-- WARNING: unhandled riscv64-linux syscall: 258\n--2255-- You may be able to write your own handler.\n--2255-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2255-- Nevertheless we consider this a bug. Please report\n--2255-- it at http://valgrind.org/support/bug_reports.html.\n--2255-- WARNING: unhandled riscv64-linux syscall: 258\n--2255-- You may be able to write your own handler.\n--2255-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2255-- Nevertheless we consider this a bug. Please report\n--2255-- it at http://valgrind.org/support/bug_reports.html.\ntrurl error: Bad scheme [hello]\ntrurl error: Try trurl -h for help\n' 123: failed --verify -f testfiles/test0000.txt --- stdout --- expected: 'http://example.org/\n' got: 'http://example.org/\n' --- returncode --- expected: 0 got: 0 --- stderr --- expected: 'trurl note: skipping long line\n' got: '--2263-- WARNING: unhandled riscv64-linux syscall: 258\n--2263-- You may be able to write your own handler.\n--2263-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2263-- Nevertheless we consider this a bug. Please report\n--2263-- it at http://valgrind.org/support/bug_reports.html.\n--2263-- WARNING: unhandled riscv64-linux syscall: 258\n--2263-- You may be able to write your own handler.\n--2263-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2263-- Nevertheless we consider this a bug. Please report\n--2263-- it at http://valgrind.org/support/bug_reports.html.\n--2263-- WARNING: unhandled riscv64-linux syscall: 258\n--2263-- You may be able to write your own handler.\n--2263-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2263-- Nevertheless we consider this a bug. Please report\n--2263-- it at http://valgrind.org/support/bug_reports.html.\n--2263-- WARNING: unhandled riscv64-linux syscall: 258\n--2263-- You may be able to write your own handler.\n--2263-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2263-- Nevertheless we consider this a bug. Please report\n--2263-- it at http://valgrind.org/support/bug_reports.html.\n--2263-- WARNING: unhandled riscv64-linux syscall: 258\n--2263-- You may be able to write your own handler.\n--2263-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2263-- Nevertheless we consider this a bug. Please report\n--2263-- it at http://valgrind.org/support/bug_reports.html.\n--2263-- WARNING: unhandled riscv64-linux syscall: 258\n--2263-- You may be able to write your own handler.\n--2263-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2263-- Nevertheless we consider this a bug. Please report\n--2263-- it at http://valgrind.org/support/bug_reports.html.\n--2263-- WARNING: unhandled riscv64-linux syscall: 258\n--2263-- You may be able to write your own handler.\n--2263-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2263-- Nevertheless we consider this a bug. Please report\n--2263-- it at http://valgrind.org/support/bug_reports.html.\n--2263-- WARNING: unhandled riscv64-linux syscall: 258\n--2263-- You may be able to write your own handler.\n--2263-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2263-- Nevertheless we consider this a bug. Please report\n--2263-- it at http://valgrind.org/support/bug_reports.html.\n--2263-- WARNING: unhandled riscv64-linux syscall: 258\n--2263-- You may be able to write your own handler.\n--2263-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2263-- Nevertheless we consider this a bug. Please report\n--2263-- it at http://valgrind.org/support/bug_reports.html.\n--2263-- WARNING: unhandled riscv64-linux syscall: 258\n--2263-- You may be able to write your own handler.\n--2263-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2263-- Nevertheless we consider this a bug. Please report\n--2263-- it at http://valgrind.org/support/bug_reports.html.\n--2263-- WARNING: unhandled riscv64-linux syscall: 258\n--2263-- You may be able to write your own handler.\n--2263-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2263-- Nevertheless we consider this a bug. Please report\n--2263-- it at http://valgrind.org/support/bug_reports.html.\n--2263-- WARNING: unhandled riscv64-linux syscall: 258\n--2263-- You may be able to write your own handler.\n--2263-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2263-- Nevertheless we consider this a bug. Please report\n--2263-- it at http://valgrind.org/support/bug_reports.html.\n--2263-- WARNING: unhandled riscv64-linux syscall: 258\n--2263-- You may be able to write your own handler.\n--2263-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2263-- Nevertheless we consider this a bug. Please report\n--2263-- it at http://valgrind.org/support/bug_reports.html.\n--2263-- WARNING: unhandled riscv64-linux syscall: 258\n--2263-- You may be able to write your own handler.\n--2263-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2263-- Nevertheless we consider this a bug. Please report\n--2263-- it at http://valgrind.org/support/bug_reports.html.\n--2263-- WARNING: unhandled riscv64-linux syscall: 258\n--2263-- You may be able to write your own handler.\n--2263-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2263-- Nevertheless we consider this a bug. Please report\n--2263-- it at http://valgrind.org/support/bug_reports.html.\n--2263-- WARNING: unhandled riscv64-linux syscall: 258\n--2263-- You may be able to write your own handler.\n--2263-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2263-- Nevertheless we consider this a bug. Please report\n--2263-- it at http://valgrind.org/support/bug_reports.html.\n--2263-- WARNING: unhandled riscv64-linux syscall: 258\n--2263-- You may be able to write your own handler.\n--2263-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2263-- Nevertheless we consider this a bug. Please report\n--2263-- it at http://valgrind.org/support/bug_reports.html.\n--2263-- WARNING: unhandled riscv64-linux syscall: 258\n--2263-- You may be able to write your own handler.\n--2263-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2263-- Nevertheless we consider this a bug. Please report\n--2263-- it at http://valgrind.org/support/bug_reports.html.\ntrurl note: skipping long line\n' 124: 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: 'https://curl.se/\nhttps://docs.python.org/\ngit://github.com/curl/curl.git\nhttp://example.org/\nxyz://hello/?hi\n' --- returncode --- expected: 0 got: 0 --- stderr --- expected: '' got: '--2271-- WARNING: unhandled riscv64-linux syscall: 258\n--2271-- You may be able to write your own handler.\n--2271-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2271-- Nevertheless we consider this a bug. Please report\n--2271-- it at http://valgrind.org/support/bug_reports.html.\n--2271-- WARNING: unhandled riscv64-linux syscall: 258\n--2271-- You may be able to write your own handler.\n--2271-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2271-- Nevertheless we consider this a bug. Please report\n--2271-- it at http://valgrind.org/support/bug_reports.html.\n--2271-- WARNING: unhandled riscv64-linux syscall: 258\n--2271-- You may be able to write your own handler.\n--2271-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2271-- Nevertheless we consider this a bug. Please report\n--2271-- it at http://valgrind.org/support/bug_reports.html.\n--2271-- WARNING: unhandled riscv64-linux syscall: 258\n--2271-- You may be able to write your own handler.\n--2271-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2271-- Nevertheless we consider this a bug. Please report\n--2271-- it at http://valgrind.org/support/bug_reports.html.\n--2271-- WARNING: unhandled riscv64-linux syscall: 258\n--2271-- You may be able to write your own handler.\n--2271-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2271-- Nevertheless we consider this a bug. Please report\n--2271-- it at http://valgrind.org/support/bug_reports.html.\n--2271-- WARNING: unhandled riscv64-linux syscall: 258\n--2271-- You may be able to write your own handler.\n--2271-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2271-- Nevertheless we consider this a bug. Please report\n--2271-- it at http://valgrind.org/support/bug_reports.html.\n--2271-- WARNING: unhandled riscv64-linux syscall: 258\n--2271-- You may be able to write your own handler.\n--2271-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2271-- Nevertheless we consider this a bug. Please report\n--2271-- it at http://valgrind.org/support/bug_reports.html.\n--2271-- WARNING: unhandled riscv64-linux syscall: 258\n--2271-- You may be able to write your own handler.\n--2271-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2271-- Nevertheless we consider this a bug. Please report\n--2271-- it at http://valgrind.org/support/bug_reports.html.\n--2271-- WARNING: unhandled riscv64-linux syscall: 258\n--2271-- You may be able to write your own handler.\n--2271-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2271-- Nevertheless we consider this a bug. Please report\n--2271-- it at http://valgrind.org/support/bug_reports.html.\n--2271-- WARNING: unhandled riscv64-linux syscall: 258\n--2271-- You may be able to write your own handler.\n--2271-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2271-- Nevertheless we consider this a bug. Please report\n--2271-- it at http://valgrind.org/support/bug_reports.html.\n--2271-- WARNING: unhandled riscv64-linux syscall: 258\n--2271-- You may be able to write your own handler.\n--2271-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2271-- Nevertheless we consider this a bug. Please report\n--2271-- it at http://valgrind.org/support/bug_reports.html.\n--2271-- WARNING: unhandled riscv64-linux syscall: 258\n--2271-- You may be able to write your own handler.\n--2271-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2271-- Nevertheless we consider this a bug. Please report\n--2271-- it at http://valgrind.org/support/bug_reports.html.\n--2271-- WARNING: unhandled riscv64-linux syscall: 258\n--2271-- You may be able to write your own handler.\n--2271-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2271-- Nevertheless we consider this a bug. Please report\n--2271-- it at http://valgrind.org/support/bug_reports.html.\n--2271-- WARNING: unhandled riscv64-linux syscall: 258\n--2271-- You may be able to write your own handler.\n--2271-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2271-- Nevertheless we consider this a bug. Please report\n--2271-- it at http://valgrind.org/support/bug_reports.html.\n--2271-- WARNING: unhandled riscv64-linux syscall: 258\n--2271-- You may be able to write your own handler.\n--2271-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2271-- Nevertheless we consider this a bug. Please report\n--2271-- it at http://valgrind.org/support/bug_reports.html.\n--2271-- WARNING: unhandled riscv64-linux syscall: 258\n--2271-- You may be able to write your own handler.\n--2271-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2271-- Nevertheless we consider this a bug. Please report\n--2271-- it at http://valgrind.org/support/bug_reports.html.\n--2271-- WARNING: unhandled riscv64-linux syscall: 258\n--2271-- You may be able to write your own handler.\n--2271-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2271-- Nevertheless we consider this a bug. Please report\n--2271-- it at http://valgrind.org/support/bug_reports.html.\n--2271-- WARNING: unhandled riscv64-linux syscall: 258\n--2271-- You may be able to write your own handler.\n--2271-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2271-- Nevertheless we consider this a bug. Please report\n--2271-- it at http://valgrind.org/support/bug_reports.html.\n' 125: failed --no-guess-scheme foo hi https://example.org hey git://curl.se --- stdout --- expected: 'https://example.org/\ngit://curl.se/\n' got: 'https://example.org/\ngit://curl.se/\n' --- returncode --- expected: 0 got: 0 --- stderr --- expected: 'trurl note: Bad scheme [foo]\ntrurl note: Bad scheme [hi]\ntrurl note: Bad scheme [hey]\n' got: '--2279-- WARNING: unhandled riscv64-linux syscall: 258\n--2279-- You may be able to write your own handler.\n--2279-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2279-- Nevertheless we consider this a bug. Please report\n--2279-- it at http://valgrind.org/support/bug_reports.html.\n--2279-- WARNING: unhandled riscv64-linux syscall: 258\n--2279-- You may be able to write your own handler.\n--2279-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2279-- Nevertheless we consider this a bug. Please report\n--2279-- it at http://valgrind.org/support/bug_reports.html.\n--2279-- WARNING: unhandled riscv64-linux syscall: 258\n--2279-- You may be able to write your own handler.\n--2279-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2279-- Nevertheless we consider this a bug. Please report\n--2279-- it at http://valgrind.org/support/bug_reports.html.\n--2279-- WARNING: unhandled riscv64-linux syscall: 258\n--2279-- You may be able to write your own handler.\n--2279-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2279-- Nevertheless we consider this a bug. Please report\n--2279-- it at http://valgrind.org/support/bug_reports.html.\n--2279-- WARNING: unhandled riscv64-linux syscall: 258\n--2279-- You may be able to write your own handler.\n--2279-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2279-- Nevertheless we consider this a bug. Please report\n--2279-- it at http://valgrind.org/support/bug_reports.html.\n--2279-- WARNING: unhandled riscv64-linux syscall: 258\n--2279-- You may be able to write your own handler.\n--2279-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2279-- Nevertheless we consider this a bug. Please report\n--2279-- it at http://valgrind.org/support/bug_reports.html.\n--2279-- WARNING: unhandled riscv64-linux syscall: 258\n--2279-- You may be able to write your own handler.\n--2279-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2279-- Nevertheless we consider this a bug. Please report\n--2279-- it at http://valgrind.org/support/bug_reports.html.\n--2279-- WARNING: unhandled riscv64-linux syscall: 258\n--2279-- You may be able to write your own handler.\n--2279-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2279-- Nevertheless we consider this a bug. Please report\n--2279-- it at http://valgrind.org/support/bug_reports.html.\n--2279-- WARNING: unhandled riscv64-linux syscall: 258\n--2279-- You may be able to write your own handler.\n--2279-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2279-- Nevertheless we consider this a bug. Please report\n--2279-- it at http://valgrind.org/support/bug_reports.html.\n--2279-- WARNING: unhandled riscv64-linux syscall: 258\n--2279-- You may be able to write your own handler.\n--2279-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2279-- Nevertheless we consider this a bug. Please report\n--2279-- it at http://valgrind.org/support/bug_reports.html.\n--2279-- WARNING: unhandled riscv64-linux syscall: 258\n--2279-- You may be able to write your own handler.\n--2279-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2279-- Nevertheless we consider this a bug. Please report\n--2279-- it at http://valgrind.org/support/bug_reports.html.\n--2279-- WARNING: unhandled riscv64-linux syscall: 258\n--2279-- You may be able to write your own handler.\n--2279-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2279-- Nevertheless we consider this a bug. Please report\n--2279-- it at http://valgrind.org/support/bug_reports.html.\n--2279-- WARNING: unhandled riscv64-linux syscall: 258\n--2279-- You may be able to write your own handler.\n--2279-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2279-- Nevertheless we consider this a bug. Please report\n--2279-- it at http://valgrind.org/support/bug_reports.html.\n--2279-- WARNING: unhandled riscv64-linux syscall: 258\n--2279-- You may be able to write your own handler.\n--2279-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2279-- Nevertheless we consider this a bug. Please report\n--2279-- it at http://valgrind.org/support/bug_reports.html.\n--2279-- WARNING: unhandled riscv64-linux syscall: 258\n--2279-- You may be able to write your own handler.\n--2279-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2279-- Nevertheless we consider this a bug. Please report\n--2279-- it at http://valgrind.org/support/bug_reports.html.\n--2279-- WARNING: unhandled riscv64-linux syscall: 258\n--2279-- You may be able to write your own handler.\n--2279-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2279-- Nevertheless we consider this a bug. Please report\n--2279-- it at http://valgrind.org/support/bug_reports.html.\n--2279-- WARNING: unhandled riscv64-linux syscall: 258\n--2279-- You may be able to write your own handler.\n--2279-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2279-- Nevertheless we consider this a bug. Please report\n--2279-- it at http://valgrind.org/support/bug_reports.html.\n--2279-- WARNING: unhandled riscv64-linux syscall: 258\n--2279-- You may be able to write your own handler.\n--2279-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2279-- Nevertheless we consider this a bug. Please report\n--2279-- it at http://valgrind.org/support/bug_reports.html.\ntrurl note: Bad scheme [foo]\ntrurl note: Bad scheme [hi]\ntrurl note: Bad scheme [hey]\n' 126: failed -f testfiles/test0002.txt --json --- stdout --- expected: '[]\n' got: '[]\n' --- returncode --- expected: 0 got: 0 --- stderr --- expected: '' got: '--2287-- WARNING: unhandled riscv64-linux syscall: 258\n--2287-- You may be able to write your own handler.\n--2287-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2287-- Nevertheless we consider this a bug. Please report\n--2287-- it at http://valgrind.org/support/bug_reports.html.\n--2287-- WARNING: unhandled riscv64-linux syscall: 258\n--2287-- You may be able to write your own handler.\n--2287-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2287-- Nevertheless we consider this a bug. Please report\n--2287-- it at http://valgrind.org/support/bug_reports.html.\n--2287-- WARNING: unhandled riscv64-linux syscall: 258\n--2287-- You may be able to write your own handler.\n--2287-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2287-- Nevertheless we consider this a bug. Please report\n--2287-- it at http://valgrind.org/support/bug_reports.html.\n--2287-- WARNING: unhandled riscv64-linux syscall: 258\n--2287-- You may be able to write your own handler.\n--2287-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2287-- Nevertheless we consider this a bug. Please report\n--2287-- it at http://valgrind.org/support/bug_reports.html.\n--2287-- WARNING: unhandled riscv64-linux syscall: 258\n--2287-- You may be able to write your own handler.\n--2287-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2287-- Nevertheless we consider this a bug. Please report\n--2287-- it at http://valgrind.org/support/bug_reports.html.\n--2287-- WARNING: unhandled riscv64-linux syscall: 258\n--2287-- You may be able to write your own handler.\n--2287-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2287-- Nevertheless we consider this a bug. Please report\n--2287-- it at http://valgrind.org/support/bug_reports.html.\n--2287-- WARNING: unhandled riscv64-linux syscall: 258\n--2287-- You may be able to write your own handler.\n--2287-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2287-- Nevertheless we consider this a bug. Please report\n--2287-- it at http://valgrind.org/support/bug_reports.html.\n--2287-- WARNING: unhandled riscv64-linux syscall: 258\n--2287-- You may be able to write your own handler.\n--2287-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2287-- Nevertheless we consider this a bug. Please report\n--2287-- it at http://valgrind.org/support/bug_reports.html.\n--2287-- WARNING: unhandled riscv64-linux syscall: 258\n--2287-- You may be able to write your own handler.\n--2287-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2287-- Nevertheless we consider this a bug. Please report\n--2287-- it at http://valgrind.org/support/bug_reports.html.\n--2287-- WARNING: unhandled riscv64-linux syscall: 258\n--2287-- You may be able to write your own handler.\n--2287-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2287-- Nevertheless we consider this a bug. Please report\n--2287-- it at http://valgrind.org/support/bug_reports.html.\n--2287-- WARNING: unhandled riscv64-linux syscall: 258\n--2287-- You may be able to write your own handler.\n--2287-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2287-- Nevertheless we consider this a bug. Please report\n--2287-- it at http://valgrind.org/support/bug_reports.html.\n--2287-- WARNING: unhandled riscv64-linux syscall: 258\n--2287-- You may be able to write your own handler.\n--2287-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2287-- Nevertheless we consider this a bug. Please report\n--2287-- it at http://valgrind.org/support/bug_reports.html.\n--2287-- WARNING: unhandled riscv64-linux syscall: 258\n--2287-- You may be able to write your own handler.\n--2287-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2287-- Nevertheless we consider this a bug. Please report\n--2287-- it at http://valgrind.org/support/bug_reports.html.\n--2287-- WARNING: unhandled riscv64-linux syscall: 258\n--2287-- You may be able to write your own handler.\n--2287-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2287-- Nevertheless we consider this a bug. Please report\n--2287-- it at http://valgrind.org/support/bug_reports.html.\n--2287-- WARNING: unhandled riscv64-linux syscall: 258\n--2287-- You may be able to write your own handler.\n--2287-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2287-- Nevertheless we consider this a bug. Please report\n--2287-- it at http://valgrind.org/support/bug_reports.html.\n--2287-- WARNING: unhandled riscv64-linux syscall: 258\n--2287-- You may be able to write your own handler.\n--2287-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2287-- Nevertheless we consider this a bug. Please report\n--2287-- it at http://valgrind.org/support/bug_reports.html.\n--2287-- WARNING: unhandled riscv64-linux syscall: 258\n--2287-- You may be able to write your own handler.\n--2287-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2287-- Nevertheless we consider this a bug. Please report\n--2287-- it at http://valgrind.org/support/bug_reports.html.\n--2287-- WARNING: unhandled riscv64-linux syscall: 258\n--2287-- You may be able to write your own handler.\n--2287-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2287-- Nevertheless we consider this a bug. Please report\n--2287-- it at http://valgrind.org/support/bug_reports.html.\n' 127: failed --accept-space -s 'query:=x=10&x=2 3' localhost --- stdout --- expected: 'http://localhost/?x=10&x=2+3\n' got: 'http://localhost/?x=10&x=2+3\n' --- returncode --- expected: 0 got: 0 --- stderr --- expected: '' got: '--2295-- WARNING: unhandled riscv64-linux syscall: 258\n--2295-- You may be able to write your own handler.\n--2295-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2295-- Nevertheless we consider this a bug. Please report\n--2295-- it at http://valgrind.org/support/bug_reports.html.\n--2295-- WARNING: unhandled riscv64-linux syscall: 258\n--2295-- You may be able to write your own handler.\n--2295-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2295-- Nevertheless we consider this a bug. Please report\n--2295-- it at http://valgrind.org/support/bug_reports.html.\n--2295-- WARNING: unhandled riscv64-linux syscall: 258\n--2295-- You may be able to write your own handler.\n--2295-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2295-- Nevertheless we consider this a bug. Please report\n--2295-- it at http://valgrind.org/support/bug_reports.html.\n--2295-- WARNING: unhandled riscv64-linux syscall: 258\n--2295-- You may be able to write your own handler.\n--2295-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2295-- Nevertheless we consider this a bug. Please report\n--2295-- it at http://valgrind.org/support/bug_reports.html.\n--2295-- WARNING: unhandled riscv64-linux syscall: 258\n--2295-- You may be able to write your own handler.\n--2295-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2295-- Nevertheless we consider this a bug. Please report\n--2295-- it at http://valgrind.org/support/bug_reports.html.\n--2295-- WARNING: unhandled riscv64-linux syscall: 258\n--2295-- You may be able to write your own handler.\n--2295-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2295-- Nevertheless we consider this a bug. Please report\n--2295-- it at http://valgrind.org/support/bug_reports.html.\n--2295-- WARNING: unhandled riscv64-linux syscall: 258\n--2295-- You may be able to write your own handler.\n--2295-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2295-- Nevertheless we consider this a bug. Please report\n--2295-- it at http://valgrind.org/support/bug_reports.html.\n--2295-- WARNING: unhandled riscv64-linux syscall: 258\n--2295-- You may be able to write your own handler.\n--2295-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2295-- Nevertheless we consider this a bug. Please report\n--2295-- it at http://valgrind.org/support/bug_reports.html.\n--2295-- WARNING: unhandled riscv64-linux syscall: 258\n--2295-- You may be able to write your own handler.\n--2295-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2295-- Nevertheless we consider this a bug. Please report\n--2295-- it at http://valgrind.org/support/bug_reports.html.\n--2295-- WARNING: unhandled riscv64-linux syscall: 258\n--2295-- You may be able to write your own handler.\n--2295-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2295-- Nevertheless we consider this a bug. Please report\n--2295-- it at http://valgrind.org/support/bug_reports.html.\n--2295-- WARNING: unhandled riscv64-linux syscall: 258\n--2295-- You may be able to write your own handler.\n--2295-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2295-- Nevertheless we consider this a bug. Please report\n--2295-- it at http://valgrind.org/support/bug_reports.html.\n--2295-- WARNING: unhandled riscv64-linux syscall: 258\n--2295-- You may be able to write your own handler.\n--2295-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2295-- Nevertheless we consider this a bug. Please report\n--2295-- it at http://valgrind.org/support/bug_reports.html.\n--2295-- WARNING: unhandled riscv64-linux syscall: 258\n--2295-- You may be able to write your own handler.\n--2295-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2295-- Nevertheless we consider this a bug. Please report\n--2295-- it at http://valgrind.org/support/bug_reports.html.\n--2295-- WARNING: unhandled riscv64-linux syscall: 258\n--2295-- You may be able to write your own handler.\n--2295-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2295-- Nevertheless we consider this a bug. Please report\n--2295-- it at http://valgrind.org/support/bug_reports.html.\n--2295-- WARNING: unhandled riscv64-linux syscall: 258\n--2295-- You may be able to write your own handler.\n--2295-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2295-- Nevertheless we consider this a bug. Please report\n--2295-- it at http://valgrind.org/support/bug_reports.html.\n--2295-- WARNING: unhandled riscv64-linux syscall: 258\n--2295-- You may be able to write your own handler.\n--2295-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2295-- Nevertheless we consider this a bug. Please report\n--2295-- it at http://valgrind.org/support/bug_reports.html.\n--2295-- WARNING: unhandled riscv64-linux syscall: 258\n--2295-- You may be able to write your own handler.\n--2295-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2295-- Nevertheless we consider this a bug. Please report\n--2295-- it at http://valgrind.org/support/bug_reports.html.\n--2295-- WARNING: unhandled riscv64-linux syscall: 258\n--2295-- You may be able to write your own handler.\n--2295-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2295-- Nevertheless we consider this a bug. Please report\n--2295-- it at http://valgrind.org/support/bug_reports.html.\n' 128: failed -s 'path=\\' -g '{path}\n{:path}' localhost --- stdout --- expected: '/\\\\\n/%5c%5c\n' got: '/\\\\\n/%5c%5c\n' --- returncode --- expected: 0 got: 0 --- stderr --- expected: '' got: '--2303-- WARNING: unhandled riscv64-linux syscall: 258\n--2303-- You may be able to write your own handler.\n--2303-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2303-- Nevertheless we consider this a bug. Please report\n--2303-- it at http://valgrind.org/support/bug_reports.html.\n--2303-- WARNING: unhandled riscv64-linux syscall: 258\n--2303-- You may be able to write your own handler.\n--2303-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2303-- Nevertheless we consider this a bug. Please report\n--2303-- it at http://valgrind.org/support/bug_reports.html.\n--2303-- WARNING: unhandled riscv64-linux syscall: 258\n--2303-- You may be able to write your own handler.\n--2303-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2303-- Nevertheless we consider this a bug. Please report\n--2303-- it at http://valgrind.org/support/bug_reports.html.\n--2303-- WARNING: unhandled riscv64-linux syscall: 258\n--2303-- You may be able to write your own handler.\n--2303-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2303-- Nevertheless we consider this a bug. Please report\n--2303-- it at http://valgrind.org/support/bug_reports.html.\n--2303-- WARNING: unhandled riscv64-linux syscall: 258\n--2303-- You may be able to write your own handler.\n--2303-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2303-- Nevertheless we consider this a bug. Please report\n--2303-- it at http://valgrind.org/support/bug_reports.html.\n--2303-- WARNING: unhandled riscv64-linux syscall: 258\n--2303-- You may be able to write your own handler.\n--2303-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2303-- Nevertheless we consider this a bug. Please report\n--2303-- it at http://valgrind.org/support/bug_reports.html.\n--2303-- WARNING: unhandled riscv64-linux syscall: 258\n--2303-- You may be able to write your own handler.\n--2303-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2303-- Nevertheless we consider this a bug. Please report\n--2303-- it at http://valgrind.org/support/bug_reports.html.\n--2303-- WARNING: unhandled riscv64-linux syscall: 258\n--2303-- You may be able to write your own handler.\n--2303-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2303-- Nevertheless we consider this a bug. Please report\n--2303-- it at http://valgrind.org/support/bug_reports.html.\n--2303-- WARNING: unhandled riscv64-linux syscall: 258\n--2303-- You may be able to write your own handler.\n--2303-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2303-- Nevertheless we consider this a bug. Please report\n--2303-- it at http://valgrind.org/support/bug_reports.html.\n--2303-- WARNING: unhandled riscv64-linux syscall: 258\n--2303-- You may be able to write your own handler.\n--2303-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2303-- Nevertheless we consider this a bug. Please report\n--2303-- it at http://valgrind.org/support/bug_reports.html.\n--2303-- WARNING: unhandled riscv64-linux syscall: 258\n--2303-- You may be able to write your own handler.\n--2303-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2303-- Nevertheless we consider this a bug. Please report\n--2303-- it at http://valgrind.org/support/bug_reports.html.\n--2303-- WARNING: unhandled riscv64-linux syscall: 258\n--2303-- You may be able to write your own handler.\n--2303-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2303-- Nevertheless we consider this a bug. Please report\n--2303-- it at http://valgrind.org/support/bug_reports.html.\n--2303-- WARNING: unhandled riscv64-linux syscall: 258\n--2303-- You may be able to write your own handler.\n--2303-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2303-- Nevertheless we consider this a bug. Please report\n--2303-- it at http://valgrind.org/support/bug_reports.html.\n--2303-- WARNING: unhandled riscv64-linux syscall: 258\n--2303-- You may be able to write your own handler.\n--2303-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2303-- Nevertheless we consider this a bug. Please report\n--2303-- it at http://valgrind.org/support/bug_reports.html.\n--2303-- WARNING: unhandled riscv64-linux syscall: 258\n--2303-- You may be able to write your own handler.\n--2303-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2303-- Nevertheless we consider this a bug. Please report\n--2303-- it at http://valgrind.org/support/bug_reports.html.\n--2303-- WARNING: unhandled riscv64-linux syscall: 258\n--2303-- You may be able to write your own handler.\n--2303-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2303-- Nevertheless we consider this a bug. Please report\n--2303-- it at http://valgrind.org/support/bug_reports.html.\n--2303-- WARNING: unhandled riscv64-linux syscall: 258\n--2303-- You may be able to write your own handler.\n--2303-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2303-- Nevertheless we consider this a bug. Please report\n--2303-- it at http://valgrind.org/support/bug_reports.html.\n--2303-- WARNING: unhandled riscv64-linux syscall: 258\n--2303-- You may be able to write your own handler.\n--2303-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2303-- Nevertheless we consider this a bug. Please report\n--2303-- it at http://valgrind.org/support/bug_reports.html.\n' 129: failed -s 'path=\\' --json localhost --- stdout --- expected: [{'url': 'http://localhost/%5c%5c', 'parts': {'scheme': 'http', 'host': 'localhost', 'path': '/\\\\'}}] got: [{'url': 'http://localhost/%5c%5c', 'parts': {'scheme': 'http', 'host': 'localhost', 'path': '/\\\\'}}] --- returncode --- expected: 0 got: 0 --- stderr --- expected: '' got: '--2311-- WARNING: unhandled riscv64-linux syscall: 258\n--2311-- You may be able to write your own handler.\n--2311-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2311-- Nevertheless we consider this a bug. Please report\n--2311-- it at http://valgrind.org/support/bug_reports.html.\n--2311-- WARNING: unhandled riscv64-linux syscall: 258\n--2311-- You may be able to write your own handler.\n--2311-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2311-- Nevertheless we consider this a bug. Please report\n--2311-- it at http://valgrind.org/support/bug_reports.html.\n--2311-- WARNING: unhandled riscv64-linux syscall: 258\n--2311-- You may be able to write your own handler.\n--2311-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2311-- Nevertheless we consider this a bug. Please report\n--2311-- it at http://valgrind.org/support/bug_reports.html.\n--2311-- WARNING: unhandled riscv64-linux syscall: 258\n--2311-- You may be able to write your own handler.\n--2311-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2311-- Nevertheless we consider this a bug. Please report\n--2311-- it at http://valgrind.org/support/bug_reports.html.\n--2311-- WARNING: unhandled riscv64-linux syscall: 258\n--2311-- You may be able to write your own handler.\n--2311-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2311-- Nevertheless we consider this a bug. Please report\n--2311-- it at http://valgrind.org/support/bug_reports.html.\n--2311-- WARNING: unhandled riscv64-linux syscall: 258\n--2311-- You may be able to write your own handler.\n--2311-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2311-- Nevertheless we consider this a bug. Please report\n--2311-- it at http://valgrind.org/support/bug_reports.html.\n--2311-- WARNING: unhandled riscv64-linux syscall: 258\n--2311-- You may be able to write your own handler.\n--2311-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2311-- Nevertheless we consider this a bug. Please report\n--2311-- it at http://valgrind.org/support/bug_reports.html.\n--2311-- WARNING: unhandled riscv64-linux syscall: 258\n--2311-- You may be able to write your own handler.\n--2311-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2311-- Nevertheless we consider this a bug. Please report\n--2311-- it at http://valgrind.org/support/bug_reports.html.\n--2311-- WARNING: unhandled riscv64-linux syscall: 258\n--2311-- You may be able to write your own handler.\n--2311-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2311-- Nevertheless we consider this a bug. Please report\n--2311-- it at http://valgrind.org/support/bug_reports.html.\n--2311-- WARNING: unhandled riscv64-linux syscall: 258\n--2311-- You may be able to write your own handler.\n--2311-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2311-- Nevertheless we consider this a bug. Please report\n--2311-- it at http://valgrind.org/support/bug_reports.html.\n--2311-- WARNING: unhandled riscv64-linux syscall: 258\n--2311-- You may be able to write your own handler.\n--2311-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2311-- Nevertheless we consider this a bug. Please report\n--2311-- it at http://valgrind.org/support/bug_reports.html.\n--2311-- WARNING: unhandled riscv64-linux syscall: 258\n--2311-- You may be able to write your own handler.\n--2311-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2311-- Nevertheless we consider this a bug. Please report\n--2311-- it at http://valgrind.org/support/bug_reports.html.\n--2311-- WARNING: unhandled riscv64-linux syscall: 258\n--2311-- You may be able to write your own handler.\n--2311-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2311-- Nevertheless we consider this a bug. Please report\n--2311-- it at http://valgrind.org/support/bug_reports.html.\n--2311-- WARNING: unhandled riscv64-linux syscall: 258\n--2311-- You may be able to write your own handler.\n--2311-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2311-- Nevertheless we consider this a bug. Please report\n--2311-- it at http://valgrind.org/support/bug_reports.html.\n--2311-- WARNING: unhandled riscv64-linux syscall: 258\n--2311-- You may be able to write your own handler.\n--2311-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2311-- Nevertheless we consider this a bug. Please report\n--2311-- it at http://valgrind.org/support/bug_reports.html.\n--2311-- WARNING: unhandled riscv64-linux syscall: 258\n--2311-- You may be able to write your own handler.\n--2311-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2311-- Nevertheless we consider this a bug. Please report\n--2311-- it at http://valgrind.org/support/bug_reports.html.\n--2311-- WARNING: unhandled riscv64-linux syscall: 258\n--2311-- You may be able to write your own handler.\n--2311-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2311-- Nevertheless we consider this a bug. Please report\n--2311-- it at http://valgrind.org/support/bug_reports.html.\n--2311-- WARNING: unhandled riscv64-linux syscall: 258\n--2311-- You may be able to write your own handler.\n--2311-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2311-- Nevertheless we consider this a bug. Please report\n--2311-- it at http://valgrind.org/support/bug_reports.html.\n' 130: failed -s 'path=\\' -g '{path}\n{:path}' --urlencode localhost --- stdout --- expected: '/%5c%5c\n/%5c%5c\n' got: '/%5c%5c\n/%5c%5c\n' --- returncode --- expected: 0 got: 0 --- stderr --- expected: '' got: '--2319-- WARNING: unhandled riscv64-linux syscall: 258\n--2319-- You may be able to write your own handler.\n--2319-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2319-- Nevertheless we consider this a bug. Please report\n--2319-- it at http://valgrind.org/support/bug_reports.html.\n--2319-- WARNING: unhandled riscv64-linux syscall: 258\n--2319-- You may be able to write your own handler.\n--2319-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2319-- Nevertheless we consider this a bug. Please report\n--2319-- it at http://valgrind.org/support/bug_reports.html.\n--2319-- WARNING: unhandled riscv64-linux syscall: 258\n--2319-- You may be able to write your own handler.\n--2319-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2319-- Nevertheless we consider this a bug. Please report\n--2319-- it at http://valgrind.org/support/bug_reports.html.\n--2319-- WARNING: unhandled riscv64-linux syscall: 258\n--2319-- You may be able to write your own handler.\n--2319-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2319-- Nevertheless we consider this a bug. Please report\n--2319-- it at http://valgrind.org/support/bug_reports.html.\n--2319-- WARNING: unhandled riscv64-linux syscall: 258\n--2319-- You may be able to write your own handler.\n--2319-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2319-- Nevertheless we consider this a bug. Please report\n--2319-- it at http://valgrind.org/support/bug_reports.html.\n--2319-- WARNING: unhandled riscv64-linux syscall: 258\n--2319-- You may be able to write your own handler.\n--2319-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2319-- Nevertheless we consider this a bug. Please report\n--2319-- it at http://valgrind.org/support/bug_reports.html.\n--2319-- WARNING: unhandled riscv64-linux syscall: 258\n--2319-- You may be able to write your own handler.\n--2319-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2319-- Nevertheless we consider this a bug. Please report\n--2319-- it at http://valgrind.org/support/bug_reports.html.\n--2319-- WARNING: unhandled riscv64-linux syscall: 258\n--2319-- You may be able to write your own handler.\n--2319-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2319-- Nevertheless we consider this a bug. Please report\n--2319-- it at http://valgrind.org/support/bug_reports.html.\n--2319-- WARNING: unhandled riscv64-linux syscall: 258\n--2319-- You may be able to write your own handler.\n--2319-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2319-- Nevertheless we consider this a bug. Please report\n--2319-- it at http://valgrind.org/support/bug_reports.html.\n--2319-- WARNING: unhandled riscv64-linux syscall: 258\n--2319-- You may be able to write your own handler.\n--2319-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2319-- Nevertheless we consider this a bug. Please report\n--2319-- it at http://valgrind.org/support/bug_reports.html.\n--2319-- WARNING: unhandled riscv64-linux syscall: 258\n--2319-- You may be able to write your own handler.\n--2319-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2319-- Nevertheless we consider this a bug. Please report\n--2319-- it at http://valgrind.org/support/bug_reports.html.\n--2319-- WARNING: unhandled riscv64-linux syscall: 258\n--2319-- You may be able to write your own handler.\n--2319-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2319-- Nevertheless we consider this a bug. Please report\n--2319-- it at http://valgrind.org/support/bug_reports.html.\n--2319-- WARNING: unhandled riscv64-linux syscall: 258\n--2319-- You may be able to write your own handler.\n--2319-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2319-- Nevertheless we consider this a bug. Please report\n--2319-- it at http://valgrind.org/support/bug_reports.html.\n--2319-- WARNING: unhandled riscv64-linux syscall: 258\n--2319-- You may be able to write your own handler.\n--2319-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2319-- Nevertheless we consider this a bug. Please report\n--2319-- it at http://valgrind.org/support/bug_reports.html.\n--2319-- WARNING: unhandled riscv64-linux syscall: 258\n--2319-- You may be able to write your own handler.\n--2319-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2319-- Nevertheless we consider this a bug. Please report\n--2319-- it at http://valgrind.org/support/bug_reports.html.\n--2319-- WARNING: unhandled riscv64-linux syscall: 258\n--2319-- You may be able to write your own handler.\n--2319-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2319-- Nevertheless we consider this a bug. Please report\n--2319-- it at http://valgrind.org/support/bug_reports.html.\n--2319-- WARNING: unhandled riscv64-linux syscall: 258\n--2319-- You may be able to write your own handler.\n--2319-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2319-- Nevertheless we consider this a bug. Please report\n--2319-- it at http://valgrind.org/support/bug_reports.html.\n--2319-- WARNING: unhandled riscv64-linux syscall: 258\n--2319-- You may be able to write your own handler.\n--2319-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2319-- Nevertheless we consider this a bug. Please report\n--2319-- it at http://valgrind.org/support/bug_reports.html.\n' 131: 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: [{'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': ''}]}] --- returncode --- expected: 0 got: 0 --- stderr --- expected: '' got: '--2327-- WARNING: unhandled riscv64-linux syscall: 258\n--2327-- You may be able to write your own handler.\n--2327-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2327-- Nevertheless we consider this a bug. Please report\n--2327-- it at http://valgrind.org/support/bug_reports.html.\n--2327-- WARNING: unhandled riscv64-linux syscall: 258\n--2327-- You may be able to write your own handler.\n--2327-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2327-- Nevertheless we consider this a bug. Please report\n--2327-- it at http://valgrind.org/support/bug_reports.html.\n--2327-- WARNING: unhandled riscv64-linux syscall: 258\n--2327-- You may be able to write your own handler.\n--2327-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2327-- Nevertheless we consider this a bug. Please report\n--2327-- it at http://valgrind.org/support/bug_reports.html.\n--2327-- WARNING: unhandled riscv64-linux syscall: 258\n--2327-- You may be able to write your own handler.\n--2327-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2327-- Nevertheless we consider this a bug. Please report\n--2327-- it at http://valgrind.org/support/bug_reports.html.\n--2327-- WARNING: unhandled riscv64-linux syscall: 258\n--2327-- You may be able to write your own handler.\n--2327-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2327-- Nevertheless we consider this a bug. Please report\n--2327-- it at http://valgrind.org/support/bug_reports.html.\n--2327-- WARNING: unhandled riscv64-linux syscall: 258\n--2327-- You may be able to write your own handler.\n--2327-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2327-- Nevertheless we consider this a bug. Please report\n--2327-- it at http://valgrind.org/support/bug_reports.html.\n--2327-- WARNING: unhandled riscv64-linux syscall: 258\n--2327-- You may be able to write your own handler.\n--2327-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2327-- Nevertheless we consider this a bug. Please report\n--2327-- it at http://valgrind.org/support/bug_reports.html.\n--2327-- WARNING: unhandled riscv64-linux syscall: 258\n--2327-- You may be able to write your own handler.\n--2327-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2327-- Nevertheless we consider this a bug. Please report\n--2327-- it at http://valgrind.org/support/bug_reports.html.\n--2327-- WARNING: unhandled riscv64-linux syscall: 258\n--2327-- You may be able to write your own handler.\n--2327-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2327-- Nevertheless we consider this a bug. Please report\n--2327-- it at http://valgrind.org/support/bug_reports.html.\n--2327-- WARNING: unhandled riscv64-linux syscall: 258\n--2327-- You may be able to write your own handler.\n--2327-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2327-- Nevertheless we consider this a bug. Please report\n--2327-- it at http://valgrind.org/support/bug_reports.html.\n--2327-- WARNING: unhandled riscv64-linux syscall: 258\n--2327-- You may be able to write your own handler.\n--2327-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2327-- Nevertheless we consider this a bug. Please report\n--2327-- it at http://valgrind.org/support/bug_reports.html.\n--2327-- WARNING: unhandled riscv64-linux syscall: 258\n--2327-- You may be able to write your own handler.\n--2327-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2327-- Nevertheless we consider this a bug. Please report\n--2327-- it at http://valgrind.org/support/bug_reports.html.\n--2327-- WARNING: unhandled riscv64-linux syscall: 258\n--2327-- You may be able to write your own handler.\n--2327-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2327-- Nevertheless we consider this a bug. Please report\n--2327-- it at http://valgrind.org/support/bug_reports.html.\n--2327-- WARNING: unhandled riscv64-linux syscall: 258\n--2327-- You may be able to write your own handler.\n--2327-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2327-- Nevertheless we consider this a bug. Please report\n--2327-- it at http://valgrind.org/support/bug_reports.html.\n--2327-- WARNING: unhandled riscv64-linux syscall: 258\n--2327-- You may be able to write your own handler.\n--2327-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2327-- Nevertheless we consider this a bug. Please report\n--2327-- it at http://valgrind.org/support/bug_reports.html.\n--2327-- WARNING: unhandled riscv64-linux syscall: 258\n--2327-- You may be able to write your own handler.\n--2327-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2327-- Nevertheless we consider this a bug. Please report\n--2327-- it at http://valgrind.org/support/bug_reports.html.\n--2327-- WARNING: unhandled riscv64-linux syscall: 258\n--2327-- You may be able to write your own handler.\n--2327-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2327-- Nevertheless we consider this a bug. Please report\n--2327-- it at http://valgrind.org/support/bug_reports.html.\n--2327-- WARNING: unhandled riscv64-linux syscall: 258\n--2327-- You may be able to write your own handler.\n--2327-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2327-- Nevertheless we consider this a bug. Please report\n--2327-- it at http://valgrind.org/support/bug_reports.html.\n' 132: 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: 'http://localhost/ABC%5c%5c?a&b&a%26b\n' --- returncode --- expected: 0 got: 0 --- stderr --- expected: '' got: '--2335-- WARNING: unhandled riscv64-linux syscall: 258\n--2335-- You may be able to write your own handler.\n--2335-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2335-- Nevertheless we consider this a bug. Please report\n--2335-- it at http://valgrind.org/support/bug_reports.html.\n--2335-- WARNING: unhandled riscv64-linux syscall: 258\n--2335-- You may be able to write your own handler.\n--2335-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2335-- Nevertheless we consider this a bug. Please report\n--2335-- it at http://valgrind.org/support/bug_reports.html.\n--2335-- WARNING: unhandled riscv64-linux syscall: 258\n--2335-- You may be able to write your own handler.\n--2335-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2335-- Nevertheless we consider this a bug. Please report\n--2335-- it at http://valgrind.org/support/bug_reports.html.\n--2335-- WARNING: unhandled riscv64-linux syscall: 258\n--2335-- You may be able to write your own handler.\n--2335-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2335-- Nevertheless we consider this a bug. Please report\n--2335-- it at http://valgrind.org/support/bug_reports.html.\n--2335-- WARNING: unhandled riscv64-linux syscall: 258\n--2335-- You may be able to write your own handler.\n--2335-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2335-- Nevertheless we consider this a bug. Please report\n--2335-- it at http://valgrind.org/support/bug_reports.html.\n--2335-- WARNING: unhandled riscv64-linux syscall: 258\n--2335-- You may be able to write your own handler.\n--2335-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2335-- Nevertheless we consider this a bug. Please report\n--2335-- it at http://valgrind.org/support/bug_reports.html.\n--2335-- WARNING: unhandled riscv64-linux syscall: 258\n--2335-- You may be able to write your own handler.\n--2335-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2335-- Nevertheless we consider this a bug. Please report\n--2335-- it at http://valgrind.org/support/bug_reports.html.\n--2335-- WARNING: unhandled riscv64-linux syscall: 258\n--2335-- You may be able to write your own handler.\n--2335-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2335-- Nevertheless we consider this a bug. Please report\n--2335-- it at http://valgrind.org/support/bug_reports.html.\n--2335-- WARNING: unhandled riscv64-linux syscall: 258\n--2335-- You may be able to write your own handler.\n--2335-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2335-- Nevertheless we consider this a bug. Please report\n--2335-- it at http://valgrind.org/support/bug_reports.html.\n--2335-- WARNING: unhandled riscv64-linux syscall: 258\n--2335-- You may be able to write your own handler.\n--2335-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2335-- Nevertheless we consider this a bug. Please report\n--2335-- it at http://valgrind.org/support/bug_reports.html.\n--2335-- WARNING: unhandled riscv64-linux syscall: 258\n--2335-- You may be able to write your own handler.\n--2335-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2335-- Nevertheless we consider this a bug. Please report\n--2335-- it at http://valgrind.org/support/bug_reports.html.\n--2335-- WARNING: unhandled riscv64-linux syscall: 258\n--2335-- You may be able to write your own handler.\n--2335-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2335-- Nevertheless we consider this a bug. Please report\n--2335-- it at http://valgrind.org/support/bug_reports.html.\n--2335-- WARNING: unhandled riscv64-linux syscall: 258\n--2335-- You may be able to write your own handler.\n--2335-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2335-- Nevertheless we consider this a bug. Please report\n--2335-- it at http://valgrind.org/support/bug_reports.html.\n--2335-- WARNING: unhandled riscv64-linux syscall: 258\n--2335-- You may be able to write your own handler.\n--2335-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2335-- Nevertheless we consider this a bug. Please report\n--2335-- it at http://valgrind.org/support/bug_reports.html.\n--2335-- WARNING: unhandled riscv64-linux syscall: 258\n--2335-- You may be able to write your own handler.\n--2335-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2335-- Nevertheless we consider this a bug. Please report\n--2335-- it at http://valgrind.org/support/bug_reports.html.\n--2335-- WARNING: unhandled riscv64-linux syscall: 258\n--2335-- You may be able to write your own handler.\n--2335-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2335-- Nevertheless we consider this a bug. Please report\n--2335-- it at http://valgrind.org/support/bug_reports.html.\n--2335-- WARNING: unhandled riscv64-linux syscall: 258\n--2335-- You may be able to write your own handler.\n--2335-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2335-- Nevertheless we consider this a bug. Please report\n--2335-- it at http://valgrind.org/support/bug_reports.html.\n--2335-- WARNING: unhandled riscv64-linux syscall: 258\n--2335-- You may be able to write your own handler.\n--2335-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2335-- Nevertheless we consider this a bug. Please report\n--2335-- it at http://valgrind.org/support/bug_reports.html.\n' 133: 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: '#\t1 &\n%23\t1 %26\n' --- returncode --- expected: 0 got: 0 --- stderr --- expected: '' got: '--2343-- WARNING: unhandled riscv64-linux syscall: 258\n--2343-- You may be able to write your own handler.\n--2343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2343-- Nevertheless we consider this a bug. Please report\n--2343-- it at http://valgrind.org/support/bug_reports.html.\n--2343-- WARNING: unhandled riscv64-linux syscall: 258\n--2343-- You may be able to write your own handler.\n--2343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2343-- Nevertheless we consider this a bug. Please report\n--2343-- it at http://valgrind.org/support/bug_reports.html.\n--2343-- WARNING: unhandled riscv64-linux syscall: 258\n--2343-- You may be able to write your own handler.\n--2343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2343-- Nevertheless we consider this a bug. Please report\n--2343-- it at http://valgrind.org/support/bug_reports.html.\n--2343-- WARNING: unhandled riscv64-linux syscall: 258\n--2343-- You may be able to write your own handler.\n--2343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2343-- Nevertheless we consider this a bug. Please report\n--2343-- it at http://valgrind.org/support/bug_reports.html.\n--2343-- WARNING: unhandled riscv64-linux syscall: 258\n--2343-- You may be able to write your own handler.\n--2343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2343-- Nevertheless we consider this a bug. Please report\n--2343-- it at http://valgrind.org/support/bug_reports.html.\n--2343-- WARNING: unhandled riscv64-linux syscall: 258\n--2343-- You may be able to write your own handler.\n--2343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2343-- Nevertheless we consider this a bug. Please report\n--2343-- it at http://valgrind.org/support/bug_reports.html.\n--2343-- WARNING: unhandled riscv64-linux syscall: 258\n--2343-- You may be able to write your own handler.\n--2343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2343-- Nevertheless we consider this a bug. Please report\n--2343-- it at http://valgrind.org/support/bug_reports.html.\n--2343-- WARNING: unhandled riscv64-linux syscall: 258\n--2343-- You may be able to write your own handler.\n--2343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2343-- Nevertheless we consider this a bug. Please report\n--2343-- it at http://valgrind.org/support/bug_reports.html.\n--2343-- WARNING: unhandled riscv64-linux syscall: 258\n--2343-- You may be able to write your own handler.\n--2343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2343-- Nevertheless we consider this a bug. Please report\n--2343-- it at http://valgrind.org/support/bug_reports.html.\n--2343-- WARNING: unhandled riscv64-linux syscall: 258\n--2343-- You may be able to write your own handler.\n--2343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2343-- Nevertheless we consider this a bug. Please report\n--2343-- it at http://valgrind.org/support/bug_reports.html.\n--2343-- WARNING: unhandled riscv64-linux syscall: 258\n--2343-- You may be able to write your own handler.\n--2343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2343-- Nevertheless we consider this a bug. Please report\n--2343-- it at http://valgrind.org/support/bug_reports.html.\n--2343-- WARNING: unhandled riscv64-linux syscall: 258\n--2343-- You may be able to write your own handler.\n--2343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2343-- Nevertheless we consider this a bug. Please report\n--2343-- it at http://valgrind.org/support/bug_reports.html.\n--2343-- WARNING: unhandled riscv64-linux syscall: 258\n--2343-- You may be able to write your own handler.\n--2343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2343-- Nevertheless we consider this a bug. Please report\n--2343-- it at http://valgrind.org/support/bug_reports.html.\n--2343-- WARNING: unhandled riscv64-linux syscall: 258\n--2343-- You may be able to write your own handler.\n--2343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2343-- Nevertheless we consider this a bug. Please report\n--2343-- it at http://valgrind.org/support/bug_reports.html.\n--2343-- WARNING: unhandled riscv64-linux syscall: 258\n--2343-- You may be able to write your own handler.\n--2343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2343-- Nevertheless we consider this a bug. Please report\n--2343-- it at http://valgrind.org/support/bug_reports.html.\n--2343-- WARNING: unhandled riscv64-linux syscall: 258\n--2343-- You may be able to write your own handler.\n--2343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2343-- Nevertheless we consider this a bug. Please report\n--2343-- it at http://valgrind.org/support/bug_reports.html.\n--2343-- WARNING: unhandled riscv64-linux syscall: 258\n--2343-- You may be able to write your own handler.\n--2343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2343-- Nevertheless we consider this a bug. Please report\n--2343-- it at http://valgrind.org/support/bug_reports.html.\n--2343-- WARNING: unhandled riscv64-linux syscall: 258\n--2343-- You may be able to write your own handler.\n--2343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2343-- Nevertheless we consider this a bug. Please report\n--2343-- it at http://valgrind.org/support/bug_reports.html.\n' 134: 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: '%23\t1 %26\n%23\t1 %26\n' --- returncode --- expected: 0 got: 0 --- stderr --- expected: '' got: '--2351-- WARNING: unhandled riscv64-linux syscall: 258\n--2351-- You may be able to write your own handler.\n--2351-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2351-- Nevertheless we consider this a bug. Please report\n--2351-- it at http://valgrind.org/support/bug_reports.html.\n--2351-- WARNING: unhandled riscv64-linux syscall: 258\n--2351-- You may be able to write your own handler.\n--2351-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2351-- Nevertheless we consider this a bug. Please report\n--2351-- it at http://valgrind.org/support/bug_reports.html.\n--2351-- WARNING: unhandled riscv64-linux syscall: 258\n--2351-- You may be able to write your own handler.\n--2351-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2351-- Nevertheless we consider this a bug. Please report\n--2351-- it at http://valgrind.org/support/bug_reports.html.\n--2351-- WARNING: unhandled riscv64-linux syscall: 258\n--2351-- You may be able to write your own handler.\n--2351-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2351-- Nevertheless we consider this a bug. Please report\n--2351-- it at http://valgrind.org/support/bug_reports.html.\n--2351-- WARNING: unhandled riscv64-linux syscall: 258\n--2351-- You may be able to write your own handler.\n--2351-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2351-- Nevertheless we consider this a bug. Please report\n--2351-- it at http://valgrind.org/support/bug_reports.html.\n--2351-- WARNING: unhandled riscv64-linux syscall: 258\n--2351-- You may be able to write your own handler.\n--2351-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2351-- Nevertheless we consider this a bug. Please report\n--2351-- it at http://valgrind.org/support/bug_reports.html.\n--2351-- WARNING: unhandled riscv64-linux syscall: 258\n--2351-- You may be able to write your own handler.\n--2351-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2351-- Nevertheless we consider this a bug. Please report\n--2351-- it at http://valgrind.org/support/bug_reports.html.\n--2351-- WARNING: unhandled riscv64-linux syscall: 258\n--2351-- You may be able to write your own handler.\n--2351-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2351-- Nevertheless we consider this a bug. Please report\n--2351-- it at http://valgrind.org/support/bug_reports.html.\n--2351-- WARNING: unhandled riscv64-linux syscall: 258\n--2351-- You may be able to write your own handler.\n--2351-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2351-- Nevertheless we consider this a bug. Please report\n--2351-- it at http://valgrind.org/support/bug_reports.html.\n--2351-- WARNING: unhandled riscv64-linux syscall: 258\n--2351-- You may be able to write your own handler.\n--2351-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2351-- Nevertheless we consider this a bug. Please report\n--2351-- it at http://valgrind.org/support/bug_reports.html.\n--2351-- WARNING: unhandled riscv64-linux syscall: 258\n--2351-- You may be able to write your own handler.\n--2351-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2351-- Nevertheless we consider this a bug. Please report\n--2351-- it at http://valgrind.org/support/bug_reports.html.\n--2351-- WARNING: unhandled riscv64-linux syscall: 258\n--2351-- You may be able to write your own handler.\n--2351-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2351-- Nevertheless we consider this a bug. Please report\n--2351-- it at http://valgrind.org/support/bug_reports.html.\n--2351-- WARNING: unhandled riscv64-linux syscall: 258\n--2351-- You may be able to write your own handler.\n--2351-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2351-- Nevertheless we consider this a bug. Please report\n--2351-- it at http://valgrind.org/support/bug_reports.html.\n--2351-- WARNING: unhandled riscv64-linux syscall: 258\n--2351-- You may be able to write your own handler.\n--2351-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2351-- Nevertheless we consider this a bug. Please report\n--2351-- it at http://valgrind.org/support/bug_reports.html.\n--2351-- WARNING: unhandled riscv64-linux syscall: 258\n--2351-- You may be able to write your own handler.\n--2351-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2351-- Nevertheless we consider this a bug. Please report\n--2351-- it at http://valgrind.org/support/bug_reports.html.\n--2351-- WARNING: unhandled riscv64-linux syscall: 258\n--2351-- You may be able to write your own handler.\n--2351-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2351-- Nevertheless we consider this a bug. Please report\n--2351-- it at http://valgrind.org/support/bug_reports.html.\n--2351-- WARNING: unhandled riscv64-linux syscall: 258\n--2351-- You may be able to write your own handler.\n--2351-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2351-- Nevertheless we consider this a bug. Please report\n--2351-- it at http://valgrind.org/support/bug_reports.html.\n--2351-- WARNING: unhandled riscv64-linux syscall: 258\n--2351-- You may be able to write your own handler.\n--2351-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2351-- Nevertheless we consider this a bug. Please report\n--2351-- it at http://valgrind.org/support/bug_reports.html.\n' 135: 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: 'https://example.org/foo?c=moo&x=hi#rye\n' --- returncode --- expected: 0 got: 0 --- stderr --- expected: '' got: '--2359-- WARNING: unhandled riscv64-linux syscall: 258\n--2359-- You may be able to write your own handler.\n--2359-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2359-- Nevertheless we consider this a bug. Please report\n--2359-- it at http://valgrind.org/support/bug_reports.html.\n--2359-- WARNING: unhandled riscv64-linux syscall: 258\n--2359-- You may be able to write your own handler.\n--2359-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2359-- Nevertheless we consider this a bug. Please report\n--2359-- it at http://valgrind.org/support/bug_reports.html.\n--2359-- WARNING: unhandled riscv64-linux syscall: 258\n--2359-- You may be able to write your own handler.\n--2359-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2359-- Nevertheless we consider this a bug. Please report\n--2359-- it at http://valgrind.org/support/bug_reports.html.\n--2359-- WARNING: unhandled riscv64-linux syscall: 258\n--2359-- You may be able to write your own handler.\n--2359-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2359-- Nevertheless we consider this a bug. Please report\n--2359-- it at http://valgrind.org/support/bug_reports.html.\n--2359-- WARNING: unhandled riscv64-linux syscall: 258\n--2359-- You may be able to write your own handler.\n--2359-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2359-- Nevertheless we consider this a bug. Please report\n--2359-- it at http://valgrind.org/support/bug_reports.html.\n--2359-- WARNING: unhandled riscv64-linux syscall: 258\n--2359-- You may be able to write your own handler.\n--2359-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2359-- Nevertheless we consider this a bug. Please report\n--2359-- it at http://valgrind.org/support/bug_reports.html.\n--2359-- WARNING: unhandled riscv64-linux syscall: 258\n--2359-- You may be able to write your own handler.\n--2359-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2359-- Nevertheless we consider this a bug. Please report\n--2359-- it at http://valgrind.org/support/bug_reports.html.\n--2359-- WARNING: unhandled riscv64-linux syscall: 258\n--2359-- You may be able to write your own handler.\n--2359-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2359-- Nevertheless we consider this a bug. Please report\n--2359-- it at http://valgrind.org/support/bug_reports.html.\n--2359-- WARNING: unhandled riscv64-linux syscall: 258\n--2359-- You may be able to write your own handler.\n--2359-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2359-- Nevertheless we consider this a bug. Please report\n--2359-- it at http://valgrind.org/support/bug_reports.html.\n--2359-- WARNING: unhandled riscv64-linux syscall: 258\n--2359-- You may be able to write your own handler.\n--2359-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2359-- Nevertheless we consider this a bug. Please report\n--2359-- it at http://valgrind.org/support/bug_reports.html.\n--2359-- WARNING: unhandled riscv64-linux syscall: 258\n--2359-- You may be able to write your own handler.\n--2359-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2359-- Nevertheless we consider this a bug. Please report\n--2359-- it at http://valgrind.org/support/bug_reports.html.\n--2359-- WARNING: unhandled riscv64-linux syscall: 258\n--2359-- You may be able to write your own handler.\n--2359-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2359-- Nevertheless we consider this a bug. Please report\n--2359-- it at http://valgrind.org/support/bug_reports.html.\n--2359-- WARNING: unhandled riscv64-linux syscall: 258\n--2359-- You may be able to write your own handler.\n--2359-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2359-- Nevertheless we consider this a bug. Please report\n--2359-- it at http://valgrind.org/support/bug_reports.html.\n--2359-- WARNING: unhandled riscv64-linux syscall: 258\n--2359-- You may be able to write your own handler.\n--2359-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2359-- Nevertheless we consider this a bug. Please report\n--2359-- it at http://valgrind.org/support/bug_reports.html.\n--2359-- WARNING: unhandled riscv64-linux syscall: 258\n--2359-- You may be able to write your own handler.\n--2359-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2359-- Nevertheless we consider this a bug. Please report\n--2359-- it at http://valgrind.org/support/bug_reports.html.\n--2359-- WARNING: unhandled riscv64-linux syscall: 258\n--2359-- You may be able to write your own handler.\n--2359-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2359-- Nevertheless we consider this a bug. Please report\n--2359-- it at http://valgrind.org/support/bug_reports.html.\n--2359-- WARNING: unhandled riscv64-linux syscall: 258\n--2359-- You may be able to write your own handler.\n--2359-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2359-- Nevertheless we consider this a bug. Please report\n--2359-- it at http://valgrind.org/support/bug_reports.html.\n--2359-- WARNING: unhandled riscv64-linux syscall: 258\n--2359-- You may be able to write your own handler.\n--2359-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2359-- Nevertheless we consider this a bug. Please report\n--2359-- it at http://valgrind.org/support/bug_reports.html.\n' 136: failed --qtrim 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: 'https://example.org/foo?b=hello&x=y&a=ciao&b=salve\n' --- returncode --- expected: 0 got: 0 --- stderr --- expected: '' got: '--2367-- WARNING: unhandled riscv64-linux syscall: 258\n--2367-- You may be able to write your own handler.\n--2367-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2367-- Nevertheless we consider this a bug. Please report\n--2367-- it at http://valgrind.org/support/bug_reports.html.\n--2367-- WARNING: unhandled riscv64-linux syscall: 258\n--2367-- You may be able to write your own handler.\n--2367-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2367-- Nevertheless we consider this a bug. Please report\n--2367-- it at http://valgrind.org/support/bug_reports.html.\n--2367-- WARNING: unhandled riscv64-linux syscall: 258\n--2367-- You may be able to write your own handler.\n--2367-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2367-- Nevertheless we consider this a bug. Please report\n--2367-- it at http://valgrind.org/support/bug_reports.html.\n--2367-- WARNING: unhandled riscv64-linux syscall: 258\n--2367-- You may be able to write your own handler.\n--2367-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2367-- Nevertheless we consider this a bug. Please report\n--2367-- it at http://valgrind.org/support/bug_reports.html.\n--2367-- WARNING: unhandled riscv64-linux syscall: 258\n--2367-- You may be able to write your own handler.\n--2367-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2367-- Nevertheless we consider this a bug. Please report\n--2367-- it at http://valgrind.org/support/bug_reports.html.\n--2367-- WARNING: unhandled riscv64-linux syscall: 258\n--2367-- You may be able to write your own handler.\n--2367-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2367-- Nevertheless we consider this a bug. Please report\n--2367-- it at http://valgrind.org/support/bug_reports.html.\n--2367-- WARNING: unhandled riscv64-linux syscall: 258\n--2367-- You may be able to write your own handler.\n--2367-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2367-- Nevertheless we consider this a bug. Please report\n--2367-- it at http://valgrind.org/support/bug_reports.html.\n--2367-- WARNING: unhandled riscv64-linux syscall: 258\n--2367-- You may be able to write your own handler.\n--2367-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2367-- Nevertheless we consider this a bug. Please report\n--2367-- it at http://valgrind.org/support/bug_reports.html.\n--2367-- WARNING: unhandled riscv64-linux syscall: 258\n--2367-- You may be able to write your own handler.\n--2367-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2367-- Nevertheless we consider this a bug. Please report\n--2367-- it at http://valgrind.org/support/bug_reports.html.\n--2367-- WARNING: unhandled riscv64-linux syscall: 258\n--2367-- You may be able to write your own handler.\n--2367-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2367-- Nevertheless we consider this a bug. Please report\n--2367-- it at http://valgrind.org/support/bug_reports.html.\n--2367-- WARNING: unhandled riscv64-linux syscall: 258\n--2367-- You may be able to write your own handler.\n--2367-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2367-- Nevertheless we consider this a bug. Please report\n--2367-- it at http://valgrind.org/support/bug_reports.html.\n--2367-- WARNING: unhandled riscv64-linux syscall: 258\n--2367-- You may be able to write your own handler.\n--2367-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2367-- Nevertheless we consider this a bug. Please report\n--2367-- it at http://valgrind.org/support/bug_reports.html.\n--2367-- WARNING: unhandled riscv64-linux syscall: 258\n--2367-- You may be able to write your own handler.\n--2367-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2367-- Nevertheless we consider this a bug. Please report\n--2367-- it at http://valgrind.org/support/bug_reports.html.\n--2367-- WARNING: unhandled riscv64-linux syscall: 258\n--2367-- You may be able to write your own handler.\n--2367-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2367-- Nevertheless we consider this a bug. Please report\n--2367-- it at http://valgrind.org/support/bug_reports.html.\n--2367-- WARNING: unhandled riscv64-linux syscall: 258\n--2367-- You may be able to write your own handler.\n--2367-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2367-- Nevertheless we consider this a bug. Please report\n--2367-- it at http://valgrind.org/support/bug_reports.html.\n--2367-- WARNING: unhandled riscv64-linux syscall: 258\n--2367-- You may be able to write your own handler.\n--2367-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2367-- Nevertheless we consider this a bug. Please report\n--2367-- it at http://valgrind.org/support/bug_reports.html.\n--2367-- WARNING: unhandled riscv64-linux syscall: 258\n--2367-- You may be able to write your own handler.\n--2367-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2367-- Nevertheless we consider this a bug. Please report\n--2367-- it at http://valgrind.org/support/bug_reports.html.\n--2367-- WARNING: unhandled riscv64-linux syscall: 258\n--2367-- You may be able to write your own handler.\n--2367-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2367-- Nevertheless we consider this a bug. Please report\n--2367-- it at http://valgrind.org/support/bug_reports.html.\n' 137: failed 'http://example.com/?q=mr%00smith' --json --urlencode --- stderr --- expected: '' got: '--2375-- WARNING: unhandled riscv64-linux syscall: 258\n--2375-- You may be able to write your own handler.\n--2375-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2375-- Nevertheless we consider this a bug. Please report\n--2375-- it at http://valgrind.org/support/bug_reports.html.\n--2375-- WARNING: unhandled riscv64-linux syscall: 258\n--2375-- You may be able to write your own handler.\n--2375-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2375-- Nevertheless we consider this a bug. Please report\n--2375-- it at http://valgrind.org/support/bug_reports.html.\n--2375-- WARNING: unhandled riscv64-linux syscall: 258\n--2375-- You may be able to write your own handler.\n--2375-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2375-- Nevertheless we consider this a bug. Please report\n--2375-- it at http://valgrind.org/support/bug_reports.html.\n--2375-- WARNING: unhandled riscv64-linux syscall: 258\n--2375-- You may be able to write your own handler.\n--2375-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2375-- Nevertheless we consider this a bug. Please report\n--2375-- it at http://valgrind.org/support/bug_reports.html.\n--2375-- WARNING: unhandled riscv64-linux syscall: 258\n--2375-- You may be able to write your own handler.\n--2375-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2375-- Nevertheless we consider this a bug. Please report\n--2375-- it at http://valgrind.org/support/bug_reports.html.\n--2375-- WARNING: unhandled riscv64-linux syscall: 258\n--2375-- You may be able to write your own handler.\n--2375-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2375-- Nevertheless we consider this a bug. Please report\n--2375-- it at http://valgrind.org/support/bug_reports.html.\n--2375-- WARNING: unhandled riscv64-linux syscall: 258\n--2375-- You may be able to write your own handler.\n--2375-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2375-- Nevertheless we consider this a bug. Please report\n--2375-- it at http://valgrind.org/support/bug_reports.html.\n--2375-- WARNING: unhandled riscv64-linux syscall: 258\n--2375-- You may be able to write your own handler.\n--2375-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2375-- Nevertheless we consider this a bug. Please report\n--2375-- it at http://valgrind.org/support/bug_reports.html.\n--2375-- WARNING: unhandled riscv64-linux syscall: 258\n--2375-- You may be able to write your own handler.\n--2375-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2375-- Nevertheless we consider this a bug. Please report\n--2375-- it at http://valgrind.org/support/bug_reports.html.\n--2375-- WARNING: unhandled riscv64-linux syscall: 258\n--2375-- You may be able to write your own handler.\n--2375-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2375-- Nevertheless we consider this a bug. Please report\n--2375-- it at http://valgrind.org/support/bug_reports.html.\n--2375-- WARNING: unhandled riscv64-linux syscall: 258\n--2375-- You may be able to write your own handler.\n--2375-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2375-- Nevertheless we consider this a bug. Please report\n--2375-- it at http://valgrind.org/support/bug_reports.html.\n--2375-- WARNING: unhandled riscv64-linux syscall: 258\n--2375-- You may be able to write your own handler.\n--2375-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2375-- Nevertheless we consider this a bug. Please report\n--2375-- it at http://valgrind.org/support/bug_reports.html.\n--2375-- WARNING: unhandled riscv64-linux syscall: 258\n--2375-- You may be able to write your own handler.\n--2375-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2375-- Nevertheless we consider this a bug. Please report\n--2375-- it at http://valgrind.org/support/bug_reports.html.\n--2375-- WARNING: unhandled riscv64-linux syscall: 258\n--2375-- You may be able to write your own handler.\n--2375-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2375-- Nevertheless we consider this a bug. Please report\n--2375-- it at http://valgrind.org/support/bug_reports.html.\n--2375-- WARNING: unhandled riscv64-linux syscall: 258\n--2375-- You may be able to write your own handler.\n--2375-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2375-- Nevertheless we consider this a bug. Please report\n--2375-- it at http://valgrind.org/support/bug_reports.html.\n--2375-- WARNING: unhandled riscv64-linux syscall: 258\n--2375-- You may be able to write your own handler.\n--2375-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2375-- Nevertheless we consider this a bug. Please report\n--2375-- it at http://valgrind.org/support/bug_reports.html.\n--2375-- WARNING: unhandled riscv64-linux syscall: 258\n--2375-- You may be able to write your own handler.\n--2375-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2375-- Nevertheless we consider this a bug. Please report\n--2375-- it at http://valgrind.org/support/bug_reports.html.\n--2375-- WARNING: unhandled riscv64-linux syscall: 258\n--2375-- You may be able to write your own handler.\n--2375-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2375-- Nevertheless we consider this a bug. Please report\n--2375-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 --- stdout --- expected: [{'url': 'http://example.com/?q=mr%00smith', 'parts': {'scheme': 'http', 'host': 'example.com', 'path': '/', 'query': 'q=mr%00smith'}, 'params': [{'key': 'q', 'value': 'mr\x00smith'}]}] got: [{'url': 'http://example.com/?q=mr%00smith', 'parts': {'scheme': 'http', 'host': 'example.com', 'path': '/', 'query': 'q=mr%00smith'}, 'params': [{'key': 'q', 'value': 'mr\x00smith'}]}] 138: failed 'http://example.com/?q=mr%00sm%00ith' --json --urlencode --- stderr --- expected: '' got: '--2383-- WARNING: unhandled riscv64-linux syscall: 258\n--2383-- You may be able to write your own handler.\n--2383-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2383-- Nevertheless we consider this a bug. Please report\n--2383-- it at http://valgrind.org/support/bug_reports.html.\n--2383-- WARNING: unhandled riscv64-linux syscall: 258\n--2383-- You may be able to write your own handler.\n--2383-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2383-- Nevertheless we consider this a bug. Please report\n--2383-- it at http://valgrind.org/support/bug_reports.html.\n--2383-- WARNING: unhandled riscv64-linux syscall: 258\n--2383-- You may be able to write your own handler.\n--2383-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2383-- Nevertheless we consider this a bug. Please report\n--2383-- it at http://valgrind.org/support/bug_reports.html.\n--2383-- WARNING: unhandled riscv64-linux syscall: 258\n--2383-- You may be able to write your own handler.\n--2383-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2383-- Nevertheless we consider this a bug. Please report\n--2383-- it at http://valgrind.org/support/bug_reports.html.\n--2383-- WARNING: unhandled riscv64-linux syscall: 258\n--2383-- You may be able to write your own handler.\n--2383-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2383-- Nevertheless we consider this a bug. Please report\n--2383-- it at http://valgrind.org/support/bug_reports.html.\n--2383-- WARNING: unhandled riscv64-linux syscall: 258\n--2383-- You may be able to write your own handler.\n--2383-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2383-- Nevertheless we consider this a bug. Please report\n--2383-- it at http://valgrind.org/support/bug_reports.html.\n--2383-- WARNING: unhandled riscv64-linux syscall: 258\n--2383-- You may be able to write your own handler.\n--2383-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2383-- Nevertheless we consider this a bug. Please report\n--2383-- it at http://valgrind.org/support/bug_reports.html.\n--2383-- WARNING: unhandled riscv64-linux syscall: 258\n--2383-- You may be able to write your own handler.\n--2383-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2383-- Nevertheless we consider this a bug. Please report\n--2383-- it at http://valgrind.org/support/bug_reports.html.\n--2383-- WARNING: unhandled riscv64-linux syscall: 258\n--2383-- You may be able to write your own handler.\n--2383-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2383-- Nevertheless we consider this a bug. Please report\n--2383-- it at http://valgrind.org/support/bug_reports.html.\n--2383-- WARNING: unhandled riscv64-linux syscall: 258\n--2383-- You may be able to write your own handler.\n--2383-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2383-- Nevertheless we consider this a bug. Please report\n--2383-- it at http://valgrind.org/support/bug_reports.html.\n--2383-- WARNING: unhandled riscv64-linux syscall: 258\n--2383-- You may be able to write your own handler.\n--2383-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2383-- Nevertheless we consider this a bug. Please report\n--2383-- it at http://valgrind.org/support/bug_reports.html.\n--2383-- WARNING: unhandled riscv64-linux syscall: 258\n--2383-- You may be able to write your own handler.\n--2383-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2383-- Nevertheless we consider this a bug. Please report\n--2383-- it at http://valgrind.org/support/bug_reports.html.\n--2383-- WARNING: unhandled riscv64-linux syscall: 258\n--2383-- You may be able to write your own handler.\n--2383-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2383-- Nevertheless we consider this a bug. Please report\n--2383-- it at http://valgrind.org/support/bug_reports.html.\n--2383-- WARNING: unhandled riscv64-linux syscall: 258\n--2383-- You may be able to write your own handler.\n--2383-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2383-- Nevertheless we consider this a bug. Please report\n--2383-- it at http://valgrind.org/support/bug_reports.html.\n--2383-- WARNING: unhandled riscv64-linux syscall: 258\n--2383-- You may be able to write your own handler.\n--2383-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2383-- Nevertheless we consider this a bug. Please report\n--2383-- it at http://valgrind.org/support/bug_reports.html.\n--2383-- WARNING: unhandled riscv64-linux syscall: 258\n--2383-- You may be able to write your own handler.\n--2383-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2383-- Nevertheless we consider this a bug. Please report\n--2383-- it at http://valgrind.org/support/bug_reports.html.\n--2383-- WARNING: unhandled riscv64-linux syscall: 258\n--2383-- You may be able to write your own handler.\n--2383-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2383-- Nevertheless we consider this a bug. Please report\n--2383-- it at http://valgrind.org/support/bug_reports.html.\n--2383-- WARNING: unhandled riscv64-linux syscall: 258\n--2383-- You may be able to write your own handler.\n--2383-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2383-- Nevertheless we consider this a bug. Please report\n--2383-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 --- stdout --- expected: [{'url': 'http://example.com/?q=mr%00sm%00ith', 'parts': {'scheme': 'http', 'host': 'example.com', 'path': '/', 'query': 'q=mr%00sm%00ith'}, 'params': [{'key': 'q', 'value': 'mr\x00sm\x00ith'}]}] got: [{'url': 'http://example.com/?q=mr%00sm%00ith', 'parts': {'scheme': 'http', 'host': 'example.com', 'path': '/', 'query': 'q=mr%00sm%00ith'}, 'params': [{'key': 'q', 'value': 'mr\x00sm\x00ith'}]}] 139: failed 'http://example.com/?q=mr%00%00%00smith' --json --urlencode --- stderr --- expected: '' got: '--2391-- WARNING: unhandled riscv64-linux syscall: 258\n--2391-- You may be able to write your own handler.\n--2391-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2391-- Nevertheless we consider this a bug. Please report\n--2391-- it at http://valgrind.org/support/bug_reports.html.\n--2391-- WARNING: unhandled riscv64-linux syscall: 258\n--2391-- You may be able to write your own handler.\n--2391-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2391-- Nevertheless we consider this a bug. Please report\n--2391-- it at http://valgrind.org/support/bug_reports.html.\n--2391-- WARNING: unhandled riscv64-linux syscall: 258\n--2391-- You may be able to write your own handler.\n--2391-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2391-- Nevertheless we consider this a bug. Please report\n--2391-- it at http://valgrind.org/support/bug_reports.html.\n--2391-- WARNING: unhandled riscv64-linux syscall: 258\n--2391-- You may be able to write your own handler.\n--2391-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2391-- Nevertheless we consider this a bug. Please report\n--2391-- it at http://valgrind.org/support/bug_reports.html.\n--2391-- WARNING: unhandled riscv64-linux syscall: 258\n--2391-- You may be able to write your own handler.\n--2391-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2391-- Nevertheless we consider this a bug. Please report\n--2391-- it at http://valgrind.org/support/bug_reports.html.\n--2391-- WARNING: unhandled riscv64-linux syscall: 258\n--2391-- You may be able to write your own handler.\n--2391-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2391-- Nevertheless we consider this a bug. Please report\n--2391-- it at http://valgrind.org/support/bug_reports.html.\n--2391-- WARNING: unhandled riscv64-linux syscall: 258\n--2391-- You may be able to write your own handler.\n--2391-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2391-- Nevertheless we consider this a bug. Please report\n--2391-- it at http://valgrind.org/support/bug_reports.html.\n--2391-- WARNING: unhandled riscv64-linux syscall: 258\n--2391-- You may be able to write your own handler.\n--2391-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2391-- Nevertheless we consider this a bug. Please report\n--2391-- it at http://valgrind.org/support/bug_reports.html.\n--2391-- WARNING: unhandled riscv64-linux syscall: 258\n--2391-- You may be able to write your own handler.\n--2391-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2391-- Nevertheless we consider this a bug. Please report\n--2391-- it at http://valgrind.org/support/bug_reports.html.\n--2391-- WARNING: unhandled riscv64-linux syscall: 258\n--2391-- You may be able to write your own handler.\n--2391-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2391-- Nevertheless we consider this a bug. Please report\n--2391-- it at http://valgrind.org/support/bug_reports.html.\n--2391-- WARNING: unhandled riscv64-linux syscall: 258\n--2391-- You may be able to write your own handler.\n--2391-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2391-- Nevertheless we consider this a bug. Please report\n--2391-- it at http://valgrind.org/support/bug_reports.html.\n--2391-- WARNING: unhandled riscv64-linux syscall: 258\n--2391-- You may be able to write your own handler.\n--2391-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2391-- Nevertheless we consider this a bug. Please report\n--2391-- it at http://valgrind.org/support/bug_reports.html.\n--2391-- WARNING: unhandled riscv64-linux syscall: 258\n--2391-- You may be able to write your own handler.\n--2391-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2391-- Nevertheless we consider this a bug. Please report\n--2391-- it at http://valgrind.org/support/bug_reports.html.\n--2391-- WARNING: unhandled riscv64-linux syscall: 258\n--2391-- You may be able to write your own handler.\n--2391-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2391-- Nevertheless we consider this a bug. Please report\n--2391-- it at http://valgrind.org/support/bug_reports.html.\n--2391-- WARNING: unhandled riscv64-linux syscall: 258\n--2391-- You may be able to write your own handler.\n--2391-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2391-- Nevertheless we consider this a bug. Please report\n--2391-- it at http://valgrind.org/support/bug_reports.html.\n--2391-- WARNING: unhandled riscv64-linux syscall: 258\n--2391-- You may be able to write your own handler.\n--2391-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2391-- Nevertheless we consider this a bug. Please report\n--2391-- it at http://valgrind.org/support/bug_reports.html.\n--2391-- WARNING: unhandled riscv64-linux syscall: 258\n--2391-- You may be able to write your own handler.\n--2391-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2391-- Nevertheless we consider this a bug. Please report\n--2391-- it at http://valgrind.org/support/bug_reports.html.\n--2391-- WARNING: unhandled riscv64-linux syscall: 258\n--2391-- You may be able to write your own handler.\n--2391-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2391-- Nevertheless we consider this a bug. Please report\n--2391-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 --- stdout --- expected: [{'url': 'http://example.com/?q=mr%00%00%00smith', 'parts': {'scheme': 'http', 'host': 'example.com', 'path': '/', 'query': 'q=mr%00%00%00smith'}, 'params': [{'key': 'q', 'value': 'mr\x00\x00\x00smith'}]}] got: [{'url': 'http://example.com/?q=mr%00%00%00smith', 'parts': {'scheme': 'http', 'host': 'example.com', 'path': '/', 'query': 'q=mr%00%00%00smith'}, 'params': [{'key': 'q', 'value': 'mr\x00\x00\x00smith'}]}] 140: failed --url 'https://curl.se/we/are.html?*=moo&user=many#more' --qtrim '\*' --- stdout --- expected: 'https://curl.se/we/are.html?user=many#more\n' got: 'https://curl.se/we/are.html?user=many#more\n' --- stderr --- expected: '' got: '--2399-- WARNING: unhandled riscv64-linux syscall: 258\n--2399-- You may be able to write your own handler.\n--2399-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2399-- Nevertheless we consider this a bug. Please report\n--2399-- it at http://valgrind.org/support/bug_reports.html.\n--2399-- WARNING: unhandled riscv64-linux syscall: 258\n--2399-- You may be able to write your own handler.\n--2399-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2399-- Nevertheless we consider this a bug. Please report\n--2399-- it at http://valgrind.org/support/bug_reports.html.\n--2399-- WARNING: unhandled riscv64-linux syscall: 258\n--2399-- You may be able to write your own handler.\n--2399-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2399-- Nevertheless we consider this a bug. Please report\n--2399-- it at http://valgrind.org/support/bug_reports.html.\n--2399-- WARNING: unhandled riscv64-linux syscall: 258\n--2399-- You may be able to write your own handler.\n--2399-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2399-- Nevertheless we consider this a bug. Please report\n--2399-- it at http://valgrind.org/support/bug_reports.html.\n--2399-- WARNING: unhandled riscv64-linux syscall: 258\n--2399-- You may be able to write your own handler.\n--2399-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2399-- Nevertheless we consider this a bug. Please report\n--2399-- it at http://valgrind.org/support/bug_reports.html.\n--2399-- WARNING: unhandled riscv64-linux syscall: 258\n--2399-- You may be able to write your own handler.\n--2399-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2399-- Nevertheless we consider this a bug. Please report\n--2399-- it at http://valgrind.org/support/bug_reports.html.\n--2399-- WARNING: unhandled riscv64-linux syscall: 258\n--2399-- You may be able to write your own handler.\n--2399-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2399-- Nevertheless we consider this a bug. Please report\n--2399-- it at http://valgrind.org/support/bug_reports.html.\n--2399-- WARNING: unhandled riscv64-linux syscall: 258\n--2399-- You may be able to write your own handler.\n--2399-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2399-- Nevertheless we consider this a bug. Please report\n--2399-- it at http://valgrind.org/support/bug_reports.html.\n--2399-- WARNING: unhandled riscv64-linux syscall: 258\n--2399-- You may be able to write your own handler.\n--2399-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2399-- Nevertheless we consider this a bug. Please report\n--2399-- it at http://valgrind.org/support/bug_reports.html.\n--2399-- WARNING: unhandled riscv64-linux syscall: 258\n--2399-- You may be able to write your own handler.\n--2399-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2399-- Nevertheless we consider this a bug. Please report\n--2399-- it at http://valgrind.org/support/bug_reports.html.\n--2399-- WARNING: unhandled riscv64-linux syscall: 258\n--2399-- You may be able to write your own handler.\n--2399-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2399-- Nevertheless we consider this a bug. Please report\n--2399-- it at http://valgrind.org/support/bug_reports.html.\n--2399-- WARNING: unhandled riscv64-linux syscall: 258\n--2399-- You may be able to write your own handler.\n--2399-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2399-- Nevertheless we consider this a bug. Please report\n--2399-- it at http://valgrind.org/support/bug_reports.html.\n--2399-- WARNING: unhandled riscv64-linux syscall: 258\n--2399-- You may be able to write your own handler.\n--2399-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2399-- Nevertheless we consider this a bug. Please report\n--2399-- it at http://valgrind.org/support/bug_reports.html.\n--2399-- WARNING: unhandled riscv64-linux syscall: 258\n--2399-- You may be able to write your own handler.\n--2399-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2399-- Nevertheless we consider this a bug. Please report\n--2399-- it at http://valgrind.org/support/bug_reports.html.\n--2399-- WARNING: unhandled riscv64-linux syscall: 258\n--2399-- You may be able to write your own handler.\n--2399-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2399-- Nevertheless we consider this a bug. Please report\n--2399-- it at http://valgrind.org/support/bug_reports.html.\n--2399-- WARNING: unhandled riscv64-linux syscall: 258\n--2399-- You may be able to write your own handler.\n--2399-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2399-- Nevertheless we consider this a bug. Please report\n--2399-- it at http://valgrind.org/support/bug_reports.html.\n--2399-- WARNING: unhandled riscv64-linux syscall: 258\n--2399-- You may be able to write your own handler.\n--2399-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2399-- Nevertheless we consider this a bug. Please report\n--2399-- it at http://valgrind.org/support/bug_reports.html.\n--2399-- WARNING: unhandled riscv64-linux syscall: 258\n--2399-- You may be able to write your own handler.\n--2399-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2399-- Nevertheless we consider this a bug. Please report\n--2399-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 141: failed --url http://xn--rksmrgs-5wao1o/ --as-idn --- stdout --- expected: 'http://räksmörgås/\n' got: 'http://räksmörgås/\n' --- stderr --- expected: '' got: '--2408-- WARNING: unhandled riscv64-linux syscall: 258\n--2408-- You may be able to write your own handler.\n--2408-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2408-- Nevertheless we consider this a bug. Please report\n--2408-- it at http://valgrind.org/support/bug_reports.html.\n--2408-- WARNING: unhandled riscv64-linux syscall: 258\n--2408-- You may be able to write your own handler.\n--2408-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2408-- Nevertheless we consider this a bug. Please report\n--2408-- it at http://valgrind.org/support/bug_reports.html.\n--2408-- WARNING: unhandled riscv64-linux syscall: 258\n--2408-- You may be able to write your own handler.\n--2408-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2408-- Nevertheless we consider this a bug. Please report\n--2408-- it at http://valgrind.org/support/bug_reports.html.\n--2408-- WARNING: unhandled riscv64-linux syscall: 258\n--2408-- You may be able to write your own handler.\n--2408-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2408-- Nevertheless we consider this a bug. Please report\n--2408-- it at http://valgrind.org/support/bug_reports.html.\n--2408-- WARNING: unhandled riscv64-linux syscall: 258\n--2408-- You may be able to write your own handler.\n--2408-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2408-- Nevertheless we consider this a bug. Please report\n--2408-- it at http://valgrind.org/support/bug_reports.html.\n--2408-- WARNING: unhandled riscv64-linux syscall: 258\n--2408-- You may be able to write your own handler.\n--2408-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2408-- Nevertheless we consider this a bug. Please report\n--2408-- it at http://valgrind.org/support/bug_reports.html.\n--2408-- WARNING: unhandled riscv64-linux syscall: 258\n--2408-- You may be able to write your own handler.\n--2408-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2408-- Nevertheless we consider this a bug. Please report\n--2408-- it at http://valgrind.org/support/bug_reports.html.\n--2408-- WARNING: unhandled riscv64-linux syscall: 258\n--2408-- You may be able to write your own handler.\n--2408-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2408-- Nevertheless we consider this a bug. Please report\n--2408-- it at http://valgrind.org/support/bug_reports.html.\n--2408-- WARNING: unhandled riscv64-linux syscall: 258\n--2408-- You may be able to write your own handler.\n--2408-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2408-- Nevertheless we consider this a bug. Please report\n--2408-- it at http://valgrind.org/support/bug_reports.html.\n--2408-- WARNING: unhandled riscv64-linux syscall: 258\n--2408-- You may be able to write your own handler.\n--2408-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2408-- Nevertheless we consider this a bug. Please report\n--2408-- it at http://valgrind.org/support/bug_reports.html.\n--2408-- WARNING: unhandled riscv64-linux syscall: 258\n--2408-- You may be able to write your own handler.\n--2408-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2408-- Nevertheless we consider this a bug. Please report\n--2408-- it at http://valgrind.org/support/bug_reports.html.\n--2408-- WARNING: unhandled riscv64-linux syscall: 258\n--2408-- You may be able to write your own handler.\n--2408-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2408-- Nevertheless we consider this a bug. Please report\n--2408-- it at http://valgrind.org/support/bug_reports.html.\n--2408-- WARNING: unhandled riscv64-linux syscall: 258\n--2408-- You may be able to write your own handler.\n--2408-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2408-- Nevertheless we consider this a bug. Please report\n--2408-- it at http://valgrind.org/support/bug_reports.html.\n--2408-- WARNING: unhandled riscv64-linux syscall: 258\n--2408-- You may be able to write your own handler.\n--2408-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2408-- Nevertheless we consider this a bug. Please report\n--2408-- it at http://valgrind.org/support/bug_reports.html.\n--2408-- WARNING: unhandled riscv64-linux syscall: 258\n--2408-- You may be able to write your own handler.\n--2408-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2408-- Nevertheless we consider this a bug. Please report\n--2408-- it at http://valgrind.org/support/bug_reports.html.\n--2408-- WARNING: unhandled riscv64-linux syscall: 258\n--2408-- You may be able to write your own handler.\n--2408-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2408-- Nevertheless we consider this a bug. Please report\n--2408-- it at http://valgrind.org/support/bug_reports.html.\n--2408-- WARNING: unhandled riscv64-linux syscall: 258\n--2408-- You may be able to write your own handler.\n--2408-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2408-- Nevertheless we consider this a bug. Please report\n--2408-- it at http://valgrind.org/support/bug_reports.html.\n--2408-- WARNING: unhandled riscv64-linux syscall: 258\n--2408-- You may be able to write your own handler.\n--2408-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2408-- Nevertheless we consider this a bug. Please report\n--2408-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 142: failed --url http://xn--rksmrgs-5wao1o/ -g '{idn:host}' --- stdout --- expected: 'räksmörgås\n' got: 'räksmörgås\n' --- stderr --- expected: '' got: '--2419-- WARNING: unhandled riscv64-linux syscall: 258\n--2419-- You may be able to write your own handler.\n--2419-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2419-- Nevertheless we consider this a bug. Please report\n--2419-- it at http://valgrind.org/support/bug_reports.html.\n--2419-- WARNING: unhandled riscv64-linux syscall: 258\n--2419-- You may be able to write your own handler.\n--2419-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2419-- Nevertheless we consider this a bug. Please report\n--2419-- it at http://valgrind.org/support/bug_reports.html.\n--2419-- WARNING: unhandled riscv64-linux syscall: 258\n--2419-- You may be able to write your own handler.\n--2419-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2419-- Nevertheless we consider this a bug. Please report\n--2419-- it at http://valgrind.org/support/bug_reports.html.\n--2419-- WARNING: unhandled riscv64-linux syscall: 258\n--2419-- You may be able to write your own handler.\n--2419-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2419-- Nevertheless we consider this a bug. Please report\n--2419-- it at http://valgrind.org/support/bug_reports.html.\n--2419-- WARNING: unhandled riscv64-linux syscall: 258\n--2419-- You may be able to write your own handler.\n--2419-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2419-- Nevertheless we consider this a bug. Please report\n--2419-- it at http://valgrind.org/support/bug_reports.html.\n--2419-- WARNING: unhandled riscv64-linux syscall: 258\n--2419-- You may be able to write your own handler.\n--2419-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2419-- Nevertheless we consider this a bug. Please report\n--2419-- it at http://valgrind.org/support/bug_reports.html.\n--2419-- WARNING: unhandled riscv64-linux syscall: 258\n--2419-- You may be able to write your own handler.\n--2419-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2419-- Nevertheless we consider this a bug. Please report\n--2419-- it at http://valgrind.org/support/bug_reports.html.\n--2419-- WARNING: unhandled riscv64-linux syscall: 258\n--2419-- You may be able to write your own handler.\n--2419-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2419-- Nevertheless we consider this a bug. Please report\n--2419-- it at http://valgrind.org/support/bug_reports.html.\n--2419-- WARNING: unhandled riscv64-linux syscall: 258\n--2419-- You may be able to write your own handler.\n--2419-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2419-- Nevertheless we consider this a bug. Please report\n--2419-- it at http://valgrind.org/support/bug_reports.html.\n--2419-- WARNING: unhandled riscv64-linux syscall: 258\n--2419-- You may be able to write your own handler.\n--2419-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2419-- Nevertheless we consider this a bug. Please report\n--2419-- it at http://valgrind.org/support/bug_reports.html.\n--2419-- WARNING: unhandled riscv64-linux syscall: 258\n--2419-- You may be able to write your own handler.\n--2419-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2419-- Nevertheless we consider this a bug. Please report\n--2419-- it at http://valgrind.org/support/bug_reports.html.\n--2419-- WARNING: unhandled riscv64-linux syscall: 258\n--2419-- You may be able to write your own handler.\n--2419-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2419-- Nevertheless we consider this a bug. Please report\n--2419-- it at http://valgrind.org/support/bug_reports.html.\n--2419-- WARNING: unhandled riscv64-linux syscall: 258\n--2419-- You may be able to write your own handler.\n--2419-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2419-- Nevertheless we consider this a bug. Please report\n--2419-- it at http://valgrind.org/support/bug_reports.html.\n--2419-- WARNING: unhandled riscv64-linux syscall: 258\n--2419-- You may be able to write your own handler.\n--2419-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2419-- Nevertheless we consider this a bug. Please report\n--2419-- it at http://valgrind.org/support/bug_reports.html.\n--2419-- WARNING: unhandled riscv64-linux syscall: 258\n--2419-- You may be able to write your own handler.\n--2419-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2419-- Nevertheless we consider this a bug. Please report\n--2419-- it at http://valgrind.org/support/bug_reports.html.\n--2419-- WARNING: unhandled riscv64-linux syscall: 258\n--2419-- You may be able to write your own handler.\n--2419-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2419-- Nevertheless we consider this a bug. Please report\n--2419-- it at http://valgrind.org/support/bug_reports.html.\n--2419-- WARNING: unhandled riscv64-linux syscall: 258\n--2419-- You may be able to write your own handler.\n--2419-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2419-- Nevertheless we consider this a bug. Please report\n--2419-- it at http://valgrind.org/support/bug_reports.html.\n--2419-- WARNING: unhandled riscv64-linux syscall: 258\n--2419-- You may be able to write your own handler.\n--2419-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2419-- Nevertheless we consider this a bug. Please report\n--2419-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 143: failed --url http://xn-----/ --as-idn --quiet --- stdout --- expected: 'http://xn-----/\n' got: 'http://xn-----/\n' --- stderr --- expected: '' got: '--2430-- WARNING: unhandled riscv64-linux syscall: 258\n--2430-- You may be able to write your own handler.\n--2430-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2430-- Nevertheless we consider this a bug. Please report\n--2430-- it at http://valgrind.org/support/bug_reports.html.\n--2430-- WARNING: unhandled riscv64-linux syscall: 258\n--2430-- You may be able to write your own handler.\n--2430-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2430-- Nevertheless we consider this a bug. Please report\n--2430-- it at http://valgrind.org/support/bug_reports.html.\n--2430-- WARNING: unhandled riscv64-linux syscall: 258\n--2430-- You may be able to write your own handler.\n--2430-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2430-- Nevertheless we consider this a bug. Please report\n--2430-- it at http://valgrind.org/support/bug_reports.html.\n--2430-- WARNING: unhandled riscv64-linux syscall: 258\n--2430-- You may be able to write your own handler.\n--2430-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2430-- Nevertheless we consider this a bug. Please report\n--2430-- it at http://valgrind.org/support/bug_reports.html.\n--2430-- WARNING: unhandled riscv64-linux syscall: 258\n--2430-- You may be able to write your own handler.\n--2430-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2430-- Nevertheless we consider this a bug. Please report\n--2430-- it at http://valgrind.org/support/bug_reports.html.\n--2430-- WARNING: unhandled riscv64-linux syscall: 258\n--2430-- You may be able to write your own handler.\n--2430-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2430-- Nevertheless we consider this a bug. Please report\n--2430-- it at http://valgrind.org/support/bug_reports.html.\n--2430-- WARNING: unhandled riscv64-linux syscall: 258\n--2430-- You may be able to write your own handler.\n--2430-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2430-- Nevertheless we consider this a bug. Please report\n--2430-- it at http://valgrind.org/support/bug_reports.html.\n--2430-- WARNING: unhandled riscv64-linux syscall: 258\n--2430-- You may be able to write your own handler.\n--2430-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2430-- Nevertheless we consider this a bug. Please report\n--2430-- it at http://valgrind.org/support/bug_reports.html.\n--2430-- WARNING: unhandled riscv64-linux syscall: 258\n--2430-- You may be able to write your own handler.\n--2430-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2430-- Nevertheless we consider this a bug. Please report\n--2430-- it at http://valgrind.org/support/bug_reports.html.\n--2430-- WARNING: unhandled riscv64-linux syscall: 258\n--2430-- You may be able to write your own handler.\n--2430-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2430-- Nevertheless we consider this a bug. Please report\n--2430-- it at http://valgrind.org/support/bug_reports.html.\n--2430-- WARNING: unhandled riscv64-linux syscall: 258\n--2430-- You may be able to write your own handler.\n--2430-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2430-- Nevertheless we consider this a bug. Please report\n--2430-- it at http://valgrind.org/support/bug_reports.html.\n--2430-- WARNING: unhandled riscv64-linux syscall: 258\n--2430-- You may be able to write your own handler.\n--2430-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2430-- Nevertheless we consider this a bug. Please report\n--2430-- it at http://valgrind.org/support/bug_reports.html.\n--2430-- WARNING: unhandled riscv64-linux syscall: 258\n--2430-- You may be able to write your own handler.\n--2430-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2430-- Nevertheless we consider this a bug. Please report\n--2430-- it at http://valgrind.org/support/bug_reports.html.\n--2430-- WARNING: unhandled riscv64-linux syscall: 258\n--2430-- You may be able to write your own handler.\n--2430-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2430-- Nevertheless we consider this a bug. Please report\n--2430-- it at http://valgrind.org/support/bug_reports.html.\n--2430-- WARNING: unhandled riscv64-linux syscall: 258\n--2430-- You may be able to write your own handler.\n--2430-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2430-- Nevertheless we consider this a bug. Please report\n--2430-- it at http://valgrind.org/support/bug_reports.html.\n--2430-- WARNING: unhandled riscv64-linux syscall: 258\n--2430-- You may be able to write your own handler.\n--2430-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2430-- Nevertheless we consider this a bug. Please report\n--2430-- it at http://valgrind.org/support/bug_reports.html.\n--2430-- WARNING: unhandled riscv64-linux syscall: 258\n--2430-- You may be able to write your own handler.\n--2430-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2430-- Nevertheless we consider this a bug. Please report\n--2430-- it at http://valgrind.org/support/bug_reports.html.\n--2430-- WARNING: unhandled riscv64-linux syscall: 258\n--2430-- You may be able to write your own handler.\n--2430-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2430-- Nevertheless we consider this a bug. Please report\n--2430-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 144: failed --url http://xn-----/ --as-idn --- stdout --- expected: 'http://xn-----/\n' got: 'http://xn-----/\n' --- stderr --- expected: 'trurl note: Error converting url to IDN [Bad hostname]\n' got: '--2439-- WARNING: unhandled riscv64-linux syscall: 258\n--2439-- You may be able to write your own handler.\n--2439-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2439-- Nevertheless we consider this a bug. Please report\n--2439-- it at http://valgrind.org/support/bug_reports.html.\n--2439-- WARNING: unhandled riscv64-linux syscall: 258\n--2439-- You may be able to write your own handler.\n--2439-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2439-- Nevertheless we consider this a bug. Please report\n--2439-- it at http://valgrind.org/support/bug_reports.html.\n--2439-- WARNING: unhandled riscv64-linux syscall: 258\n--2439-- You may be able to write your own handler.\n--2439-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2439-- Nevertheless we consider this a bug. Please report\n--2439-- it at http://valgrind.org/support/bug_reports.html.\n--2439-- WARNING: unhandled riscv64-linux syscall: 258\n--2439-- You may be able to write your own handler.\n--2439-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2439-- Nevertheless we consider this a bug. Please report\n--2439-- it at http://valgrind.org/support/bug_reports.html.\n--2439-- WARNING: unhandled riscv64-linux syscall: 258\n--2439-- You may be able to write your own handler.\n--2439-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2439-- Nevertheless we consider this a bug. Please report\n--2439-- it at http://valgrind.org/support/bug_reports.html.\n--2439-- WARNING: unhandled riscv64-linux syscall: 258\n--2439-- You may be able to write your own handler.\n--2439-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2439-- Nevertheless we consider this a bug. Please report\n--2439-- it at http://valgrind.org/support/bug_reports.html.\n--2439-- WARNING: unhandled riscv64-linux syscall: 258\n--2439-- You may be able to write your own handler.\n--2439-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2439-- Nevertheless we consider this a bug. Please report\n--2439-- it at http://valgrind.org/support/bug_reports.html.\n--2439-- WARNING: unhandled riscv64-linux syscall: 258\n--2439-- You may be able to write your own handler.\n--2439-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2439-- Nevertheless we consider this a bug. Please report\n--2439-- it at http://valgrind.org/support/bug_reports.html.\n--2439-- WARNING: unhandled riscv64-linux syscall: 258\n--2439-- You may be able to write your own handler.\n--2439-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2439-- Nevertheless we consider this a bug. Please report\n--2439-- it at http://valgrind.org/support/bug_reports.html.\n--2439-- WARNING: unhandled riscv64-linux syscall: 258\n--2439-- You may be able to write your own handler.\n--2439-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2439-- Nevertheless we consider this a bug. Please report\n--2439-- it at http://valgrind.org/support/bug_reports.html.\n--2439-- WARNING: unhandled riscv64-linux syscall: 258\n--2439-- You may be able to write your own handler.\n--2439-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2439-- Nevertheless we consider this a bug. Please report\n--2439-- it at http://valgrind.org/support/bug_reports.html.\n--2439-- WARNING: unhandled riscv64-linux syscall: 258\n--2439-- You may be able to write your own handler.\n--2439-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2439-- Nevertheless we consider this a bug. Please report\n--2439-- it at http://valgrind.org/support/bug_reports.html.\n--2439-- WARNING: unhandled riscv64-linux syscall: 258\n--2439-- You may be able to write your own handler.\n--2439-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2439-- Nevertheless we consider this a bug. Please report\n--2439-- it at http://valgrind.org/support/bug_reports.html.\n--2439-- WARNING: unhandled riscv64-linux syscall: 258\n--2439-- You may be able to write your own handler.\n--2439-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2439-- Nevertheless we consider this a bug. Please report\n--2439-- it at http://valgrind.org/support/bug_reports.html.\n--2439-- WARNING: unhandled riscv64-linux syscall: 258\n--2439-- You may be able to write your own handler.\n--2439-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2439-- Nevertheless we consider this a bug. Please report\n--2439-- it at http://valgrind.org/support/bug_reports.html.\n--2439-- WARNING: unhandled riscv64-linux syscall: 258\n--2439-- You may be able to write your own handler.\n--2439-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2439-- Nevertheless we consider this a bug. Please report\n--2439-- it at http://valgrind.org/support/bug_reports.html.\n--2439-- WARNING: unhandled riscv64-linux syscall: 258\n--2439-- You may be able to write your own handler.\n--2439-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2439-- Nevertheless we consider this a bug. Please report\n--2439-- it at http://valgrind.org/support/bug_reports.html.\n--2439-- WARNING: unhandled riscv64-linux syscall: 258\n--2439-- You may be able to write your own handler.\n--2439-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2439-- Nevertheless we consider this a bug. Please report\n--2439-- it at http://valgrind.org/support/bug_reports.html.\ntrurl note: Error converting url to IDN [Bad hostname]\n' --- returncode --- expected: 0 got: 0 145: failed --verify -f testfiles/test0000.txt --quiet --- stdout --- expected: 'http://example.org/\n' got: 'http://example.org/\n' --- returncode --- expected: 0 got: 0 --- stderr --- expected: '' got: '--2447-- WARNING: unhandled riscv64-linux syscall: 258\n--2447-- You may be able to write your own handler.\n--2447-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2447-- Nevertheless we consider this a bug. Please report\n--2447-- it at http://valgrind.org/support/bug_reports.html.\n--2447-- WARNING: unhandled riscv64-linux syscall: 258\n--2447-- You may be able to write your own handler.\n--2447-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2447-- Nevertheless we consider this a bug. Please report\n--2447-- it at http://valgrind.org/support/bug_reports.html.\n--2447-- WARNING: unhandled riscv64-linux syscall: 258\n--2447-- You may be able to write your own handler.\n--2447-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2447-- Nevertheless we consider this a bug. Please report\n--2447-- it at http://valgrind.org/support/bug_reports.html.\n--2447-- WARNING: unhandled riscv64-linux syscall: 258\n--2447-- You may be able to write your own handler.\n--2447-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2447-- Nevertheless we consider this a bug. Please report\n--2447-- it at http://valgrind.org/support/bug_reports.html.\n--2447-- WARNING: unhandled riscv64-linux syscall: 258\n--2447-- You may be able to write your own handler.\n--2447-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2447-- Nevertheless we consider this a bug. Please report\n--2447-- it at http://valgrind.org/support/bug_reports.html.\n--2447-- WARNING: unhandled riscv64-linux syscall: 258\n--2447-- You may be able to write your own handler.\n--2447-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2447-- Nevertheless we consider this a bug. Please report\n--2447-- it at http://valgrind.org/support/bug_reports.html.\n--2447-- WARNING: unhandled riscv64-linux syscall: 258\n--2447-- You may be able to write your own handler.\n--2447-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2447-- Nevertheless we consider this a bug. Please report\n--2447-- it at http://valgrind.org/support/bug_reports.html.\n--2447-- WARNING: unhandled riscv64-linux syscall: 258\n--2447-- You may be able to write your own handler.\n--2447-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2447-- Nevertheless we consider this a bug. Please report\n--2447-- it at http://valgrind.org/support/bug_reports.html.\n--2447-- WARNING: unhandled riscv64-linux syscall: 258\n--2447-- You may be able to write your own handler.\n--2447-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2447-- Nevertheless we consider this a bug. Please report\n--2447-- it at http://valgrind.org/support/bug_reports.html.\n--2447-- WARNING: unhandled riscv64-linux syscall: 258\n--2447-- You may be able to write your own handler.\n--2447-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2447-- Nevertheless we consider this a bug. Please report\n--2447-- it at http://valgrind.org/support/bug_reports.html.\n--2447-- WARNING: unhandled riscv64-linux syscall: 258\n--2447-- You may be able to write your own handler.\n--2447-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2447-- Nevertheless we consider this a bug. Please report\n--2447-- it at http://valgrind.org/support/bug_reports.html.\n--2447-- WARNING: unhandled riscv64-linux syscall: 258\n--2447-- You may be able to write your own handler.\n--2447-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2447-- Nevertheless we consider this a bug. Please report\n--2447-- it at http://valgrind.org/support/bug_reports.html.\n--2447-- WARNING: unhandled riscv64-linux syscall: 258\n--2447-- You may be able to write your own handler.\n--2447-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2447-- Nevertheless we consider this a bug. Please report\n--2447-- it at http://valgrind.org/support/bug_reports.html.\n--2447-- WARNING: unhandled riscv64-linux syscall: 258\n--2447-- You may be able to write your own handler.\n--2447-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2447-- Nevertheless we consider this a bug. Please report\n--2447-- it at http://valgrind.org/support/bug_reports.html.\n--2447-- WARNING: unhandled riscv64-linux syscall: 258\n--2447-- You may be able to write your own handler.\n--2447-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2447-- Nevertheless we consider this a bug. Please report\n--2447-- it at http://valgrind.org/support/bug_reports.html.\n--2447-- WARNING: unhandled riscv64-linux syscall: 258\n--2447-- You may be able to write your own handler.\n--2447-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2447-- Nevertheless we consider this a bug. Please report\n--2447-- it at http://valgrind.org/support/bug_reports.html.\n--2447-- WARNING: unhandled riscv64-linux syscall: 258\n--2447-- You may be able to write your own handler.\n--2447-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2447-- Nevertheless we consider this a bug. Please report\n--2447-- it at http://valgrind.org/support/bug_reports.html.\n--2447-- WARNING: unhandled riscv64-linux syscall: 258\n--2447-- You may be able to write your own handler.\n--2447-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2447-- Nevertheless we consider this a bug. Please report\n--2447-- it at http://valgrind.org/support/bug_reports.html.\n' 147: failed 'http://test.org/?key=val' --replace key=foo --- stdout --- expected: 'http://test.org/?key=foo\n' got: 'http://test.org/?key=foo\n' --- stderr --- expected: '' got: '--2463-- WARNING: unhandled riscv64-linux syscall: 258\n--2463-- You may be able to write your own handler.\n--2463-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2463-- Nevertheless we consider this a bug. Please report\n--2463-- it at http://valgrind.org/support/bug_reports.html.\n--2463-- WARNING: unhandled riscv64-linux syscall: 258\n--2463-- You may be able to write your own handler.\n--2463-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2463-- Nevertheless we consider this a bug. Please report\n--2463-- it at http://valgrind.org/support/bug_reports.html.\n--2463-- WARNING: unhandled riscv64-linux syscall: 258\n--2463-- You may be able to write your own handler.\n--2463-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2463-- Nevertheless we consider this a bug. Please report\n--2463-- it at http://valgrind.org/support/bug_reports.html.\n--2463-- WARNING: unhandled riscv64-linux syscall: 258\n--2463-- You may be able to write your own handler.\n--2463-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2463-- Nevertheless we consider this a bug. Please report\n--2463-- it at http://valgrind.org/support/bug_reports.html.\n--2463-- WARNING: unhandled riscv64-linux syscall: 258\n--2463-- You may be able to write your own handler.\n--2463-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2463-- Nevertheless we consider this a bug. Please report\n--2463-- it at http://valgrind.org/support/bug_reports.html.\n--2463-- WARNING: unhandled riscv64-linux syscall: 258\n--2463-- You may be able to write your own handler.\n--2463-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2463-- Nevertheless we consider this a bug. Please report\n--2463-- it at http://valgrind.org/support/bug_reports.html.\n--2463-- WARNING: unhandled riscv64-linux syscall: 258\n--2463-- You may be able to write your own handler.\n--2463-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2463-- Nevertheless we consider this a bug. Please report\n--2463-- it at http://valgrind.org/support/bug_reports.html.\n--2463-- WARNING: unhandled riscv64-linux syscall: 258\n--2463-- You may be able to write your own handler.\n--2463-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2463-- Nevertheless we consider this a bug. Please report\n--2463-- it at http://valgrind.org/support/bug_reports.html.\n--2463-- WARNING: unhandled riscv64-linux syscall: 258\n--2463-- You may be able to write your own handler.\n--2463-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2463-- Nevertheless we consider this a bug. Please report\n--2463-- it at http://valgrind.org/support/bug_reports.html.\n--2463-- WARNING: unhandled riscv64-linux syscall: 258\n--2463-- You may be able to write your own handler.\n--2463-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2463-- Nevertheless we consider this a bug. Please report\n--2463-- it at http://valgrind.org/support/bug_reports.html.\n--2463-- WARNING: unhandled riscv64-linux syscall: 258\n--2463-- You may be able to write your own handler.\n--2463-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2463-- Nevertheless we consider this a bug. Please report\n--2463-- it at http://valgrind.org/support/bug_reports.html.\n--2463-- WARNING: unhandled riscv64-linux syscall: 258\n--2463-- You may be able to write your own handler.\n--2463-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2463-- Nevertheless we consider this a bug. Please report\n--2463-- it at http://valgrind.org/support/bug_reports.html.\n--2463-- WARNING: unhandled riscv64-linux syscall: 258\n--2463-- You may be able to write your own handler.\n--2463-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2463-- Nevertheless we consider this a bug. Please report\n--2463-- it at http://valgrind.org/support/bug_reports.html.\n--2463-- WARNING: unhandled riscv64-linux syscall: 258\n--2463-- You may be able to write your own handler.\n--2463-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2463-- Nevertheless we consider this a bug. Please report\n--2463-- it at http://valgrind.org/support/bug_reports.html.\n--2463-- WARNING: unhandled riscv64-linux syscall: 258\n--2463-- You may be able to write your own handler.\n--2463-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2463-- Nevertheless we consider this a bug. Please report\n--2463-- it at http://valgrind.org/support/bug_reports.html.\n--2463-- WARNING: unhandled riscv64-linux syscall: 258\n--2463-- You may be able to write your own handler.\n--2463-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2463-- Nevertheless we consider this a bug. Please report\n--2463-- it at http://valgrind.org/support/bug_reports.html.\n--2463-- WARNING: unhandled riscv64-linux syscall: 258\n--2463-- You may be able to write your own handler.\n--2463-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2463-- Nevertheless we consider this a bug. Please report\n--2463-- it at http://valgrind.org/support/bug_reports.html.\n--2463-- WARNING: unhandled riscv64-linux syscall: 258\n--2463-- You may be able to write your own handler.\n--2463-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2463-- Nevertheless we consider this a bug. Please report\n--2463-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 148: failed 'http://test.org/?that=thing&key=val' --replace key=foo --- stdout --- expected: 'http://test.org/?that=thing&key=foo\n' got: 'http://test.org/?that=thing&key=foo\n' --- stderr --- expected: '' got: '--2471-- WARNING: unhandled riscv64-linux syscall: 258\n--2471-- You may be able to write your own handler.\n--2471-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2471-- Nevertheless we consider this a bug. Please report\n--2471-- it at http://valgrind.org/support/bug_reports.html.\n--2471-- WARNING: unhandled riscv64-linux syscall: 258\n--2471-- You may be able to write your own handler.\n--2471-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2471-- Nevertheless we consider this a bug. Please report\n--2471-- it at http://valgrind.org/support/bug_reports.html.\n--2471-- WARNING: unhandled riscv64-linux syscall: 258\n--2471-- You may be able to write your own handler.\n--2471-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2471-- Nevertheless we consider this a bug. Please report\n--2471-- it at http://valgrind.org/support/bug_reports.html.\n--2471-- WARNING: unhandled riscv64-linux syscall: 258\n--2471-- You may be able to write your own handler.\n--2471-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2471-- Nevertheless we consider this a bug. Please report\n--2471-- it at http://valgrind.org/support/bug_reports.html.\n--2471-- WARNING: unhandled riscv64-linux syscall: 258\n--2471-- You may be able to write your own handler.\n--2471-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2471-- Nevertheless we consider this a bug. Please report\n--2471-- it at http://valgrind.org/support/bug_reports.html.\n--2471-- WARNING: unhandled riscv64-linux syscall: 258\n--2471-- You may be able to write your own handler.\n--2471-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2471-- Nevertheless we consider this a bug. Please report\n--2471-- it at http://valgrind.org/support/bug_reports.html.\n--2471-- WARNING: unhandled riscv64-linux syscall: 258\n--2471-- You may be able to write your own handler.\n--2471-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2471-- Nevertheless we consider this a bug. Please report\n--2471-- it at http://valgrind.org/support/bug_reports.html.\n--2471-- WARNING: unhandled riscv64-linux syscall: 258\n--2471-- You may be able to write your own handler.\n--2471-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2471-- Nevertheless we consider this a bug. Please report\n--2471-- it at http://valgrind.org/support/bug_reports.html.\n--2471-- WARNING: unhandled riscv64-linux syscall: 258\n--2471-- You may be able to write your own handler.\n--2471-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2471-- Nevertheless we consider this a bug. Please report\n--2471-- it at http://valgrind.org/support/bug_reports.html.\n--2471-- WARNING: unhandled riscv64-linux syscall: 258\n--2471-- You may be able to write your own handler.\n--2471-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2471-- Nevertheless we consider this a bug. Please report\n--2471-- it at http://valgrind.org/support/bug_reports.html.\n--2471-- WARNING: unhandled riscv64-linux syscall: 258\n--2471-- You may be able to write your own handler.\n--2471-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2471-- Nevertheless we consider this a bug. Please report\n--2471-- it at http://valgrind.org/support/bug_reports.html.\n--2471-- WARNING: unhandled riscv64-linux syscall: 258\n--2471-- You may be able to write your own handler.\n--2471-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2471-- Nevertheless we consider this a bug. Please report\n--2471-- it at http://valgrind.org/support/bug_reports.html.\n--2471-- WARNING: unhandled riscv64-linux syscall: 258\n--2471-- You may be able to write your own handler.\n--2471-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2471-- Nevertheless we consider this a bug. Please report\n--2471-- it at http://valgrind.org/support/bug_reports.html.\n--2471-- WARNING: unhandled riscv64-linux syscall: 258\n--2471-- You may be able to write your own handler.\n--2471-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2471-- Nevertheless we consider this a bug. Please report\n--2471-- it at http://valgrind.org/support/bug_reports.html.\n--2471-- WARNING: unhandled riscv64-linux syscall: 258\n--2471-- You may be able to write your own handler.\n--2471-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2471-- Nevertheless we consider this a bug. Please report\n--2471-- it at http://valgrind.org/support/bug_reports.html.\n--2471-- WARNING: unhandled riscv64-linux syscall: 258\n--2471-- You may be able to write your own handler.\n--2471-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2471-- Nevertheless we consider this a bug. Please report\n--2471-- it at http://valgrind.org/support/bug_reports.html.\n--2471-- WARNING: unhandled riscv64-linux syscall: 258\n--2471-- You may be able to write your own handler.\n--2471-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2471-- Nevertheless we consider this a bug. Please report\n--2471-- it at http://valgrind.org/support/bug_reports.html.\n--2471-- WARNING: unhandled riscv64-linux syscall: 258\n--2471-- You may be able to write your own handler.\n--2471-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2471-- Nevertheless we consider this a bug. Please report\n--2471-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 149: failed 'http://test.org/?that=thing&key' --replace key=foo --- stdout --- expected: 'http://test.org/?that=thing&key=foo\n' got: 'http://test.org/?that=thing&key=foo\n' --- stderr --- expected: '' got: '--2479-- WARNING: unhandled riscv64-linux syscall: 258\n--2479-- You may be able to write your own handler.\n--2479-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2479-- Nevertheless we consider this a bug. Please report\n--2479-- it at http://valgrind.org/support/bug_reports.html.\n--2479-- WARNING: unhandled riscv64-linux syscall: 258\n--2479-- You may be able to write your own handler.\n--2479-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2479-- Nevertheless we consider this a bug. Please report\n--2479-- it at http://valgrind.org/support/bug_reports.html.\n--2479-- WARNING: unhandled riscv64-linux syscall: 258\n--2479-- You may be able to write your own handler.\n--2479-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2479-- Nevertheless we consider this a bug. Please report\n--2479-- it at http://valgrind.org/support/bug_reports.html.\n--2479-- WARNING: unhandled riscv64-linux syscall: 258\n--2479-- You may be able to write your own handler.\n--2479-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2479-- Nevertheless we consider this a bug. Please report\n--2479-- it at http://valgrind.org/support/bug_reports.html.\n--2479-- WARNING: unhandled riscv64-linux syscall: 258\n--2479-- You may be able to write your own handler.\n--2479-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2479-- Nevertheless we consider this a bug. Please report\n--2479-- it at http://valgrind.org/support/bug_reports.html.\n--2479-- WARNING: unhandled riscv64-linux syscall: 258\n--2479-- You may be able to write your own handler.\n--2479-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2479-- Nevertheless we consider this a bug. Please report\n--2479-- it at http://valgrind.org/support/bug_reports.html.\n--2479-- WARNING: unhandled riscv64-linux syscall: 258\n--2479-- You may be able to write your own handler.\n--2479-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2479-- Nevertheless we consider this a bug. Please report\n--2479-- it at http://valgrind.org/support/bug_reports.html.\n--2479-- WARNING: unhandled riscv64-linux syscall: 258\n--2479-- You may be able to write your own handler.\n--2479-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2479-- Nevertheless we consider this a bug. Please report\n--2479-- it at http://valgrind.org/support/bug_reports.html.\n--2479-- WARNING: unhandled riscv64-linux syscall: 258\n--2479-- You may be able to write your own handler.\n--2479-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2479-- Nevertheless we consider this a bug. Please report\n--2479-- it at http://valgrind.org/support/bug_reports.html.\n--2479-- WARNING: unhandled riscv64-linux syscall: 258\n--2479-- You may be able to write your own handler.\n--2479-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2479-- Nevertheless we consider this a bug. Please report\n--2479-- it at http://valgrind.org/support/bug_reports.html.\n--2479-- WARNING: unhandled riscv64-linux syscall: 258\n--2479-- You may be able to write your own handler.\n--2479-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2479-- Nevertheless we consider this a bug. Please report\n--2479-- it at http://valgrind.org/support/bug_reports.html.\n--2479-- WARNING: unhandled riscv64-linux syscall: 258\n--2479-- You may be able to write your own handler.\n--2479-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2479-- Nevertheless we consider this a bug. Please report\n--2479-- it at http://valgrind.org/support/bug_reports.html.\n--2479-- WARNING: unhandled riscv64-linux syscall: 258\n--2479-- You may be able to write your own handler.\n--2479-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2479-- Nevertheless we consider this a bug. Please report\n--2479-- it at http://valgrind.org/support/bug_reports.html.\n--2479-- WARNING: unhandled riscv64-linux syscall: 258\n--2479-- You may be able to write your own handler.\n--2479-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2479-- Nevertheless we consider this a bug. Please report\n--2479-- it at http://valgrind.org/support/bug_reports.html.\n--2479-- WARNING: unhandled riscv64-linux syscall: 258\n--2479-- You may be able to write your own handler.\n--2479-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2479-- Nevertheless we consider this a bug. Please report\n--2479-- it at http://valgrind.org/support/bug_reports.html.\n--2479-- WARNING: unhandled riscv64-linux syscall: 258\n--2479-- You may be able to write your own handler.\n--2479-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2479-- Nevertheless we consider this a bug. Please report\n--2479-- it at http://valgrind.org/support/bug_reports.html.\n--2479-- WARNING: unhandled riscv64-linux syscall: 258\n--2479-- You may be able to write your own handler.\n--2479-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2479-- Nevertheless we consider this a bug. Please report\n--2479-- it at http://valgrind.org/support/bug_reports.html.\n--2479-- WARNING: unhandled riscv64-linux syscall: 258\n--2479-- You may be able to write your own handler.\n--2479-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2479-- Nevertheless we consider this a bug. Please report\n--2479-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 150: failed 'http://test.org/?that=thing&key=foo' --replace key --- stdout --- expected: 'http://test.org/?that=thing&key\n' got: 'http://test.org/?that=thing&key\n' --- stderr --- expected: '' got: '--2487-- WARNING: unhandled riscv64-linux syscall: 258\n--2487-- You may be able to write your own handler.\n--2487-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2487-- Nevertheless we consider this a bug. Please report\n--2487-- it at http://valgrind.org/support/bug_reports.html.\n--2487-- WARNING: unhandled riscv64-linux syscall: 258\n--2487-- You may be able to write your own handler.\n--2487-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2487-- Nevertheless we consider this a bug. Please report\n--2487-- it at http://valgrind.org/support/bug_reports.html.\n--2487-- WARNING: unhandled riscv64-linux syscall: 258\n--2487-- You may be able to write your own handler.\n--2487-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2487-- Nevertheless we consider this a bug. Please report\n--2487-- it at http://valgrind.org/support/bug_reports.html.\n--2487-- WARNING: unhandled riscv64-linux syscall: 258\n--2487-- You may be able to write your own handler.\n--2487-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2487-- Nevertheless we consider this a bug. Please report\n--2487-- it at http://valgrind.org/support/bug_reports.html.\n--2487-- WARNING: unhandled riscv64-linux syscall: 258\n--2487-- You may be able to write your own handler.\n--2487-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2487-- Nevertheless we consider this a bug. Please report\n--2487-- it at http://valgrind.org/support/bug_reports.html.\n--2487-- WARNING: unhandled riscv64-linux syscall: 258\n--2487-- You may be able to write your own handler.\n--2487-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2487-- Nevertheless we consider this a bug. Please report\n--2487-- it at http://valgrind.org/support/bug_reports.html.\n--2487-- WARNING: unhandled riscv64-linux syscall: 258\n--2487-- You may be able to write your own handler.\n--2487-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2487-- Nevertheless we consider this a bug. Please report\n--2487-- it at http://valgrind.org/support/bug_reports.html.\n--2487-- WARNING: unhandled riscv64-linux syscall: 258\n--2487-- You may be able to write your own handler.\n--2487-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2487-- Nevertheless we consider this a bug. Please report\n--2487-- it at http://valgrind.org/support/bug_reports.html.\n--2487-- WARNING: unhandled riscv64-linux syscall: 258\n--2487-- You may be able to write your own handler.\n--2487-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2487-- Nevertheless we consider this a bug. Please report\n--2487-- it at http://valgrind.org/support/bug_reports.html.\n--2487-- WARNING: unhandled riscv64-linux syscall: 258\n--2487-- You may be able to write your own handler.\n--2487-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2487-- Nevertheless we consider this a bug. Please report\n--2487-- it at http://valgrind.org/support/bug_reports.html.\n--2487-- WARNING: unhandled riscv64-linux syscall: 258\n--2487-- You may be able to write your own handler.\n--2487-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2487-- Nevertheless we consider this a bug. Please report\n--2487-- it at http://valgrind.org/support/bug_reports.html.\n--2487-- WARNING: unhandled riscv64-linux syscall: 258\n--2487-- You may be able to write your own handler.\n--2487-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2487-- Nevertheless we consider this a bug. Please report\n--2487-- it at http://valgrind.org/support/bug_reports.html.\n--2487-- WARNING: unhandled riscv64-linux syscall: 258\n--2487-- You may be able to write your own handler.\n--2487-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2487-- Nevertheless we consider this a bug. Please report\n--2487-- it at http://valgrind.org/support/bug_reports.html.\n--2487-- WARNING: unhandled riscv64-linux syscall: 258\n--2487-- You may be able to write your own handler.\n--2487-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2487-- Nevertheless we consider this a bug. Please report\n--2487-- it at http://valgrind.org/support/bug_reports.html.\n--2487-- WARNING: unhandled riscv64-linux syscall: 258\n--2487-- You may be able to write your own handler.\n--2487-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2487-- Nevertheless we consider this a bug. Please report\n--2487-- it at http://valgrind.org/support/bug_reports.html.\n--2487-- WARNING: unhandled riscv64-linux syscall: 258\n--2487-- You may be able to write your own handler.\n--2487-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2487-- Nevertheless we consider this a bug. Please report\n--2487-- it at http://valgrind.org/support/bug_reports.html.\n--2487-- WARNING: unhandled riscv64-linux syscall: 258\n--2487-- You may be able to write your own handler.\n--2487-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2487-- Nevertheless we consider this a bug. Please report\n--2487-- it at http://valgrind.org/support/bug_reports.html.\n--2487-- WARNING: unhandled riscv64-linux syscall: 258\n--2487-- You may be able to write your own handler.\n--2487-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2487-- Nevertheless we consider this a bug. Please report\n--2487-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 151: failed 'https://example.com?a=123&b=321&b=987' --replace b=foo --- stdout --- expected: 'https://example.com/?a=123&b=foo\n' got: 'https://example.com/?a=123&b=foo\n' --- stderr --- expected: '' got: '--2495-- WARNING: unhandled riscv64-linux syscall: 258\n--2495-- You may be able to write your own handler.\n--2495-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2495-- Nevertheless we consider this a bug. Please report\n--2495-- it at http://valgrind.org/support/bug_reports.html.\n--2495-- WARNING: unhandled riscv64-linux syscall: 258\n--2495-- You may be able to write your own handler.\n--2495-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2495-- Nevertheless we consider this a bug. Please report\n--2495-- it at http://valgrind.org/support/bug_reports.html.\n--2495-- WARNING: unhandled riscv64-linux syscall: 258\n--2495-- You may be able to write your own handler.\n--2495-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2495-- Nevertheless we consider this a bug. Please report\n--2495-- it at http://valgrind.org/support/bug_reports.html.\n--2495-- WARNING: unhandled riscv64-linux syscall: 258\n--2495-- You may be able to write your own handler.\n--2495-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2495-- Nevertheless we consider this a bug. Please report\n--2495-- it at http://valgrind.org/support/bug_reports.html.\n--2495-- WARNING: unhandled riscv64-linux syscall: 258\n--2495-- You may be able to write your own handler.\n--2495-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2495-- Nevertheless we consider this a bug. Please report\n--2495-- it at http://valgrind.org/support/bug_reports.html.\n--2495-- WARNING: unhandled riscv64-linux syscall: 258\n--2495-- You may be able to write your own handler.\n--2495-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2495-- Nevertheless we consider this a bug. Please report\n--2495-- it at http://valgrind.org/support/bug_reports.html.\n--2495-- WARNING: unhandled riscv64-linux syscall: 258\n--2495-- You may be able to write your own handler.\n--2495-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2495-- Nevertheless we consider this a bug. Please report\n--2495-- it at http://valgrind.org/support/bug_reports.html.\n--2495-- WARNING: unhandled riscv64-linux syscall: 258\n--2495-- You may be able to write your own handler.\n--2495-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2495-- Nevertheless we consider this a bug. Please report\n--2495-- it at http://valgrind.org/support/bug_reports.html.\n--2495-- WARNING: unhandled riscv64-linux syscall: 258\n--2495-- You may be able to write your own handler.\n--2495-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2495-- Nevertheless we consider this a bug. Please report\n--2495-- it at http://valgrind.org/support/bug_reports.html.\n--2495-- WARNING: unhandled riscv64-linux syscall: 258\n--2495-- You may be able to write your own handler.\n--2495-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2495-- Nevertheless we consider this a bug. Please report\n--2495-- it at http://valgrind.org/support/bug_reports.html.\n--2495-- WARNING: unhandled riscv64-linux syscall: 258\n--2495-- You may be able to write your own handler.\n--2495-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2495-- Nevertheless we consider this a bug. Please report\n--2495-- it at http://valgrind.org/support/bug_reports.html.\n--2495-- WARNING: unhandled riscv64-linux syscall: 258\n--2495-- You may be able to write your own handler.\n--2495-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2495-- Nevertheless we consider this a bug. Please report\n--2495-- it at http://valgrind.org/support/bug_reports.html.\n--2495-- WARNING: unhandled riscv64-linux syscall: 258\n--2495-- You may be able to write your own handler.\n--2495-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2495-- Nevertheless we consider this a bug. Please report\n--2495-- it at http://valgrind.org/support/bug_reports.html.\n--2495-- WARNING: unhandled riscv64-linux syscall: 258\n--2495-- You may be able to write your own handler.\n--2495-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2495-- Nevertheless we consider this a bug. Please report\n--2495-- it at http://valgrind.org/support/bug_reports.html.\n--2495-- WARNING: unhandled riscv64-linux syscall: 258\n--2495-- You may be able to write your own handler.\n--2495-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2495-- Nevertheless we consider this a bug. Please report\n--2495-- it at http://valgrind.org/support/bug_reports.html.\n--2495-- WARNING: unhandled riscv64-linux syscall: 258\n--2495-- You may be able to write your own handler.\n--2495-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2495-- Nevertheless we consider this a bug. Please report\n--2495-- it at http://valgrind.org/support/bug_reports.html.\n--2495-- WARNING: unhandled riscv64-linux syscall: 258\n--2495-- You may be able to write your own handler.\n--2495-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2495-- Nevertheless we consider this a bug. Please report\n--2495-- it at http://valgrind.org/support/bug_reports.html.\n--2495-- WARNING: unhandled riscv64-linux syscall: 258\n--2495-- You may be able to write your own handler.\n--2495-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2495-- Nevertheless we consider this a bug. Please report\n--2495-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 152: failed 'example.org/?quest=best' --replace quest=%00 --json --urlencode --- stdout --- expected: [{'url': 'http://example.org/?quest=%2500', 'parts': {'scheme': 'http', 'host': 'example.org', 'path': '/', 'query': 'quest=%2500'}, 'params': [{'key': 'quest', 'value': '%00'}]}] got: [{'url': 'http://example.org/?quest=%2500', 'parts': {'scheme': 'http', 'host': 'example.org', 'path': '/', 'query': 'quest=%2500'}, 'params': [{'key': 'quest', 'value': '%00'}]}] --- stderr --- expected: '' got: '--2503-- WARNING: unhandled riscv64-linux syscall: 258\n--2503-- You may be able to write your own handler.\n--2503-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2503-- Nevertheless we consider this a bug. Please report\n--2503-- it at http://valgrind.org/support/bug_reports.html.\n--2503-- WARNING: unhandled riscv64-linux syscall: 258\n--2503-- You may be able to write your own handler.\n--2503-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2503-- Nevertheless we consider this a bug. Please report\n--2503-- it at http://valgrind.org/support/bug_reports.html.\n--2503-- WARNING: unhandled riscv64-linux syscall: 258\n--2503-- You may be able to write your own handler.\n--2503-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2503-- Nevertheless we consider this a bug. Please report\n--2503-- it at http://valgrind.org/support/bug_reports.html.\n--2503-- WARNING: unhandled riscv64-linux syscall: 258\n--2503-- You may be able to write your own handler.\n--2503-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2503-- Nevertheless we consider this a bug. Please report\n--2503-- it at http://valgrind.org/support/bug_reports.html.\n--2503-- WARNING: unhandled riscv64-linux syscall: 258\n--2503-- You may be able to write your own handler.\n--2503-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2503-- Nevertheless we consider this a bug. Please report\n--2503-- it at http://valgrind.org/support/bug_reports.html.\n--2503-- WARNING: unhandled riscv64-linux syscall: 258\n--2503-- You may be able to write your own handler.\n--2503-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2503-- Nevertheless we consider this a bug. Please report\n--2503-- it at http://valgrind.org/support/bug_reports.html.\n--2503-- WARNING: unhandled riscv64-linux syscall: 258\n--2503-- You may be able to write your own handler.\n--2503-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2503-- Nevertheless we consider this a bug. Please report\n--2503-- it at http://valgrind.org/support/bug_reports.html.\n--2503-- WARNING: unhandled riscv64-linux syscall: 258\n--2503-- You may be able to write your own handler.\n--2503-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2503-- Nevertheless we consider this a bug. Please report\n--2503-- it at http://valgrind.org/support/bug_reports.html.\n--2503-- WARNING: unhandled riscv64-linux syscall: 258\n--2503-- You may be able to write your own handler.\n--2503-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2503-- Nevertheless we consider this a bug. Please report\n--2503-- it at http://valgrind.org/support/bug_reports.html.\n--2503-- WARNING: unhandled riscv64-linux syscall: 258\n--2503-- You may be able to write your own handler.\n--2503-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2503-- Nevertheless we consider this a bug. Please report\n--2503-- it at http://valgrind.org/support/bug_reports.html.\n--2503-- WARNING: unhandled riscv64-linux syscall: 258\n--2503-- You may be able to write your own handler.\n--2503-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2503-- Nevertheless we consider this a bug. Please report\n--2503-- it at http://valgrind.org/support/bug_reports.html.\n--2503-- WARNING: unhandled riscv64-linux syscall: 258\n--2503-- You may be able to write your own handler.\n--2503-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2503-- Nevertheless we consider this a bug. Please report\n--2503-- it at http://valgrind.org/support/bug_reports.html.\n--2503-- WARNING: unhandled riscv64-linux syscall: 258\n--2503-- You may be able to write your own handler.\n--2503-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2503-- Nevertheless we consider this a bug. Please report\n--2503-- it at http://valgrind.org/support/bug_reports.html.\n--2503-- WARNING: unhandled riscv64-linux syscall: 258\n--2503-- You may be able to write your own handler.\n--2503-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2503-- Nevertheless we consider this a bug. Please report\n--2503-- it at http://valgrind.org/support/bug_reports.html.\n--2503-- WARNING: unhandled riscv64-linux syscall: 258\n--2503-- You may be able to write your own handler.\n--2503-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2503-- Nevertheless we consider this a bug. Please report\n--2503-- it at http://valgrind.org/support/bug_reports.html.\n--2503-- WARNING: unhandled riscv64-linux syscall: 258\n--2503-- You may be able to write your own handler.\n--2503-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2503-- Nevertheless we consider this a bug. Please report\n--2503-- it at http://valgrind.org/support/bug_reports.html.\n--2503-- WARNING: unhandled riscv64-linux syscall: 258\n--2503-- You may be able to write your own handler.\n--2503-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2503-- Nevertheless we consider this a bug. Please report\n--2503-- it at http://valgrind.org/support/bug_reports.html.\n--2503-- WARNING: unhandled riscv64-linux syscall: 258\n--2503-- You may be able to write your own handler.\n--2503-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2503-- Nevertheless we consider this a bug. Please report\n--2503-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 153: failed example.com --replace --- stderr --- expected: 'trurl error: No data passed to replace component\ntrurl error: Try trurl -h for help\n' got: '--2511-- WARNING: unhandled riscv64-linux syscall: 258\n--2511-- You may be able to write your own handler.\n--2511-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2511-- Nevertheless we consider this a bug. Please report\n--2511-- it at http://valgrind.org/support/bug_reports.html.\n--2511-- WARNING: unhandled riscv64-linux syscall: 258\n--2511-- You may be able to write your own handler.\n--2511-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2511-- Nevertheless we consider this a bug. Please report\n--2511-- it at http://valgrind.org/support/bug_reports.html.\n--2511-- WARNING: unhandled riscv64-linux syscall: 258\n--2511-- You may be able to write your own handler.\n--2511-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2511-- Nevertheless we consider this a bug. Please report\n--2511-- it at http://valgrind.org/support/bug_reports.html.\n--2511-- WARNING: unhandled riscv64-linux syscall: 258\n--2511-- You may be able to write your own handler.\n--2511-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2511-- Nevertheless we consider this a bug. Please report\n--2511-- it at http://valgrind.org/support/bug_reports.html.\n--2511-- WARNING: unhandled riscv64-linux syscall: 258\n--2511-- You may be able to write your own handler.\n--2511-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2511-- Nevertheless we consider this a bug. Please report\n--2511-- it at http://valgrind.org/support/bug_reports.html.\n--2511-- WARNING: unhandled riscv64-linux syscall: 258\n--2511-- You may be able to write your own handler.\n--2511-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2511-- Nevertheless we consider this a bug. Please report\n--2511-- it at http://valgrind.org/support/bug_reports.html.\n--2511-- WARNING: unhandled riscv64-linux syscall: 258\n--2511-- You may be able to write your own handler.\n--2511-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2511-- Nevertheless we consider this a bug. Please report\n--2511-- it at http://valgrind.org/support/bug_reports.html.\n--2511-- WARNING: unhandled riscv64-linux syscall: 258\n--2511-- You may be able to write your own handler.\n--2511-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2511-- Nevertheless we consider this a bug. Please report\n--2511-- it at http://valgrind.org/support/bug_reports.html.\n--2511-- WARNING: unhandled riscv64-linux syscall: 258\n--2511-- You may be able to write your own handler.\n--2511-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2511-- Nevertheless we consider this a bug. Please report\n--2511-- it at http://valgrind.org/support/bug_reports.html.\n--2511-- WARNING: unhandled riscv64-linux syscall: 258\n--2511-- You may be able to write your own handler.\n--2511-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2511-- Nevertheless we consider this a bug. Please report\n--2511-- it at http://valgrind.org/support/bug_reports.html.\n--2511-- WARNING: unhandled riscv64-linux syscall: 258\n--2511-- You may be able to write your own handler.\n--2511-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2511-- Nevertheless we consider this a bug. Please report\n--2511-- it at http://valgrind.org/support/bug_reports.html.\n--2511-- WARNING: unhandled riscv64-linux syscall: 258\n--2511-- You may be able to write your own handler.\n--2511-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2511-- Nevertheless we consider this a bug. Please report\n--2511-- it at http://valgrind.org/support/bug_reports.html.\n--2511-- WARNING: unhandled riscv64-linux syscall: 258\n--2511-- You may be able to write your own handler.\n--2511-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2511-- Nevertheless we consider this a bug. Please report\n--2511-- it at http://valgrind.org/support/bug_reports.html.\n--2511-- WARNING: unhandled riscv64-linux syscall: 258\n--2511-- You may be able to write your own handler.\n--2511-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2511-- Nevertheless we consider this a bug. Please report\n--2511-- it at http://valgrind.org/support/bug_reports.html.\n--2511-- WARNING: unhandled riscv64-linux syscall: 258\n--2511-- You may be able to write your own handler.\n--2511-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2511-- Nevertheless we consider this a bug. Please report\n--2511-- it at http://valgrind.org/support/bug_reports.html.\n--2511-- WARNING: unhandled riscv64-linux syscall: 258\n--2511-- You may be able to write your own handler.\n--2511-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2511-- Nevertheless we consider this a bug. Please report\n--2511-- it at http://valgrind.org/support/bug_reports.html.\n--2511-- WARNING: unhandled riscv64-linux syscall: 258\n--2511-- You may be able to write your own handler.\n--2511-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2511-- Nevertheless we consider this a bug. Please report\n--2511-- it at http://valgrind.org/support/bug_reports.html.\n--2511-- WARNING: unhandled riscv64-linux syscall: 258\n--2511-- You may be able to write your own handler.\n--2511-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2511-- Nevertheless we consider this a bug. Please report\n--2511-- it at http://valgrind.org/support/bug_reports.html.\ntrurl error: No data passed to replace component\ntrurl error: Try trurl -h for help\n' --- stdout --- expected: '' got: '' --- returncode --- expected: 12 got: 12 154: failed 'http://test.org/?that=thing' --force-replace key=foo --- stdout --- expected: 'http://test.org/?that=thing&key=foo\n' got: 'http://test.org/?that=thing&key=foo\n' --- stderr --- expected: '' got: '--2519-- WARNING: unhandled riscv64-linux syscall: 258\n--2519-- You may be able to write your own handler.\n--2519-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2519-- Nevertheless we consider this a bug. Please report\n--2519-- it at http://valgrind.org/support/bug_reports.html.\n--2519-- WARNING: unhandled riscv64-linux syscall: 258\n--2519-- You may be able to write your own handler.\n--2519-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2519-- Nevertheless we consider this a bug. Please report\n--2519-- it at http://valgrind.org/support/bug_reports.html.\n--2519-- WARNING: unhandled riscv64-linux syscall: 258\n--2519-- You may be able to write your own handler.\n--2519-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2519-- Nevertheless we consider this a bug. Please report\n--2519-- it at http://valgrind.org/support/bug_reports.html.\n--2519-- WARNING: unhandled riscv64-linux syscall: 258\n--2519-- You may be able to write your own handler.\n--2519-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2519-- Nevertheless we consider this a bug. Please report\n--2519-- it at http://valgrind.org/support/bug_reports.html.\n--2519-- WARNING: unhandled riscv64-linux syscall: 258\n--2519-- You may be able to write your own handler.\n--2519-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2519-- Nevertheless we consider this a bug. Please report\n--2519-- it at http://valgrind.org/support/bug_reports.html.\n--2519-- WARNING: unhandled riscv64-linux syscall: 258\n--2519-- You may be able to write your own handler.\n--2519-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2519-- Nevertheless we consider this a bug. Please report\n--2519-- it at http://valgrind.org/support/bug_reports.html.\n--2519-- WARNING: unhandled riscv64-linux syscall: 258\n--2519-- You may be able to write your own handler.\n--2519-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2519-- Nevertheless we consider this a bug. Please report\n--2519-- it at http://valgrind.org/support/bug_reports.html.\n--2519-- WARNING: unhandled riscv64-linux syscall: 258\n--2519-- You may be able to write your own handler.\n--2519-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2519-- Nevertheless we consider this a bug. Please report\n--2519-- it at http://valgrind.org/support/bug_reports.html.\n--2519-- WARNING: unhandled riscv64-linux syscall: 258\n--2519-- You may be able to write your own handler.\n--2519-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2519-- Nevertheless we consider this a bug. Please report\n--2519-- it at http://valgrind.org/support/bug_reports.html.\n--2519-- WARNING: unhandled riscv64-linux syscall: 258\n--2519-- You may be able to write your own handler.\n--2519-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2519-- Nevertheless we consider this a bug. Please report\n--2519-- it at http://valgrind.org/support/bug_reports.html.\n--2519-- WARNING: unhandled riscv64-linux syscall: 258\n--2519-- You may be able to write your own handler.\n--2519-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2519-- Nevertheless we consider this a bug. Please report\n--2519-- it at http://valgrind.org/support/bug_reports.html.\n--2519-- WARNING: unhandled riscv64-linux syscall: 258\n--2519-- You may be able to write your own handler.\n--2519-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2519-- Nevertheless we consider this a bug. Please report\n--2519-- it at http://valgrind.org/support/bug_reports.html.\n--2519-- WARNING: unhandled riscv64-linux syscall: 258\n--2519-- You may be able to write your own handler.\n--2519-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2519-- Nevertheless we consider this a bug. Please report\n--2519-- it at http://valgrind.org/support/bug_reports.html.\n--2519-- WARNING: unhandled riscv64-linux syscall: 258\n--2519-- You may be able to write your own handler.\n--2519-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2519-- Nevertheless we consider this a bug. Please report\n--2519-- it at http://valgrind.org/support/bug_reports.html.\n--2519-- WARNING: unhandled riscv64-linux syscall: 258\n--2519-- You may be able to write your own handler.\n--2519-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2519-- Nevertheless we consider this a bug. Please report\n--2519-- it at http://valgrind.org/support/bug_reports.html.\n--2519-- WARNING: unhandled riscv64-linux syscall: 258\n--2519-- You may be able to write your own handler.\n--2519-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2519-- Nevertheless we consider this a bug. Please report\n--2519-- it at http://valgrind.org/support/bug_reports.html.\n--2519-- WARNING: unhandled riscv64-linux syscall: 258\n--2519-- You may be able to write your own handler.\n--2519-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2519-- Nevertheless we consider this a bug. Please report\n--2519-- it at http://valgrind.org/support/bug_reports.html.\n--2519-- WARNING: unhandled riscv64-linux syscall: 258\n--2519-- You may be able to write your own handler.\n--2519-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2519-- Nevertheless we consider this a bug. Please report\n--2519-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 155: failed 'http://test.org/?that=thing' --replace-append key=foo --- stdout --- expected: 'http://test.org/?that=thing&key=foo\n' got: 'http://test.org/?that=thing&key=foo\n' --- stderr --- expected: '' got: '--2527-- WARNING: unhandled riscv64-linux syscall: 258\n--2527-- You may be able to write your own handler.\n--2527-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2527-- Nevertheless we consider this a bug. Please report\n--2527-- it at http://valgrind.org/support/bug_reports.html.\n--2527-- WARNING: unhandled riscv64-linux syscall: 258\n--2527-- You may be able to write your own handler.\n--2527-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2527-- Nevertheless we consider this a bug. Please report\n--2527-- it at http://valgrind.org/support/bug_reports.html.\n--2527-- WARNING: unhandled riscv64-linux syscall: 258\n--2527-- You may be able to write your own handler.\n--2527-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2527-- Nevertheless we consider this a bug. Please report\n--2527-- it at http://valgrind.org/support/bug_reports.html.\n--2527-- WARNING: unhandled riscv64-linux syscall: 258\n--2527-- You may be able to write your own handler.\n--2527-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2527-- Nevertheless we consider this a bug. Please report\n--2527-- it at http://valgrind.org/support/bug_reports.html.\n--2527-- WARNING: unhandled riscv64-linux syscall: 258\n--2527-- You may be able to write your own handler.\n--2527-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2527-- Nevertheless we consider this a bug. Please report\n--2527-- it at http://valgrind.org/support/bug_reports.html.\n--2527-- WARNING: unhandled riscv64-linux syscall: 258\n--2527-- You may be able to write your own handler.\n--2527-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2527-- Nevertheless we consider this a bug. Please report\n--2527-- it at http://valgrind.org/support/bug_reports.html.\n--2527-- WARNING: unhandled riscv64-linux syscall: 258\n--2527-- You may be able to write your own handler.\n--2527-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2527-- Nevertheless we consider this a bug. Please report\n--2527-- it at http://valgrind.org/support/bug_reports.html.\n--2527-- WARNING: unhandled riscv64-linux syscall: 258\n--2527-- You may be able to write your own handler.\n--2527-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2527-- Nevertheless we consider this a bug. Please report\n--2527-- it at http://valgrind.org/support/bug_reports.html.\n--2527-- WARNING: unhandled riscv64-linux syscall: 258\n--2527-- You may be able to write your own handler.\n--2527-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2527-- Nevertheless we consider this a bug. Please report\n--2527-- it at http://valgrind.org/support/bug_reports.html.\n--2527-- WARNING: unhandled riscv64-linux syscall: 258\n--2527-- You may be able to write your own handler.\n--2527-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2527-- Nevertheless we consider this a bug. Please report\n--2527-- it at http://valgrind.org/support/bug_reports.html.\n--2527-- WARNING: unhandled riscv64-linux syscall: 258\n--2527-- You may be able to write your own handler.\n--2527-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2527-- Nevertheless we consider this a bug. Please report\n--2527-- it at http://valgrind.org/support/bug_reports.html.\n--2527-- WARNING: unhandled riscv64-linux syscall: 258\n--2527-- You may be able to write your own handler.\n--2527-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2527-- Nevertheless we consider this a bug. Please report\n--2527-- it at http://valgrind.org/support/bug_reports.html.\n--2527-- WARNING: unhandled riscv64-linux syscall: 258\n--2527-- You may be able to write your own handler.\n--2527-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2527-- Nevertheless we consider this a bug. Please report\n--2527-- it at http://valgrind.org/support/bug_reports.html.\n--2527-- WARNING: unhandled riscv64-linux syscall: 258\n--2527-- You may be able to write your own handler.\n--2527-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2527-- Nevertheless we consider this a bug. Please report\n--2527-- it at http://valgrind.org/support/bug_reports.html.\n--2527-- WARNING: unhandled riscv64-linux syscall: 258\n--2527-- You may be able to write your own handler.\n--2527-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2527-- Nevertheless we consider this a bug. Please report\n--2527-- it at http://valgrind.org/support/bug_reports.html.\n--2527-- WARNING: unhandled riscv64-linux syscall: 258\n--2527-- You may be able to write your own handler.\n--2527-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2527-- Nevertheless we consider this a bug. Please report\n--2527-- it at http://valgrind.org/support/bug_reports.html.\n--2527-- WARNING: unhandled riscv64-linux syscall: 258\n--2527-- You may be able to write your own handler.\n--2527-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2527-- Nevertheless we consider this a bug. Please report\n--2527-- it at http://valgrind.org/support/bug_reports.html.\n--2527-- WARNING: unhandled riscv64-linux syscall: 258\n--2527-- You may be able to write your own handler.\n--2527-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2527-- Nevertheless we consider this a bug. Please report\n--2527-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 156: failed '0?00%000000000000000000000=0000000000' --- stdout --- expected: 'http://0.0.0.0/?00%000000000000000000000=0000000000\n' got: 'http://0.0.0.0/?00%000000000000000000000=0000000000\n' --- stderr --- expected: '' got: '--2535-- WARNING: unhandled riscv64-linux syscall: 258\n--2535-- You may be able to write your own handler.\n--2535-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2535-- Nevertheless we consider this a bug. Please report\n--2535-- it at http://valgrind.org/support/bug_reports.html.\n--2535-- WARNING: unhandled riscv64-linux syscall: 258\n--2535-- You may be able to write your own handler.\n--2535-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2535-- Nevertheless we consider this a bug. Please report\n--2535-- it at http://valgrind.org/support/bug_reports.html.\n--2535-- WARNING: unhandled riscv64-linux syscall: 258\n--2535-- You may be able to write your own handler.\n--2535-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2535-- Nevertheless we consider this a bug. Please report\n--2535-- it at http://valgrind.org/support/bug_reports.html.\n--2535-- WARNING: unhandled riscv64-linux syscall: 258\n--2535-- You may be able to write your own handler.\n--2535-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2535-- Nevertheless we consider this a bug. Please report\n--2535-- it at http://valgrind.org/support/bug_reports.html.\n--2535-- WARNING: unhandled riscv64-linux syscall: 258\n--2535-- You may be able to write your own handler.\n--2535-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2535-- Nevertheless we consider this a bug. Please report\n--2535-- it at http://valgrind.org/support/bug_reports.html.\n--2535-- WARNING: unhandled riscv64-linux syscall: 258\n--2535-- You may be able to write your own handler.\n--2535-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2535-- Nevertheless we consider this a bug. Please report\n--2535-- it at http://valgrind.org/support/bug_reports.html.\n--2535-- WARNING: unhandled riscv64-linux syscall: 258\n--2535-- You may be able to write your own handler.\n--2535-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2535-- Nevertheless we consider this a bug. Please report\n--2535-- it at http://valgrind.org/support/bug_reports.html.\n--2535-- WARNING: unhandled riscv64-linux syscall: 258\n--2535-- You may be able to write your own handler.\n--2535-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2535-- Nevertheless we consider this a bug. Please report\n--2535-- it at http://valgrind.org/support/bug_reports.html.\n--2535-- WARNING: unhandled riscv64-linux syscall: 258\n--2535-- You may be able to write your own handler.\n--2535-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2535-- Nevertheless we consider this a bug. Please report\n--2535-- it at http://valgrind.org/support/bug_reports.html.\n--2535-- WARNING: unhandled riscv64-linux syscall: 258\n--2535-- You may be able to write your own handler.\n--2535-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2535-- Nevertheless we consider this a bug. Please report\n--2535-- it at http://valgrind.org/support/bug_reports.html.\n--2535-- WARNING: unhandled riscv64-linux syscall: 258\n--2535-- You may be able to write your own handler.\n--2535-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2535-- Nevertheless we consider this a bug. Please report\n--2535-- it at http://valgrind.org/support/bug_reports.html.\n--2535-- WARNING: unhandled riscv64-linux syscall: 258\n--2535-- You may be able to write your own handler.\n--2535-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2535-- Nevertheless we consider this a bug. Please report\n--2535-- it at http://valgrind.org/support/bug_reports.html.\n--2535-- WARNING: unhandled riscv64-linux syscall: 258\n--2535-- You may be able to write your own handler.\n--2535-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2535-- Nevertheless we consider this a bug. Please report\n--2535-- it at http://valgrind.org/support/bug_reports.html.\n--2535-- WARNING: unhandled riscv64-linux syscall: 258\n--2535-- You may be able to write your own handler.\n--2535-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2535-- Nevertheless we consider this a bug. Please report\n--2535-- it at http://valgrind.org/support/bug_reports.html.\n--2535-- WARNING: unhandled riscv64-linux syscall: 258\n--2535-- You may be able to write your own handler.\n--2535-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2535-- Nevertheless we consider this a bug. Please report\n--2535-- it at http://valgrind.org/support/bug_reports.html.\n--2535-- WARNING: unhandled riscv64-linux syscall: 258\n--2535-- You may be able to write your own handler.\n--2535-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2535-- Nevertheless we consider this a bug. Please report\n--2535-- it at http://valgrind.org/support/bug_reports.html.\n--2535-- WARNING: unhandled riscv64-linux syscall: 258\n--2535-- You may be able to write your own handler.\n--2535-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2535-- Nevertheless we consider this a bug. Please report\n--2535-- it at http://valgrind.org/support/bug_reports.html.\n--2535-- WARNING: unhandled riscv64-linux syscall: 258\n--2535-- You may be able to write your own handler.\n--2535-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2535-- Nevertheless we consider this a bug. Please report\n--2535-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 157: failed --json '0?0%000000000000000000000000000000000' --urlencode --- returncode --- expected: 0 got: 0 --- stderr --- expected: '' got: '--2543-- WARNING: unhandled riscv64-linux syscall: 258\n--2543-- You may be able to write your own handler.\n--2543-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2543-- Nevertheless we consider this a bug. Please report\n--2543-- it at http://valgrind.org/support/bug_reports.html.\n--2543-- WARNING: unhandled riscv64-linux syscall: 258\n--2543-- You may be able to write your own handler.\n--2543-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2543-- Nevertheless we consider this a bug. Please report\n--2543-- it at http://valgrind.org/support/bug_reports.html.\n--2543-- WARNING: unhandled riscv64-linux syscall: 258\n--2543-- You may be able to write your own handler.\n--2543-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2543-- Nevertheless we consider this a bug. Please report\n--2543-- it at http://valgrind.org/support/bug_reports.html.\n--2543-- WARNING: unhandled riscv64-linux syscall: 258\n--2543-- You may be able to write your own handler.\n--2543-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2543-- Nevertheless we consider this a bug. Please report\n--2543-- it at http://valgrind.org/support/bug_reports.html.\n--2543-- WARNING: unhandled riscv64-linux syscall: 258\n--2543-- You may be able to write your own handler.\n--2543-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2543-- Nevertheless we consider this a bug. Please report\n--2543-- it at http://valgrind.org/support/bug_reports.html.\n--2543-- WARNING: unhandled riscv64-linux syscall: 258\n--2543-- You may be able to write your own handler.\n--2543-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2543-- Nevertheless we consider this a bug. Please report\n--2543-- it at http://valgrind.org/support/bug_reports.html.\n--2543-- WARNING: unhandled riscv64-linux syscall: 258\n--2543-- You may be able to write your own handler.\n--2543-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2543-- Nevertheless we consider this a bug. Please report\n--2543-- it at http://valgrind.org/support/bug_reports.html.\n--2543-- WARNING: unhandled riscv64-linux syscall: 258\n--2543-- You may be able to write your own handler.\n--2543-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2543-- Nevertheless we consider this a bug. Please report\n--2543-- it at http://valgrind.org/support/bug_reports.html.\n--2543-- WARNING: unhandled riscv64-linux syscall: 258\n--2543-- You may be able to write your own handler.\n--2543-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2543-- Nevertheless we consider this a bug. Please report\n--2543-- it at http://valgrind.org/support/bug_reports.html.\n--2543-- WARNING: unhandled riscv64-linux syscall: 258\n--2543-- You may be able to write your own handler.\n--2543-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2543-- Nevertheless we consider this a bug. Please report\n--2543-- it at http://valgrind.org/support/bug_reports.html.\n--2543-- WARNING: unhandled riscv64-linux syscall: 258\n--2543-- You may be able to write your own handler.\n--2543-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2543-- Nevertheless we consider this a bug. Please report\n--2543-- it at http://valgrind.org/support/bug_reports.html.\n--2543-- WARNING: unhandled riscv64-linux syscall: 258\n--2543-- You may be able to write your own handler.\n--2543-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2543-- Nevertheless we consider this a bug. Please report\n--2543-- it at http://valgrind.org/support/bug_reports.html.\n--2543-- WARNING: unhandled riscv64-linux syscall: 258\n--2543-- You may be able to write your own handler.\n--2543-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2543-- Nevertheless we consider this a bug. Please report\n--2543-- it at http://valgrind.org/support/bug_reports.html.\n--2543-- WARNING: unhandled riscv64-linux syscall: 258\n--2543-- You may be able to write your own handler.\n--2543-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2543-- Nevertheless we consider this a bug. Please report\n--2543-- it at http://valgrind.org/support/bug_reports.html.\n--2543-- WARNING: unhandled riscv64-linux syscall: 258\n--2543-- You may be able to write your own handler.\n--2543-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2543-- Nevertheless we consider this a bug. Please report\n--2543-- it at http://valgrind.org/support/bug_reports.html.\n--2543-- WARNING: unhandled riscv64-linux syscall: 258\n--2543-- You may be able to write your own handler.\n--2543-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2543-- Nevertheless we consider this a bug. Please report\n--2543-- it at http://valgrind.org/support/bug_reports.html.\n--2543-- WARNING: unhandled riscv64-linux syscall: 258\n--2543-- You may be able to write your own handler.\n--2543-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2543-- Nevertheless we consider this a bug. Please report\n--2543-- it at http://valgrind.org/support/bug_reports.html.\n--2543-- WARNING: unhandled riscv64-linux syscall: 258\n--2543-- You may be able to write your own handler.\n--2543-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2543-- Nevertheless we consider this a bug. Please report\n--2543-- it at http://valgrind.org/support/bug_reports.html.\n' --- stdout --- expected: [{'url': 'http://0.0.0.0/?0%000000000000000000000000000000000', 'parts': {'scheme': 'http', 'host': '0.0.0.0', 'path': '/', 'query': '0%000000000000000000000000000000000'}, 'params': [{'key': '0\x000000000000000000000000000000000', 'value': ''}]}] got: [{'url': 'http://0.0.0.0/?0%000000000000000000000000000000000', 'parts': {'scheme': 'http', 'host': '0.0.0.0', 'path': '/', 'query': '0%000000000000000000000000000000000'}, 'params': [{'key': '0\x000000000000000000000000000000000', 'value': ''}]}] 158: failed --json '0?0%000000000000000000000000000000000=000%0000000000' --urlencode --- returncode --- expected: 0 got: 0 --- stderr --- expected: '' got: '--2551-- WARNING: unhandled riscv64-linux syscall: 258\n--2551-- You may be able to write your own handler.\n--2551-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2551-- Nevertheless we consider this a bug. Please report\n--2551-- it at http://valgrind.org/support/bug_reports.html.\n--2551-- WARNING: unhandled riscv64-linux syscall: 258\n--2551-- You may be able to write your own handler.\n--2551-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2551-- Nevertheless we consider this a bug. Please report\n--2551-- it at http://valgrind.org/support/bug_reports.html.\n--2551-- WARNING: unhandled riscv64-linux syscall: 258\n--2551-- You may be able to write your own handler.\n--2551-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2551-- Nevertheless we consider this a bug. Please report\n--2551-- it at http://valgrind.org/support/bug_reports.html.\n--2551-- WARNING: unhandled riscv64-linux syscall: 258\n--2551-- You may be able to write your own handler.\n--2551-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2551-- Nevertheless we consider this a bug. Please report\n--2551-- it at http://valgrind.org/support/bug_reports.html.\n--2551-- WARNING: unhandled riscv64-linux syscall: 258\n--2551-- You may be able to write your own handler.\n--2551-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2551-- Nevertheless we consider this a bug. Please report\n--2551-- it at http://valgrind.org/support/bug_reports.html.\n--2551-- WARNING: unhandled riscv64-linux syscall: 258\n--2551-- You may be able to write your own handler.\n--2551-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2551-- Nevertheless we consider this a bug. Please report\n--2551-- it at http://valgrind.org/support/bug_reports.html.\n--2551-- WARNING: unhandled riscv64-linux syscall: 258\n--2551-- You may be able to write your own handler.\n--2551-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2551-- Nevertheless we consider this a bug. Please report\n--2551-- it at http://valgrind.org/support/bug_reports.html.\n--2551-- WARNING: unhandled riscv64-linux syscall: 258\n--2551-- You may be able to write your own handler.\n--2551-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2551-- Nevertheless we consider this a bug. Please report\n--2551-- it at http://valgrind.org/support/bug_reports.html.\n--2551-- WARNING: unhandled riscv64-linux syscall: 258\n--2551-- You may be able to write your own handler.\n--2551-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2551-- Nevertheless we consider this a bug. Please report\n--2551-- it at http://valgrind.org/support/bug_reports.html.\n--2551-- WARNING: unhandled riscv64-linux syscall: 258\n--2551-- You may be able to write your own handler.\n--2551-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2551-- Nevertheless we consider this a bug. Please report\n--2551-- it at http://valgrind.org/support/bug_reports.html.\n--2551-- WARNING: unhandled riscv64-linux syscall: 258\n--2551-- You may be able to write your own handler.\n--2551-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2551-- Nevertheless we consider this a bug. Please report\n--2551-- it at http://valgrind.org/support/bug_reports.html.\n--2551-- WARNING: unhandled riscv64-linux syscall: 258\n--2551-- You may be able to write your own handler.\n--2551-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2551-- Nevertheless we consider this a bug. Please report\n--2551-- it at http://valgrind.org/support/bug_reports.html.\n--2551-- WARNING: unhandled riscv64-linux syscall: 258\n--2551-- You may be able to write your own handler.\n--2551-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2551-- Nevertheless we consider this a bug. Please report\n--2551-- it at http://valgrind.org/support/bug_reports.html.\n--2551-- WARNING: unhandled riscv64-linux syscall: 258\n--2551-- You may be able to write your own handler.\n--2551-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2551-- Nevertheless we consider this a bug. Please report\n--2551-- it at http://valgrind.org/support/bug_reports.html.\n--2551-- WARNING: unhandled riscv64-linux syscall: 258\n--2551-- You may be able to write your own handler.\n--2551-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2551-- Nevertheless we consider this a bug. Please report\n--2551-- it at http://valgrind.org/support/bug_reports.html.\n--2551-- WARNING: unhandled riscv64-linux syscall: 258\n--2551-- You may be able to write your own handler.\n--2551-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2551-- Nevertheless we consider this a bug. Please report\n--2551-- it at http://valgrind.org/support/bug_reports.html.\n--2551-- WARNING: unhandled riscv64-linux syscall: 258\n--2551-- You may be able to write your own handler.\n--2551-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2551-- Nevertheless we consider this a bug. Please report\n--2551-- it at http://valgrind.org/support/bug_reports.html.\n--2551-- WARNING: unhandled riscv64-linux syscall: 258\n--2551-- You may be able to write your own handler.\n--2551-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2551-- Nevertheless we consider this a bug. Please report\n--2551-- it at http://valgrind.org/support/bug_reports.html.\n' --- stdout --- expected: [{'url': 'http://0.0.0.0/?0%000000000000000000000000000000000=000%0000000000', 'parts': {'scheme': 'http', 'host': '0.0.0.0', 'path': '/', 'query': '0%000000000000000000000000000000000=000%0000000000'}, 'params': [{'key': '0\x000000000000000000000000000000000', 'value': '000\x0000000000'}]}] got: [{'url': 'http://0.0.0.0/?0%000000000000000000000000000000000=000%0000000000', 'parts': {'scheme': 'http', 'host': '0.0.0.0', 'path': '/', 'query': '0%000000000000000000000000000000000=000%0000000000'}, 'params': [{'key': '0\x000000000000000000000000000000000', 'value': '000\x0000000000'}]}] 159: failed example.com --set 'host=[::1]' --- stdout --- expected: 'http://[::1]/\n' got: 'http://[::1]/\n' --- stderr --- expected: '' got: '--2559-- WARNING: unhandled riscv64-linux syscall: 258\n--2559-- You may be able to write your own handler.\n--2559-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2559-- Nevertheless we consider this a bug. Please report\n--2559-- it at http://valgrind.org/support/bug_reports.html.\n--2559-- WARNING: unhandled riscv64-linux syscall: 258\n--2559-- You may be able to write your own handler.\n--2559-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2559-- Nevertheless we consider this a bug. Please report\n--2559-- it at http://valgrind.org/support/bug_reports.html.\n--2559-- WARNING: unhandled riscv64-linux syscall: 258\n--2559-- You may be able to write your own handler.\n--2559-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2559-- Nevertheless we consider this a bug. Please report\n--2559-- it at http://valgrind.org/support/bug_reports.html.\n--2559-- WARNING: unhandled riscv64-linux syscall: 258\n--2559-- You may be able to write your own handler.\n--2559-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2559-- Nevertheless we consider this a bug. Please report\n--2559-- it at http://valgrind.org/support/bug_reports.html.\n--2559-- WARNING: unhandled riscv64-linux syscall: 258\n--2559-- You may be able to write your own handler.\n--2559-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2559-- Nevertheless we consider this a bug. Please report\n--2559-- it at http://valgrind.org/support/bug_reports.html.\n--2559-- WARNING: unhandled riscv64-linux syscall: 258\n--2559-- You may be able to write your own handler.\n--2559-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2559-- Nevertheless we consider this a bug. Please report\n--2559-- it at http://valgrind.org/support/bug_reports.html.\n--2559-- WARNING: unhandled riscv64-linux syscall: 258\n--2559-- You may be able to write your own handler.\n--2559-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2559-- Nevertheless we consider this a bug. Please report\n--2559-- it at http://valgrind.org/support/bug_reports.html.\n--2559-- WARNING: unhandled riscv64-linux syscall: 258\n--2559-- You may be able to write your own handler.\n--2559-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2559-- Nevertheless we consider this a bug. Please report\n--2559-- it at http://valgrind.org/support/bug_reports.html.\n--2559-- WARNING: unhandled riscv64-linux syscall: 258\n--2559-- You may be able to write your own handler.\n--2559-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2559-- Nevertheless we consider this a bug. Please report\n--2559-- it at http://valgrind.org/support/bug_reports.html.\n--2559-- WARNING: unhandled riscv64-linux syscall: 258\n--2559-- You may be able to write your own handler.\n--2559-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2559-- Nevertheless we consider this a bug. Please report\n--2559-- it at http://valgrind.org/support/bug_reports.html.\n--2559-- WARNING: unhandled riscv64-linux syscall: 258\n--2559-- You may be able to write your own handler.\n--2559-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2559-- Nevertheless we consider this a bug. Please report\n--2559-- it at http://valgrind.org/support/bug_reports.html.\n--2559-- WARNING: unhandled riscv64-linux syscall: 258\n--2559-- You may be able to write your own handler.\n--2559-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2559-- Nevertheless we consider this a bug. Please report\n--2559-- it at http://valgrind.org/support/bug_reports.html.\n--2559-- WARNING: unhandled riscv64-linux syscall: 258\n--2559-- You may be able to write your own handler.\n--2559-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2559-- Nevertheless we consider this a bug. Please report\n--2559-- it at http://valgrind.org/support/bug_reports.html.\n--2559-- WARNING: unhandled riscv64-linux syscall: 258\n--2559-- You may be able to write your own handler.\n--2559-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2559-- Nevertheless we consider this a bug. Please report\n--2559-- it at http://valgrind.org/support/bug_reports.html.\n--2559-- WARNING: unhandled riscv64-linux syscall: 258\n--2559-- You may be able to write your own handler.\n--2559-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2559-- Nevertheless we consider this a bug. Please report\n--2559-- it at http://valgrind.org/support/bug_reports.html.\n--2559-- WARNING: unhandled riscv64-linux syscall: 258\n--2559-- You may be able to write your own handler.\n--2559-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2559-- Nevertheless we consider this a bug. Please report\n--2559-- it at http://valgrind.org/support/bug_reports.html.\n--2559-- WARNING: unhandled riscv64-linux syscall: 258\n--2559-- You may be able to write your own handler.\n--2559-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2559-- Nevertheless we consider this a bug. Please report\n--2559-- it at http://valgrind.org/support/bug_reports.html.\n--2559-- WARNING: unhandled riscv64-linux syscall: 258\n--2559-- You may be able to write your own handler.\n--2559-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2559-- Nevertheless we consider this a bug. Please report\n--2559-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 160: failed example.com:88 --set 'port?=99' --- stdout --- expected: 'http://example.com:88/\n' got: 'http://example.com:88/\n' --- stderr --- expected: '' got: '--2567-- WARNING: unhandled riscv64-linux syscall: 258\n--2567-- You may be able to write your own handler.\n--2567-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2567-- Nevertheless we consider this a bug. Please report\n--2567-- it at http://valgrind.org/support/bug_reports.html.\n--2567-- WARNING: unhandled riscv64-linux syscall: 258\n--2567-- You may be able to write your own handler.\n--2567-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2567-- Nevertheless we consider this a bug. Please report\n--2567-- it at http://valgrind.org/support/bug_reports.html.\n--2567-- WARNING: unhandled riscv64-linux syscall: 258\n--2567-- You may be able to write your own handler.\n--2567-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2567-- Nevertheless we consider this a bug. Please report\n--2567-- it at http://valgrind.org/support/bug_reports.html.\n--2567-- WARNING: unhandled riscv64-linux syscall: 258\n--2567-- You may be able to write your own handler.\n--2567-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2567-- Nevertheless we consider this a bug. Please report\n--2567-- it at http://valgrind.org/support/bug_reports.html.\n--2567-- WARNING: unhandled riscv64-linux syscall: 258\n--2567-- You may be able to write your own handler.\n--2567-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2567-- Nevertheless we consider this a bug. Please report\n--2567-- it at http://valgrind.org/support/bug_reports.html.\n--2567-- WARNING: unhandled riscv64-linux syscall: 258\n--2567-- You may be able to write your own handler.\n--2567-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2567-- Nevertheless we consider this a bug. Please report\n--2567-- it at http://valgrind.org/support/bug_reports.html.\n--2567-- WARNING: unhandled riscv64-linux syscall: 258\n--2567-- You may be able to write your own handler.\n--2567-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2567-- Nevertheless we consider this a bug. Please report\n--2567-- it at http://valgrind.org/support/bug_reports.html.\n--2567-- WARNING: unhandled riscv64-linux syscall: 258\n--2567-- You may be able to write your own handler.\n--2567-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2567-- Nevertheless we consider this a bug. Please report\n--2567-- it at http://valgrind.org/support/bug_reports.html.\n--2567-- WARNING: unhandled riscv64-linux syscall: 258\n--2567-- You may be able to write your own handler.\n--2567-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2567-- Nevertheless we consider this a bug. Please report\n--2567-- it at http://valgrind.org/support/bug_reports.html.\n--2567-- WARNING: unhandled riscv64-linux syscall: 258\n--2567-- You may be able to write your own handler.\n--2567-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2567-- Nevertheless we consider this a bug. Please report\n--2567-- it at http://valgrind.org/support/bug_reports.html.\n--2567-- WARNING: unhandled riscv64-linux syscall: 258\n--2567-- You may be able to write your own handler.\n--2567-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2567-- Nevertheless we consider this a bug. Please report\n--2567-- it at http://valgrind.org/support/bug_reports.html.\n--2567-- WARNING: unhandled riscv64-linux syscall: 258\n--2567-- You may be able to write your own handler.\n--2567-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2567-- Nevertheless we consider this a bug. Please report\n--2567-- it at http://valgrind.org/support/bug_reports.html.\n--2567-- WARNING: unhandled riscv64-linux syscall: 258\n--2567-- You may be able to write your own handler.\n--2567-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2567-- Nevertheless we consider this a bug. Please report\n--2567-- it at http://valgrind.org/support/bug_reports.html.\n--2567-- WARNING: unhandled riscv64-linux syscall: 258\n--2567-- You may be able to write your own handler.\n--2567-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2567-- Nevertheless we consider this a bug. Please report\n--2567-- it at http://valgrind.org/support/bug_reports.html.\n--2567-- WARNING: unhandled riscv64-linux syscall: 258\n--2567-- You may be able to write your own handler.\n--2567-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2567-- Nevertheless we consider this a bug. Please report\n--2567-- it at http://valgrind.org/support/bug_reports.html.\n--2567-- WARNING: unhandled riscv64-linux syscall: 258\n--2567-- You may be able to write your own handler.\n--2567-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2567-- Nevertheless we consider this a bug. Please report\n--2567-- it at http://valgrind.org/support/bug_reports.html.\n--2567-- WARNING: unhandled riscv64-linux syscall: 258\n--2567-- You may be able to write your own handler.\n--2567-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2567-- Nevertheless we consider this a bug. Please report\n--2567-- it at http://valgrind.org/support/bug_reports.html.\n--2567-- WARNING: unhandled riscv64-linux syscall: 258\n--2567-- You may be able to write your own handler.\n--2567-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2567-- Nevertheless we consider this a bug. Please report\n--2567-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 161: failed example.com --set 'port?=99' --- stdout --- expected: 'http://example.com:99/\n' got: 'http://example.com:99/\n' --- stderr --- expected: '' got: '--2575-- WARNING: unhandled riscv64-linux syscall: 258\n--2575-- You may be able to write your own handler.\n--2575-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2575-- Nevertheless we consider this a bug. Please report\n--2575-- it at http://valgrind.org/support/bug_reports.html.\n--2575-- WARNING: unhandled riscv64-linux syscall: 258\n--2575-- You may be able to write your own handler.\n--2575-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2575-- Nevertheless we consider this a bug. Please report\n--2575-- it at http://valgrind.org/support/bug_reports.html.\n--2575-- WARNING: unhandled riscv64-linux syscall: 258\n--2575-- You may be able to write your own handler.\n--2575-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2575-- Nevertheless we consider this a bug. Please report\n--2575-- it at http://valgrind.org/support/bug_reports.html.\n--2575-- WARNING: unhandled riscv64-linux syscall: 258\n--2575-- You may be able to write your own handler.\n--2575-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2575-- Nevertheless we consider this a bug. Please report\n--2575-- it at http://valgrind.org/support/bug_reports.html.\n--2575-- WARNING: unhandled riscv64-linux syscall: 258\n--2575-- You may be able to write your own handler.\n--2575-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2575-- Nevertheless we consider this a bug. Please report\n--2575-- it at http://valgrind.org/support/bug_reports.html.\n--2575-- WARNING: unhandled riscv64-linux syscall: 258\n--2575-- You may be able to write your own handler.\n--2575-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2575-- Nevertheless we consider this a bug. Please report\n--2575-- it at http://valgrind.org/support/bug_reports.html.\n--2575-- WARNING: unhandled riscv64-linux syscall: 258\n--2575-- You may be able to write your own handler.\n--2575-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2575-- Nevertheless we consider this a bug. Please report\n--2575-- it at http://valgrind.org/support/bug_reports.html.\n--2575-- WARNING: unhandled riscv64-linux syscall: 258\n--2575-- You may be able to write your own handler.\n--2575-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2575-- Nevertheless we consider this a bug. Please report\n--2575-- it at http://valgrind.org/support/bug_reports.html.\n--2575-- WARNING: unhandled riscv64-linux syscall: 258\n--2575-- You may be able to write your own handler.\n--2575-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2575-- Nevertheless we consider this a bug. Please report\n--2575-- it at http://valgrind.org/support/bug_reports.html.\n--2575-- WARNING: unhandled riscv64-linux syscall: 258\n--2575-- You may be able to write your own handler.\n--2575-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2575-- Nevertheless we consider this a bug. Please report\n--2575-- it at http://valgrind.org/support/bug_reports.html.\n--2575-- WARNING: unhandled riscv64-linux syscall: 258\n--2575-- You may be able to write your own handler.\n--2575-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2575-- Nevertheless we consider this a bug. Please report\n--2575-- it at http://valgrind.org/support/bug_reports.html.\n--2575-- WARNING: unhandled riscv64-linux syscall: 258\n--2575-- You may be able to write your own handler.\n--2575-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2575-- Nevertheless we consider this a bug. Please report\n--2575-- it at http://valgrind.org/support/bug_reports.html.\n--2575-- WARNING: unhandled riscv64-linux syscall: 258\n--2575-- You may be able to write your own handler.\n--2575-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2575-- Nevertheless we consider this a bug. Please report\n--2575-- it at http://valgrind.org/support/bug_reports.html.\n--2575-- WARNING: unhandled riscv64-linux syscall: 258\n--2575-- You may be able to write your own handler.\n--2575-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2575-- Nevertheless we consider this a bug. Please report\n--2575-- it at http://valgrind.org/support/bug_reports.html.\n--2575-- WARNING: unhandled riscv64-linux syscall: 258\n--2575-- You may be able to write your own handler.\n--2575-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2575-- Nevertheless we consider this a bug. Please report\n--2575-- it at http://valgrind.org/support/bug_reports.html.\n--2575-- WARNING: unhandled riscv64-linux syscall: 258\n--2575-- You may be able to write your own handler.\n--2575-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2575-- Nevertheless we consider this a bug. Please report\n--2575-- it at http://valgrind.org/support/bug_reports.html.\n--2575-- WARNING: unhandled riscv64-linux syscall: 258\n--2575-- You may be able to write your own handler.\n--2575-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2575-- Nevertheless we consider this a bug. Please report\n--2575-- it at http://valgrind.org/support/bug_reports.html.\n--2575-- WARNING: unhandled riscv64-linux syscall: 258\n--2575-- You may be able to write your own handler.\n--2575-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2575-- Nevertheless we consider this a bug. Please report\n--2575-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 162: failed example.com --append query=add --iterate 'scheme=http ftp' --- stdout --- expected: 'http://example.com/?add\nftp://example.com/?add\n' got: 'http://example.com/?add\nftp://example.com/?add\n' --- stderr --- expected: '' got: '--2583-- WARNING: unhandled riscv64-linux syscall: 258\n--2583-- You may be able to write your own handler.\n--2583-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2583-- Nevertheless we consider this a bug. Please report\n--2583-- it at http://valgrind.org/support/bug_reports.html.\n--2583-- WARNING: unhandled riscv64-linux syscall: 258\n--2583-- You may be able to write your own handler.\n--2583-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2583-- Nevertheless we consider this a bug. Please report\n--2583-- it at http://valgrind.org/support/bug_reports.html.\n--2583-- WARNING: unhandled riscv64-linux syscall: 258\n--2583-- You may be able to write your own handler.\n--2583-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2583-- Nevertheless we consider this a bug. Please report\n--2583-- it at http://valgrind.org/support/bug_reports.html.\n--2583-- WARNING: unhandled riscv64-linux syscall: 258\n--2583-- You may be able to write your own handler.\n--2583-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2583-- Nevertheless we consider this a bug. Please report\n--2583-- it at http://valgrind.org/support/bug_reports.html.\n--2583-- WARNING: unhandled riscv64-linux syscall: 258\n--2583-- You may be able to write your own handler.\n--2583-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2583-- Nevertheless we consider this a bug. Please report\n--2583-- it at http://valgrind.org/support/bug_reports.html.\n--2583-- WARNING: unhandled riscv64-linux syscall: 258\n--2583-- You may be able to write your own handler.\n--2583-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2583-- Nevertheless we consider this a bug. Please report\n--2583-- it at http://valgrind.org/support/bug_reports.html.\n--2583-- WARNING: unhandled riscv64-linux syscall: 258\n--2583-- You may be able to write your own handler.\n--2583-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2583-- Nevertheless we consider this a bug. Please report\n--2583-- it at http://valgrind.org/support/bug_reports.html.\n--2583-- WARNING: unhandled riscv64-linux syscall: 258\n--2583-- You may be able to write your own handler.\n--2583-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2583-- Nevertheless we consider this a bug. Please report\n--2583-- it at http://valgrind.org/support/bug_reports.html.\n--2583-- WARNING: unhandled riscv64-linux syscall: 258\n--2583-- You may be able to write your own handler.\n--2583-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2583-- Nevertheless we consider this a bug. Please report\n--2583-- it at http://valgrind.org/support/bug_reports.html.\n--2583-- WARNING: unhandled riscv64-linux syscall: 258\n--2583-- You may be able to write your own handler.\n--2583-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2583-- Nevertheless we consider this a bug. Please report\n--2583-- it at http://valgrind.org/support/bug_reports.html.\n--2583-- WARNING: unhandled riscv64-linux syscall: 258\n--2583-- You may be able to write your own handler.\n--2583-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2583-- Nevertheless we consider this a bug. Please report\n--2583-- it at http://valgrind.org/support/bug_reports.html.\n--2583-- WARNING: unhandled riscv64-linux syscall: 258\n--2583-- You may be able to write your own handler.\n--2583-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2583-- Nevertheless we consider this a bug. Please report\n--2583-- it at http://valgrind.org/support/bug_reports.html.\n--2583-- WARNING: unhandled riscv64-linux syscall: 258\n--2583-- You may be able to write your own handler.\n--2583-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2583-- Nevertheless we consider this a bug. Please report\n--2583-- it at http://valgrind.org/support/bug_reports.html.\n--2583-- WARNING: unhandled riscv64-linux syscall: 258\n--2583-- You may be able to write your own handler.\n--2583-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2583-- Nevertheless we consider this a bug. Please report\n--2583-- it at http://valgrind.org/support/bug_reports.html.\n--2583-- WARNING: unhandled riscv64-linux syscall: 258\n--2583-- You may be able to write your own handler.\n--2583-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2583-- Nevertheless we consider this a bug. Please report\n--2583-- it at http://valgrind.org/support/bug_reports.html.\n--2583-- WARNING: unhandled riscv64-linux syscall: 258\n--2583-- You may be able to write your own handler.\n--2583-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2583-- Nevertheless we consider this a bug. Please report\n--2583-- it at http://valgrind.org/support/bug_reports.html.\n--2583-- WARNING: unhandled riscv64-linux syscall: 258\n--2583-- You may be able to write your own handler.\n--2583-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2583-- Nevertheless we consider this a bug. Please report\n--2583-- it at http://valgrind.org/support/bug_reports.html.\n--2583-- WARNING: unhandled riscv64-linux syscall: 258\n--2583-- You may be able to write your own handler.\n--2583-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2583-- Nevertheless we consider this a bug. Please report\n--2583-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 163: failed example.com --append path=add --iterate 'scheme=http ftp' --- stdout --- expected: 'http://example.com/add\nftp://example.com/add\n' got: 'http://example.com/add\nftp://example.com/add\n' --- stderr --- expected: '' got: '--2591-- WARNING: unhandled riscv64-linux syscall: 258\n--2591-- You may be able to write your own handler.\n--2591-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2591-- Nevertheless we consider this a bug. Please report\n--2591-- it at http://valgrind.org/support/bug_reports.html.\n--2591-- WARNING: unhandled riscv64-linux syscall: 258\n--2591-- You may be able to write your own handler.\n--2591-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2591-- Nevertheless we consider this a bug. Please report\n--2591-- it at http://valgrind.org/support/bug_reports.html.\n--2591-- WARNING: unhandled riscv64-linux syscall: 258\n--2591-- You may be able to write your own handler.\n--2591-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2591-- Nevertheless we consider this a bug. Please report\n--2591-- it at http://valgrind.org/support/bug_reports.html.\n--2591-- WARNING: unhandled riscv64-linux syscall: 258\n--2591-- You may be able to write your own handler.\n--2591-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2591-- Nevertheless we consider this a bug. Please report\n--2591-- it at http://valgrind.org/support/bug_reports.html.\n--2591-- WARNING: unhandled riscv64-linux syscall: 258\n--2591-- You may be able to write your own handler.\n--2591-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2591-- Nevertheless we consider this a bug. Please report\n--2591-- it at http://valgrind.org/support/bug_reports.html.\n--2591-- WARNING: unhandled riscv64-linux syscall: 258\n--2591-- You may be able to write your own handler.\n--2591-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2591-- Nevertheless we consider this a bug. Please report\n--2591-- it at http://valgrind.org/support/bug_reports.html.\n--2591-- WARNING: unhandled riscv64-linux syscall: 258\n--2591-- You may be able to write your own handler.\n--2591-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2591-- Nevertheless we consider this a bug. Please report\n--2591-- it at http://valgrind.org/support/bug_reports.html.\n--2591-- WARNING: unhandled riscv64-linux syscall: 258\n--2591-- You may be able to write your own handler.\n--2591-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2591-- Nevertheless we consider this a bug. Please report\n--2591-- it at http://valgrind.org/support/bug_reports.html.\n--2591-- WARNING: unhandled riscv64-linux syscall: 258\n--2591-- You may be able to write your own handler.\n--2591-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2591-- Nevertheless we consider this a bug. Please report\n--2591-- it at http://valgrind.org/support/bug_reports.html.\n--2591-- WARNING: unhandled riscv64-linux syscall: 258\n--2591-- You may be able to write your own handler.\n--2591-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2591-- Nevertheless we consider this a bug. Please report\n--2591-- it at http://valgrind.org/support/bug_reports.html.\n--2591-- WARNING: unhandled riscv64-linux syscall: 258\n--2591-- You may be able to write your own handler.\n--2591-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2591-- Nevertheless we consider this a bug. Please report\n--2591-- it at http://valgrind.org/support/bug_reports.html.\n--2591-- WARNING: unhandled riscv64-linux syscall: 258\n--2591-- You may be able to write your own handler.\n--2591-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2591-- Nevertheless we consider this a bug. Please report\n--2591-- it at http://valgrind.org/support/bug_reports.html.\n--2591-- WARNING: unhandled riscv64-linux syscall: 258\n--2591-- You may be able to write your own handler.\n--2591-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2591-- Nevertheless we consider this a bug. Please report\n--2591-- it at http://valgrind.org/support/bug_reports.html.\n--2591-- WARNING: unhandled riscv64-linux syscall: 258\n--2591-- You may be able to write your own handler.\n--2591-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2591-- Nevertheless we consider this a bug. Please report\n--2591-- it at http://valgrind.org/support/bug_reports.html.\n--2591-- WARNING: unhandled riscv64-linux syscall: 258\n--2591-- You may be able to write your own handler.\n--2591-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2591-- Nevertheless we consider this a bug. Please report\n--2591-- it at http://valgrind.org/support/bug_reports.html.\n--2591-- WARNING: unhandled riscv64-linux syscall: 258\n--2591-- You may be able to write your own handler.\n--2591-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2591-- Nevertheless we consider this a bug. Please report\n--2591-- it at http://valgrind.org/support/bug_reports.html.\n--2591-- WARNING: unhandled riscv64-linux syscall: 258\n--2591-- You may be able to write your own handler.\n--2591-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2591-- Nevertheless we consider this a bug. Please report\n--2591-- it at http://valgrind.org/support/bug_reports.html.\n--2591-- WARNING: unhandled riscv64-linux syscall: 258\n--2591-- You may be able to write your own handler.\n--2591-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2591-- Nevertheless we consider this a bug. Please report\n--2591-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 164: failed example.com --append path=add --append path=two --- stdout --- expected: 'http://example.com/add/two\n' got: 'http://example.com/add/two\n' --- stderr --- expected: '' got: '--2599-- WARNING: unhandled riscv64-linux syscall: 258\n--2599-- You may be able to write your own handler.\n--2599-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2599-- Nevertheless we consider this a bug. Please report\n--2599-- it at http://valgrind.org/support/bug_reports.html.\n--2599-- WARNING: unhandled riscv64-linux syscall: 258\n--2599-- You may be able to write your own handler.\n--2599-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2599-- Nevertheless we consider this a bug. Please report\n--2599-- it at http://valgrind.org/support/bug_reports.html.\n--2599-- WARNING: unhandled riscv64-linux syscall: 258\n--2599-- You may be able to write your own handler.\n--2599-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2599-- Nevertheless we consider this a bug. Please report\n--2599-- it at http://valgrind.org/support/bug_reports.html.\n--2599-- WARNING: unhandled riscv64-linux syscall: 258\n--2599-- You may be able to write your own handler.\n--2599-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2599-- Nevertheless we consider this a bug. Please report\n--2599-- it at http://valgrind.org/support/bug_reports.html.\n--2599-- WARNING: unhandled riscv64-linux syscall: 258\n--2599-- You may be able to write your own handler.\n--2599-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2599-- Nevertheless we consider this a bug. Please report\n--2599-- it at http://valgrind.org/support/bug_reports.html.\n--2599-- WARNING: unhandled riscv64-linux syscall: 258\n--2599-- You may be able to write your own handler.\n--2599-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2599-- Nevertheless we consider this a bug. Please report\n--2599-- it at http://valgrind.org/support/bug_reports.html.\n--2599-- WARNING: unhandled riscv64-linux syscall: 258\n--2599-- You may be able to write your own handler.\n--2599-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2599-- Nevertheless we consider this a bug. Please report\n--2599-- it at http://valgrind.org/support/bug_reports.html.\n--2599-- WARNING: unhandled riscv64-linux syscall: 258\n--2599-- You may be able to write your own handler.\n--2599-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2599-- Nevertheless we consider this a bug. Please report\n--2599-- it at http://valgrind.org/support/bug_reports.html.\n--2599-- WARNING: unhandled riscv64-linux syscall: 258\n--2599-- You may be able to write your own handler.\n--2599-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2599-- Nevertheless we consider this a bug. Please report\n--2599-- it at http://valgrind.org/support/bug_reports.html.\n--2599-- WARNING: unhandled riscv64-linux syscall: 258\n--2599-- You may be able to write your own handler.\n--2599-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2599-- Nevertheless we consider this a bug. Please report\n--2599-- it at http://valgrind.org/support/bug_reports.html.\n--2599-- WARNING: unhandled riscv64-linux syscall: 258\n--2599-- You may be able to write your own handler.\n--2599-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2599-- Nevertheless we consider this a bug. Please report\n--2599-- it at http://valgrind.org/support/bug_reports.html.\n--2599-- WARNING: unhandled riscv64-linux syscall: 258\n--2599-- You may be able to write your own handler.\n--2599-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2599-- Nevertheless we consider this a bug. Please report\n--2599-- it at http://valgrind.org/support/bug_reports.html.\n--2599-- WARNING: unhandled riscv64-linux syscall: 258\n--2599-- You may be able to write your own handler.\n--2599-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2599-- Nevertheless we consider this a bug. Please report\n--2599-- it at http://valgrind.org/support/bug_reports.html.\n--2599-- WARNING: unhandled riscv64-linux syscall: 258\n--2599-- You may be able to write your own handler.\n--2599-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2599-- Nevertheless we consider this a bug. Please report\n--2599-- it at http://valgrind.org/support/bug_reports.html.\n--2599-- WARNING: unhandled riscv64-linux syscall: 258\n--2599-- You may be able to write your own handler.\n--2599-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2599-- Nevertheless we consider this a bug. Please report\n--2599-- it at http://valgrind.org/support/bug_reports.html.\n--2599-- WARNING: unhandled riscv64-linux syscall: 258\n--2599-- You may be able to write your own handler.\n--2599-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2599-- Nevertheless we consider this a bug. Please report\n--2599-- it at http://valgrind.org/support/bug_reports.html.\n--2599-- WARNING: unhandled riscv64-linux syscall: 258\n--2599-- You may be able to write your own handler.\n--2599-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2599-- Nevertheless we consider this a bug. Please report\n--2599-- it at http://valgrind.org/support/bug_reports.html.\n--2599-- WARNING: unhandled riscv64-linux syscall: 258\n--2599-- You may be able to write your own handler.\n--2599-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2599-- Nevertheless we consider this a bug. Please report\n--2599-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 165: failed 'https://curl.se?name=mr%00smith' --get '{query}' --- stderr --- expected: 'trurl note: URL decode error, most likely because of rubbish in the input (query)\n' got: '--2607-- WARNING: unhandled riscv64-linux syscall: 258\n--2607-- You may be able to write your own handler.\n--2607-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2607-- Nevertheless we consider this a bug. Please report\n--2607-- it at http://valgrind.org/support/bug_reports.html.\n--2607-- WARNING: unhandled riscv64-linux syscall: 258\n--2607-- You may be able to write your own handler.\n--2607-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2607-- Nevertheless we consider this a bug. Please report\n--2607-- it at http://valgrind.org/support/bug_reports.html.\n--2607-- WARNING: unhandled riscv64-linux syscall: 258\n--2607-- You may be able to write your own handler.\n--2607-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2607-- Nevertheless we consider this a bug. Please report\n--2607-- it at http://valgrind.org/support/bug_reports.html.\n--2607-- WARNING: unhandled riscv64-linux syscall: 258\n--2607-- You may be able to write your own handler.\n--2607-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2607-- Nevertheless we consider this a bug. Please report\n--2607-- it at http://valgrind.org/support/bug_reports.html.\n--2607-- WARNING: unhandled riscv64-linux syscall: 258\n--2607-- You may be able to write your own handler.\n--2607-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2607-- Nevertheless we consider this a bug. Please report\n--2607-- it at http://valgrind.org/support/bug_reports.html.\n--2607-- WARNING: unhandled riscv64-linux syscall: 258\n--2607-- You may be able to write your own handler.\n--2607-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2607-- Nevertheless we consider this a bug. Please report\n--2607-- it at http://valgrind.org/support/bug_reports.html.\n--2607-- WARNING: unhandled riscv64-linux syscall: 258\n--2607-- You may be able to write your own handler.\n--2607-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2607-- Nevertheless we consider this a bug. Please report\n--2607-- it at http://valgrind.org/support/bug_reports.html.\n--2607-- WARNING: unhandled riscv64-linux syscall: 258\n--2607-- You may be able to write your own handler.\n--2607-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2607-- Nevertheless we consider this a bug. Please report\n--2607-- it at http://valgrind.org/support/bug_reports.html.\n--2607-- WARNING: unhandled riscv64-linux syscall: 258\n--2607-- You may be able to write your own handler.\n--2607-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2607-- Nevertheless we consider this a bug. Please report\n--2607-- it at http://valgrind.org/support/bug_reports.html.\n--2607-- WARNING: unhandled riscv64-linux syscall: 258\n--2607-- You may be able to write your own handler.\n--2607-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2607-- Nevertheless we consider this a bug. Please report\n--2607-- it at http://valgrind.org/support/bug_reports.html.\n--2607-- WARNING: unhandled riscv64-linux syscall: 258\n--2607-- You may be able to write your own handler.\n--2607-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2607-- Nevertheless we consider this a bug. Please report\n--2607-- it at http://valgrind.org/support/bug_reports.html.\n--2607-- WARNING: unhandled riscv64-linux syscall: 258\n--2607-- You may be able to write your own handler.\n--2607-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2607-- Nevertheless we consider this a bug. Please report\n--2607-- it at http://valgrind.org/support/bug_reports.html.\n--2607-- WARNING: unhandled riscv64-linux syscall: 258\n--2607-- You may be able to write your own handler.\n--2607-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2607-- Nevertheless we consider this a bug. Please report\n--2607-- it at http://valgrind.org/support/bug_reports.html.\n--2607-- WARNING: unhandled riscv64-linux syscall: 258\n--2607-- You may be able to write your own handler.\n--2607-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2607-- Nevertheless we consider this a bug. Please report\n--2607-- it at http://valgrind.org/support/bug_reports.html.\n--2607-- WARNING: unhandled riscv64-linux syscall: 258\n--2607-- You may be able to write your own handler.\n--2607-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2607-- Nevertheless we consider this a bug. Please report\n--2607-- it at http://valgrind.org/support/bug_reports.html.\n--2607-- WARNING: unhandled riscv64-linux syscall: 258\n--2607-- You may be able to write your own handler.\n--2607-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2607-- Nevertheless we consider this a bug. Please report\n--2607-- it at http://valgrind.org/support/bug_reports.html.\n--2607-- WARNING: unhandled riscv64-linux syscall: 258\n--2607-- You may be able to write your own handler.\n--2607-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2607-- Nevertheless we consider this a bug. Please report\n--2607-- it at http://valgrind.org/support/bug_reports.html.\n--2607-- WARNING: unhandled riscv64-linux syscall: 258\n--2607-- You may be able to write your own handler.\n--2607-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2607-- Nevertheless we consider this a bug. Please report\n--2607-- it at http://valgrind.org/support/bug_reports.html.\ntrurl note: URL decode error, most likely because of rubbish in the input (query)\n' --- returncode --- expected: 0 got: 0 --- stdout --- expected: '\n' got: '\n' 166: failed 'https://curl.se?name=mr%00smith' --get '{strict:query}' --- stderr --- expected: 'trurl error: problems URL decoding query\ntrurl error: Try trurl -h for help\n' got: '--2615-- WARNING: unhandled riscv64-linux syscall: 258\n--2615-- You may be able to write your own handler.\n--2615-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2615-- Nevertheless we consider this a bug. Please report\n--2615-- it at http://valgrind.org/support/bug_reports.html.\n--2615-- WARNING: unhandled riscv64-linux syscall: 258\n--2615-- You may be able to write your own handler.\n--2615-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2615-- Nevertheless we consider this a bug. Please report\n--2615-- it at http://valgrind.org/support/bug_reports.html.\n--2615-- WARNING: unhandled riscv64-linux syscall: 258\n--2615-- You may be able to write your own handler.\n--2615-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2615-- Nevertheless we consider this a bug. Please report\n--2615-- it at http://valgrind.org/support/bug_reports.html.\n--2615-- WARNING: unhandled riscv64-linux syscall: 258\n--2615-- You may be able to write your own handler.\n--2615-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2615-- Nevertheless we consider this a bug. Please report\n--2615-- it at http://valgrind.org/support/bug_reports.html.\n--2615-- WARNING: unhandled riscv64-linux syscall: 258\n--2615-- You may be able to write your own handler.\n--2615-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2615-- Nevertheless we consider this a bug. Please report\n--2615-- it at http://valgrind.org/support/bug_reports.html.\n--2615-- WARNING: unhandled riscv64-linux syscall: 258\n--2615-- You may be able to write your own handler.\n--2615-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2615-- Nevertheless we consider this a bug. Please report\n--2615-- it at http://valgrind.org/support/bug_reports.html.\n--2615-- WARNING: unhandled riscv64-linux syscall: 258\n--2615-- You may be able to write your own handler.\n--2615-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2615-- Nevertheless we consider this a bug. Please report\n--2615-- it at http://valgrind.org/support/bug_reports.html.\n--2615-- WARNING: unhandled riscv64-linux syscall: 258\n--2615-- You may be able to write your own handler.\n--2615-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2615-- Nevertheless we consider this a bug. Please report\n--2615-- it at http://valgrind.org/support/bug_reports.html.\n--2615-- WARNING: unhandled riscv64-linux syscall: 258\n--2615-- You may be able to write your own handler.\n--2615-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2615-- Nevertheless we consider this a bug. Please report\n--2615-- it at http://valgrind.org/support/bug_reports.html.\n--2615-- WARNING: unhandled riscv64-linux syscall: 258\n--2615-- You may be able to write your own handler.\n--2615-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2615-- Nevertheless we consider this a bug. Please report\n--2615-- it at http://valgrind.org/support/bug_reports.html.\n--2615-- WARNING: unhandled riscv64-linux syscall: 258\n--2615-- You may be able to write your own handler.\n--2615-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2615-- Nevertheless we consider this a bug. Please report\n--2615-- it at http://valgrind.org/support/bug_reports.html.\n--2615-- WARNING: unhandled riscv64-linux syscall: 258\n--2615-- You may be able to write your own handler.\n--2615-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2615-- Nevertheless we consider this a bug. Please report\n--2615-- it at http://valgrind.org/support/bug_reports.html.\n--2615-- WARNING: unhandled riscv64-linux syscall: 258\n--2615-- You may be able to write your own handler.\n--2615-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2615-- Nevertheless we consider this a bug. Please report\n--2615-- it at http://valgrind.org/support/bug_reports.html.\n--2615-- WARNING: unhandled riscv64-linux syscall: 258\n--2615-- You may be able to write your own handler.\n--2615-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2615-- Nevertheless we consider this a bug. Please report\n--2615-- it at http://valgrind.org/support/bug_reports.html.\n--2615-- WARNING: unhandled riscv64-linux syscall: 258\n--2615-- You may be able to write your own handler.\n--2615-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2615-- Nevertheless we consider this a bug. Please report\n--2615-- it at http://valgrind.org/support/bug_reports.html.\n--2615-- WARNING: unhandled riscv64-linux syscall: 258\n--2615-- You may be able to write your own handler.\n--2615-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2615-- Nevertheless we consider this a bug. Please report\n--2615-- it at http://valgrind.org/support/bug_reports.html.\n--2615-- WARNING: unhandled riscv64-linux syscall: 258\n--2615-- You may be able to write your own handler.\n--2615-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2615-- Nevertheless we consider this a bug. Please report\n--2615-- it at http://valgrind.org/support/bug_reports.html.\n--2615-- WARNING: unhandled riscv64-linux syscall: 258\n--2615-- You may be able to write your own handler.\n--2615-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2615-- Nevertheless we consider this a bug. Please report\n--2615-- it at http://valgrind.org/support/bug_reports.html.\ntrurl error: problems URL decoding query\ntrurl error: Try trurl -h for help\n' --- returncode --- expected: 10 got: 10 --- stdout --- expected: '' got: '' 167: failed example.com --set 'scheme?=https' --- stdout --- expected: 'https://example.com/\n' got: 'https://example.com/\n' --- stderr --- expected: '' got: '--2623-- WARNING: unhandled riscv64-linux syscall: 258\n--2623-- You may be able to write your own handler.\n--2623-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2623-- Nevertheless we consider this a bug. Please report\n--2623-- it at http://valgrind.org/support/bug_reports.html.\n--2623-- WARNING: unhandled riscv64-linux syscall: 258\n--2623-- You may be able to write your own handler.\n--2623-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2623-- Nevertheless we consider this a bug. Please report\n--2623-- it at http://valgrind.org/support/bug_reports.html.\n--2623-- WARNING: unhandled riscv64-linux syscall: 258\n--2623-- You may be able to write your own handler.\n--2623-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2623-- Nevertheless we consider this a bug. Please report\n--2623-- it at http://valgrind.org/support/bug_reports.html.\n--2623-- WARNING: unhandled riscv64-linux syscall: 258\n--2623-- You may be able to write your own handler.\n--2623-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2623-- Nevertheless we consider this a bug. Please report\n--2623-- it at http://valgrind.org/support/bug_reports.html.\n--2623-- WARNING: unhandled riscv64-linux syscall: 258\n--2623-- You may be able to write your own handler.\n--2623-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2623-- Nevertheless we consider this a bug. Please report\n--2623-- it at http://valgrind.org/support/bug_reports.html.\n--2623-- WARNING: unhandled riscv64-linux syscall: 258\n--2623-- You may be able to write your own handler.\n--2623-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2623-- Nevertheless we consider this a bug. Please report\n--2623-- it at http://valgrind.org/support/bug_reports.html.\n--2623-- WARNING: unhandled riscv64-linux syscall: 258\n--2623-- You may be able to write your own handler.\n--2623-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2623-- Nevertheless we consider this a bug. Please report\n--2623-- it at http://valgrind.org/support/bug_reports.html.\n--2623-- WARNING: unhandled riscv64-linux syscall: 258\n--2623-- You may be able to write your own handler.\n--2623-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2623-- Nevertheless we consider this a bug. Please report\n--2623-- it at http://valgrind.org/support/bug_reports.html.\n--2623-- WARNING: unhandled riscv64-linux syscall: 258\n--2623-- You may be able to write your own handler.\n--2623-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2623-- Nevertheless we consider this a bug. Please report\n--2623-- it at http://valgrind.org/support/bug_reports.html.\n--2623-- WARNING: unhandled riscv64-linux syscall: 258\n--2623-- You may be able to write your own handler.\n--2623-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2623-- Nevertheless we consider this a bug. Please report\n--2623-- it at http://valgrind.org/support/bug_reports.html.\n--2623-- WARNING: unhandled riscv64-linux syscall: 258\n--2623-- You may be able to write your own handler.\n--2623-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2623-- Nevertheless we consider this a bug. Please report\n--2623-- it at http://valgrind.org/support/bug_reports.html.\n--2623-- WARNING: unhandled riscv64-linux syscall: 258\n--2623-- You may be able to write your own handler.\n--2623-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2623-- Nevertheless we consider this a bug. Please report\n--2623-- it at http://valgrind.org/support/bug_reports.html.\n--2623-- WARNING: unhandled riscv64-linux syscall: 258\n--2623-- You may be able to write your own handler.\n--2623-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2623-- Nevertheless we consider this a bug. Please report\n--2623-- it at http://valgrind.org/support/bug_reports.html.\n--2623-- WARNING: unhandled riscv64-linux syscall: 258\n--2623-- You may be able to write your own handler.\n--2623-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2623-- Nevertheless we consider this a bug. Please report\n--2623-- it at http://valgrind.org/support/bug_reports.html.\n--2623-- WARNING: unhandled riscv64-linux syscall: 258\n--2623-- You may be able to write your own handler.\n--2623-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2623-- Nevertheless we consider this a bug. Please report\n--2623-- it at http://valgrind.org/support/bug_reports.html.\n--2623-- WARNING: unhandled riscv64-linux syscall: 258\n--2623-- You may be able to write your own handler.\n--2623-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2623-- Nevertheless we consider this a bug. Please report\n--2623-- it at http://valgrind.org/support/bug_reports.html.\n--2623-- WARNING: unhandled riscv64-linux syscall: 258\n--2623-- You may be able to write your own handler.\n--2623-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2623-- Nevertheless we consider this a bug. Please report\n--2623-- it at http://valgrind.org/support/bug_reports.html.\n--2623-- WARNING: unhandled riscv64-linux syscall: 258\n--2623-- You may be able to write your own handler.\n--2623-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2623-- Nevertheless we consider this a bug. Please report\n--2623-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 168: failed ftp://example.com --set 'scheme?=https' --- stdout --- expected: 'ftp://example.com/\n' got: 'ftp://example.com/\n' --- stderr --- expected: '' got: '--2631-- WARNING: unhandled riscv64-linux syscall: 258\n--2631-- You may be able to write your own handler.\n--2631-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2631-- Nevertheless we consider this a bug. Please report\n--2631-- it at http://valgrind.org/support/bug_reports.html.\n--2631-- WARNING: unhandled riscv64-linux syscall: 258\n--2631-- You may be able to write your own handler.\n--2631-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2631-- Nevertheless we consider this a bug. Please report\n--2631-- it at http://valgrind.org/support/bug_reports.html.\n--2631-- WARNING: unhandled riscv64-linux syscall: 258\n--2631-- You may be able to write your own handler.\n--2631-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2631-- Nevertheless we consider this a bug. Please report\n--2631-- it at http://valgrind.org/support/bug_reports.html.\n--2631-- WARNING: unhandled riscv64-linux syscall: 258\n--2631-- You may be able to write your own handler.\n--2631-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2631-- Nevertheless we consider this a bug. Please report\n--2631-- it at http://valgrind.org/support/bug_reports.html.\n--2631-- WARNING: unhandled riscv64-linux syscall: 258\n--2631-- You may be able to write your own handler.\n--2631-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2631-- Nevertheless we consider this a bug. Please report\n--2631-- it at http://valgrind.org/support/bug_reports.html.\n--2631-- WARNING: unhandled riscv64-linux syscall: 258\n--2631-- You may be able to write your own handler.\n--2631-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2631-- Nevertheless we consider this a bug. Please report\n--2631-- it at http://valgrind.org/support/bug_reports.html.\n--2631-- WARNING: unhandled riscv64-linux syscall: 258\n--2631-- You may be able to write your own handler.\n--2631-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2631-- Nevertheless we consider this a bug. Please report\n--2631-- it at http://valgrind.org/support/bug_reports.html.\n--2631-- WARNING: unhandled riscv64-linux syscall: 258\n--2631-- You may be able to write your own handler.\n--2631-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2631-- Nevertheless we consider this a bug. Please report\n--2631-- it at http://valgrind.org/support/bug_reports.html.\n--2631-- WARNING: unhandled riscv64-linux syscall: 258\n--2631-- You may be able to write your own handler.\n--2631-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2631-- Nevertheless we consider this a bug. Please report\n--2631-- it at http://valgrind.org/support/bug_reports.html.\n--2631-- WARNING: unhandled riscv64-linux syscall: 258\n--2631-- You may be able to write your own handler.\n--2631-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2631-- Nevertheless we consider this a bug. Please report\n--2631-- it at http://valgrind.org/support/bug_reports.html.\n--2631-- WARNING: unhandled riscv64-linux syscall: 258\n--2631-- You may be able to write your own handler.\n--2631-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2631-- Nevertheless we consider this a bug. Please report\n--2631-- it at http://valgrind.org/support/bug_reports.html.\n--2631-- WARNING: unhandled riscv64-linux syscall: 258\n--2631-- You may be able to write your own handler.\n--2631-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2631-- Nevertheless we consider this a bug. Please report\n--2631-- it at http://valgrind.org/support/bug_reports.html.\n--2631-- WARNING: unhandled riscv64-linux syscall: 258\n--2631-- You may be able to write your own handler.\n--2631-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2631-- Nevertheless we consider this a bug. Please report\n--2631-- it at http://valgrind.org/support/bug_reports.html.\n--2631-- WARNING: unhandled riscv64-linux syscall: 258\n--2631-- You may be able to write your own handler.\n--2631-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2631-- Nevertheless we consider this a bug. Please report\n--2631-- it at http://valgrind.org/support/bug_reports.html.\n--2631-- WARNING: unhandled riscv64-linux syscall: 258\n--2631-- You may be able to write your own handler.\n--2631-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2631-- Nevertheless we consider this a bug. Please report\n--2631-- it at http://valgrind.org/support/bug_reports.html.\n--2631-- WARNING: unhandled riscv64-linux syscall: 258\n--2631-- You may be able to write your own handler.\n--2631-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2631-- Nevertheless we consider this a bug. Please report\n--2631-- it at http://valgrind.org/support/bug_reports.html.\n--2631-- WARNING: unhandled riscv64-linux syscall: 258\n--2631-- You may be able to write your own handler.\n--2631-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2631-- Nevertheless we consider this a bug. Please report\n--2631-- it at http://valgrind.org/support/bug_reports.html.\n--2631-- WARNING: unhandled riscv64-linux syscall: 258\n--2631-- You may be able to write your own handler.\n--2631-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2631-- Nevertheless we consider this a bug. Please report\n--2631-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 169: failed http://example.org/%18 --json --- stdout --- expected: [{'url': 'http://example.org/%18', 'parts': {'scheme': 'http', 'host': 'example.org', 'path': '/\x18'}}] got: [{'url': 'http://example.org/%18', 'parts': {'scheme': 'http', 'host': 'example.org', 'path': '/\x18'}}] --- stderr --- expected: '' got: '--2639-- WARNING: unhandled riscv64-linux syscall: 258\n--2639-- You may be able to write your own handler.\n--2639-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2639-- Nevertheless we consider this a bug. Please report\n--2639-- it at http://valgrind.org/support/bug_reports.html.\n--2639-- WARNING: unhandled riscv64-linux syscall: 258\n--2639-- You may be able to write your own handler.\n--2639-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2639-- Nevertheless we consider this a bug. Please report\n--2639-- it at http://valgrind.org/support/bug_reports.html.\n--2639-- WARNING: unhandled riscv64-linux syscall: 258\n--2639-- You may be able to write your own handler.\n--2639-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2639-- Nevertheless we consider this a bug. Please report\n--2639-- it at http://valgrind.org/support/bug_reports.html.\n--2639-- WARNING: unhandled riscv64-linux syscall: 258\n--2639-- You may be able to write your own handler.\n--2639-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2639-- Nevertheless we consider this a bug. Please report\n--2639-- it at http://valgrind.org/support/bug_reports.html.\n--2639-- WARNING: unhandled riscv64-linux syscall: 258\n--2639-- You may be able to write your own handler.\n--2639-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2639-- Nevertheless we consider this a bug. Please report\n--2639-- it at http://valgrind.org/support/bug_reports.html.\n--2639-- WARNING: unhandled riscv64-linux syscall: 258\n--2639-- You may be able to write your own handler.\n--2639-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2639-- Nevertheless we consider this a bug. Please report\n--2639-- it at http://valgrind.org/support/bug_reports.html.\n--2639-- WARNING: unhandled riscv64-linux syscall: 258\n--2639-- You may be able to write your own handler.\n--2639-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2639-- Nevertheless we consider this a bug. Please report\n--2639-- it at http://valgrind.org/support/bug_reports.html.\n--2639-- WARNING: unhandled riscv64-linux syscall: 258\n--2639-- You may be able to write your own handler.\n--2639-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2639-- Nevertheless we consider this a bug. Please report\n--2639-- it at http://valgrind.org/support/bug_reports.html.\n--2639-- WARNING: unhandled riscv64-linux syscall: 258\n--2639-- You may be able to write your own handler.\n--2639-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2639-- Nevertheless we consider this a bug. Please report\n--2639-- it at http://valgrind.org/support/bug_reports.html.\n--2639-- WARNING: unhandled riscv64-linux syscall: 258\n--2639-- You may be able to write your own handler.\n--2639-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2639-- Nevertheless we consider this a bug. Please report\n--2639-- it at http://valgrind.org/support/bug_reports.html.\n--2639-- WARNING: unhandled riscv64-linux syscall: 258\n--2639-- You may be able to write your own handler.\n--2639-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2639-- Nevertheless we consider this a bug. Please report\n--2639-- it at http://valgrind.org/support/bug_reports.html.\n--2639-- WARNING: unhandled riscv64-linux syscall: 258\n--2639-- You may be able to write your own handler.\n--2639-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2639-- Nevertheless we consider this a bug. Please report\n--2639-- it at http://valgrind.org/support/bug_reports.html.\n--2639-- WARNING: unhandled riscv64-linux syscall: 258\n--2639-- You may be able to write your own handler.\n--2639-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2639-- Nevertheless we consider this a bug. Please report\n--2639-- it at http://valgrind.org/support/bug_reports.html.\n--2639-- WARNING: unhandled riscv64-linux syscall: 258\n--2639-- You may be able to write your own handler.\n--2639-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2639-- Nevertheless we consider this a bug. Please report\n--2639-- it at http://valgrind.org/support/bug_reports.html.\n--2639-- WARNING: unhandled riscv64-linux syscall: 258\n--2639-- You may be able to write your own handler.\n--2639-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2639-- Nevertheless we consider this a bug. Please report\n--2639-- it at http://valgrind.org/support/bug_reports.html.\n--2639-- WARNING: unhandled riscv64-linux syscall: 258\n--2639-- You may be able to write your own handler.\n--2639-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2639-- Nevertheless we consider this a bug. Please report\n--2639-- it at http://valgrind.org/support/bug_reports.html.\n--2639-- WARNING: unhandled riscv64-linux syscall: 258\n--2639-- You may be able to write your own handler.\n--2639-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2639-- Nevertheless we consider this a bug. Please report\n--2639-- it at http://valgrind.org/support/bug_reports.html.\n--2639-- WARNING: unhandled riscv64-linux syscall: 258\n--2639-- You may be able to write your own handler.\n--2639-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2639-- Nevertheless we consider this a bug. Please report\n--2639-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 170: failed http://example.org/%18 --json --urlencode --- stdout --- expected: [{'url': 'http://example.org/%18', 'parts': {'scheme': 'http', 'host': 'example.org', 'path': '/%18'}}] got: [{'url': 'http://example.org/%18', 'parts': {'scheme': 'http', 'host': 'example.org', 'path': '/%18'}}] --- stderr --- expected: '' got: '--2647-- WARNING: unhandled riscv64-linux syscall: 258\n--2647-- You may be able to write your own handler.\n--2647-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2647-- Nevertheless we consider this a bug. Please report\n--2647-- it at http://valgrind.org/support/bug_reports.html.\n--2647-- WARNING: unhandled riscv64-linux syscall: 258\n--2647-- You may be able to write your own handler.\n--2647-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2647-- Nevertheless we consider this a bug. Please report\n--2647-- it at http://valgrind.org/support/bug_reports.html.\n--2647-- WARNING: unhandled riscv64-linux syscall: 258\n--2647-- You may be able to write your own handler.\n--2647-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2647-- Nevertheless we consider this a bug. Please report\n--2647-- it at http://valgrind.org/support/bug_reports.html.\n--2647-- WARNING: unhandled riscv64-linux syscall: 258\n--2647-- You may be able to write your own handler.\n--2647-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2647-- Nevertheless we consider this a bug. Please report\n--2647-- it at http://valgrind.org/support/bug_reports.html.\n--2647-- WARNING: unhandled riscv64-linux syscall: 258\n--2647-- You may be able to write your own handler.\n--2647-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2647-- Nevertheless we consider this a bug. Please report\n--2647-- it at http://valgrind.org/support/bug_reports.html.\n--2647-- WARNING: unhandled riscv64-linux syscall: 258\n--2647-- You may be able to write your own handler.\n--2647-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2647-- Nevertheless we consider this a bug. Please report\n--2647-- it at http://valgrind.org/support/bug_reports.html.\n--2647-- WARNING: unhandled riscv64-linux syscall: 258\n--2647-- You may be able to write your own handler.\n--2647-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2647-- Nevertheless we consider this a bug. Please report\n--2647-- it at http://valgrind.org/support/bug_reports.html.\n--2647-- WARNING: unhandled riscv64-linux syscall: 258\n--2647-- You may be able to write your own handler.\n--2647-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2647-- Nevertheless we consider this a bug. Please report\n--2647-- it at http://valgrind.org/support/bug_reports.html.\n--2647-- WARNING: unhandled riscv64-linux syscall: 258\n--2647-- You may be able to write your own handler.\n--2647-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2647-- Nevertheless we consider this a bug. Please report\n--2647-- it at http://valgrind.org/support/bug_reports.html.\n--2647-- WARNING: unhandled riscv64-linux syscall: 258\n--2647-- You may be able to write your own handler.\n--2647-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2647-- Nevertheless we consider this a bug. Please report\n--2647-- it at http://valgrind.org/support/bug_reports.html.\n--2647-- WARNING: unhandled riscv64-linux syscall: 258\n--2647-- You may be able to write your own handler.\n--2647-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2647-- Nevertheless we consider this a bug. Please report\n--2647-- it at http://valgrind.org/support/bug_reports.html.\n--2647-- WARNING: unhandled riscv64-linux syscall: 258\n--2647-- You may be able to write your own handler.\n--2647-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2647-- Nevertheless we consider this a bug. Please report\n--2647-- it at http://valgrind.org/support/bug_reports.html.\n--2647-- WARNING: unhandled riscv64-linux syscall: 258\n--2647-- You may be able to write your own handler.\n--2647-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2647-- Nevertheless we consider this a bug. Please report\n--2647-- it at http://valgrind.org/support/bug_reports.html.\n--2647-- WARNING: unhandled riscv64-linux syscall: 258\n--2647-- You may be able to write your own handler.\n--2647-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2647-- Nevertheless we consider this a bug. Please report\n--2647-- it at http://valgrind.org/support/bug_reports.html.\n--2647-- WARNING: unhandled riscv64-linux syscall: 258\n--2647-- You may be able to write your own handler.\n--2647-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2647-- Nevertheless we consider this a bug. Please report\n--2647-- it at http://valgrind.org/support/bug_reports.html.\n--2647-- WARNING: unhandled riscv64-linux syscall: 258\n--2647-- You may be able to write your own handler.\n--2647-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2647-- Nevertheless we consider this a bug. Please report\n--2647-- it at http://valgrind.org/support/bug_reports.html.\n--2647-- WARNING: unhandled riscv64-linux syscall: 258\n--2647-- You may be able to write your own handler.\n--2647-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2647-- Nevertheless we consider this a bug. Please report\n--2647-- it at http://valgrind.org/support/bug_reports.html.\n--2647-- WARNING: unhandled riscv64-linux syscall: 258\n--2647-- You may be able to write your own handler.\n--2647-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2647-- Nevertheless we consider this a bug. Please report\n--2647-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 171: failed https://example.com/one/t%61o/%2F%42/ --- stdout --- expected: 'https://example.com/one/tao/%2fB/\n' got: 'https://example.com/one/tao/%2fB/\n' --- stderr --- expected: '' got: '--2655-- WARNING: unhandled riscv64-linux syscall: 258\n--2655-- You may be able to write your own handler.\n--2655-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2655-- Nevertheless we consider this a bug. Please report\n--2655-- it at http://valgrind.org/support/bug_reports.html.\n--2655-- WARNING: unhandled riscv64-linux syscall: 258\n--2655-- You may be able to write your own handler.\n--2655-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2655-- Nevertheless we consider this a bug. Please report\n--2655-- it at http://valgrind.org/support/bug_reports.html.\n--2655-- WARNING: unhandled riscv64-linux syscall: 258\n--2655-- You may be able to write your own handler.\n--2655-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2655-- Nevertheless we consider this a bug. Please report\n--2655-- it at http://valgrind.org/support/bug_reports.html.\n--2655-- WARNING: unhandled riscv64-linux syscall: 258\n--2655-- You may be able to write your own handler.\n--2655-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2655-- Nevertheless we consider this a bug. Please report\n--2655-- it at http://valgrind.org/support/bug_reports.html.\n--2655-- WARNING: unhandled riscv64-linux syscall: 258\n--2655-- You may be able to write your own handler.\n--2655-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2655-- Nevertheless we consider this a bug. Please report\n--2655-- it at http://valgrind.org/support/bug_reports.html.\n--2655-- WARNING: unhandled riscv64-linux syscall: 258\n--2655-- You may be able to write your own handler.\n--2655-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2655-- Nevertheless we consider this a bug. Please report\n--2655-- it at http://valgrind.org/support/bug_reports.html.\n--2655-- WARNING: unhandled riscv64-linux syscall: 258\n--2655-- You may be able to write your own handler.\n--2655-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2655-- Nevertheless we consider this a bug. Please report\n--2655-- it at http://valgrind.org/support/bug_reports.html.\n--2655-- WARNING: unhandled riscv64-linux syscall: 258\n--2655-- You may be able to write your own handler.\n--2655-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2655-- Nevertheless we consider this a bug. Please report\n--2655-- it at http://valgrind.org/support/bug_reports.html.\n--2655-- WARNING: unhandled riscv64-linux syscall: 258\n--2655-- You may be able to write your own handler.\n--2655-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2655-- Nevertheless we consider this a bug. Please report\n--2655-- it at http://valgrind.org/support/bug_reports.html.\n--2655-- WARNING: unhandled riscv64-linux syscall: 258\n--2655-- You may be able to write your own handler.\n--2655-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2655-- Nevertheless we consider this a bug. Please report\n--2655-- it at http://valgrind.org/support/bug_reports.html.\n--2655-- WARNING: unhandled riscv64-linux syscall: 258\n--2655-- You may be able to write your own handler.\n--2655-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2655-- Nevertheless we consider this a bug. Please report\n--2655-- it at http://valgrind.org/support/bug_reports.html.\n--2655-- WARNING: unhandled riscv64-linux syscall: 258\n--2655-- You may be able to write your own handler.\n--2655-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2655-- Nevertheless we consider this a bug. Please report\n--2655-- it at http://valgrind.org/support/bug_reports.html.\n--2655-- WARNING: unhandled riscv64-linux syscall: 258\n--2655-- You may be able to write your own handler.\n--2655-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2655-- Nevertheless we consider this a bug. Please report\n--2655-- it at http://valgrind.org/support/bug_reports.html.\n--2655-- WARNING: unhandled riscv64-linux syscall: 258\n--2655-- You may be able to write your own handler.\n--2655-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2655-- Nevertheless we consider this a bug. Please report\n--2655-- it at http://valgrind.org/support/bug_reports.html.\n--2655-- WARNING: unhandled riscv64-linux syscall: 258\n--2655-- You may be able to write your own handler.\n--2655-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2655-- Nevertheless we consider this a bug. Please report\n--2655-- it at http://valgrind.org/support/bug_reports.html.\n--2655-- WARNING: unhandled riscv64-linux syscall: 258\n--2655-- You may be able to write your own handler.\n--2655-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2655-- Nevertheless we consider this a bug. Please report\n--2655-- it at http://valgrind.org/support/bug_reports.html.\n--2655-- WARNING: unhandled riscv64-linux syscall: 258\n--2655-- You may be able to write your own handler.\n--2655-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2655-- Nevertheless we consider this a bug. Please report\n--2655-- it at http://valgrind.org/support/bug_reports.html.\n--2655-- WARNING: unhandled riscv64-linux syscall: 258\n--2655-- You may be able to write your own handler.\n--2655-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2655-- Nevertheless we consider this a bug. Please report\n--2655-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 172: failed https://example.com/one/t%61o/%2F%42/ --append path=%61 --- stdout --- expected: 'https://example.com/one/tao/%2fB/%2561\n' got: 'https://example.com/one/tao/%2fB/%2561\n' --- stderr --- expected: '' got: '--2663-- WARNING: unhandled riscv64-linux syscall: 258\n--2663-- You may be able to write your own handler.\n--2663-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2663-- Nevertheless we consider this a bug. Please report\n--2663-- it at http://valgrind.org/support/bug_reports.html.\n--2663-- WARNING: unhandled riscv64-linux syscall: 258\n--2663-- You may be able to write your own handler.\n--2663-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2663-- Nevertheless we consider this a bug. Please report\n--2663-- it at http://valgrind.org/support/bug_reports.html.\n--2663-- WARNING: unhandled riscv64-linux syscall: 258\n--2663-- You may be able to write your own handler.\n--2663-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2663-- Nevertheless we consider this a bug. Please report\n--2663-- it at http://valgrind.org/support/bug_reports.html.\n--2663-- WARNING: unhandled riscv64-linux syscall: 258\n--2663-- You may be able to write your own handler.\n--2663-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2663-- Nevertheless we consider this a bug. Please report\n--2663-- it at http://valgrind.org/support/bug_reports.html.\n--2663-- WARNING: unhandled riscv64-linux syscall: 258\n--2663-- You may be able to write your own handler.\n--2663-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2663-- Nevertheless we consider this a bug. Please report\n--2663-- it at http://valgrind.org/support/bug_reports.html.\n--2663-- WARNING: unhandled riscv64-linux syscall: 258\n--2663-- You may be able to write your own handler.\n--2663-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2663-- Nevertheless we consider this a bug. Please report\n--2663-- it at http://valgrind.org/support/bug_reports.html.\n--2663-- WARNING: unhandled riscv64-linux syscall: 258\n--2663-- You may be able to write your own handler.\n--2663-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2663-- Nevertheless we consider this a bug. Please report\n--2663-- it at http://valgrind.org/support/bug_reports.html.\n--2663-- WARNING: unhandled riscv64-linux syscall: 258\n--2663-- You may be able to write your own handler.\n--2663-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2663-- Nevertheless we consider this a bug. Please report\n--2663-- it at http://valgrind.org/support/bug_reports.html.\n--2663-- WARNING: unhandled riscv64-linux syscall: 258\n--2663-- You may be able to write your own handler.\n--2663-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2663-- Nevertheless we consider this a bug. Please report\n--2663-- it at http://valgrind.org/support/bug_reports.html.\n--2663-- WARNING: unhandled riscv64-linux syscall: 258\n--2663-- You may be able to write your own handler.\n--2663-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2663-- Nevertheless we consider this a bug. Please report\n--2663-- it at http://valgrind.org/support/bug_reports.html.\n--2663-- WARNING: unhandled riscv64-linux syscall: 258\n--2663-- You may be able to write your own handler.\n--2663-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2663-- Nevertheless we consider this a bug. Please report\n--2663-- it at http://valgrind.org/support/bug_reports.html.\n--2663-- WARNING: unhandled riscv64-linux syscall: 258\n--2663-- You may be able to write your own handler.\n--2663-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2663-- Nevertheless we consider this a bug. Please report\n--2663-- it at http://valgrind.org/support/bug_reports.html.\n--2663-- WARNING: unhandled riscv64-linux syscall: 258\n--2663-- You may be able to write your own handler.\n--2663-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2663-- Nevertheless we consider this a bug. Please report\n--2663-- it at http://valgrind.org/support/bug_reports.html.\n--2663-- WARNING: unhandled riscv64-linux syscall: 258\n--2663-- You may be able to write your own handler.\n--2663-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2663-- Nevertheless we consider this a bug. Please report\n--2663-- it at http://valgrind.org/support/bug_reports.html.\n--2663-- WARNING: unhandled riscv64-linux syscall: 258\n--2663-- You may be able to write your own handler.\n--2663-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2663-- Nevertheless we consider this a bug. Please report\n--2663-- it at http://valgrind.org/support/bug_reports.html.\n--2663-- WARNING: unhandled riscv64-linux syscall: 258\n--2663-- You may be able to write your own handler.\n--2663-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2663-- Nevertheless we consider this a bug. Please report\n--2663-- it at http://valgrind.org/support/bug_reports.html.\n--2663-- WARNING: unhandled riscv64-linux syscall: 258\n--2663-- You may be able to write your own handler.\n--2663-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2663-- Nevertheless we consider this a bug. Please report\n--2663-- it at http://valgrind.org/support/bug_reports.html.\n--2663-- WARNING: unhandled riscv64-linux syscall: 258\n--2663-- You may be able to write your own handler.\n--2663-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2663-- Nevertheless we consider this a bug. Please report\n--2663-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 173: failed 'https://ex%61mple.com/h%61s/?wh%61t' --- stdout --- expected: 'https://example.com/has/?what\n' got: 'https://example.com/has/?what\n' --- stderr --- expected: '' got: '--2671-- WARNING: unhandled riscv64-linux syscall: 258\n--2671-- You may be able to write your own handler.\n--2671-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2671-- Nevertheless we consider this a bug. Please report\n--2671-- it at http://valgrind.org/support/bug_reports.html.\n--2671-- WARNING: unhandled riscv64-linux syscall: 258\n--2671-- You may be able to write your own handler.\n--2671-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2671-- Nevertheless we consider this a bug. Please report\n--2671-- it at http://valgrind.org/support/bug_reports.html.\n--2671-- WARNING: unhandled riscv64-linux syscall: 258\n--2671-- You may be able to write your own handler.\n--2671-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2671-- Nevertheless we consider this a bug. Please report\n--2671-- it at http://valgrind.org/support/bug_reports.html.\n--2671-- WARNING: unhandled riscv64-linux syscall: 258\n--2671-- You may be able to write your own handler.\n--2671-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2671-- Nevertheless we consider this a bug. Please report\n--2671-- it at http://valgrind.org/support/bug_reports.html.\n--2671-- WARNING: unhandled riscv64-linux syscall: 258\n--2671-- You may be able to write your own handler.\n--2671-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2671-- Nevertheless we consider this a bug. Please report\n--2671-- it at http://valgrind.org/support/bug_reports.html.\n--2671-- WARNING: unhandled riscv64-linux syscall: 258\n--2671-- You may be able to write your own handler.\n--2671-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2671-- Nevertheless we consider this a bug. Please report\n--2671-- it at http://valgrind.org/support/bug_reports.html.\n--2671-- WARNING: unhandled riscv64-linux syscall: 258\n--2671-- You may be able to write your own handler.\n--2671-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2671-- Nevertheless we consider this a bug. Please report\n--2671-- it at http://valgrind.org/support/bug_reports.html.\n--2671-- WARNING: unhandled riscv64-linux syscall: 258\n--2671-- You may be able to write your own handler.\n--2671-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2671-- Nevertheless we consider this a bug. Please report\n--2671-- it at http://valgrind.org/support/bug_reports.html.\n--2671-- WARNING: unhandled riscv64-linux syscall: 258\n--2671-- You may be able to write your own handler.\n--2671-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2671-- Nevertheless we consider this a bug. Please report\n--2671-- it at http://valgrind.org/support/bug_reports.html.\n--2671-- WARNING: unhandled riscv64-linux syscall: 258\n--2671-- You may be able to write your own handler.\n--2671-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2671-- Nevertheless we consider this a bug. Please report\n--2671-- it at http://valgrind.org/support/bug_reports.html.\n--2671-- WARNING: unhandled riscv64-linux syscall: 258\n--2671-- You may be able to write your own handler.\n--2671-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2671-- Nevertheless we consider this a bug. Please report\n--2671-- it at http://valgrind.org/support/bug_reports.html.\n--2671-- WARNING: unhandled riscv64-linux syscall: 258\n--2671-- You may be able to write your own handler.\n--2671-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2671-- Nevertheless we consider this a bug. Please report\n--2671-- it at http://valgrind.org/support/bug_reports.html.\n--2671-- WARNING: unhandled riscv64-linux syscall: 258\n--2671-- You may be able to write your own handler.\n--2671-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2671-- Nevertheless we consider this a bug. Please report\n--2671-- it at http://valgrind.org/support/bug_reports.html.\n--2671-- WARNING: unhandled riscv64-linux syscall: 258\n--2671-- You may be able to write your own handler.\n--2671-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2671-- Nevertheless we consider this a bug. Please report\n--2671-- it at http://valgrind.org/support/bug_reports.html.\n--2671-- WARNING: unhandled riscv64-linux syscall: 258\n--2671-- You may be able to write your own handler.\n--2671-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2671-- Nevertheless we consider this a bug. Please report\n--2671-- it at http://valgrind.org/support/bug_reports.html.\n--2671-- WARNING: unhandled riscv64-linux syscall: 258\n--2671-- You may be able to write your own handler.\n--2671-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2671-- Nevertheless we consider this a bug. Please report\n--2671-- it at http://valgrind.org/support/bug_reports.html.\n--2671-- WARNING: unhandled riscv64-linux syscall: 258\n--2671-- You may be able to write your own handler.\n--2671-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2671-- Nevertheless we consider this a bug. Please report\n--2671-- it at http://valgrind.org/support/bug_reports.html.\n--2671-- WARNING: unhandled riscv64-linux syscall: 258\n--2671-- You may be able to write your own handler.\n--2671-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2671-- Nevertheless we consider this a bug. Please report\n--2671-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 174: failed https://example.com/ --get '{must:query}' --- stdout --- expected: '' got: '' --- stderr --- expected: 'trurl error: missing must:query\ntrurl error: Try trurl -h for help\n' got: '--2679-- WARNING: unhandled riscv64-linux syscall: 258\n--2679-- You may be able to write your own handler.\n--2679-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2679-- Nevertheless we consider this a bug. Please report\n--2679-- it at http://valgrind.org/support/bug_reports.html.\n--2679-- WARNING: unhandled riscv64-linux syscall: 258\n--2679-- You may be able to write your own handler.\n--2679-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2679-- Nevertheless we consider this a bug. Please report\n--2679-- it at http://valgrind.org/support/bug_reports.html.\n--2679-- WARNING: unhandled riscv64-linux syscall: 258\n--2679-- You may be able to write your own handler.\n--2679-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2679-- Nevertheless we consider this a bug. Please report\n--2679-- it at http://valgrind.org/support/bug_reports.html.\n--2679-- WARNING: unhandled riscv64-linux syscall: 258\n--2679-- You may be able to write your own handler.\n--2679-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2679-- Nevertheless we consider this a bug. Please report\n--2679-- it at http://valgrind.org/support/bug_reports.html.\n--2679-- WARNING: unhandled riscv64-linux syscall: 258\n--2679-- You may be able to write your own handler.\n--2679-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2679-- Nevertheless we consider this a bug. Please report\n--2679-- it at http://valgrind.org/support/bug_reports.html.\n--2679-- WARNING: unhandled riscv64-linux syscall: 258\n--2679-- You may be able to write your own handler.\n--2679-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2679-- Nevertheless we consider this a bug. Please report\n--2679-- it at http://valgrind.org/support/bug_reports.html.\n--2679-- WARNING: unhandled riscv64-linux syscall: 258\n--2679-- You may be able to write your own handler.\n--2679-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2679-- Nevertheless we consider this a bug. Please report\n--2679-- it at http://valgrind.org/support/bug_reports.html.\n--2679-- WARNING: unhandled riscv64-linux syscall: 258\n--2679-- You may be able to write your own handler.\n--2679-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2679-- Nevertheless we consider this a bug. Please report\n--2679-- it at http://valgrind.org/support/bug_reports.html.\n--2679-- WARNING: unhandled riscv64-linux syscall: 258\n--2679-- You may be able to write your own handler.\n--2679-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2679-- Nevertheless we consider this a bug. Please report\n--2679-- it at http://valgrind.org/support/bug_reports.html.\n--2679-- WARNING: unhandled riscv64-linux syscall: 258\n--2679-- You may be able to write your own handler.\n--2679-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2679-- Nevertheless we consider this a bug. Please report\n--2679-- it at http://valgrind.org/support/bug_reports.html.\n--2679-- WARNING: unhandled riscv64-linux syscall: 258\n--2679-- You may be able to write your own handler.\n--2679-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2679-- Nevertheless we consider this a bug. Please report\n--2679-- it at http://valgrind.org/support/bug_reports.html.\n--2679-- WARNING: unhandled riscv64-linux syscall: 258\n--2679-- You may be able to write your own handler.\n--2679-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2679-- Nevertheless we consider this a bug. Please report\n--2679-- it at http://valgrind.org/support/bug_reports.html.\n--2679-- WARNING: unhandled riscv64-linux syscall: 258\n--2679-- You may be able to write your own handler.\n--2679-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2679-- Nevertheless we consider this a bug. Please report\n--2679-- it at http://valgrind.org/support/bug_reports.html.\n--2679-- WARNING: unhandled riscv64-linux syscall: 258\n--2679-- You may be able to write your own handler.\n--2679-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2679-- Nevertheless we consider this a bug. Please report\n--2679-- it at http://valgrind.org/support/bug_reports.html.\n--2679-- WARNING: unhandled riscv64-linux syscall: 258\n--2679-- You may be able to write your own handler.\n--2679-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2679-- Nevertheless we consider this a bug. Please report\n--2679-- it at http://valgrind.org/support/bug_reports.html.\n--2679-- WARNING: unhandled riscv64-linux syscall: 258\n--2679-- You may be able to write your own handler.\n--2679-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2679-- Nevertheless we consider this a bug. Please report\n--2679-- it at http://valgrind.org/support/bug_reports.html.\n--2679-- WARNING: unhandled riscv64-linux syscall: 258\n--2679-- You may be able to write your own handler.\n--2679-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2679-- Nevertheless we consider this a bug. Please report\n--2679-- it at http://valgrind.org/support/bug_reports.html.\n--2679-- WARNING: unhandled riscv64-linux syscall: 258\n--2679-- You may be able to write your own handler.\n--2679-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2679-- Nevertheless we consider this a bug. Please report\n--2679-- it at http://valgrind.org/support/bug_reports.html.\ntrurl error: missing must:query\ntrurl error: Try trurl -h for help\n' --- returncode --- expected: 10 got: 10 175: failed 'https://example.com/?' --get '{must:query}' --- stdout --- expected: '\n' got: '\n' --- stderr --- expected: '' got: '--2687-- WARNING: unhandled riscv64-linux syscall: 258\n--2687-- You may be able to write your own handler.\n--2687-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2687-- Nevertheless we consider this a bug. Please report\n--2687-- it at http://valgrind.org/support/bug_reports.html.\n--2687-- WARNING: unhandled riscv64-linux syscall: 258\n--2687-- You may be able to write your own handler.\n--2687-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2687-- Nevertheless we consider this a bug. Please report\n--2687-- it at http://valgrind.org/support/bug_reports.html.\n--2687-- WARNING: unhandled riscv64-linux syscall: 258\n--2687-- You may be able to write your own handler.\n--2687-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2687-- Nevertheless we consider this a bug. Please report\n--2687-- it at http://valgrind.org/support/bug_reports.html.\n--2687-- WARNING: unhandled riscv64-linux syscall: 258\n--2687-- You may be able to write your own handler.\n--2687-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2687-- Nevertheless we consider this a bug. Please report\n--2687-- it at http://valgrind.org/support/bug_reports.html.\n--2687-- WARNING: unhandled riscv64-linux syscall: 258\n--2687-- You may be able to write your own handler.\n--2687-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2687-- Nevertheless we consider this a bug. Please report\n--2687-- it at http://valgrind.org/support/bug_reports.html.\n--2687-- WARNING: unhandled riscv64-linux syscall: 258\n--2687-- You may be able to write your own handler.\n--2687-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2687-- Nevertheless we consider this a bug. Please report\n--2687-- it at http://valgrind.org/support/bug_reports.html.\n--2687-- WARNING: unhandled riscv64-linux syscall: 258\n--2687-- You may be able to write your own handler.\n--2687-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2687-- Nevertheless we consider this a bug. Please report\n--2687-- it at http://valgrind.org/support/bug_reports.html.\n--2687-- WARNING: unhandled riscv64-linux syscall: 258\n--2687-- You may be able to write your own handler.\n--2687-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2687-- Nevertheless we consider this a bug. Please report\n--2687-- it at http://valgrind.org/support/bug_reports.html.\n--2687-- WARNING: unhandled riscv64-linux syscall: 258\n--2687-- You may be able to write your own handler.\n--2687-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2687-- Nevertheless we consider this a bug. Please report\n--2687-- it at http://valgrind.org/support/bug_reports.html.\n--2687-- WARNING: unhandled riscv64-linux syscall: 258\n--2687-- You may be able to write your own handler.\n--2687-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2687-- Nevertheless we consider this a bug. Please report\n--2687-- it at http://valgrind.org/support/bug_reports.html.\n--2687-- WARNING: unhandled riscv64-linux syscall: 258\n--2687-- You may be able to write your own handler.\n--2687-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2687-- Nevertheless we consider this a bug. Please report\n--2687-- it at http://valgrind.org/support/bug_reports.html.\n--2687-- WARNING: unhandled riscv64-linux syscall: 258\n--2687-- You may be able to write your own handler.\n--2687-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2687-- Nevertheless we consider this a bug. Please report\n--2687-- it at http://valgrind.org/support/bug_reports.html.\n--2687-- WARNING: unhandled riscv64-linux syscall: 258\n--2687-- You may be able to write your own handler.\n--2687-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2687-- Nevertheless we consider this a bug. Please report\n--2687-- it at http://valgrind.org/support/bug_reports.html.\n--2687-- WARNING: unhandled riscv64-linux syscall: 258\n--2687-- You may be able to write your own handler.\n--2687-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2687-- Nevertheless we consider this a bug. Please report\n--2687-- it at http://valgrind.org/support/bug_reports.html.\n--2687-- WARNING: unhandled riscv64-linux syscall: 258\n--2687-- You may be able to write your own handler.\n--2687-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2687-- Nevertheless we consider this a bug. Please report\n--2687-- it at http://valgrind.org/support/bug_reports.html.\n--2687-- WARNING: unhandled riscv64-linux syscall: 258\n--2687-- You may be able to write your own handler.\n--2687-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2687-- Nevertheless we consider this a bug. Please report\n--2687-- it at http://valgrind.org/support/bug_reports.html.\n--2687-- WARNING: unhandled riscv64-linux syscall: 258\n--2687-- You may be able to write your own handler.\n--2687-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2687-- Nevertheless we consider this a bug. Please report\n--2687-- it at http://valgrind.org/support/bug_reports.html.\n--2687-- WARNING: unhandled riscv64-linux syscall: 258\n--2687-- You may be able to write your own handler.\n--2687-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2687-- Nevertheless we consider this a bug. Please report\n--2687-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 176: failed https://example.com/ --get '{must:fragment}' --- stdout --- expected: '' got: '' --- stderr --- expected: 'trurl error: missing must:fragment\ntrurl error: Try trurl -h for help\n' got: '--2695-- WARNING: unhandled riscv64-linux syscall: 258\n--2695-- You may be able to write your own handler.\n--2695-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2695-- Nevertheless we consider this a bug. Please report\n--2695-- it at http://valgrind.org/support/bug_reports.html.\n--2695-- WARNING: unhandled riscv64-linux syscall: 258\n--2695-- You may be able to write your own handler.\n--2695-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2695-- Nevertheless we consider this a bug. Please report\n--2695-- it at http://valgrind.org/support/bug_reports.html.\n--2695-- WARNING: unhandled riscv64-linux syscall: 258\n--2695-- You may be able to write your own handler.\n--2695-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2695-- Nevertheless we consider this a bug. Please report\n--2695-- it at http://valgrind.org/support/bug_reports.html.\n--2695-- WARNING: unhandled riscv64-linux syscall: 258\n--2695-- You may be able to write your own handler.\n--2695-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2695-- Nevertheless we consider this a bug. Please report\n--2695-- it at http://valgrind.org/support/bug_reports.html.\n--2695-- WARNING: unhandled riscv64-linux syscall: 258\n--2695-- You may be able to write your own handler.\n--2695-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2695-- Nevertheless we consider this a bug. Please report\n--2695-- it at http://valgrind.org/support/bug_reports.html.\n--2695-- WARNING: unhandled riscv64-linux syscall: 258\n--2695-- You may be able to write your own handler.\n--2695-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2695-- Nevertheless we consider this a bug. Please report\n--2695-- it at http://valgrind.org/support/bug_reports.html.\n--2695-- WARNING: unhandled riscv64-linux syscall: 258\n--2695-- You may be able to write your own handler.\n--2695-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2695-- Nevertheless we consider this a bug. Please report\n--2695-- it at http://valgrind.org/support/bug_reports.html.\n--2695-- WARNING: unhandled riscv64-linux syscall: 258\n--2695-- You may be able to write your own handler.\n--2695-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2695-- Nevertheless we consider this a bug. Please report\n--2695-- it at http://valgrind.org/support/bug_reports.html.\n--2695-- WARNING: unhandled riscv64-linux syscall: 258\n--2695-- You may be able to write your own handler.\n--2695-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2695-- Nevertheless we consider this a bug. Please report\n--2695-- it at http://valgrind.org/support/bug_reports.html.\n--2695-- WARNING: unhandled riscv64-linux syscall: 258\n--2695-- You may be able to write your own handler.\n--2695-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2695-- Nevertheless we consider this a bug. Please report\n--2695-- it at http://valgrind.org/support/bug_reports.html.\n--2695-- WARNING: unhandled riscv64-linux syscall: 258\n--2695-- You may be able to write your own handler.\n--2695-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2695-- Nevertheless we consider this a bug. Please report\n--2695-- it at http://valgrind.org/support/bug_reports.html.\n--2695-- WARNING: unhandled riscv64-linux syscall: 258\n--2695-- You may be able to write your own handler.\n--2695-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2695-- Nevertheless we consider this a bug. Please report\n--2695-- it at http://valgrind.org/support/bug_reports.html.\n--2695-- WARNING: unhandled riscv64-linux syscall: 258\n--2695-- You may be able to write your own handler.\n--2695-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2695-- Nevertheless we consider this a bug. Please report\n--2695-- it at http://valgrind.org/support/bug_reports.html.\n--2695-- WARNING: unhandled riscv64-linux syscall: 258\n--2695-- You may be able to write your own handler.\n--2695-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2695-- Nevertheless we consider this a bug. Please report\n--2695-- it at http://valgrind.org/support/bug_reports.html.\n--2695-- WARNING: unhandled riscv64-linux syscall: 258\n--2695-- You may be able to write your own handler.\n--2695-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2695-- Nevertheless we consider this a bug. Please report\n--2695-- it at http://valgrind.org/support/bug_reports.html.\n--2695-- WARNING: unhandled riscv64-linux syscall: 258\n--2695-- You may be able to write your own handler.\n--2695-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2695-- Nevertheless we consider this a bug. Please report\n--2695-- it at http://valgrind.org/support/bug_reports.html.\n--2695-- WARNING: unhandled riscv64-linux syscall: 258\n--2695-- You may be able to write your own handler.\n--2695-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2695-- Nevertheless we consider this a bug. Please report\n--2695-- it at http://valgrind.org/support/bug_reports.html.\n--2695-- WARNING: unhandled riscv64-linux syscall: 258\n--2695-- You may be able to write your own handler.\n--2695-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2695-- Nevertheless we consider this a bug. Please report\n--2695-- it at http://valgrind.org/support/bug_reports.html.\ntrurl error: missing must:fragment\ntrurl error: Try trurl -h for help\n' --- returncode --- expected: 10 got: 10 177: failed http://example.org/%18 --get '{path}' --- stdout --- expected: '/\x18\n' got: '/\x18\n' --- stderr --- expected: '' got: '--2703-- WARNING: unhandled riscv64-linux syscall: 258\n--2703-- You may be able to write your own handler.\n--2703-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2703-- Nevertheless we consider this a bug. Please report\n--2703-- it at http://valgrind.org/support/bug_reports.html.\n--2703-- WARNING: unhandled riscv64-linux syscall: 258\n--2703-- You may be able to write your own handler.\n--2703-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2703-- Nevertheless we consider this a bug. Please report\n--2703-- it at http://valgrind.org/support/bug_reports.html.\n--2703-- WARNING: unhandled riscv64-linux syscall: 258\n--2703-- You may be able to write your own handler.\n--2703-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2703-- Nevertheless we consider this a bug. Please report\n--2703-- it at http://valgrind.org/support/bug_reports.html.\n--2703-- WARNING: unhandled riscv64-linux syscall: 258\n--2703-- You may be able to write your own handler.\n--2703-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2703-- Nevertheless we consider this a bug. Please report\n--2703-- it at http://valgrind.org/support/bug_reports.html.\n--2703-- WARNING: unhandled riscv64-linux syscall: 258\n--2703-- You may be able to write your own handler.\n--2703-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2703-- Nevertheless we consider this a bug. Please report\n--2703-- it at http://valgrind.org/support/bug_reports.html.\n--2703-- WARNING: unhandled riscv64-linux syscall: 258\n--2703-- You may be able to write your own handler.\n--2703-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2703-- Nevertheless we consider this a bug. Please report\n--2703-- it at http://valgrind.org/support/bug_reports.html.\n--2703-- WARNING: unhandled riscv64-linux syscall: 258\n--2703-- You may be able to write your own handler.\n--2703-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2703-- Nevertheless we consider this a bug. Please report\n--2703-- it at http://valgrind.org/support/bug_reports.html.\n--2703-- WARNING: unhandled riscv64-linux syscall: 258\n--2703-- You may be able to write your own handler.\n--2703-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2703-- Nevertheless we consider this a bug. Please report\n--2703-- it at http://valgrind.org/support/bug_reports.html.\n--2703-- WARNING: unhandled riscv64-linux syscall: 258\n--2703-- You may be able to write your own handler.\n--2703-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2703-- Nevertheless we consider this a bug. Please report\n--2703-- it at http://valgrind.org/support/bug_reports.html.\n--2703-- WARNING: unhandled riscv64-linux syscall: 258\n--2703-- You may be able to write your own handler.\n--2703-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2703-- Nevertheless we consider this a bug. Please report\n--2703-- it at http://valgrind.org/support/bug_reports.html.\n--2703-- WARNING: unhandled riscv64-linux syscall: 258\n--2703-- You may be able to write your own handler.\n--2703-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2703-- Nevertheless we consider this a bug. Please report\n--2703-- it at http://valgrind.org/support/bug_reports.html.\n--2703-- WARNING: unhandled riscv64-linux syscall: 258\n--2703-- You may be able to write your own handler.\n--2703-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2703-- Nevertheless we consider this a bug. Please report\n--2703-- it at http://valgrind.org/support/bug_reports.html.\n--2703-- WARNING: unhandled riscv64-linux syscall: 258\n--2703-- You may be able to write your own handler.\n--2703-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2703-- Nevertheless we consider this a bug. Please report\n--2703-- it at http://valgrind.org/support/bug_reports.html.\n--2703-- WARNING: unhandled riscv64-linux syscall: 258\n--2703-- You may be able to write your own handler.\n--2703-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2703-- Nevertheless we consider this a bug. Please report\n--2703-- it at http://valgrind.org/support/bug_reports.html.\n--2703-- WARNING: unhandled riscv64-linux syscall: 258\n--2703-- You may be able to write your own handler.\n--2703-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2703-- Nevertheless we consider this a bug. Please report\n--2703-- it at http://valgrind.org/support/bug_reports.html.\n--2703-- WARNING: unhandled riscv64-linux syscall: 258\n--2703-- You may be able to write your own handler.\n--2703-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2703-- Nevertheless we consider this a bug. Please report\n--2703-- it at http://valgrind.org/support/bug_reports.html.\n--2703-- WARNING: unhandled riscv64-linux syscall: 258\n--2703-- You may be able to write your own handler.\n--2703-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2703-- Nevertheless we consider this a bug. Please report\n--2703-- it at http://valgrind.org/support/bug_reports.html.\n--2703-- WARNING: unhandled riscv64-linux syscall: 258\n--2703-- You may be able to write your own handler.\n--2703-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2703-- Nevertheless we consider this a bug. Please report\n--2703-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 178: failed 'http://example.org/?a=&b=1' --- stdout --- expected: 'http://example.org/?a=&b=1\n' got: 'http://example.org/?a=&b=1\n' --- stderr --- expected: '' got: '--2711-- WARNING: unhandled riscv64-linux syscall: 258\n--2711-- You may be able to write your own handler.\n--2711-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2711-- Nevertheless we consider this a bug. Please report\n--2711-- it at http://valgrind.org/support/bug_reports.html.\n--2711-- WARNING: unhandled riscv64-linux syscall: 258\n--2711-- You may be able to write your own handler.\n--2711-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2711-- Nevertheless we consider this a bug. Please report\n--2711-- it at http://valgrind.org/support/bug_reports.html.\n--2711-- WARNING: unhandled riscv64-linux syscall: 258\n--2711-- You may be able to write your own handler.\n--2711-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2711-- Nevertheless we consider this a bug. Please report\n--2711-- it at http://valgrind.org/support/bug_reports.html.\n--2711-- WARNING: unhandled riscv64-linux syscall: 258\n--2711-- You may be able to write your own handler.\n--2711-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2711-- Nevertheless we consider this a bug. Please report\n--2711-- it at http://valgrind.org/support/bug_reports.html.\n--2711-- WARNING: unhandled riscv64-linux syscall: 258\n--2711-- You may be able to write your own handler.\n--2711-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2711-- Nevertheless we consider this a bug. Please report\n--2711-- it at http://valgrind.org/support/bug_reports.html.\n--2711-- WARNING: unhandled riscv64-linux syscall: 258\n--2711-- You may be able to write your own handler.\n--2711-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2711-- Nevertheless we consider this a bug. Please report\n--2711-- it at http://valgrind.org/support/bug_reports.html.\n--2711-- WARNING: unhandled riscv64-linux syscall: 258\n--2711-- You may be able to write your own handler.\n--2711-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2711-- Nevertheless we consider this a bug. Please report\n--2711-- it at http://valgrind.org/support/bug_reports.html.\n--2711-- WARNING: unhandled riscv64-linux syscall: 258\n--2711-- You may be able to write your own handler.\n--2711-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2711-- Nevertheless we consider this a bug. Please report\n--2711-- it at http://valgrind.org/support/bug_reports.html.\n--2711-- WARNING: unhandled riscv64-linux syscall: 258\n--2711-- You may be able to write your own handler.\n--2711-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2711-- Nevertheless we consider this a bug. Please report\n--2711-- it at http://valgrind.org/support/bug_reports.html.\n--2711-- WARNING: unhandled riscv64-linux syscall: 258\n--2711-- You may be able to write your own handler.\n--2711-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2711-- Nevertheless we consider this a bug. Please report\n--2711-- it at http://valgrind.org/support/bug_reports.html.\n--2711-- WARNING: unhandled riscv64-linux syscall: 258\n--2711-- You may be able to write your own handler.\n--2711-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2711-- Nevertheless we consider this a bug. Please report\n--2711-- it at http://valgrind.org/support/bug_reports.html.\n--2711-- WARNING: unhandled riscv64-linux syscall: 258\n--2711-- You may be able to write your own handler.\n--2711-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2711-- Nevertheless we consider this a bug. Please report\n--2711-- it at http://valgrind.org/support/bug_reports.html.\n--2711-- WARNING: unhandled riscv64-linux syscall: 258\n--2711-- You may be able to write your own handler.\n--2711-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2711-- Nevertheless we consider this a bug. Please report\n--2711-- it at http://valgrind.org/support/bug_reports.html.\n--2711-- WARNING: unhandled riscv64-linux syscall: 258\n--2711-- You may be able to write your own handler.\n--2711-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2711-- Nevertheless we consider this a bug. Please report\n--2711-- it at http://valgrind.org/support/bug_reports.html.\n--2711-- WARNING: unhandled riscv64-linux syscall: 258\n--2711-- You may be able to write your own handler.\n--2711-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2711-- Nevertheless we consider this a bug. Please report\n--2711-- it at http://valgrind.org/support/bug_reports.html.\n--2711-- WARNING: unhandled riscv64-linux syscall: 258\n--2711-- You may be able to write your own handler.\n--2711-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2711-- Nevertheless we consider this a bug. Please report\n--2711-- it at http://valgrind.org/support/bug_reports.html.\n--2711-- WARNING: unhandled riscv64-linux syscall: 258\n--2711-- You may be able to write your own handler.\n--2711-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2711-- Nevertheless we consider this a bug. Please report\n--2711-- it at http://valgrind.org/support/bug_reports.html.\n--2711-- WARNING: unhandled riscv64-linux syscall: 258\n--2711-- You may be able to write your own handler.\n--2711-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2711-- Nevertheless we consider this a bug. Please report\n--2711-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 179: failed 'http://example.org/?a=1&b=' --- stdout --- expected: 'http://example.org/?a=1&b=\n' got: 'http://example.org/?a=1&b=\n' --- stderr --- expected: '' got: '--2719-- WARNING: unhandled riscv64-linux syscall: 258\n--2719-- You may be able to write your own handler.\n--2719-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2719-- Nevertheless we consider this a bug. Please report\n--2719-- it at http://valgrind.org/support/bug_reports.html.\n--2719-- WARNING: unhandled riscv64-linux syscall: 258\n--2719-- You may be able to write your own handler.\n--2719-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2719-- Nevertheless we consider this a bug. Please report\n--2719-- it at http://valgrind.org/support/bug_reports.html.\n--2719-- WARNING: unhandled riscv64-linux syscall: 258\n--2719-- You may be able to write your own handler.\n--2719-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2719-- Nevertheless we consider this a bug. Please report\n--2719-- it at http://valgrind.org/support/bug_reports.html.\n--2719-- WARNING: unhandled riscv64-linux syscall: 258\n--2719-- You may be able to write your own handler.\n--2719-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2719-- Nevertheless we consider this a bug. Please report\n--2719-- it at http://valgrind.org/support/bug_reports.html.\n--2719-- WARNING: unhandled riscv64-linux syscall: 258\n--2719-- You may be able to write your own handler.\n--2719-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2719-- Nevertheless we consider this a bug. Please report\n--2719-- it at http://valgrind.org/support/bug_reports.html.\n--2719-- WARNING: unhandled riscv64-linux syscall: 258\n--2719-- You may be able to write your own handler.\n--2719-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2719-- Nevertheless we consider this a bug. Please report\n--2719-- it at http://valgrind.org/support/bug_reports.html.\n--2719-- WARNING: unhandled riscv64-linux syscall: 258\n--2719-- You may be able to write your own handler.\n--2719-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2719-- Nevertheless we consider this a bug. Please report\n--2719-- it at http://valgrind.org/support/bug_reports.html.\n--2719-- WARNING: unhandled riscv64-linux syscall: 258\n--2719-- You may be able to write your own handler.\n--2719-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2719-- Nevertheless we consider this a bug. Please report\n--2719-- it at http://valgrind.org/support/bug_reports.html.\n--2719-- WARNING: unhandled riscv64-linux syscall: 258\n--2719-- You may be able to write your own handler.\n--2719-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2719-- Nevertheless we consider this a bug. Please report\n--2719-- it at http://valgrind.org/support/bug_reports.html.\n--2719-- WARNING: unhandled riscv64-linux syscall: 258\n--2719-- You may be able to write your own handler.\n--2719-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2719-- Nevertheless we consider this a bug. Please report\n--2719-- it at http://valgrind.org/support/bug_reports.html.\n--2719-- WARNING: unhandled riscv64-linux syscall: 258\n--2719-- You may be able to write your own handler.\n--2719-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2719-- Nevertheless we consider this a bug. Please report\n--2719-- it at http://valgrind.org/support/bug_reports.html.\n--2719-- WARNING: unhandled riscv64-linux syscall: 258\n--2719-- You may be able to write your own handler.\n--2719-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2719-- Nevertheless we consider this a bug. Please report\n--2719-- it at http://valgrind.org/support/bug_reports.html.\n--2719-- WARNING: unhandled riscv64-linux syscall: 258\n--2719-- You may be able to write your own handler.\n--2719-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2719-- Nevertheless we consider this a bug. Please report\n--2719-- it at http://valgrind.org/support/bug_reports.html.\n--2719-- WARNING: unhandled riscv64-linux syscall: 258\n--2719-- You may be able to write your own handler.\n--2719-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2719-- Nevertheless we consider this a bug. Please report\n--2719-- it at http://valgrind.org/support/bug_reports.html.\n--2719-- WARNING: unhandled riscv64-linux syscall: 258\n--2719-- You may be able to write your own handler.\n--2719-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2719-- Nevertheless we consider this a bug. Please report\n--2719-- it at http://valgrind.org/support/bug_reports.html.\n--2719-- WARNING: unhandled riscv64-linux syscall: 258\n--2719-- You may be able to write your own handler.\n--2719-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2719-- Nevertheless we consider this a bug. Please report\n--2719-- it at http://valgrind.org/support/bug_reports.html.\n--2719-- WARNING: unhandled riscv64-linux syscall: 258\n--2719-- You may be able to write your own handler.\n--2719-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2719-- Nevertheless we consider this a bug. Please report\n--2719-- it at http://valgrind.org/support/bug_reports.html.\n--2719-- WARNING: unhandled riscv64-linux syscall: 258\n--2719-- You may be able to write your own handler.\n--2719-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2719-- Nevertheless we consider this a bug. Please report\n--2719-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 180: failed 'http://example.org/?a=1&b=&c=2' --- stdout --- expected: 'http://example.org/?a=1&b=&c=2\n' got: 'http://example.org/?a=1&b=&c=2\n' --- stderr --- expected: '' got: '--2727-- WARNING: unhandled riscv64-linux syscall: 258\n--2727-- You may be able to write your own handler.\n--2727-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2727-- Nevertheless we consider this a bug. Please report\n--2727-- it at http://valgrind.org/support/bug_reports.html.\n--2727-- WARNING: unhandled riscv64-linux syscall: 258\n--2727-- You may be able to write your own handler.\n--2727-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2727-- Nevertheless we consider this a bug. Please report\n--2727-- it at http://valgrind.org/support/bug_reports.html.\n--2727-- WARNING: unhandled riscv64-linux syscall: 258\n--2727-- You may be able to write your own handler.\n--2727-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2727-- Nevertheless we consider this a bug. Please report\n--2727-- it at http://valgrind.org/support/bug_reports.html.\n--2727-- WARNING: unhandled riscv64-linux syscall: 258\n--2727-- You may be able to write your own handler.\n--2727-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2727-- Nevertheless we consider this a bug. Please report\n--2727-- it at http://valgrind.org/support/bug_reports.html.\n--2727-- WARNING: unhandled riscv64-linux syscall: 258\n--2727-- You may be able to write your own handler.\n--2727-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2727-- Nevertheless we consider this a bug. Please report\n--2727-- it at http://valgrind.org/support/bug_reports.html.\n--2727-- WARNING: unhandled riscv64-linux syscall: 258\n--2727-- You may be able to write your own handler.\n--2727-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2727-- Nevertheless we consider this a bug. Please report\n--2727-- it at http://valgrind.org/support/bug_reports.html.\n--2727-- WARNING: unhandled riscv64-linux syscall: 258\n--2727-- You may be able to write your own handler.\n--2727-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2727-- Nevertheless we consider this a bug. Please report\n--2727-- it at http://valgrind.org/support/bug_reports.html.\n--2727-- WARNING: unhandled riscv64-linux syscall: 258\n--2727-- You may be able to write your own handler.\n--2727-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2727-- Nevertheless we consider this a bug. Please report\n--2727-- it at http://valgrind.org/support/bug_reports.html.\n--2727-- WARNING: unhandled riscv64-linux syscall: 258\n--2727-- You may be able to write your own handler.\n--2727-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2727-- Nevertheless we consider this a bug. Please report\n--2727-- it at http://valgrind.org/support/bug_reports.html.\n--2727-- WARNING: unhandled riscv64-linux syscall: 258\n--2727-- You may be able to write your own handler.\n--2727-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2727-- Nevertheless we consider this a bug. Please report\n--2727-- it at http://valgrind.org/support/bug_reports.html.\n--2727-- WARNING: unhandled riscv64-linux syscall: 258\n--2727-- You may be able to write your own handler.\n--2727-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2727-- Nevertheless we consider this a bug. Please report\n--2727-- it at http://valgrind.org/support/bug_reports.html.\n--2727-- WARNING: unhandled riscv64-linux syscall: 258\n--2727-- You may be able to write your own handler.\n--2727-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2727-- Nevertheless we consider this a bug. Please report\n--2727-- it at http://valgrind.org/support/bug_reports.html.\n--2727-- WARNING: unhandled riscv64-linux syscall: 258\n--2727-- You may be able to write your own handler.\n--2727-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2727-- Nevertheless we consider this a bug. Please report\n--2727-- it at http://valgrind.org/support/bug_reports.html.\n--2727-- WARNING: unhandled riscv64-linux syscall: 258\n--2727-- You may be able to write your own handler.\n--2727-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2727-- Nevertheless we consider this a bug. Please report\n--2727-- it at http://valgrind.org/support/bug_reports.html.\n--2727-- WARNING: unhandled riscv64-linux syscall: 258\n--2727-- You may be able to write your own handler.\n--2727-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2727-- Nevertheless we consider this a bug. Please report\n--2727-- it at http://valgrind.org/support/bug_reports.html.\n--2727-- WARNING: unhandled riscv64-linux syscall: 258\n--2727-- You may be able to write your own handler.\n--2727-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2727-- Nevertheless we consider this a bug. Please report\n--2727-- it at http://valgrind.org/support/bug_reports.html.\n--2727-- WARNING: unhandled riscv64-linux syscall: 258\n--2727-- You may be able to write your own handler.\n--2727-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2727-- Nevertheless we consider this a bug. Please report\n--2727-- it at http://valgrind.org/support/bug_reports.html.\n--2727-- WARNING: unhandled riscv64-linux syscall: 258\n--2727-- You may be able to write your own handler.\n--2727-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2727-- Nevertheless we consider this a bug. Please report\n--2727-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 181: failed 'http://example.org/?a=1&b=&c=2' --json --- stdout --- expected: [{'url': 'http://example.org/?a=1&b=&c=2', 'parts': {'scheme': 'http', 'host': 'example.org', 'path': '/', 'query': 'a=1&b=&c=2'}, 'params': [{'key': 'a', 'value': '1'}, {'key': 'b', 'value': ''}, {'key': 'c', 'value': '2'}]}] got: [{'url': 'http://example.org/?a=1&b=&c=2', 'parts': {'scheme': 'http', 'host': 'example.org', 'path': '/', 'query': 'a=1&b=&c=2'}, 'params': [{'key': 'a', 'value': '1'}, {'key': 'b', 'value': ''}, {'key': 'c', 'value': '2'}]}] --- stderr --- expected: '' got: '--2735-- WARNING: unhandled riscv64-linux syscall: 258\n--2735-- You may be able to write your own handler.\n--2735-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2735-- Nevertheless we consider this a bug. Please report\n--2735-- it at http://valgrind.org/support/bug_reports.html.\n--2735-- WARNING: unhandled riscv64-linux syscall: 258\n--2735-- You may be able to write your own handler.\n--2735-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2735-- Nevertheless we consider this a bug. Please report\n--2735-- it at http://valgrind.org/support/bug_reports.html.\n--2735-- WARNING: unhandled riscv64-linux syscall: 258\n--2735-- You may be able to write your own handler.\n--2735-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2735-- Nevertheless we consider this a bug. Please report\n--2735-- it at http://valgrind.org/support/bug_reports.html.\n--2735-- WARNING: unhandled riscv64-linux syscall: 258\n--2735-- You may be able to write your own handler.\n--2735-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2735-- Nevertheless we consider this a bug. Please report\n--2735-- it at http://valgrind.org/support/bug_reports.html.\n--2735-- WARNING: unhandled riscv64-linux syscall: 258\n--2735-- You may be able to write your own handler.\n--2735-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2735-- Nevertheless we consider this a bug. Please report\n--2735-- it at http://valgrind.org/support/bug_reports.html.\n--2735-- WARNING: unhandled riscv64-linux syscall: 258\n--2735-- You may be able to write your own handler.\n--2735-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2735-- Nevertheless we consider this a bug. Please report\n--2735-- it at http://valgrind.org/support/bug_reports.html.\n--2735-- WARNING: unhandled riscv64-linux syscall: 258\n--2735-- You may be able to write your own handler.\n--2735-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2735-- Nevertheless we consider this a bug. Please report\n--2735-- it at http://valgrind.org/support/bug_reports.html.\n--2735-- WARNING: unhandled riscv64-linux syscall: 258\n--2735-- You may be able to write your own handler.\n--2735-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2735-- Nevertheless we consider this a bug. Please report\n--2735-- it at http://valgrind.org/support/bug_reports.html.\n--2735-- WARNING: unhandled riscv64-linux syscall: 258\n--2735-- You may be able to write your own handler.\n--2735-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2735-- Nevertheless we consider this a bug. Please report\n--2735-- it at http://valgrind.org/support/bug_reports.html.\n--2735-- WARNING: unhandled riscv64-linux syscall: 258\n--2735-- You may be able to write your own handler.\n--2735-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2735-- Nevertheless we consider this a bug. Please report\n--2735-- it at http://valgrind.org/support/bug_reports.html.\n--2735-- WARNING: unhandled riscv64-linux syscall: 258\n--2735-- You may be able to write your own handler.\n--2735-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2735-- Nevertheless we consider this a bug. Please report\n--2735-- it at http://valgrind.org/support/bug_reports.html.\n--2735-- WARNING: unhandled riscv64-linux syscall: 258\n--2735-- You may be able to write your own handler.\n--2735-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2735-- Nevertheless we consider this a bug. Please report\n--2735-- it at http://valgrind.org/support/bug_reports.html.\n--2735-- WARNING: unhandled riscv64-linux syscall: 258\n--2735-- You may be able to write your own handler.\n--2735-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2735-- Nevertheless we consider this a bug. Please report\n--2735-- it at http://valgrind.org/support/bug_reports.html.\n--2735-- WARNING: unhandled riscv64-linux syscall: 258\n--2735-- You may be able to write your own handler.\n--2735-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2735-- Nevertheless we consider this a bug. Please report\n--2735-- it at http://valgrind.org/support/bug_reports.html.\n--2735-- WARNING: unhandled riscv64-linux syscall: 258\n--2735-- You may be able to write your own handler.\n--2735-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2735-- Nevertheless we consider this a bug. Please report\n--2735-- it at http://valgrind.org/support/bug_reports.html.\n--2735-- WARNING: unhandled riscv64-linux syscall: 258\n--2735-- You may be able to write your own handler.\n--2735-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2735-- Nevertheless we consider this a bug. Please report\n--2735-- it at http://valgrind.org/support/bug_reports.html.\n--2735-- WARNING: unhandled riscv64-linux syscall: 258\n--2735-- You may be able to write your own handler.\n--2735-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2735-- Nevertheless we consider this a bug. Please report\n--2735-- it at http://valgrind.org/support/bug_reports.html.\n--2735-- WARNING: unhandled riscv64-linux syscall: 258\n--2735-- You may be able to write your own handler.\n--2735-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2735-- Nevertheless we consider this a bug. Please report\n--2735-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 182: failed 'http://example.org/?=1&b=2&c=&=3' --- stdout --- expected: 'http://example.org/?=1&b=2&c=&=3\n' got: 'http://example.org/?=1&b=2&c=&=3\n' --- stderr --- expected: '' got: '--2743-- WARNING: unhandled riscv64-linux syscall: 258\n--2743-- You may be able to write your own handler.\n--2743-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2743-- Nevertheless we consider this a bug. Please report\n--2743-- it at http://valgrind.org/support/bug_reports.html.\n--2743-- WARNING: unhandled riscv64-linux syscall: 258\n--2743-- You may be able to write your own handler.\n--2743-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2743-- Nevertheless we consider this a bug. Please report\n--2743-- it at http://valgrind.org/support/bug_reports.html.\n--2743-- WARNING: unhandled riscv64-linux syscall: 258\n--2743-- You may be able to write your own handler.\n--2743-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2743-- Nevertheless we consider this a bug. Please report\n--2743-- it at http://valgrind.org/support/bug_reports.html.\n--2743-- WARNING: unhandled riscv64-linux syscall: 258\n--2743-- You may be able to write your own handler.\n--2743-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2743-- Nevertheless we consider this a bug. Please report\n--2743-- it at http://valgrind.org/support/bug_reports.html.\n--2743-- WARNING: unhandled riscv64-linux syscall: 258\n--2743-- You may be able to write your own handler.\n--2743-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2743-- Nevertheless we consider this a bug. Please report\n--2743-- it at http://valgrind.org/support/bug_reports.html.\n--2743-- WARNING: unhandled riscv64-linux syscall: 258\n--2743-- You may be able to write your own handler.\n--2743-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2743-- Nevertheless we consider this a bug. Please report\n--2743-- it at http://valgrind.org/support/bug_reports.html.\n--2743-- WARNING: unhandled riscv64-linux syscall: 258\n--2743-- You may be able to write your own handler.\n--2743-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2743-- Nevertheless we consider this a bug. Please report\n--2743-- it at http://valgrind.org/support/bug_reports.html.\n--2743-- WARNING: unhandled riscv64-linux syscall: 258\n--2743-- You may be able to write your own handler.\n--2743-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2743-- Nevertheless we consider this a bug. Please report\n--2743-- it at http://valgrind.org/support/bug_reports.html.\n--2743-- WARNING: unhandled riscv64-linux syscall: 258\n--2743-- You may be able to write your own handler.\n--2743-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2743-- Nevertheless we consider this a bug. Please report\n--2743-- it at http://valgrind.org/support/bug_reports.html.\n--2743-- WARNING: unhandled riscv64-linux syscall: 258\n--2743-- You may be able to write your own handler.\n--2743-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2743-- Nevertheless we consider this a bug. Please report\n--2743-- it at http://valgrind.org/support/bug_reports.html.\n--2743-- WARNING: unhandled riscv64-linux syscall: 258\n--2743-- You may be able to write your own handler.\n--2743-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2743-- Nevertheless we consider this a bug. Please report\n--2743-- it at http://valgrind.org/support/bug_reports.html.\n--2743-- WARNING: unhandled riscv64-linux syscall: 258\n--2743-- You may be able to write your own handler.\n--2743-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2743-- Nevertheless we consider this a bug. Please report\n--2743-- it at http://valgrind.org/support/bug_reports.html.\n--2743-- WARNING: unhandled riscv64-linux syscall: 258\n--2743-- You may be able to write your own handler.\n--2743-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2743-- Nevertheless we consider this a bug. Please report\n--2743-- it at http://valgrind.org/support/bug_reports.html.\n--2743-- WARNING: unhandled riscv64-linux syscall: 258\n--2743-- You may be able to write your own handler.\n--2743-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2743-- Nevertheless we consider this a bug. Please report\n--2743-- it at http://valgrind.org/support/bug_reports.html.\n--2743-- WARNING: unhandled riscv64-linux syscall: 258\n--2743-- You may be able to write your own handler.\n--2743-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2743-- Nevertheless we consider this a bug. Please report\n--2743-- it at http://valgrind.org/support/bug_reports.html.\n--2743-- WARNING: unhandled riscv64-linux syscall: 258\n--2743-- You may be able to write your own handler.\n--2743-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2743-- Nevertheless we consider this a bug. Please report\n--2743-- it at http://valgrind.org/support/bug_reports.html.\n--2743-- WARNING: unhandled riscv64-linux syscall: 258\n--2743-- You may be able to write your own handler.\n--2743-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2743-- Nevertheless we consider this a bug. Please report\n--2743-- it at http://valgrind.org/support/bug_reports.html.\n--2743-- WARNING: unhandled riscv64-linux syscall: 258\n--2743-- You may be able to write your own handler.\n--2743-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2743-- Nevertheless we consider this a bug. Please report\n--2743-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 183: failed 'http://example.com/?a=%5D' --- stdout --- expected: 'http://example.com/?a=%5d\n' got: 'http://example.com/?a=%5d\n' --- stderr --- expected: '' got: '--2751-- WARNING: unhandled riscv64-linux syscall: 258\n--2751-- You may be able to write your own handler.\n--2751-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2751-- Nevertheless we consider this a bug. Please report\n--2751-- it at http://valgrind.org/support/bug_reports.html.\n--2751-- WARNING: unhandled riscv64-linux syscall: 258\n--2751-- You may be able to write your own handler.\n--2751-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2751-- Nevertheless we consider this a bug. Please report\n--2751-- it at http://valgrind.org/support/bug_reports.html.\n--2751-- WARNING: unhandled riscv64-linux syscall: 258\n--2751-- You may be able to write your own handler.\n--2751-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2751-- Nevertheless we consider this a bug. Please report\n--2751-- it at http://valgrind.org/support/bug_reports.html.\n--2751-- WARNING: unhandled riscv64-linux syscall: 258\n--2751-- You may be able to write your own handler.\n--2751-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2751-- Nevertheless we consider this a bug. Please report\n--2751-- it at http://valgrind.org/support/bug_reports.html.\n--2751-- WARNING: unhandled riscv64-linux syscall: 258\n--2751-- You may be able to write your own handler.\n--2751-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2751-- Nevertheless we consider this a bug. Please report\n--2751-- it at http://valgrind.org/support/bug_reports.html.\n--2751-- WARNING: unhandled riscv64-linux syscall: 258\n--2751-- You may be able to write your own handler.\n--2751-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2751-- Nevertheless we consider this a bug. Please report\n--2751-- it at http://valgrind.org/support/bug_reports.html.\n--2751-- WARNING: unhandled riscv64-linux syscall: 258\n--2751-- You may be able to write your own handler.\n--2751-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2751-- Nevertheless we consider this a bug. Please report\n--2751-- it at http://valgrind.org/support/bug_reports.html.\n--2751-- WARNING: unhandled riscv64-linux syscall: 258\n--2751-- You may be able to write your own handler.\n--2751-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2751-- Nevertheless we consider this a bug. Please report\n--2751-- it at http://valgrind.org/support/bug_reports.html.\n--2751-- WARNING: unhandled riscv64-linux syscall: 258\n--2751-- You may be able to write your own handler.\n--2751-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2751-- Nevertheless we consider this a bug. Please report\n--2751-- it at http://valgrind.org/support/bug_reports.html.\n--2751-- WARNING: unhandled riscv64-linux syscall: 258\n--2751-- You may be able to write your own handler.\n--2751-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2751-- Nevertheless we consider this a bug. Please report\n--2751-- it at http://valgrind.org/support/bug_reports.html.\n--2751-- WARNING: unhandled riscv64-linux syscall: 258\n--2751-- You may be able to write your own handler.\n--2751-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2751-- Nevertheless we consider this a bug. Please report\n--2751-- it at http://valgrind.org/support/bug_reports.html.\n--2751-- WARNING: unhandled riscv64-linux syscall: 258\n--2751-- You may be able to write your own handler.\n--2751-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2751-- Nevertheless we consider this a bug. Please report\n--2751-- it at http://valgrind.org/support/bug_reports.html.\n--2751-- WARNING: unhandled riscv64-linux syscall: 258\n--2751-- You may be able to write your own handler.\n--2751-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2751-- Nevertheless we consider this a bug. Please report\n--2751-- it at http://valgrind.org/support/bug_reports.html.\n--2751-- WARNING: unhandled riscv64-linux syscall: 258\n--2751-- You may be able to write your own handler.\n--2751-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2751-- Nevertheless we consider this a bug. Please report\n--2751-- it at http://valgrind.org/support/bug_reports.html.\n--2751-- WARNING: unhandled riscv64-linux syscall: 258\n--2751-- You may be able to write your own handler.\n--2751-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2751-- Nevertheless we consider this a bug. Please report\n--2751-- it at http://valgrind.org/support/bug_reports.html.\n--2751-- WARNING: unhandled riscv64-linux syscall: 258\n--2751-- You may be able to write your own handler.\n--2751-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2751-- Nevertheless we consider this a bug. Please report\n--2751-- it at http://valgrind.org/support/bug_reports.html.\n--2751-- WARNING: unhandled riscv64-linux syscall: 258\n--2751-- You may be able to write your own handler.\n--2751-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2751-- Nevertheless we consider this a bug. Please report\n--2751-- it at http://valgrind.org/support/bug_reports.html.\n--2751-- WARNING: unhandled riscv64-linux syscall: 258\n--2751-- You may be able to write your own handler.\n--2751-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2751-- Nevertheless we consider this a bug. Please report\n--2751-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 184: failed 'http://example.com/?a=%5D&b=%5D' --- stdout --- expected: 'http://example.com/?a=%5d&b=%5d\n' got: 'http://example.com/?a=%5d&b=%5d\n' --- stderr --- expected: '' got: '--2759-- WARNING: unhandled riscv64-linux syscall: 258\n--2759-- You may be able to write your own handler.\n--2759-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2759-- Nevertheless we consider this a bug. Please report\n--2759-- it at http://valgrind.org/support/bug_reports.html.\n--2759-- WARNING: unhandled riscv64-linux syscall: 258\n--2759-- You may be able to write your own handler.\n--2759-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2759-- Nevertheless we consider this a bug. Please report\n--2759-- it at http://valgrind.org/support/bug_reports.html.\n--2759-- WARNING: unhandled riscv64-linux syscall: 258\n--2759-- You may be able to write your own handler.\n--2759-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2759-- Nevertheless we consider this a bug. Please report\n--2759-- it at http://valgrind.org/support/bug_reports.html.\n--2759-- WARNING: unhandled riscv64-linux syscall: 258\n--2759-- You may be able to write your own handler.\n--2759-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2759-- Nevertheless we consider this a bug. Please report\n--2759-- it at http://valgrind.org/support/bug_reports.html.\n--2759-- WARNING: unhandled riscv64-linux syscall: 258\n--2759-- You may be able to write your own handler.\n--2759-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2759-- Nevertheless we consider this a bug. Please report\n--2759-- it at http://valgrind.org/support/bug_reports.html.\n--2759-- WARNING: unhandled riscv64-linux syscall: 258\n--2759-- You may be able to write your own handler.\n--2759-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2759-- Nevertheless we consider this a bug. Please report\n--2759-- it at http://valgrind.org/support/bug_reports.html.\n--2759-- WARNING: unhandled riscv64-linux syscall: 258\n--2759-- You may be able to write your own handler.\n--2759-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2759-- Nevertheless we consider this a bug. Please report\n--2759-- it at http://valgrind.org/support/bug_reports.html.\n--2759-- WARNING: unhandled riscv64-linux syscall: 258\n--2759-- You may be able to write your own handler.\n--2759-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2759-- Nevertheless we consider this a bug. Please report\n--2759-- it at http://valgrind.org/support/bug_reports.html.\n--2759-- WARNING: unhandled riscv64-linux syscall: 258\n--2759-- You may be able to write your own handler.\n--2759-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2759-- Nevertheless we consider this a bug. Please report\n--2759-- it at http://valgrind.org/support/bug_reports.html.\n--2759-- WARNING: unhandled riscv64-linux syscall: 258\n--2759-- You may be able to write your own handler.\n--2759-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2759-- Nevertheless we consider this a bug. Please report\n--2759-- it at http://valgrind.org/support/bug_reports.html.\n--2759-- WARNING: unhandled riscv64-linux syscall: 258\n--2759-- You may be able to write your own handler.\n--2759-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2759-- Nevertheless we consider this a bug. Please report\n--2759-- it at http://valgrind.org/support/bug_reports.html.\n--2759-- WARNING: unhandled riscv64-linux syscall: 258\n--2759-- You may be able to write your own handler.\n--2759-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2759-- Nevertheless we consider this a bug. Please report\n--2759-- it at http://valgrind.org/support/bug_reports.html.\n--2759-- WARNING: unhandled riscv64-linux syscall: 258\n--2759-- You may be able to write your own handler.\n--2759-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2759-- Nevertheless we consider this a bug. Please report\n--2759-- it at http://valgrind.org/support/bug_reports.html.\n--2759-- WARNING: unhandled riscv64-linux syscall: 258\n--2759-- You may be able to write your own handler.\n--2759-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2759-- Nevertheless we consider this a bug. Please report\n--2759-- it at http://valgrind.org/support/bug_reports.html.\n--2759-- WARNING: unhandled riscv64-linux syscall: 258\n--2759-- You may be able to write your own handler.\n--2759-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2759-- Nevertheless we consider this a bug. Please report\n--2759-- it at http://valgrind.org/support/bug_reports.html.\n--2759-- WARNING: unhandled riscv64-linux syscall: 258\n--2759-- You may be able to write your own handler.\n--2759-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2759-- Nevertheless we consider this a bug. Please report\n--2759-- it at http://valgrind.org/support/bug_reports.html.\n--2759-- WARNING: unhandled riscv64-linux syscall: 258\n--2759-- You may be able to write your own handler.\n--2759-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2759-- Nevertheless we consider this a bug. Please report\n--2759-- it at http://valgrind.org/support/bug_reports.html.\n--2759-- WARNING: unhandled riscv64-linux syscall: 258\n--2759-- You may be able to write your own handler.\n--2759-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2759-- Nevertheless we consider this a bug. Please report\n--2759-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 185: failed 'sftp://us%65r:pwd;giraffe@odd' --- stdout --- expected: 'sftp://user:pwd%3bgiraffe@odd/\n' got: 'sftp://user:pwd%3bgiraffe@odd/\n' --- stderr --- expected: '' got: '--2767-- WARNING: unhandled riscv64-linux syscall: 258\n--2767-- You may be able to write your own handler.\n--2767-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2767-- Nevertheless we consider this a bug. Please report\n--2767-- it at http://valgrind.org/support/bug_reports.html.\n--2767-- WARNING: unhandled riscv64-linux syscall: 258\n--2767-- You may be able to write your own handler.\n--2767-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2767-- Nevertheless we consider this a bug. Please report\n--2767-- it at http://valgrind.org/support/bug_reports.html.\n--2767-- WARNING: unhandled riscv64-linux syscall: 258\n--2767-- You may be able to write your own handler.\n--2767-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2767-- Nevertheless we consider this a bug. Please report\n--2767-- it at http://valgrind.org/support/bug_reports.html.\n--2767-- WARNING: unhandled riscv64-linux syscall: 258\n--2767-- You may be able to write your own handler.\n--2767-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2767-- Nevertheless we consider this a bug. Please report\n--2767-- it at http://valgrind.org/support/bug_reports.html.\n--2767-- WARNING: unhandled riscv64-linux syscall: 258\n--2767-- You may be able to write your own handler.\n--2767-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2767-- Nevertheless we consider this a bug. Please report\n--2767-- it at http://valgrind.org/support/bug_reports.html.\n--2767-- WARNING: unhandled riscv64-linux syscall: 258\n--2767-- You may be able to write your own handler.\n--2767-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2767-- Nevertheless we consider this a bug. Please report\n--2767-- it at http://valgrind.org/support/bug_reports.html.\n--2767-- WARNING: unhandled riscv64-linux syscall: 258\n--2767-- You may be able to write your own handler.\n--2767-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2767-- Nevertheless we consider this a bug. Please report\n--2767-- it at http://valgrind.org/support/bug_reports.html.\n--2767-- WARNING: unhandled riscv64-linux syscall: 258\n--2767-- You may be able to write your own handler.\n--2767-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2767-- Nevertheless we consider this a bug. Please report\n--2767-- it at http://valgrind.org/support/bug_reports.html.\n--2767-- WARNING: unhandled riscv64-linux syscall: 258\n--2767-- You may be able to write your own handler.\n--2767-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2767-- Nevertheless we consider this a bug. Please report\n--2767-- it at http://valgrind.org/support/bug_reports.html.\n--2767-- WARNING: unhandled riscv64-linux syscall: 258\n--2767-- You may be able to write your own handler.\n--2767-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2767-- Nevertheless we consider this a bug. Please report\n--2767-- it at http://valgrind.org/support/bug_reports.html.\n--2767-- WARNING: unhandled riscv64-linux syscall: 258\n--2767-- You may be able to write your own handler.\n--2767-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2767-- Nevertheless we consider this a bug. Please report\n--2767-- it at http://valgrind.org/support/bug_reports.html.\n--2767-- WARNING: unhandled riscv64-linux syscall: 258\n--2767-- You may be able to write your own handler.\n--2767-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2767-- Nevertheless we consider this a bug. Please report\n--2767-- it at http://valgrind.org/support/bug_reports.html.\n--2767-- WARNING: unhandled riscv64-linux syscall: 258\n--2767-- You may be able to write your own handler.\n--2767-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2767-- Nevertheless we consider this a bug. Please report\n--2767-- it at http://valgrind.org/support/bug_reports.html.\n--2767-- WARNING: unhandled riscv64-linux syscall: 258\n--2767-- You may be able to write your own handler.\n--2767-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2767-- Nevertheless we consider this a bug. Please report\n--2767-- it at http://valgrind.org/support/bug_reports.html.\n--2767-- WARNING: unhandled riscv64-linux syscall: 258\n--2767-- You may be able to write your own handler.\n--2767-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2767-- Nevertheless we consider this a bug. Please report\n--2767-- it at http://valgrind.org/support/bug_reports.html.\n--2767-- WARNING: unhandled riscv64-linux syscall: 258\n--2767-- You may be able to write your own handler.\n--2767-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2767-- Nevertheless we consider this a bug. Please report\n--2767-- it at http://valgrind.org/support/bug_reports.html.\n--2767-- WARNING: unhandled riscv64-linux syscall: 258\n--2767-- You may be able to write your own handler.\n--2767-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2767-- Nevertheless we consider this a bug. Please report\n--2767-- it at http://valgrind.org/support/bug_reports.html.\n--2767-- WARNING: unhandled riscv64-linux syscall: 258\n--2767-- You may be able to write your own handler.\n--2767-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2767-- Nevertheless we consider this a bug. Please report\n--2767-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 186: failed 'imap://us%65r:pwd;gir%41ffe@odd' --- stdout --- expected: 'imap://user:pwd;girAffe@odd/\n' got: 'imap://user:pwd;girAffe@odd/\n' --- stderr --- expected: '' got: '--2775-- WARNING: unhandled riscv64-linux syscall: 258\n--2775-- You may be able to write your own handler.\n--2775-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2775-- Nevertheless we consider this a bug. Please report\n--2775-- it at http://valgrind.org/support/bug_reports.html.\n--2775-- WARNING: unhandled riscv64-linux syscall: 258\n--2775-- You may be able to write your own handler.\n--2775-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2775-- Nevertheless we consider this a bug. Please report\n--2775-- it at http://valgrind.org/support/bug_reports.html.\n--2775-- WARNING: unhandled riscv64-linux syscall: 258\n--2775-- You may be able to write your own handler.\n--2775-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2775-- Nevertheless we consider this a bug. Please report\n--2775-- it at http://valgrind.org/support/bug_reports.html.\n--2775-- WARNING: unhandled riscv64-linux syscall: 258\n--2775-- You may be able to write your own handler.\n--2775-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2775-- Nevertheless we consider this a bug. Please report\n--2775-- it at http://valgrind.org/support/bug_reports.html.\n--2775-- WARNING: unhandled riscv64-linux syscall: 258\n--2775-- You may be able to write your own handler.\n--2775-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2775-- Nevertheless we consider this a bug. Please report\n--2775-- it at http://valgrind.org/support/bug_reports.html.\n--2775-- WARNING: unhandled riscv64-linux syscall: 258\n--2775-- You may be able to write your own handler.\n--2775-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2775-- Nevertheless we consider this a bug. Please report\n--2775-- it at http://valgrind.org/support/bug_reports.html.\n--2775-- WARNING: unhandled riscv64-linux syscall: 258\n--2775-- You may be able to write your own handler.\n--2775-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2775-- Nevertheless we consider this a bug. Please report\n--2775-- it at http://valgrind.org/support/bug_reports.html.\n--2775-- WARNING: unhandled riscv64-linux syscall: 258\n--2775-- You may be able to write your own handler.\n--2775-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2775-- Nevertheless we consider this a bug. Please report\n--2775-- it at http://valgrind.org/support/bug_reports.html.\n--2775-- WARNING: unhandled riscv64-linux syscall: 258\n--2775-- You may be able to write your own handler.\n--2775-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2775-- Nevertheless we consider this a bug. Please report\n--2775-- it at http://valgrind.org/support/bug_reports.html.\n--2775-- WARNING: unhandled riscv64-linux syscall: 258\n--2775-- You may be able to write your own handler.\n--2775-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2775-- Nevertheless we consider this a bug. Please report\n--2775-- it at http://valgrind.org/support/bug_reports.html.\n--2775-- WARNING: unhandled riscv64-linux syscall: 258\n--2775-- You may be able to write your own handler.\n--2775-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2775-- Nevertheless we consider this a bug. Please report\n--2775-- it at http://valgrind.org/support/bug_reports.html.\n--2775-- WARNING: unhandled riscv64-linux syscall: 258\n--2775-- You may be able to write your own handler.\n--2775-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2775-- Nevertheless we consider this a bug. Please report\n--2775-- it at http://valgrind.org/support/bug_reports.html.\n--2775-- WARNING: unhandled riscv64-linux syscall: 258\n--2775-- You may be able to write your own handler.\n--2775-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2775-- Nevertheless we consider this a bug. Please report\n--2775-- it at http://valgrind.org/support/bug_reports.html.\n--2775-- WARNING: unhandled riscv64-linux syscall: 258\n--2775-- You may be able to write your own handler.\n--2775-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2775-- Nevertheless we consider this a bug. Please report\n--2775-- it at http://valgrind.org/support/bug_reports.html.\n--2775-- WARNING: unhandled riscv64-linux syscall: 258\n--2775-- You may be able to write your own handler.\n--2775-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2775-- Nevertheless we consider this a bug. Please report\n--2775-- it at http://valgrind.org/support/bug_reports.html.\n--2775-- WARNING: unhandled riscv64-linux syscall: 258\n--2775-- You may be able to write your own handler.\n--2775-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2775-- Nevertheless we consider this a bug. Please report\n--2775-- it at http://valgrind.org/support/bug_reports.html.\n--2775-- WARNING: unhandled riscv64-linux syscall: 258\n--2775-- You may be able to write your own handler.\n--2775-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2775-- Nevertheless we consider this a bug. Please report\n--2775-- it at http://valgrind.org/support/bug_reports.html.\n--2775-- WARNING: unhandled riscv64-linux syscall: 258\n--2775-- You may be able to write your own handler.\n--2775-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2775-- Nevertheless we consider this a bug. Please report\n--2775-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 187: failed 'sftp://us%65r:pwd;giraffe@odd' --get '[password]' --- stdout --- expected: 'pwd;giraffe\n' got: 'pwd;giraffe\n' --- stderr --- expected: '' got: '--2783-- WARNING: unhandled riscv64-linux syscall: 258\n--2783-- You may be able to write your own handler.\n--2783-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2783-- Nevertheless we consider this a bug. Please report\n--2783-- it at http://valgrind.org/support/bug_reports.html.\n--2783-- WARNING: unhandled riscv64-linux syscall: 258\n--2783-- You may be able to write your own handler.\n--2783-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2783-- Nevertheless we consider this a bug. Please report\n--2783-- it at http://valgrind.org/support/bug_reports.html.\n--2783-- WARNING: unhandled riscv64-linux syscall: 258\n--2783-- You may be able to write your own handler.\n--2783-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2783-- Nevertheless we consider this a bug. Please report\n--2783-- it at http://valgrind.org/support/bug_reports.html.\n--2783-- WARNING: unhandled riscv64-linux syscall: 258\n--2783-- You may be able to write your own handler.\n--2783-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2783-- Nevertheless we consider this a bug. Please report\n--2783-- it at http://valgrind.org/support/bug_reports.html.\n--2783-- WARNING: unhandled riscv64-linux syscall: 258\n--2783-- You may be able to write your own handler.\n--2783-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2783-- Nevertheless we consider this a bug. Please report\n--2783-- it at http://valgrind.org/support/bug_reports.html.\n--2783-- WARNING: unhandled riscv64-linux syscall: 258\n--2783-- You may be able to write your own handler.\n--2783-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2783-- Nevertheless we consider this a bug. Please report\n--2783-- it at http://valgrind.org/support/bug_reports.html.\n--2783-- WARNING: unhandled riscv64-linux syscall: 258\n--2783-- You may be able to write your own handler.\n--2783-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2783-- Nevertheless we consider this a bug. Please report\n--2783-- it at http://valgrind.org/support/bug_reports.html.\n--2783-- WARNING: unhandled riscv64-linux syscall: 258\n--2783-- You may be able to write your own handler.\n--2783-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2783-- Nevertheless we consider this a bug. Please report\n--2783-- it at http://valgrind.org/support/bug_reports.html.\n--2783-- WARNING: unhandled riscv64-linux syscall: 258\n--2783-- You may be able to write your own handler.\n--2783-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2783-- Nevertheless we consider this a bug. Please report\n--2783-- it at http://valgrind.org/support/bug_reports.html.\n--2783-- WARNING: unhandled riscv64-linux syscall: 258\n--2783-- You may be able to write your own handler.\n--2783-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2783-- Nevertheless we consider this a bug. Please report\n--2783-- it at http://valgrind.org/support/bug_reports.html.\n--2783-- WARNING: unhandled riscv64-linux syscall: 258\n--2783-- You may be able to write your own handler.\n--2783-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2783-- Nevertheless we consider this a bug. Please report\n--2783-- it at http://valgrind.org/support/bug_reports.html.\n--2783-- WARNING: unhandled riscv64-linux syscall: 258\n--2783-- You may be able to write your own handler.\n--2783-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2783-- Nevertheless we consider this a bug. Please report\n--2783-- it at http://valgrind.org/support/bug_reports.html.\n--2783-- WARNING: unhandled riscv64-linux syscall: 258\n--2783-- You may be able to write your own handler.\n--2783-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2783-- Nevertheless we consider this a bug. Please report\n--2783-- it at http://valgrind.org/support/bug_reports.html.\n--2783-- WARNING: unhandled riscv64-linux syscall: 258\n--2783-- You may be able to write your own handler.\n--2783-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2783-- Nevertheless we consider this a bug. Please report\n--2783-- it at http://valgrind.org/support/bug_reports.html.\n--2783-- WARNING: unhandled riscv64-linux syscall: 258\n--2783-- You may be able to write your own handler.\n--2783-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2783-- Nevertheless we consider this a bug. Please report\n--2783-- it at http://valgrind.org/support/bug_reports.html.\n--2783-- WARNING: unhandled riscv64-linux syscall: 258\n--2783-- You may be able to write your own handler.\n--2783-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2783-- Nevertheless we consider this a bug. Please report\n--2783-- it at http://valgrind.org/support/bug_reports.html.\n--2783-- WARNING: unhandled riscv64-linux syscall: 258\n--2783-- You may be able to write your own handler.\n--2783-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2783-- Nevertheless we consider this a bug. Please report\n--2783-- it at http://valgrind.org/support/bug_reports.html.\n--2783-- WARNING: unhandled riscv64-linux syscall: 258\n--2783-- You may be able to write your own handler.\n--2783-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2783-- Nevertheless we consider this a bug. Please report\n--2783-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 188: failed 'sftp://us%65r:pwd;giraffe@odd' --get '[:password]' --- stdout --- expected: 'pwd%3bgiraffe\n' got: 'pwd%3bgiraffe\n' --- stderr --- expected: '' got: '--2791-- WARNING: unhandled riscv64-linux syscall: 258\n--2791-- You may be able to write your own handler.\n--2791-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2791-- Nevertheless we consider this a bug. Please report\n--2791-- it at http://valgrind.org/support/bug_reports.html.\n--2791-- WARNING: unhandled riscv64-linux syscall: 258\n--2791-- You may be able to write your own handler.\n--2791-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2791-- Nevertheless we consider this a bug. Please report\n--2791-- it at http://valgrind.org/support/bug_reports.html.\n--2791-- WARNING: unhandled riscv64-linux syscall: 258\n--2791-- You may be able to write your own handler.\n--2791-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2791-- Nevertheless we consider this a bug. Please report\n--2791-- it at http://valgrind.org/support/bug_reports.html.\n--2791-- WARNING: unhandled riscv64-linux syscall: 258\n--2791-- You may be able to write your own handler.\n--2791-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2791-- Nevertheless we consider this a bug. Please report\n--2791-- it at http://valgrind.org/support/bug_reports.html.\n--2791-- WARNING: unhandled riscv64-linux syscall: 258\n--2791-- You may be able to write your own handler.\n--2791-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2791-- Nevertheless we consider this a bug. Please report\n--2791-- it at http://valgrind.org/support/bug_reports.html.\n--2791-- WARNING: unhandled riscv64-linux syscall: 258\n--2791-- You may be able to write your own handler.\n--2791-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2791-- Nevertheless we consider this a bug. Please report\n--2791-- it at http://valgrind.org/support/bug_reports.html.\n--2791-- WARNING: unhandled riscv64-linux syscall: 258\n--2791-- You may be able to write your own handler.\n--2791-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2791-- Nevertheless we consider this a bug. Please report\n--2791-- it at http://valgrind.org/support/bug_reports.html.\n--2791-- WARNING: unhandled riscv64-linux syscall: 258\n--2791-- You may be able to write your own handler.\n--2791-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2791-- Nevertheless we consider this a bug. Please report\n--2791-- it at http://valgrind.org/support/bug_reports.html.\n--2791-- WARNING: unhandled riscv64-linux syscall: 258\n--2791-- You may be able to write your own handler.\n--2791-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2791-- Nevertheless we consider this a bug. Please report\n--2791-- it at http://valgrind.org/support/bug_reports.html.\n--2791-- WARNING: unhandled riscv64-linux syscall: 258\n--2791-- You may be able to write your own handler.\n--2791-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2791-- Nevertheless we consider this a bug. Please report\n--2791-- it at http://valgrind.org/support/bug_reports.html.\n--2791-- WARNING: unhandled riscv64-linux syscall: 258\n--2791-- You may be able to write your own handler.\n--2791-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2791-- Nevertheless we consider this a bug. Please report\n--2791-- it at http://valgrind.org/support/bug_reports.html.\n--2791-- WARNING: unhandled riscv64-linux syscall: 258\n--2791-- You may be able to write your own handler.\n--2791-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2791-- Nevertheless we consider this a bug. Please report\n--2791-- it at http://valgrind.org/support/bug_reports.html.\n--2791-- WARNING: unhandled riscv64-linux syscall: 258\n--2791-- You may be able to write your own handler.\n--2791-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2791-- Nevertheless we consider this a bug. Please report\n--2791-- it at http://valgrind.org/support/bug_reports.html.\n--2791-- WARNING: unhandled riscv64-linux syscall: 258\n--2791-- You may be able to write your own handler.\n--2791-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2791-- Nevertheless we consider this a bug. Please report\n--2791-- it at http://valgrind.org/support/bug_reports.html.\n--2791-- WARNING: unhandled riscv64-linux syscall: 258\n--2791-- You may be able to write your own handler.\n--2791-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2791-- Nevertheless we consider this a bug. Please report\n--2791-- it at http://valgrind.org/support/bug_reports.html.\n--2791-- WARNING: unhandled riscv64-linux syscall: 258\n--2791-- You may be able to write your own handler.\n--2791-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2791-- Nevertheless we consider this a bug. Please report\n--2791-- it at http://valgrind.org/support/bug_reports.html.\n--2791-- WARNING: unhandled riscv64-linux syscall: 258\n--2791-- You may be able to write your own handler.\n--2791-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2791-- Nevertheless we consider this a bug. Please report\n--2791-- it at http://valgrind.org/support/bug_reports.html.\n--2791-- WARNING: unhandled riscv64-linux syscall: 258\n--2791-- You may be able to write your own handler.\n--2791-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2791-- Nevertheless we consider this a bug. Please report\n--2791-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 189: failed --url 'http://åäö/' --punycode -s port=21 --- stdout --- expected: 'http://xn--4cab6c:21/\n' got: 'http://xn--4cab6c:21/\n' --- stderr --- expected: '' got: '--2800-- WARNING: unhandled riscv64-linux syscall: 258\n--2800-- You may be able to write your own handler.\n--2800-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2800-- Nevertheless we consider this a bug. Please report\n--2800-- it at http://valgrind.org/support/bug_reports.html.\n--2800-- WARNING: unhandled riscv64-linux syscall: 258\n--2800-- You may be able to write your own handler.\n--2800-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2800-- Nevertheless we consider this a bug. Please report\n--2800-- it at http://valgrind.org/support/bug_reports.html.\n--2800-- WARNING: unhandled riscv64-linux syscall: 258\n--2800-- You may be able to write your own handler.\n--2800-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2800-- Nevertheless we consider this a bug. Please report\n--2800-- it at http://valgrind.org/support/bug_reports.html.\n--2800-- WARNING: unhandled riscv64-linux syscall: 258\n--2800-- You may be able to write your own handler.\n--2800-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2800-- Nevertheless we consider this a bug. Please report\n--2800-- it at http://valgrind.org/support/bug_reports.html.\n--2800-- WARNING: unhandled riscv64-linux syscall: 258\n--2800-- You may be able to write your own handler.\n--2800-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2800-- Nevertheless we consider this a bug. Please report\n--2800-- it at http://valgrind.org/support/bug_reports.html.\n--2800-- WARNING: unhandled riscv64-linux syscall: 258\n--2800-- You may be able to write your own handler.\n--2800-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2800-- Nevertheless we consider this a bug. Please report\n--2800-- it at http://valgrind.org/support/bug_reports.html.\n--2800-- WARNING: unhandled riscv64-linux syscall: 258\n--2800-- You may be able to write your own handler.\n--2800-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2800-- Nevertheless we consider this a bug. Please report\n--2800-- it at http://valgrind.org/support/bug_reports.html.\n--2800-- WARNING: unhandled riscv64-linux syscall: 258\n--2800-- You may be able to write your own handler.\n--2800-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2800-- Nevertheless we consider this a bug. Please report\n--2800-- it at http://valgrind.org/support/bug_reports.html.\n--2800-- WARNING: unhandled riscv64-linux syscall: 258\n--2800-- You may be able to write your own handler.\n--2800-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2800-- Nevertheless we consider this a bug. Please report\n--2800-- it at http://valgrind.org/support/bug_reports.html.\n--2800-- WARNING: unhandled riscv64-linux syscall: 258\n--2800-- You may be able to write your own handler.\n--2800-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2800-- Nevertheless we consider this a bug. Please report\n--2800-- it at http://valgrind.org/support/bug_reports.html.\n--2800-- WARNING: unhandled riscv64-linux syscall: 258\n--2800-- You may be able to write your own handler.\n--2800-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2800-- Nevertheless we consider this a bug. Please report\n--2800-- it at http://valgrind.org/support/bug_reports.html.\n--2800-- WARNING: unhandled riscv64-linux syscall: 258\n--2800-- You may be able to write your own handler.\n--2800-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2800-- Nevertheless we consider this a bug. Please report\n--2800-- it at http://valgrind.org/support/bug_reports.html.\n--2800-- WARNING: unhandled riscv64-linux syscall: 258\n--2800-- You may be able to write your own handler.\n--2800-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2800-- Nevertheless we consider this a bug. Please report\n--2800-- it at http://valgrind.org/support/bug_reports.html.\n--2800-- WARNING: unhandled riscv64-linux syscall: 258\n--2800-- You may be able to write your own handler.\n--2800-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2800-- Nevertheless we consider this a bug. Please report\n--2800-- it at http://valgrind.org/support/bug_reports.html.\n--2800-- WARNING: unhandled riscv64-linux syscall: 258\n--2800-- You may be able to write your own handler.\n--2800-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2800-- Nevertheless we consider this a bug. Please report\n--2800-- it at http://valgrind.org/support/bug_reports.html.\n--2800-- WARNING: unhandled riscv64-linux syscall: 258\n--2800-- You may be able to write your own handler.\n--2800-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2800-- Nevertheless we consider this a bug. Please report\n--2800-- it at http://valgrind.org/support/bug_reports.html.\n--2800-- WARNING: unhandled riscv64-linux syscall: 258\n--2800-- You may be able to write your own handler.\n--2800-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2800-- Nevertheless we consider this a bug. Please report\n--2800-- it at http://valgrind.org/support/bug_reports.html.\n--2800-- WARNING: unhandled riscv64-linux syscall: 258\n--2800-- You may be able to write your own handler.\n--2800-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2800-- Nevertheless we consider this a bug. Please report\n--2800-- it at http://valgrind.org/support/bug_reports.html.\n' --- returncode --- expected: 0 got: 0 190: failed sftp://odd --set port=144 --set port=145 --- stdout --- expected: '' got: '' --- stderr --- expected: 'trurl error: duplicate --set for component port\ntrurl error: Try trurl -h for help\n' got: '--2810-- WARNING: unhandled riscv64-linux syscall: 258\n--2810-- You may be able to write your own handler.\n--2810-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2810-- Nevertheless we consider this a bug. Please report\n--2810-- it at http://valgrind.org/support/bug_reports.html.\n--2810-- WARNING: unhandled riscv64-linux syscall: 258\n--2810-- You may be able to write your own handler.\n--2810-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2810-- Nevertheless we consider this a bug. Please report\n--2810-- it at http://valgrind.org/support/bug_reports.html.\n--2810-- WARNING: unhandled riscv64-linux syscall: 258\n--2810-- You may be able to write your own handler.\n--2810-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2810-- Nevertheless we consider this a bug. Please report\n--2810-- it at http://valgrind.org/support/bug_reports.html.\n--2810-- WARNING: unhandled riscv64-linux syscall: 258\n--2810-- You may be able to write your own handler.\n--2810-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2810-- Nevertheless we consider this a bug. Please report\n--2810-- it at http://valgrind.org/support/bug_reports.html.\n--2810-- WARNING: unhandled riscv64-linux syscall: 258\n--2810-- You may be able to write your own handler.\n--2810-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2810-- Nevertheless we consider this a bug. Please report\n--2810-- it at http://valgrind.org/support/bug_reports.html.\n--2810-- WARNING: unhandled riscv64-linux syscall: 258\n--2810-- You may be able to write your own handler.\n--2810-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2810-- Nevertheless we consider this a bug. Please report\n--2810-- it at http://valgrind.org/support/bug_reports.html.\n--2810-- WARNING: unhandled riscv64-linux syscall: 258\n--2810-- You may be able to write your own handler.\n--2810-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2810-- Nevertheless we consider this a bug. Please report\n--2810-- it at http://valgrind.org/support/bug_reports.html.\n--2810-- WARNING: unhandled riscv64-linux syscall: 258\n--2810-- You may be able to write your own handler.\n--2810-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2810-- Nevertheless we consider this a bug. Please report\n--2810-- it at http://valgrind.org/support/bug_reports.html.\n--2810-- WARNING: unhandled riscv64-linux syscall: 258\n--2810-- You may be able to write your own handler.\n--2810-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2810-- Nevertheless we consider this a bug. Please report\n--2810-- it at http://valgrind.org/support/bug_reports.html.\n--2810-- WARNING: unhandled riscv64-linux syscall: 258\n--2810-- You may be able to write your own handler.\n--2810-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2810-- Nevertheless we consider this a bug. Please report\n--2810-- it at http://valgrind.org/support/bug_reports.html.\n--2810-- WARNING: unhandled riscv64-linux syscall: 258\n--2810-- You may be able to write your own handler.\n--2810-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2810-- Nevertheless we consider this a bug. Please report\n--2810-- it at http://valgrind.org/support/bug_reports.html.\n--2810-- WARNING: unhandled riscv64-linux syscall: 258\n--2810-- You may be able to write your own handler.\n--2810-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2810-- Nevertheless we consider this a bug. Please report\n--2810-- it at http://valgrind.org/support/bug_reports.html.\n--2810-- WARNING: unhandled riscv64-linux syscall: 258\n--2810-- You may be able to write your own handler.\n--2810-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2810-- Nevertheless we consider this a bug. Please report\n--2810-- it at http://valgrind.org/support/bug_reports.html.\n--2810-- WARNING: unhandled riscv64-linux syscall: 258\n--2810-- You may be able to write your own handler.\n--2810-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2810-- Nevertheless we consider this a bug. Please report\n--2810-- it at http://valgrind.org/support/bug_reports.html.\n--2810-- WARNING: unhandled riscv64-linux syscall: 258\n--2810-- You may be able to write your own handler.\n--2810-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2810-- Nevertheless we consider this a bug. Please report\n--2810-- it at http://valgrind.org/support/bug_reports.html.\n--2810-- WARNING: unhandled riscv64-linux syscall: 258\n--2810-- You may be able to write your own handler.\n--2810-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2810-- Nevertheless we consider this a bug. Please report\n--2810-- it at http://valgrind.org/support/bug_reports.html.\n--2810-- WARNING: unhandled riscv64-linux syscall: 258\n--2810-- You may be able to write your own handler.\n--2810-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2810-- Nevertheless we consider this a bug. Please report\n--2810-- it at http://valgrind.org/support/bug_reports.html.\n--2810-- WARNING: unhandled riscv64-linux syscall: 258\n--2810-- You may be able to write your own handler.\n--2810-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2810-- Nevertheless we consider this a bug. Please report\n--2810-- it at http://valgrind.org/support/bug_reports.html.\ntrurl error: duplicate --set for component port\ntrurl error: Try trurl -h for help\n' --- returncode --- expected: 5 got: 5 191: failed sftp://odd --get '[port]' --get '{port}' --- stdout --- expected: '' got: '' --- stderr --- expected: 'trurl error: only one --get is supported\ntrurl error: Try trurl -h for help\n' got: '--2818-- WARNING: unhandled riscv64-linux syscall: 258\n--2818-- You may be able to write your own handler.\n--2818-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2818-- Nevertheless we consider this a bug. Please report\n--2818-- it at http://valgrind.org/support/bug_reports.html.\n--2818-- WARNING: unhandled riscv64-linux syscall: 258\n--2818-- You may be able to write your own handler.\n--2818-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2818-- Nevertheless we consider this a bug. Please report\n--2818-- it at http://valgrind.org/support/bug_reports.html.\n--2818-- WARNING: unhandled riscv64-linux syscall: 258\n--2818-- You may be able to write your own handler.\n--2818-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2818-- Nevertheless we consider this a bug. Please report\n--2818-- it at http://valgrind.org/support/bug_reports.html.\n--2818-- WARNING: unhandled riscv64-linux syscall: 258\n--2818-- You may be able to write your own handler.\n--2818-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2818-- Nevertheless we consider this a bug. Please report\n--2818-- it at http://valgrind.org/support/bug_reports.html.\n--2818-- WARNING: unhandled riscv64-linux syscall: 258\n--2818-- You may be able to write your own handler.\n--2818-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2818-- Nevertheless we consider this a bug. Please report\n--2818-- it at http://valgrind.org/support/bug_reports.html.\n--2818-- WARNING: unhandled riscv64-linux syscall: 258\n--2818-- You may be able to write your own handler.\n--2818-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2818-- Nevertheless we consider this a bug. Please report\n--2818-- it at http://valgrind.org/support/bug_reports.html.\n--2818-- WARNING: unhandled riscv64-linux syscall: 258\n--2818-- You may be able to write your own handler.\n--2818-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2818-- Nevertheless we consider this a bug. Please report\n--2818-- it at http://valgrind.org/support/bug_reports.html.\n--2818-- WARNING: unhandled riscv64-linux syscall: 258\n--2818-- You may be able to write your own handler.\n--2818-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2818-- Nevertheless we consider this a bug. Please report\n--2818-- it at http://valgrind.org/support/bug_reports.html.\n--2818-- WARNING: unhandled riscv64-linux syscall: 258\n--2818-- You may be able to write your own handler.\n--2818-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2818-- Nevertheless we consider this a bug. Please report\n--2818-- it at http://valgrind.org/support/bug_reports.html.\n--2818-- WARNING: unhandled riscv64-linux syscall: 258\n--2818-- You may be able to write your own handler.\n--2818-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2818-- Nevertheless we consider this a bug. Please report\n--2818-- it at http://valgrind.org/support/bug_reports.html.\n--2818-- WARNING: unhandled riscv64-linux syscall: 258\n--2818-- You may be able to write your own handler.\n--2818-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2818-- Nevertheless we consider this a bug. Please report\n--2818-- it at http://valgrind.org/support/bug_reports.html.\n--2818-- WARNING: unhandled riscv64-linux syscall: 258\n--2818-- You may be able to write your own handler.\n--2818-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2818-- Nevertheless we consider this a bug. Please report\n--2818-- it at http://valgrind.org/support/bug_reports.html.\n--2818-- WARNING: unhandled riscv64-linux syscall: 258\n--2818-- You may be able to write your own handler.\n--2818-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2818-- Nevertheless we consider this a bug. Please report\n--2818-- it at http://valgrind.org/support/bug_reports.html.\n--2818-- WARNING: unhandled riscv64-linux syscall: 258\n--2818-- You may be able to write your own handler.\n--2818-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2818-- Nevertheless we consider this a bug. Please report\n--2818-- it at http://valgrind.org/support/bug_reports.html.\n--2818-- WARNING: unhandled riscv64-linux syscall: 258\n--2818-- You may be able to write your own handler.\n--2818-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2818-- Nevertheless we consider this a bug. Please report\n--2818-- it at http://valgrind.org/support/bug_reports.html.\n--2818-- WARNING: unhandled riscv64-linux syscall: 258\n--2818-- You may be able to write your own handler.\n--2818-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2818-- Nevertheless we consider this a bug. Please report\n--2818-- it at http://valgrind.org/support/bug_reports.html.\n--2818-- WARNING: unhandled riscv64-linux syscall: 258\n--2818-- You may be able to write your own handler.\n--2818-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2818-- Nevertheless we consider this a bug. Please report\n--2818-- it at http://valgrind.org/support/bug_reports.html.\n--2818-- WARNING: unhandled riscv64-linux syscall: 258\n--2818-- You may be able to write your own handler.\n--2818-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2818-- Nevertheless we consider this a bug. Please report\n--2818-- it at http://valgrind.org/support/bug_reports.html.\ntrurl error: only one --get is supported\ntrurl error: Try trurl -h for help\n' --- returncode --- expected: 4 got: 4 192: failed url -f testfiles/test0000.txt -f testfiles/test0000.txt --- stdout --- expected: '' got: '' --- returncode --- expected: 4 got: 4 --- stderr --- expected: 'trurl error: only one --url-file is supported\ntrurl error: Try trurl -h for help\n' got: '--2826-- WARNING: unhandled riscv64-linux syscall: 258\n--2826-- You may be able to write your own handler.\n--2826-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2826-- Nevertheless we consider this a bug. Please report\n--2826-- it at http://valgrind.org/support/bug_reports.html.\n--2826-- WARNING: unhandled riscv64-linux syscall: 258\n--2826-- You may be able to write your own handler.\n--2826-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2826-- Nevertheless we consider this a bug. Please report\n--2826-- it at http://valgrind.org/support/bug_reports.html.\n--2826-- WARNING: unhandled riscv64-linux syscall: 258\n--2826-- You may be able to write your own handler.\n--2826-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2826-- Nevertheless we consider this a bug. Please report\n--2826-- it at http://valgrind.org/support/bug_reports.html.\n--2826-- WARNING: unhandled riscv64-linux syscall: 258\n--2826-- You may be able to write your own handler.\n--2826-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2826-- Nevertheless we consider this a bug. Please report\n--2826-- it at http://valgrind.org/support/bug_reports.html.\n--2826-- WARNING: unhandled riscv64-linux syscall: 258\n--2826-- You may be able to write your own handler.\n--2826-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2826-- Nevertheless we consider this a bug. Please report\n--2826-- it at http://valgrind.org/support/bug_reports.html.\n--2826-- WARNING: unhandled riscv64-linux syscall: 258\n--2826-- You may be able to write your own handler.\n--2826-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2826-- Nevertheless we consider this a bug. Please report\n--2826-- it at http://valgrind.org/support/bug_reports.html.\n--2826-- WARNING: unhandled riscv64-linux syscall: 258\n--2826-- You may be able to write your own handler.\n--2826-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2826-- Nevertheless we consider this a bug. Please report\n--2826-- it at http://valgrind.org/support/bug_reports.html.\n--2826-- WARNING: unhandled riscv64-linux syscall: 258\n--2826-- You may be able to write your own handler.\n--2826-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2826-- Nevertheless we consider this a bug. Please report\n--2826-- it at http://valgrind.org/support/bug_reports.html.\n--2826-- WARNING: unhandled riscv64-linux syscall: 258\n--2826-- You may be able to write your own handler.\n--2826-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2826-- Nevertheless we consider this a bug. Please report\n--2826-- it at http://valgrind.org/support/bug_reports.html.\n--2826-- WARNING: unhandled riscv64-linux syscall: 258\n--2826-- You may be able to write your own handler.\n--2826-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2826-- Nevertheless we consider this a bug. Please report\n--2826-- it at http://valgrind.org/support/bug_reports.html.\n--2826-- WARNING: unhandled riscv64-linux syscall: 258\n--2826-- You may be able to write your own handler.\n--2826-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2826-- Nevertheless we consider this a bug. Please report\n--2826-- it at http://valgrind.org/support/bug_reports.html.\n--2826-- WARNING: unhandled riscv64-linux syscall: 258\n--2826-- You may be able to write your own handler.\n--2826-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2826-- Nevertheless we consider this a bug. Please report\n--2826-- it at http://valgrind.org/support/bug_reports.html.\n--2826-- WARNING: unhandled riscv64-linux syscall: 258\n--2826-- You may be able to write your own handler.\n--2826-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2826-- Nevertheless we consider this a bug. Please report\n--2826-- it at http://valgrind.org/support/bug_reports.html.\n--2826-- WARNING: unhandled riscv64-linux syscall: 258\n--2826-- You may be able to write your own handler.\n--2826-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2826-- Nevertheless we consider this a bug. Please report\n--2826-- it at http://valgrind.org/support/bug_reports.html.\n--2826-- WARNING: unhandled riscv64-linux syscall: 258\n--2826-- You may be able to write your own handler.\n--2826-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2826-- Nevertheless we consider this a bug. Please report\n--2826-- it at http://valgrind.org/support/bug_reports.html.\n--2826-- WARNING: unhandled riscv64-linux syscall: 258\n--2826-- You may be able to write your own handler.\n--2826-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2826-- Nevertheless we consider this a bug. Please report\n--2826-- it at http://valgrind.org/support/bug_reports.html.\n--2826-- WARNING: unhandled riscv64-linux syscall: 258\n--2826-- You may be able to write your own handler.\n--2826-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2826-- Nevertheless we consider this a bug. Please report\n--2826-- it at http://valgrind.org/support/bug_reports.html.\n--2826-- WARNING: unhandled riscv64-linux syscall: 258\n--2826-- You may be able to write your own handler.\n--2826-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2826-- Nevertheless we consider this a bug. Please report\n--2826-- it at http://valgrind.org/support/bug_reports.html.\ntrurl error: only one --url-file is supported\ntrurl error: Try trurl -h for help\n' 193: failed --url --- stdout --- expected: '' got: '' --- stderr --- expected: 'trurl error: Missing argument for --url\ntrurl error: Try trurl -h for help\n' got: '--2834-- WARNING: unhandled riscv64-linux syscall: 258\n--2834-- You may be able to write your own handler.\n--2834-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2834-- Nevertheless we consider this a bug. Please report\n--2834-- it at http://valgrind.org/support/bug_reports.html.\n--2834-- WARNING: unhandled riscv64-linux syscall: 258\n--2834-- You may be able to write your own handler.\n--2834-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2834-- Nevertheless we consider this a bug. Please report\n--2834-- it at http://valgrind.org/support/bug_reports.html.\n--2834-- WARNING: unhandled riscv64-linux syscall: 258\n--2834-- You may be able to write your own handler.\n--2834-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2834-- Nevertheless we consider this a bug. Please report\n--2834-- it at http://valgrind.org/support/bug_reports.html.\n--2834-- WARNING: unhandled riscv64-linux syscall: 258\n--2834-- You may be able to write your own handler.\n--2834-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2834-- Nevertheless we consider this a bug. Please report\n--2834-- it at http://valgrind.org/support/bug_reports.html.\n--2834-- WARNING: unhandled riscv64-linux syscall: 258\n--2834-- You may be able to write your own handler.\n--2834-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2834-- Nevertheless we consider this a bug. Please report\n--2834-- it at http://valgrind.org/support/bug_reports.html.\n--2834-- WARNING: unhandled riscv64-linux syscall: 258\n--2834-- You may be able to write your own handler.\n--2834-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2834-- Nevertheless we consider this a bug. Please report\n--2834-- it at http://valgrind.org/support/bug_reports.html.\n--2834-- WARNING: unhandled riscv64-linux syscall: 258\n--2834-- You may be able to write your own handler.\n--2834-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2834-- Nevertheless we consider this a bug. Please report\n--2834-- it at http://valgrind.org/support/bug_reports.html.\n--2834-- WARNING: unhandled riscv64-linux syscall: 258\n--2834-- You may be able to write your own handler.\n--2834-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2834-- Nevertheless we consider this a bug. Please report\n--2834-- it at http://valgrind.org/support/bug_reports.html.\n--2834-- WARNING: unhandled riscv64-linux syscall: 258\n--2834-- You may be able to write your own handler.\n--2834-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2834-- Nevertheless we consider this a bug. Please report\n--2834-- it at http://valgrind.org/support/bug_reports.html.\n--2834-- WARNING: unhandled riscv64-linux syscall: 258\n--2834-- You may be able to write your own handler.\n--2834-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2834-- Nevertheless we consider this a bug. Please report\n--2834-- it at http://valgrind.org/support/bug_reports.html.\n--2834-- WARNING: unhandled riscv64-linux syscall: 258\n--2834-- You may be able to write your own handler.\n--2834-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2834-- Nevertheless we consider this a bug. Please report\n--2834-- it at http://valgrind.org/support/bug_reports.html.\n--2834-- WARNING: unhandled riscv64-linux syscall: 258\n--2834-- You may be able to write your own handler.\n--2834-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2834-- Nevertheless we consider this a bug. Please report\n--2834-- it at http://valgrind.org/support/bug_reports.html.\n--2834-- WARNING: unhandled riscv64-linux syscall: 258\n--2834-- You may be able to write your own handler.\n--2834-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2834-- Nevertheless we consider this a bug. Please report\n--2834-- it at http://valgrind.org/support/bug_reports.html.\n--2834-- WARNING: unhandled riscv64-linux syscall: 258\n--2834-- You may be able to write your own handler.\n--2834-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2834-- Nevertheless we consider this a bug. Please report\n--2834-- it at http://valgrind.org/support/bug_reports.html.\n--2834-- WARNING: unhandled riscv64-linux syscall: 258\n--2834-- You may be able to write your own handler.\n--2834-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2834-- Nevertheless we consider this a bug. Please report\n--2834-- it at http://valgrind.org/support/bug_reports.html.\n--2834-- WARNING: unhandled riscv64-linux syscall: 258\n--2834-- You may be able to write your own handler.\n--2834-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2834-- Nevertheless we consider this a bug. Please report\n--2834-- it at http://valgrind.org/support/bug_reports.html.\n--2834-- WARNING: unhandled riscv64-linux syscall: 258\n--2834-- You may be able to write your own handler.\n--2834-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2834-- Nevertheless we consider this a bug. Please report\n--2834-- it at http://valgrind.org/support/bug_reports.html.\n--2834-- WARNING: unhandled riscv64-linux syscall: 258\n--2834-- You may be able to write your own handler.\n--2834-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2834-- Nevertheless we consider this a bug. Please report\n--2834-- it at http://valgrind.org/support/bug_reports.html.\ntrurl error: Missing argument for --url\ntrurl error: Try trurl -h for help\n' --- returncode --- expected: 3 got: 3 194: failed url --set --- stdout --- expected: '' got: '' --- stderr --- expected: 'trurl error: Missing argument for --set\ntrurl error: Try trurl -h for help\n' got: '--2842-- WARNING: unhandled riscv64-linux syscall: 258\n--2842-- You may be able to write your own handler.\n--2842-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2842-- Nevertheless we consider this a bug. Please report\n--2842-- it at http://valgrind.org/support/bug_reports.html.\n--2842-- WARNING: unhandled riscv64-linux syscall: 258\n--2842-- You may be able to write your own handler.\n--2842-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2842-- Nevertheless we consider this a bug. Please report\n--2842-- it at http://valgrind.org/support/bug_reports.html.\n--2842-- WARNING: unhandled riscv64-linux syscall: 258\n--2842-- You may be able to write your own handler.\n--2842-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2842-- Nevertheless we consider this a bug. Please report\n--2842-- it at http://valgrind.org/support/bug_reports.html.\n--2842-- WARNING: unhandled riscv64-linux syscall: 258\n--2842-- You may be able to write your own handler.\n--2842-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2842-- Nevertheless we consider this a bug. Please report\n--2842-- it at http://valgrind.org/support/bug_reports.html.\n--2842-- WARNING: unhandled riscv64-linux syscall: 258\n--2842-- You may be able to write your own handler.\n--2842-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2842-- Nevertheless we consider this a bug. Please report\n--2842-- it at http://valgrind.org/support/bug_reports.html.\n--2842-- WARNING: unhandled riscv64-linux syscall: 258\n--2842-- You may be able to write your own handler.\n--2842-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2842-- Nevertheless we consider this a bug. Please report\n--2842-- it at http://valgrind.org/support/bug_reports.html.\n--2842-- WARNING: unhandled riscv64-linux syscall: 258\n--2842-- You may be able to write your own handler.\n--2842-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2842-- Nevertheless we consider this a bug. Please report\n--2842-- it at http://valgrind.org/support/bug_reports.html.\n--2842-- WARNING: unhandled riscv64-linux syscall: 258\n--2842-- You may be able to write your own handler.\n--2842-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2842-- Nevertheless we consider this a bug. Please report\n--2842-- it at http://valgrind.org/support/bug_reports.html.\n--2842-- WARNING: unhandled riscv64-linux syscall: 258\n--2842-- You may be able to write your own handler.\n--2842-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2842-- Nevertheless we consider this a bug. Please report\n--2842-- it at http://valgrind.org/support/bug_reports.html.\n--2842-- WARNING: unhandled riscv64-linux syscall: 258\n--2842-- You may be able to write your own handler.\n--2842-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2842-- Nevertheless we consider this a bug. Please report\n--2842-- it at http://valgrind.org/support/bug_reports.html.\n--2842-- WARNING: unhandled riscv64-linux syscall: 258\n--2842-- You may be able to write your own handler.\n--2842-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2842-- Nevertheless we consider this a bug. Please report\n--2842-- it at http://valgrind.org/support/bug_reports.html.\n--2842-- WARNING: unhandled riscv64-linux syscall: 258\n--2842-- You may be able to write your own handler.\n--2842-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2842-- Nevertheless we consider this a bug. Please report\n--2842-- it at http://valgrind.org/support/bug_reports.html.\n--2842-- WARNING: unhandled riscv64-linux syscall: 258\n--2842-- You may be able to write your own handler.\n--2842-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2842-- Nevertheless we consider this a bug. Please report\n--2842-- it at http://valgrind.org/support/bug_reports.html.\n--2842-- WARNING: unhandled riscv64-linux syscall: 258\n--2842-- You may be able to write your own handler.\n--2842-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2842-- Nevertheless we consider this a bug. Please report\n--2842-- it at http://valgrind.org/support/bug_reports.html.\n--2842-- WARNING: unhandled riscv64-linux syscall: 258\n--2842-- You may be able to write your own handler.\n--2842-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2842-- Nevertheless we consider this a bug. Please report\n--2842-- it at http://valgrind.org/support/bug_reports.html.\n--2842-- WARNING: unhandled riscv64-linux syscall: 258\n--2842-- You may be able to write your own handler.\n--2842-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2842-- Nevertheless we consider this a bug. Please report\n--2842-- it at http://valgrind.org/support/bug_reports.html.\n--2842-- WARNING: unhandled riscv64-linux syscall: 258\n--2842-- You may be able to write your own handler.\n--2842-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2842-- Nevertheless we consider this a bug. Please report\n--2842-- it at http://valgrind.org/support/bug_reports.html.\n--2842-- WARNING: unhandled riscv64-linux syscall: 258\n--2842-- You may be able to write your own handler.\n--2842-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2842-- Nevertheless we consider this a bug. Please report\n--2842-- it at http://valgrind.org/support/bug_reports.html.\ntrurl error: Missing argument for --set\ntrurl error: Try trurl -h for help\n' --- returncode --- expected: 3 got: 3 195: failed url --redirect --- stdout --- expected: '' got: '' --- stderr --- expected: 'trurl error: Missing argument for --redirect\ntrurl error: Try trurl -h for help\n' got: '--2850-- WARNING: unhandled riscv64-linux syscall: 258\n--2850-- You may be able to write your own handler.\n--2850-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2850-- Nevertheless we consider this a bug. Please report\n--2850-- it at http://valgrind.org/support/bug_reports.html.\n--2850-- WARNING: unhandled riscv64-linux syscall: 258\n--2850-- You may be able to write your own handler.\n--2850-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2850-- Nevertheless we consider this a bug. Please report\n--2850-- it at http://valgrind.org/support/bug_reports.html.\n--2850-- WARNING: unhandled riscv64-linux syscall: 258\n--2850-- You may be able to write your own handler.\n--2850-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2850-- Nevertheless we consider this a bug. Please report\n--2850-- it at http://valgrind.org/support/bug_reports.html.\n--2850-- WARNING: unhandled riscv64-linux syscall: 258\n--2850-- You may be able to write your own handler.\n--2850-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2850-- Nevertheless we consider this a bug. Please report\n--2850-- it at http://valgrind.org/support/bug_reports.html.\n--2850-- WARNING: unhandled riscv64-linux syscall: 258\n--2850-- You may be able to write your own handler.\n--2850-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2850-- Nevertheless we consider this a bug. Please report\n--2850-- it at http://valgrind.org/support/bug_reports.html.\n--2850-- WARNING: unhandled riscv64-linux syscall: 258\n--2850-- You may be able to write your own handler.\n--2850-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2850-- Nevertheless we consider this a bug. Please report\n--2850-- it at http://valgrind.org/support/bug_reports.html.\n--2850-- WARNING: unhandled riscv64-linux syscall: 258\n--2850-- You may be able to write your own handler.\n--2850-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2850-- Nevertheless we consider this a bug. Please report\n--2850-- it at http://valgrind.org/support/bug_reports.html.\n--2850-- WARNING: unhandled riscv64-linux syscall: 258\n--2850-- You may be able to write your own handler.\n--2850-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2850-- Nevertheless we consider this a bug. Please report\n--2850-- it at http://valgrind.org/support/bug_reports.html.\n--2850-- WARNING: unhandled riscv64-linux syscall: 258\n--2850-- You may be able to write your own handler.\n--2850-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2850-- Nevertheless we consider this a bug. Please report\n--2850-- it at http://valgrind.org/support/bug_reports.html.\n--2850-- WARNING: unhandled riscv64-linux syscall: 258\n--2850-- You may be able to write your own handler.\n--2850-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2850-- Nevertheless we consider this a bug. Please report\n--2850-- it at http://valgrind.org/support/bug_reports.html.\n--2850-- WARNING: unhandled riscv64-linux syscall: 258\n--2850-- You may be able to write your own handler.\n--2850-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2850-- Nevertheless we consider this a bug. Please report\n--2850-- it at http://valgrind.org/support/bug_reports.html.\n--2850-- WARNING: unhandled riscv64-linux syscall: 258\n--2850-- You may be able to write your own handler.\n--2850-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2850-- Nevertheless we consider this a bug. Please report\n--2850-- it at http://valgrind.org/support/bug_reports.html.\n--2850-- WARNING: unhandled riscv64-linux syscall: 258\n--2850-- You may be able to write your own handler.\n--2850-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2850-- Nevertheless we consider this a bug. Please report\n--2850-- it at http://valgrind.org/support/bug_reports.html.\n--2850-- WARNING: unhandled riscv64-linux syscall: 258\n--2850-- You may be able to write your own handler.\n--2850-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2850-- Nevertheless we consider this a bug. Please report\n--2850-- it at http://valgrind.org/support/bug_reports.html.\n--2850-- WARNING: unhandled riscv64-linux syscall: 258\n--2850-- You may be able to write your own handler.\n--2850-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2850-- Nevertheless we consider this a bug. Please report\n--2850-- it at http://valgrind.org/support/bug_reports.html.\n--2850-- WARNING: unhandled riscv64-linux syscall: 258\n--2850-- You may be able to write your own handler.\n--2850-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2850-- Nevertheless we consider this a bug. Please report\n--2850-- it at http://valgrind.org/support/bug_reports.html.\n--2850-- WARNING: unhandled riscv64-linux syscall: 258\n--2850-- You may be able to write your own handler.\n--2850-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2850-- Nevertheless we consider this a bug. Please report\n--2850-- it at http://valgrind.org/support/bug_reports.html.\n--2850-- WARNING: unhandled riscv64-linux syscall: 258\n--2850-- You may be able to write your own handler.\n--2850-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2850-- Nevertheless we consider this a bug. Please report\n--2850-- it at http://valgrind.org/support/bug_reports.html.\ntrurl error: Missing argument for --redirect\ntrurl error: Try trurl -h for help\n' --- returncode --- expected: 3 got: 3 196: failed url --get --- stdout --- expected: '' got: '' --- stderr --- expected: 'trurl error: Missing argument for --get\ntrurl error: Try trurl -h for help\n' got: '--2858-- WARNING: unhandled riscv64-linux syscall: 258\n--2858-- You may be able to write your own handler.\n--2858-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2858-- Nevertheless we consider this a bug. Please report\n--2858-- it at http://valgrind.org/support/bug_reports.html.\n--2858-- WARNING: unhandled riscv64-linux syscall: 258\n--2858-- You may be able to write your own handler.\n--2858-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2858-- Nevertheless we consider this a bug. Please report\n--2858-- it at http://valgrind.org/support/bug_reports.html.\n--2858-- WARNING: unhandled riscv64-linux syscall: 258\n--2858-- You may be able to write your own handler.\n--2858-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2858-- Nevertheless we consider this a bug. Please report\n--2858-- it at http://valgrind.org/support/bug_reports.html.\n--2858-- WARNING: unhandled riscv64-linux syscall: 258\n--2858-- You may be able to write your own handler.\n--2858-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2858-- Nevertheless we consider this a bug. Please report\n--2858-- it at http://valgrind.org/support/bug_reports.html.\n--2858-- WARNING: unhandled riscv64-linux syscall: 258\n--2858-- You may be able to write your own handler.\n--2858-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2858-- Nevertheless we consider this a bug. Please report\n--2858-- it at http://valgrind.org/support/bug_reports.html.\n--2858-- WARNING: unhandled riscv64-linux syscall: 258\n--2858-- You may be able to write your own handler.\n--2858-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2858-- Nevertheless we consider this a bug. Please report\n--2858-- it at http://valgrind.org/support/bug_reports.html.\n--2858-- WARNING: unhandled riscv64-linux syscall: 258\n--2858-- You may be able to write your own handler.\n--2858-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2858-- Nevertheless we consider this a bug. Please report\n--2858-- it at http://valgrind.org/support/bug_reports.html.\n--2858-- WARNING: unhandled riscv64-linux syscall: 258\n--2858-- You may be able to write your own handler.\n--2858-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2858-- Nevertheless we consider this a bug. Please report\n--2858-- it at http://valgrind.org/support/bug_reports.html.\n--2858-- WARNING: unhandled riscv64-linux syscall: 258\n--2858-- You may be able to write your own handler.\n--2858-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2858-- Nevertheless we consider this a bug. Please report\n--2858-- it at http://valgrind.org/support/bug_reports.html.\n--2858-- WARNING: unhandled riscv64-linux syscall: 258\n--2858-- You may be able to write your own handler.\n--2858-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2858-- Nevertheless we consider this a bug. Please report\n--2858-- it at http://valgrind.org/support/bug_reports.html.\n--2858-- WARNING: unhandled riscv64-linux syscall: 258\n--2858-- You may be able to write your own handler.\n--2858-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2858-- Nevertheless we consider this a bug. Please report\n--2858-- it at http://valgrind.org/support/bug_reports.html.\n--2858-- WARNING: unhandled riscv64-linux syscall: 258\n--2858-- You may be able to write your own handler.\n--2858-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2858-- Nevertheless we consider this a bug. Please report\n--2858-- it at http://valgrind.org/support/bug_reports.html.\n--2858-- WARNING: unhandled riscv64-linux syscall: 258\n--2858-- You may be able to write your own handler.\n--2858-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2858-- Nevertheless we consider this a bug. Please report\n--2858-- it at http://valgrind.org/support/bug_reports.html.\n--2858-- WARNING: unhandled riscv64-linux syscall: 258\n--2858-- You may be able to write your own handler.\n--2858-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2858-- Nevertheless we consider this a bug. Please report\n--2858-- it at http://valgrind.org/support/bug_reports.html.\n--2858-- WARNING: unhandled riscv64-linux syscall: 258\n--2858-- You may be able to write your own handler.\n--2858-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2858-- Nevertheless we consider this a bug. Please report\n--2858-- it at http://valgrind.org/support/bug_reports.html.\n--2858-- WARNING: unhandled riscv64-linux syscall: 258\n--2858-- You may be able to write your own handler.\n--2858-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2858-- Nevertheless we consider this a bug. Please report\n--2858-- it at http://valgrind.org/support/bug_reports.html.\n--2858-- WARNING: unhandled riscv64-linux syscall: 258\n--2858-- You may be able to write your own handler.\n--2858-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2858-- Nevertheless we consider this a bug. Please report\n--2858-- it at http://valgrind.org/support/bug_reports.html.\n--2858-- WARNING: unhandled riscv64-linux syscall: 258\n--2858-- You may be able to write your own handler.\n--2858-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2858-- Nevertheless we consider this a bug. Please report\n--2858-- it at http://valgrind.org/support/bug_reports.html.\ntrurl error: Missing argument for --get\ntrurl error: Try trurl -h for help\n' --- returncode --- expected: 3 got: 3 197: failed url --replace --- stdout --- expected: '' got: '' --- stderr --- expected: 'trurl error: No data passed to replace component\ntrurl error: Try trurl -h for help\n' got: '--2866-- WARNING: unhandled riscv64-linux syscall: 258\n--2866-- You may be able to write your own handler.\n--2866-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2866-- Nevertheless we consider this a bug. Please report\n--2866-- it at http://valgrind.org/support/bug_reports.html.\n--2866-- WARNING: unhandled riscv64-linux syscall: 258\n--2866-- You may be able to write your own handler.\n--2866-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2866-- Nevertheless we consider this a bug. Please report\n--2866-- it at http://valgrind.org/support/bug_reports.html.\n--2866-- WARNING: unhandled riscv64-linux syscall: 258\n--2866-- You may be able to write your own handler.\n--2866-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2866-- Nevertheless we consider this a bug. Please report\n--2866-- it at http://valgrind.org/support/bug_reports.html.\n--2866-- WARNING: unhandled riscv64-linux syscall: 258\n--2866-- You may be able to write your own handler.\n--2866-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2866-- Nevertheless we consider this a bug. Please report\n--2866-- it at http://valgrind.org/support/bug_reports.html.\n--2866-- WARNING: unhandled riscv64-linux syscall: 258\n--2866-- You may be able to write your own handler.\n--2866-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2866-- Nevertheless we consider this a bug. Please report\n--2866-- it at http://valgrind.org/support/bug_reports.html.\n--2866-- WARNING: unhandled riscv64-linux syscall: 258\n--2866-- You may be able to write your own handler.\n--2866-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2866-- Nevertheless we consider this a bug. Please report\n--2866-- it at http://valgrind.org/support/bug_reports.html.\n--2866-- WARNING: unhandled riscv64-linux syscall: 258\n--2866-- You may be able to write your own handler.\n--2866-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2866-- Nevertheless we consider this a bug. Please report\n--2866-- it at http://valgrind.org/support/bug_reports.html.\n--2866-- WARNING: unhandled riscv64-linux syscall: 258\n--2866-- You may be able to write your own handler.\n--2866-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2866-- Nevertheless we consider this a bug. Please report\n--2866-- it at http://valgrind.org/support/bug_reports.html.\n--2866-- WARNING: unhandled riscv64-linux syscall: 258\n--2866-- You may be able to write your own handler.\n--2866-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2866-- Nevertheless we consider this a bug. Please report\n--2866-- it at http://valgrind.org/support/bug_reports.html.\n--2866-- WARNING: unhandled riscv64-linux syscall: 258\n--2866-- You may be able to write your own handler.\n--2866-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2866-- Nevertheless we consider this a bug. Please report\n--2866-- it at http://valgrind.org/support/bug_reports.html.\n--2866-- WARNING: unhandled riscv64-linux syscall: 258\n--2866-- You may be able to write your own handler.\n--2866-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2866-- Nevertheless we consider this a bug. Please report\n--2866-- it at http://valgrind.org/support/bug_reports.html.\n--2866-- WARNING: unhandled riscv64-linux syscall: 258\n--2866-- You may be able to write your own handler.\n--2866-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2866-- Nevertheless we consider this a bug. Please report\n--2866-- it at http://valgrind.org/support/bug_reports.html.\n--2866-- WARNING: unhandled riscv64-linux syscall: 258\n--2866-- You may be able to write your own handler.\n--2866-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2866-- Nevertheless we consider this a bug. Please report\n--2866-- it at http://valgrind.org/support/bug_reports.html.\n--2866-- WARNING: unhandled riscv64-linux syscall: 258\n--2866-- You may be able to write your own handler.\n--2866-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2866-- Nevertheless we consider this a bug. Please report\n--2866-- it at http://valgrind.org/support/bug_reports.html.\n--2866-- WARNING: unhandled riscv64-linux syscall: 258\n--2866-- You may be able to write your own handler.\n--2866-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2866-- Nevertheless we consider this a bug. Please report\n--2866-- it at http://valgrind.org/support/bug_reports.html.\n--2866-- WARNING: unhandled riscv64-linux syscall: 258\n--2866-- You may be able to write your own handler.\n--2866-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2866-- Nevertheless we consider this a bug. Please report\n--2866-- it at http://valgrind.org/support/bug_reports.html.\n--2866-- WARNING: unhandled riscv64-linux syscall: 258\n--2866-- You may be able to write your own handler.\n--2866-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2866-- Nevertheless we consider this a bug. Please report\n--2866-- it at http://valgrind.org/support/bug_reports.html.\n--2866-- WARNING: unhandled riscv64-linux syscall: 258\n--2866-- You may be able to write your own handler.\n--2866-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2866-- Nevertheless we consider this a bug. Please report\n--2866-- it at http://valgrind.org/support/bug_reports.html.\ntrurl error: No data passed to replace component\ntrurl error: Try trurl -h for help\n' --- returncode --- expected: 12 got: 12 198: failed url --replace-append --- stdout --- expected: '' got: '' --- stderr --- expected: 'trurl error: No data passed to replace component\ntrurl error: Try trurl -h for help\n' got: '--2874-- WARNING: unhandled riscv64-linux syscall: 258\n--2874-- You may be able to write your own handler.\n--2874-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2874-- Nevertheless we consider this a bug. Please report\n--2874-- it at http://valgrind.org/support/bug_reports.html.\n--2874-- WARNING: unhandled riscv64-linux syscall: 258\n--2874-- You may be able to write your own handler.\n--2874-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2874-- Nevertheless we consider this a bug. Please report\n--2874-- it at http://valgrind.org/support/bug_reports.html.\n--2874-- WARNING: unhandled riscv64-linux syscall: 258\n--2874-- You may be able to write your own handler.\n--2874-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2874-- Nevertheless we consider this a bug. Please report\n--2874-- it at http://valgrind.org/support/bug_reports.html.\n--2874-- WARNING: unhandled riscv64-linux syscall: 258\n--2874-- You may be able to write your own handler.\n--2874-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2874-- Nevertheless we consider this a bug. Please report\n--2874-- it at http://valgrind.org/support/bug_reports.html.\n--2874-- WARNING: unhandled riscv64-linux syscall: 258\n--2874-- You may be able to write your own handler.\n--2874-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2874-- Nevertheless we consider this a bug. Please report\n--2874-- it at http://valgrind.org/support/bug_reports.html.\n--2874-- WARNING: unhandled riscv64-linux syscall: 258\n--2874-- You may be able to write your own handler.\n--2874-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2874-- Nevertheless we consider this a bug. Please report\n--2874-- it at http://valgrind.org/support/bug_reports.html.\n--2874-- WARNING: unhandled riscv64-linux syscall: 258\n--2874-- You may be able to write your own handler.\n--2874-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2874-- Nevertheless we consider this a bug. Please report\n--2874-- it at http://valgrind.org/support/bug_reports.html.\n--2874-- WARNING: unhandled riscv64-linux syscall: 258\n--2874-- You may be able to write your own handler.\n--2874-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2874-- Nevertheless we consider this a bug. Please report\n--2874-- it at http://valgrind.org/support/bug_reports.html.\n--2874-- WARNING: unhandled riscv64-linux syscall: 258\n--2874-- You may be able to write your own handler.\n--2874-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2874-- Nevertheless we consider this a bug. Please report\n--2874-- it at http://valgrind.org/support/bug_reports.html.\n--2874-- WARNING: unhandled riscv64-linux syscall: 258\n--2874-- You may be able to write your own handler.\n--2874-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2874-- Nevertheless we consider this a bug. Please report\n--2874-- it at http://valgrind.org/support/bug_reports.html.\n--2874-- WARNING: unhandled riscv64-linux syscall: 258\n--2874-- You may be able to write your own handler.\n--2874-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2874-- Nevertheless we consider this a bug. Please report\n--2874-- it at http://valgrind.org/support/bug_reports.html.\n--2874-- WARNING: unhandled riscv64-linux syscall: 258\n--2874-- You may be able to write your own handler.\n--2874-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2874-- Nevertheless we consider this a bug. Please report\n--2874-- it at http://valgrind.org/support/bug_reports.html.\n--2874-- WARNING: unhandled riscv64-linux syscall: 258\n--2874-- You may be able to write your own handler.\n--2874-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2874-- Nevertheless we consider this a bug. Please report\n--2874-- it at http://valgrind.org/support/bug_reports.html.\n--2874-- WARNING: unhandled riscv64-linux syscall: 258\n--2874-- You may be able to write your own handler.\n--2874-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2874-- Nevertheless we consider this a bug. Please report\n--2874-- it at http://valgrind.org/support/bug_reports.html.\n--2874-- WARNING: unhandled riscv64-linux syscall: 258\n--2874-- You may be able to write your own handler.\n--2874-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2874-- Nevertheless we consider this a bug. Please report\n--2874-- it at http://valgrind.org/support/bug_reports.html.\n--2874-- WARNING: unhandled riscv64-linux syscall: 258\n--2874-- You may be able to write your own handler.\n--2874-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2874-- Nevertheless we consider this a bug. Please report\n--2874-- it at http://valgrind.org/support/bug_reports.html.\n--2874-- WARNING: unhandled riscv64-linux syscall: 258\n--2874-- You may be able to write your own handler.\n--2874-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2874-- Nevertheless we consider this a bug. Please report\n--2874-- it at http://valgrind.org/support/bug_reports.html.\n--2874-- WARNING: unhandled riscv64-linux syscall: 258\n--2874-- You may be able to write your own handler.\n--2874-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2874-- Nevertheless we consider this a bug. Please report\n--2874-- it at http://valgrind.org/support/bug_reports.html.\ntrurl error: No data passed to replace component\ntrurl error: Try trurl -h for help\n' --- returncode --- expected: 12 got: 12 199: failed url --append --- stdout --- expected: '' got: '' --- stderr --- expected: 'trurl error: Missing argument for --append\ntrurl error: Try trurl -h for help\n' got: '--2882-- WARNING: unhandled riscv64-linux syscall: 258\n--2882-- You may be able to write your own handler.\n--2882-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2882-- Nevertheless we consider this a bug. Please report\n--2882-- it at http://valgrind.org/support/bug_reports.html.\n--2882-- WARNING: unhandled riscv64-linux syscall: 258\n--2882-- You may be able to write your own handler.\n--2882-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2882-- Nevertheless we consider this a bug. Please report\n--2882-- it at http://valgrind.org/support/bug_reports.html.\n--2882-- WARNING: unhandled riscv64-linux syscall: 258\n--2882-- You may be able to write your own handler.\n--2882-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2882-- Nevertheless we consider this a bug. Please report\n--2882-- it at http://valgrind.org/support/bug_reports.html.\n--2882-- WARNING: unhandled riscv64-linux syscall: 258\n--2882-- You may be able to write your own handler.\n--2882-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2882-- Nevertheless we consider this a bug. Please report\n--2882-- it at http://valgrind.org/support/bug_reports.html.\n--2882-- WARNING: unhandled riscv64-linux syscall: 258\n--2882-- You may be able to write your own handler.\n--2882-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2882-- Nevertheless we consider this a bug. Please report\n--2882-- it at http://valgrind.org/support/bug_reports.html.\n--2882-- WARNING: unhandled riscv64-linux syscall: 258\n--2882-- You may be able to write your own handler.\n--2882-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2882-- Nevertheless we consider this a bug. Please report\n--2882-- it at http://valgrind.org/support/bug_reports.html.\n--2882-- WARNING: unhandled riscv64-linux syscall: 258\n--2882-- You may be able to write your own handler.\n--2882-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2882-- Nevertheless we consider this a bug. Please report\n--2882-- it at http://valgrind.org/support/bug_reports.html.\n--2882-- WARNING: unhandled riscv64-linux syscall: 258\n--2882-- You may be able to write your own handler.\n--2882-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2882-- Nevertheless we consider this a bug. Please report\n--2882-- it at http://valgrind.org/support/bug_reports.html.\n--2882-- WARNING: unhandled riscv64-linux syscall: 258\n--2882-- You may be able to write your own handler.\n--2882-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2882-- Nevertheless we consider this a bug. Please report\n--2882-- it at http://valgrind.org/support/bug_reports.html.\n--2882-- WARNING: unhandled riscv64-linux syscall: 258\n--2882-- You may be able to write your own handler.\n--2882-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2882-- Nevertheless we consider this a bug. Please report\n--2882-- it at http://valgrind.org/support/bug_reports.html.\n--2882-- WARNING: unhandled riscv64-linux syscall: 258\n--2882-- You may be able to write your own handler.\n--2882-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2882-- Nevertheless we consider this a bug. Please report\n--2882-- it at http://valgrind.org/support/bug_reports.html.\n--2882-- WARNING: unhandled riscv64-linux syscall: 258\n--2882-- You may be able to write your own handler.\n--2882-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2882-- Nevertheless we consider this a bug. Please report\n--2882-- it at http://valgrind.org/support/bug_reports.html.\n--2882-- WARNING: unhandled riscv64-linux syscall: 258\n--2882-- You may be able to write your own handler.\n--2882-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2882-- Nevertheless we consider this a bug. Please report\n--2882-- it at http://valgrind.org/support/bug_reports.html.\n--2882-- WARNING: unhandled riscv64-linux syscall: 258\n--2882-- You may be able to write your own handler.\n--2882-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2882-- Nevertheless we consider this a bug. Please report\n--2882-- it at http://valgrind.org/support/bug_reports.html.\n--2882-- WARNING: unhandled riscv64-linux syscall: 258\n--2882-- You may be able to write your own handler.\n--2882-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2882-- Nevertheless we consider this a bug. Please report\n--2882-- it at http://valgrind.org/support/bug_reports.html.\n--2882-- WARNING: unhandled riscv64-linux syscall: 258\n--2882-- You may be able to write your own handler.\n--2882-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2882-- Nevertheless we consider this a bug. Please report\n--2882-- it at http://valgrind.org/support/bug_reports.html.\n--2882-- WARNING: unhandled riscv64-linux syscall: 258\n--2882-- You may be able to write your own handler.\n--2882-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2882-- Nevertheless we consider this a bug. Please report\n--2882-- it at http://valgrind.org/support/bug_reports.html.\n--2882-- WARNING: unhandled riscv64-linux syscall: 258\n--2882-- You may be able to write your own handler.\n--2882-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2882-- Nevertheless we consider this a bug. Please report\n--2882-- it at http://valgrind.org/support/bug_reports.html.\ntrurl error: Missing argument for --append\ntrurl error: Try trurl -h for help\n' --- returncode --- expected: 3 got: 3 200: failed url --query-separator ''"'"''"'"'' --- stdout --- expected: '' got: '' --- stderr --- expected: 'trurl error: only single-letter query separators are supported\ntrurl error: Try trurl -h for help\n' got: '--2890-- WARNING: unhandled riscv64-linux syscall: 258\n--2890-- You may be able to write your own handler.\n--2890-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2890-- Nevertheless we consider this a bug. Please report\n--2890-- it at http://valgrind.org/support/bug_reports.html.\n--2890-- WARNING: unhandled riscv64-linux syscall: 258\n--2890-- You may be able to write your own handler.\n--2890-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2890-- Nevertheless we consider this a bug. Please report\n--2890-- it at http://valgrind.org/support/bug_reports.html.\n--2890-- WARNING: unhandled riscv64-linux syscall: 258\n--2890-- You may be able to write your own handler.\n--2890-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2890-- Nevertheless we consider this a bug. Please report\n--2890-- it at http://valgrind.org/support/bug_reports.html.\n--2890-- WARNING: unhandled riscv64-linux syscall: 258\n--2890-- You may be able to write your own handler.\n--2890-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2890-- Nevertheless we consider this a bug. Please report\n--2890-- it at http://valgrind.org/support/bug_reports.html.\n--2890-- WARNING: unhandled riscv64-linux syscall: 258\n--2890-- You may be able to write your own handler.\n--2890-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2890-- Nevertheless we consider this a bug. Please report\n--2890-- it at http://valgrind.org/support/bug_reports.html.\n--2890-- WARNING: unhandled riscv64-linux syscall: 258\n--2890-- You may be able to write your own handler.\n--2890-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2890-- Nevertheless we consider this a bug. Please report\n--2890-- it at http://valgrind.org/support/bug_reports.html.\n--2890-- WARNING: unhandled riscv64-linux syscall: 258\n--2890-- You may be able to write your own handler.\n--2890-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2890-- Nevertheless we consider this a bug. Please report\n--2890-- it at http://valgrind.org/support/bug_reports.html.\n--2890-- WARNING: unhandled riscv64-linux syscall: 258\n--2890-- You may be able to write your own handler.\n--2890-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2890-- Nevertheless we consider this a bug. Please report\n--2890-- it at http://valgrind.org/support/bug_reports.html.\n--2890-- WARNING: unhandled riscv64-linux syscall: 258\n--2890-- You may be able to write your own handler.\n--2890-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2890-- Nevertheless we consider this a bug. Please report\n--2890-- it at http://valgrind.org/support/bug_reports.html.\n--2890-- WARNING: unhandled riscv64-linux syscall: 258\n--2890-- You may be able to write your own handler.\n--2890-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2890-- Nevertheless we consider this a bug. Please report\n--2890-- it at http://valgrind.org/support/bug_reports.html.\n--2890-- WARNING: unhandled riscv64-linux syscall: 258\n--2890-- You may be able to write your own handler.\n--2890-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2890-- Nevertheless we consider this a bug. Please report\n--2890-- it at http://valgrind.org/support/bug_reports.html.\n--2890-- WARNING: unhandled riscv64-linux syscall: 258\n--2890-- You may be able to write your own handler.\n--2890-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2890-- Nevertheless we consider this a bug. Please report\n--2890-- it at http://valgrind.org/support/bug_reports.html.\n--2890-- WARNING: unhandled riscv64-linux syscall: 258\n--2890-- You may be able to write your own handler.\n--2890-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2890-- Nevertheless we consider this a bug. Please report\n--2890-- it at http://valgrind.org/support/bug_reports.html.\n--2890-- WARNING: unhandled riscv64-linux syscall: 258\n--2890-- You may be able to write your own handler.\n--2890-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2890-- Nevertheless we consider this a bug. Please report\n--2890-- it at http://valgrind.org/support/bug_reports.html.\n--2890-- WARNING: unhandled riscv64-linux syscall: 258\n--2890-- You may be able to write your own handler.\n--2890-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2890-- Nevertheless we consider this a bug. Please report\n--2890-- it at http://valgrind.org/support/bug_reports.html.\n--2890-- WARNING: unhandled riscv64-linux syscall: 258\n--2890-- You may be able to write your own handler.\n--2890-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2890-- Nevertheless we consider this a bug. Please report\n--2890-- it at http://valgrind.org/support/bug_reports.html.\n--2890-- WARNING: unhandled riscv64-linux syscall: 258\n--2890-- You may be able to write your own handler.\n--2890-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2890-- Nevertheless we consider this a bug. Please report\n--2890-- it at http://valgrind.org/support/bug_reports.html.\n--2890-- WARNING: unhandled riscv64-linux syscall: 258\n--2890-- You may be able to write your own handler.\n--2890-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2890-- Nevertheless we consider this a bug. Please report\n--2890-- it at http://valgrind.org/support/bug_reports.html.\ntrurl error: only single-letter query separators are supported\ntrurl error: Try trurl -h for help\n' --- returncode --- expected: 4 got: 4 201: failed url --query-separator aa --- stdout --- expected: '' got: '' --- stderr --- expected: 'trurl error: only single-letter query separators are supported\ntrurl error: Try trurl -h for help\n' got: '--2898-- WARNING: unhandled riscv64-linux syscall: 258\n--2898-- You may be able to write your own handler.\n--2898-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2898-- Nevertheless we consider this a bug. Please report\n--2898-- it at http://valgrind.org/support/bug_reports.html.\n--2898-- WARNING: unhandled riscv64-linux syscall: 258\n--2898-- You may be able to write your own handler.\n--2898-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2898-- Nevertheless we consider this a bug. Please report\n--2898-- it at http://valgrind.org/support/bug_reports.html.\n--2898-- WARNING: unhandled riscv64-linux syscall: 258\n--2898-- You may be able to write your own handler.\n--2898-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2898-- Nevertheless we consider this a bug. Please report\n--2898-- it at http://valgrind.org/support/bug_reports.html.\n--2898-- WARNING: unhandled riscv64-linux syscall: 258\n--2898-- You may be able to write your own handler.\n--2898-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2898-- Nevertheless we consider this a bug. Please report\n--2898-- it at http://valgrind.org/support/bug_reports.html.\n--2898-- WARNING: unhandled riscv64-linux syscall: 258\n--2898-- You may be able to write your own handler.\n--2898-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2898-- Nevertheless we consider this a bug. Please report\n--2898-- it at http://valgrind.org/support/bug_reports.html.\n--2898-- WARNING: unhandled riscv64-linux syscall: 258\n--2898-- You may be able to write your own handler.\n--2898-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2898-- Nevertheless we consider this a bug. Please report\n--2898-- it at http://valgrind.org/support/bug_reports.html.\n--2898-- WARNING: unhandled riscv64-linux syscall: 258\n--2898-- You may be able to write your own handler.\n--2898-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2898-- Nevertheless we consider this a bug. Please report\n--2898-- it at http://valgrind.org/support/bug_reports.html.\n--2898-- WARNING: unhandled riscv64-linux syscall: 258\n--2898-- You may be able to write your own handler.\n--2898-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2898-- Nevertheless we consider this a bug. Please report\n--2898-- it at http://valgrind.org/support/bug_reports.html.\n--2898-- WARNING: unhandled riscv64-linux syscall: 258\n--2898-- You may be able to write your own handler.\n--2898-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2898-- Nevertheless we consider this a bug. Please report\n--2898-- it at http://valgrind.org/support/bug_reports.html.\n--2898-- WARNING: unhandled riscv64-linux syscall: 258\n--2898-- You may be able to write your own handler.\n--2898-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2898-- Nevertheless we consider this a bug. Please report\n--2898-- it at http://valgrind.org/support/bug_reports.html.\n--2898-- WARNING: unhandled riscv64-linux syscall: 258\n--2898-- You may be able to write your own handler.\n--2898-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2898-- Nevertheless we consider this a bug. Please report\n--2898-- it at http://valgrind.org/support/bug_reports.html.\n--2898-- WARNING: unhandled riscv64-linux syscall: 258\n--2898-- You may be able to write your own handler.\n--2898-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2898-- Nevertheless we consider this a bug. Please report\n--2898-- it at http://valgrind.org/support/bug_reports.html.\n--2898-- WARNING: unhandled riscv64-linux syscall: 258\n--2898-- You may be able to write your own handler.\n--2898-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2898-- Nevertheless we consider this a bug. Please report\n--2898-- it at http://valgrind.org/support/bug_reports.html.\n--2898-- WARNING: unhandled riscv64-linux syscall: 258\n--2898-- You may be able to write your own handler.\n--2898-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2898-- Nevertheless we consider this a bug. Please report\n--2898-- it at http://valgrind.org/support/bug_reports.html.\n--2898-- WARNING: unhandled riscv64-linux syscall: 258\n--2898-- You may be able to write your own handler.\n--2898-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2898-- Nevertheless we consider this a bug. Please report\n--2898-- it at http://valgrind.org/support/bug_reports.html.\n--2898-- WARNING: unhandled riscv64-linux syscall: 258\n--2898-- You may be able to write your own handler.\n--2898-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2898-- Nevertheless we consider this a bug. Please report\n--2898-- it at http://valgrind.org/support/bug_reports.html.\n--2898-- WARNING: unhandled riscv64-linux syscall: 258\n--2898-- You may be able to write your own handler.\n--2898-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2898-- Nevertheless we consider this a bug. Please report\n--2898-- it at http://valgrind.org/support/bug_reports.html.\n--2898-- WARNING: unhandled riscv64-linux syscall: 258\n--2898-- You may be able to write your own handler.\n--2898-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2898-- Nevertheless we consider this a bug. Please report\n--2898-- it at http://valgrind.org/support/bug_reports.html.\ntrurl error: only single-letter query separators are supported\ntrurl error: Try trurl -h for help\n' --- returncode --- expected: 4 got: 4 202: failed url --json --get '{port}' --- stdout --- expected: '' got: '' --- stderr --- expected: 'trurl error: --get is mutually exclusive with --json\ntrurl error: Try trurl -h for help\n' got: '--2906-- WARNING: unhandled riscv64-linux syscall: 258\n--2906-- You may be able to write your own handler.\n--2906-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2906-- Nevertheless we consider this a bug. Please report\n--2906-- it at http://valgrind.org/support/bug_reports.html.\n--2906-- WARNING: unhandled riscv64-linux syscall: 258\n--2906-- You may be able to write your own handler.\n--2906-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2906-- Nevertheless we consider this a bug. Please report\n--2906-- it at http://valgrind.org/support/bug_reports.html.\n--2906-- WARNING: unhandled riscv64-linux syscall: 258\n--2906-- You may be able to write your own handler.\n--2906-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2906-- Nevertheless we consider this a bug. Please report\n--2906-- it at http://valgrind.org/support/bug_reports.html.\n--2906-- WARNING: unhandled riscv64-linux syscall: 258\n--2906-- You may be able to write your own handler.\n--2906-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2906-- Nevertheless we consider this a bug. Please report\n--2906-- it at http://valgrind.org/support/bug_reports.html.\n--2906-- WARNING: unhandled riscv64-linux syscall: 258\n--2906-- You may be able to write your own handler.\n--2906-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2906-- Nevertheless we consider this a bug. Please report\n--2906-- it at http://valgrind.org/support/bug_reports.html.\n--2906-- WARNING: unhandled riscv64-linux syscall: 258\n--2906-- You may be able to write your own handler.\n--2906-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2906-- Nevertheless we consider this a bug. Please report\n--2906-- it at http://valgrind.org/support/bug_reports.html.\n--2906-- WARNING: unhandled riscv64-linux syscall: 258\n--2906-- You may be able to write your own handler.\n--2906-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2906-- Nevertheless we consider this a bug. Please report\n--2906-- it at http://valgrind.org/support/bug_reports.html.\n--2906-- WARNING: unhandled riscv64-linux syscall: 258\n--2906-- You may be able to write your own handler.\n--2906-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2906-- Nevertheless we consider this a bug. Please report\n--2906-- it at http://valgrind.org/support/bug_reports.html.\n--2906-- WARNING: unhandled riscv64-linux syscall: 258\n--2906-- You may be able to write your own handler.\n--2906-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2906-- Nevertheless we consider this a bug. Please report\n--2906-- it at http://valgrind.org/support/bug_reports.html.\n--2906-- WARNING: unhandled riscv64-linux syscall: 258\n--2906-- You may be able to write your own handler.\n--2906-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2906-- Nevertheless we consider this a bug. Please report\n--2906-- it at http://valgrind.org/support/bug_reports.html.\n--2906-- WARNING: unhandled riscv64-linux syscall: 258\n--2906-- You may be able to write your own handler.\n--2906-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2906-- Nevertheless we consider this a bug. Please report\n--2906-- it at http://valgrind.org/support/bug_reports.html.\n--2906-- WARNING: unhandled riscv64-linux syscall: 258\n--2906-- You may be able to write your own handler.\n--2906-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2906-- Nevertheless we consider this a bug. Please report\n--2906-- it at http://valgrind.org/support/bug_reports.html.\n--2906-- WARNING: unhandled riscv64-linux syscall: 258\n--2906-- You may be able to write your own handler.\n--2906-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2906-- Nevertheless we consider this a bug. Please report\n--2906-- it at http://valgrind.org/support/bug_reports.html.\n--2906-- WARNING: unhandled riscv64-linux syscall: 258\n--2906-- You may be able to write your own handler.\n--2906-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2906-- Nevertheless we consider this a bug. Please report\n--2906-- it at http://valgrind.org/support/bug_reports.html.\n--2906-- WARNING: unhandled riscv64-linux syscall: 258\n--2906-- You may be able to write your own handler.\n--2906-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2906-- Nevertheless we consider this a bug. Please report\n--2906-- it at http://valgrind.org/support/bug_reports.html.\n--2906-- WARNING: unhandled riscv64-linux syscall: 258\n--2906-- You may be able to write your own handler.\n--2906-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2906-- Nevertheless we consider this a bug. Please report\n--2906-- it at http://valgrind.org/support/bug_reports.html.\n--2906-- WARNING: unhandled riscv64-linux syscall: 258\n--2906-- You may be able to write your own handler.\n--2906-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2906-- Nevertheless we consider this a bug. Please report\n--2906-- it at http://valgrind.org/support/bug_reports.html.\n--2906-- WARNING: unhandled riscv64-linux syscall: 258\n--2906-- You may be able to write your own handler.\n--2906-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2906-- Nevertheless we consider this a bug. Please report\n--2906-- it at http://valgrind.org/support/bug_reports.html.\ntrurl error: --get is mutually exclusive with --json\ntrurl error: Try trurl -h for help\n' --- returncode --- expected: 4 got: 4 203: failed url --get '{port}' --json --- stdout --- expected: '' got: '' --- stderr --- expected: 'trurl error: --json is mutually exclusive with --get\ntrurl error: Try trurl -h for help\n' got: '--2914-- WARNING: unhandled riscv64-linux syscall: 258\n--2914-- You may be able to write your own handler.\n--2914-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2914-- Nevertheless we consider this a bug. Please report\n--2914-- it at http://valgrind.org/support/bug_reports.html.\n--2914-- WARNING: unhandled riscv64-linux syscall: 258\n--2914-- You may be able to write your own handler.\n--2914-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2914-- Nevertheless we consider this a bug. Please report\n--2914-- it at http://valgrind.org/support/bug_reports.html.\n--2914-- WARNING: unhandled riscv64-linux syscall: 258\n--2914-- You may be able to write your own handler.\n--2914-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2914-- Nevertheless we consider this a bug. Please report\n--2914-- it at http://valgrind.org/support/bug_reports.html.\n--2914-- WARNING: unhandled riscv64-linux syscall: 258\n--2914-- You may be able to write your own handler.\n--2914-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2914-- Nevertheless we consider this a bug. Please report\n--2914-- it at http://valgrind.org/support/bug_reports.html.\n--2914-- WARNING: unhandled riscv64-linux syscall: 258\n--2914-- You may be able to write your own handler.\n--2914-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2914-- Nevertheless we consider this a bug. Please report\n--2914-- it at http://valgrind.org/support/bug_reports.html.\n--2914-- WARNING: unhandled riscv64-linux syscall: 258\n--2914-- You may be able to write your own handler.\n--2914-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2914-- Nevertheless we consider this a bug. Please report\n--2914-- it at http://valgrind.org/support/bug_reports.html.\n--2914-- WARNING: unhandled riscv64-linux syscall: 258\n--2914-- You may be able to write your own handler.\n--2914-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2914-- Nevertheless we consider this a bug. Please report\n--2914-- it at http://valgrind.org/support/bug_reports.html.\n--2914-- WARNING: unhandled riscv64-linux syscall: 258\n--2914-- You may be able to write your own handler.\n--2914-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2914-- Nevertheless we consider this a bug. Please report\n--2914-- it at http://valgrind.org/support/bug_reports.html.\n--2914-- WARNING: unhandled riscv64-linux syscall: 258\n--2914-- You may be able to write your own handler.\n--2914-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2914-- Nevertheless we consider this a bug. Please report\n--2914-- it at http://valgrind.org/support/bug_reports.html.\n--2914-- WARNING: unhandled riscv64-linux syscall: 258\n--2914-- You may be able to write your own handler.\n--2914-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2914-- Nevertheless we consider this a bug. Please report\n--2914-- it at http://valgrind.org/support/bug_reports.html.\n--2914-- WARNING: unhandled riscv64-linux syscall: 258\n--2914-- You may be able to write your own handler.\n--2914-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2914-- Nevertheless we consider this a bug. Please report\n--2914-- it at http://valgrind.org/support/bug_reports.html.\n--2914-- WARNING: unhandled riscv64-linux syscall: 258\n--2914-- You may be able to write your own handler.\n--2914-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2914-- Nevertheless we consider this a bug. Please report\n--2914-- it at http://valgrind.org/support/bug_reports.html.\n--2914-- WARNING: unhandled riscv64-linux syscall: 258\n--2914-- You may be able to write your own handler.\n--2914-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2914-- Nevertheless we consider this a bug. Please report\n--2914-- it at http://valgrind.org/support/bug_reports.html.\n--2914-- WARNING: unhandled riscv64-linux syscall: 258\n--2914-- You may be able to write your own handler.\n--2914-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2914-- Nevertheless we consider this a bug. Please report\n--2914-- it at http://valgrind.org/support/bug_reports.html.\n--2914-- WARNING: unhandled riscv64-linux syscall: 258\n--2914-- You may be able to write your own handler.\n--2914-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2914-- Nevertheless we consider this a bug. Please report\n--2914-- it at http://valgrind.org/support/bug_reports.html.\n--2914-- WARNING: unhandled riscv64-linux syscall: 258\n--2914-- You may be able to write your own handler.\n--2914-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2914-- Nevertheless we consider this a bug. Please report\n--2914-- it at http://valgrind.org/support/bug_reports.html.\n--2914-- WARNING: unhandled riscv64-linux syscall: 258\n--2914-- You may be able to write your own handler.\n--2914-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2914-- Nevertheless we consider this a bug. Please report\n--2914-- it at http://valgrind.org/support/bug_reports.html.\n--2914-- WARNING: unhandled riscv64-linux syscall: 258\n--2914-- You may be able to write your own handler.\n--2914-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2914-- Nevertheless we consider this a bug. Please report\n--2914-- it at http://valgrind.org/support/bug_reports.html.\ntrurl error: --json is mutually exclusive with --get\ntrurl error: Try trurl -h for help\n' --- returncode --- expected: 4 got: 4 108: passed --verify --json ftp://example.org '' git://curl.se/ 117: passed 'imap://user:password;crazy@[ff00::1234%hello]:1234/path?a=b&c=d#fragment' --json 118: passed imap://example.com/ --get 'port: {port}, default:port: {default:port}' 119: passed http://example.com:8080/ --get 'port: {port}, default:port: {default:port}' 121: passed emanuele6://curl.se/trurl '' https://example.org 146: passed --curl --verify foo://bar Finished: Failed! - Failed: 197, Passed: 6, Skipped: 0, Total: 203 make: *** [Makefile:69: test-memory] Error 1 ==> ERROR: A failure occurred in check().  Aborting... ==> ERROR: Build failed, check /var/lib/archbuild/extra-riscv64/felix-2/build [?25h[?25h[?25hreceiving incremental file list trurl-0.16-1.1-riscv64-build.log trurl-0.16-1.1-riscv64-check.log sent 62 bytes received 21,600 bytes 43,324.00 bytes/sec total size is 1,099,353 speedup is 50.75