==> Building on centiskorch
==> Checking for remote environment...
==> Syncing package to remote host...
sending incremental file list
created directory packages/trurl
./
.SRCINFO

            616 100%    0.00kB/s    0:00:00  
            616 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

            536 100%  523.44kB/s    0:00:00  
            536 100%  523.44kB/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 3,018 bytes  received 167 bytes  6,370.00 bytes/sec
total size is 3,490  speedup is 1.10
==> Ensuring required PGP keys are present...
  -> Checking for 27EDEAF22F3ABCEB50DB9A125CC908FDB71E12C2...
==> 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-9
==> Building trurl for [extra] (riscv64)
]2;🔵 Container arch-nspawn-2977686 on centiskorch.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-9]...done
==> Making package: trurl 0.16.1-1 (Mon May 12 13:30:35 2025)
==> Retrieving sources...
  -> Downloading trurl-0.16.1.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

  8 64088    8  5191    0     0   2700      0  0:00:23  0:00:01  0:00:22  2700
100 64088  100 64088    0     0  31078      0  0:00:02  0:00:02 --:--:--  410k
  -> Downloading trurl-0.16.1.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

100   488  100   488    0     0    381      0  0:00:01  0:00:01 --:--:--   381
100   488  100   488    0     0    380      0  0:00:01  0:00:01 --:--:--     0
==> Validating source files with sha256sums...
    trurl-0.16.1.tar.gz ... Passed
    trurl-0.16.1.tar.gz.asc ... Skipped
==> Verifying source file signatures with gpg...
    trurl-0.16.1.tar.gz ... Passed
]2;🔵 Container arch-nspawn-2978912 on centiskorch.felixc.at\==> Making package: trurl 0.16.1-1 (Mon May 12 17:30:55 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.3-1     108.92 MiB
extra/valgrind      3.23.0-5      20.41 MiB

Total Installed Size:  130.51 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.1.tar.gz
  -> Found trurl-0.16.1.tar.gz.asc
==> WARNING: Skipping all source file integrity checks.
==> Extracting sources...
  -> Extracting trurl-0.16.1.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
204: passed	'e?e&&'
205: passed	'e?e&'
206: passed	'e?e&&&&&&&&&&&&&&&&&&&&&'
207: passed	'e?e&&&&&&&&&&a&&&&&&&&&&&'
Finished:
Passed! -  Failed: 0, Passed: 207, Skipped: 0, Total: 207
1: failed	example.com
--- stdout --- 
expected:
'http://example.com/\n'
got:
'http://example.com/\n'
--- stderr --- 
expected:
''
got:
'--1273-- WARNING: unhandled riscv64-linux syscall: 258\n--1273-- You may be able to write your own handler.\n--1273-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1273-- Nevertheless we consider this a bug.  Please report\n--1273-- it at http://valgrind.org/support/bug_reports.html.\n--1273-- WARNING: unhandled riscv64-linux syscall: 258\n--1273-- You may be able to write your own handler.\n--1273-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1273-- Nevertheless we consider this a bug.  Please report\n--1273-- it at http://valgrind.org/support/bug_reports.html.\n--1273-- WARNING: unhandled riscv64-linux syscall: 258\n--1273-- You may be able to write your own handler.\n--1273-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1273-- Nevertheless we consider this a bug.  Please report\n--1273-- it at http://valgrind.org/support/bug_reports.html.\n--1273-- WARNING: unhandled riscv64-linux syscall: 258\n--1273-- You may be able to write your own handler.\n--1273-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1273-- Nevertheless we consider this a bug.  Please report\n--1273-- it at http://valgrind.org/support/bug_reports.html.\n--1273-- WARNING: unhandled riscv64-linux syscall: 258\n--1273-- You may be able to write your own handler.\n--1273-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1273-- Nevertheless we consider this a bug.  Please report\n--1273-- it at http://valgrind.org/support/bug_reports.html.\n--1273-- WARNING: unhandled riscv64-linux syscall: 258\n--1273-- You may be able to write your own handler.\n--1273-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1273-- Nevertheless we consider this a bug.  Please report\n--1273-- it at http://valgrind.org/support/bug_reports.html.\n--1273-- WARNING: unhandled riscv64-linux syscall: 258\n--1273-- You may be able to write your own handler.\n--1273-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1273-- Nevertheless we consider this a bug.  Please report\n--1273-- it at http://valgrind.org/support/bug_reports.html.\n--1273-- WARNING: unhandled riscv64-linux syscall: 258\n--1273-- You may be able to write your own handler.\n--1273-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1273-- Nevertheless we consider this a bug.  Please report\n--1273-- it at http://valgrind.org/support/bug_reports.html.\n--1273-- WARNING: unhandled riscv64-linux syscall: 258\n--1273-- You may be able to write your own handler.\n--1273-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1273-- Nevertheless we consider this a bug.  Please report\n--1273-- it at http://valgrind.org/support/bug_reports.html.\n--1273-- WARNING: unhandled riscv64-linux syscall: 258\n--1273-- You may be able to write your own handler.\n--1273-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1273-- Nevertheless we consider this a bug.  Please report\n--1273-- it at http://valgrind.org/support/bug_reports.html.\n--1273-- WARNING: unhandled riscv64-linux syscall: 258\n--1273-- You may be able to write your own handler.\n--1273-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1273-- Nevertheless we consider this a bug.  Please report\n--1273-- it at http://valgrind.org/support/bug_reports.html.\n--1273-- WARNING: unhandled riscv64-linux syscall: 258\n--1273-- You may be able to write your own handler.\n--1273-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1273-- Nevertheless we consider this a bug.  Please report\n--1273-- it at http://valgrind.org/support/bug_reports.html.\n--1273-- WARNING: unhandled riscv64-linux syscall: 258\n--1273-- You may be able to write your own handler.\n--1273-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1273-- Nevertheless we consider this a bug.  Please report\n--1273-- it at http://valgrind.org/support/bug_reports.html.\n--1273-- WARNING: unhandled riscv64-linux syscall: 258\n--1273-- You may be able to write your own handler.\n--1273-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1273-- Nevertheless we consider this a bug.  Please report\n--1273-- it at http://valgrind.org/support/bug_reports.html.\n--1273-- WARNING: unhandled riscv64-linux syscall: 258\n--1273-- You may be able to write your own handler.\n--1273-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1273-- Nevertheless we consider this a bug.  Please report\n--1273-- it at http://valgrind.org/support/bug_reports.html.\n--1273-- WARNING: unhandled riscv64-linux syscall: 258\n--1273-- You may be able to write your own handler.\n--1273-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1273-- Nevertheless we consider this a bug.  Please report\n--1273-- it at http://valgrind.org/support/bug_reports.html.\n--1273-- WARNING: unhandled riscv64-linux syscall: 258\n--1273-- You may be able to write your own handler.\n--1273-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1273-- Nevertheless we consider this a bug.  Please report\n--1273-- it at http://valgrind.org/support/bug_reports.html.\n--1273-- WARNING: unhandled riscv64-linux syscall: 258\n--1273-- You may be able to write your own handler.\n--1273-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1273-- Nevertheless we consider this a bug.  Please report\n--1273-- 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:
'--1288-- WARNING: unhandled riscv64-linux syscall: 258\n--1288-- You may be able to write your own handler.\n--1288-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1288-- Nevertheless we consider this a bug.  Please report\n--1288-- it at http://valgrind.org/support/bug_reports.html.\n--1288-- WARNING: unhandled riscv64-linux syscall: 258\n--1288-- You may be able to write your own handler.\n--1288-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1288-- Nevertheless we consider this a bug.  Please report\n--1288-- it at http://valgrind.org/support/bug_reports.html.\n--1288-- WARNING: unhandled riscv64-linux syscall: 258\n--1288-- You may be able to write your own handler.\n--1288-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1288-- Nevertheless we consider this a bug.  Please report\n--1288-- it at http://valgrind.org/support/bug_reports.html.\n--1288-- WARNING: unhandled riscv64-linux syscall: 258\n--1288-- You may be able to write your own handler.\n--1288-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1288-- Nevertheless we consider this a bug.  Please report\n--1288-- it at http://valgrind.org/support/bug_reports.html.\n--1288-- WARNING: unhandled riscv64-linux syscall: 258\n--1288-- You may be able to write your own handler.\n--1288-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1288-- Nevertheless we consider this a bug.  Please report\n--1288-- it at http://valgrind.org/support/bug_reports.html.\n--1288-- WARNING: unhandled riscv64-linux syscall: 258\n--1288-- You may be able to write your own handler.\n--1288-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1288-- Nevertheless we consider this a bug.  Please report\n--1288-- it at http://valgrind.org/support/bug_reports.html.\n--1288-- WARNING: unhandled riscv64-linux syscall: 258\n--1288-- You may be able to write your own handler.\n--1288-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1288-- Nevertheless we consider this a bug.  Please report\n--1288-- it at http://valgrind.org/support/bug_reports.html.\n--1288-- WARNING: unhandled riscv64-linux syscall: 258\n--1288-- You may be able to write your own handler.\n--1288-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1288-- Nevertheless we consider this a bug.  Please report\n--1288-- it at http://valgrind.org/support/bug_reports.html.\n--1288-- WARNING: unhandled riscv64-linux syscall: 258\n--1288-- You may be able to write your own handler.\n--1288-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1288-- Nevertheless we consider this a bug.  Please report\n--1288-- it at http://valgrind.org/support/bug_reports.html.\n--1288-- WARNING: unhandled riscv64-linux syscall: 258\n--1288-- You may be able to write your own handler.\n--1288-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1288-- Nevertheless we consider this a bug.  Please report\n--1288-- it at http://valgrind.org/support/bug_reports.html.\n--1288-- WARNING: unhandled riscv64-linux syscall: 258\n--1288-- You may be able to write your own handler.\n--1288-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1288-- Nevertheless we consider this a bug.  Please report\n--1288-- it at http://valgrind.org/support/bug_reports.html.\n--1288-- WARNING: unhandled riscv64-linux syscall: 258\n--1288-- You may be able to write your own handler.\n--1288-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1288-- Nevertheless we consider this a bug.  Please report\n--1288-- it at http://valgrind.org/support/bug_reports.html.\n--1288-- WARNING: unhandled riscv64-linux syscall: 258\n--1288-- You may be able to write your own handler.\n--1288-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1288-- Nevertheless we consider this a bug.  Please report\n--1288-- it at http://valgrind.org/support/bug_reports.html.\n--1288-- WARNING: unhandled riscv64-linux syscall: 258\n--1288-- You may be able to write your own handler.\n--1288-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1288-- Nevertheless we consider this a bug.  Please report\n--1288-- it at http://valgrind.org/support/bug_reports.html.\n--1288-- WARNING: unhandled riscv64-linux syscall: 258\n--1288-- You may be able to write your own handler.\n--1288-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1288-- Nevertheless we consider this a bug.  Please report\n--1288-- it at http://valgrind.org/support/bug_reports.html.\n--1288-- WARNING: unhandled riscv64-linux syscall: 258\n--1288-- You may be able to write your own handler.\n--1288-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1288-- Nevertheless we consider this a bug.  Please report\n--1288-- it at http://valgrind.org/support/bug_reports.html.\n--1288-- WARNING: unhandled riscv64-linux syscall: 258\n--1288-- You may be able to write your own handler.\n--1288-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1288-- Nevertheless we consider this a bug.  Please report\n--1288-- it at http://valgrind.org/support/bug_reports.html.\n--1288-- WARNING: unhandled riscv64-linux syscall: 258\n--1288-- You may be able to write your own handler.\n--1288-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1288-- Nevertheless we consider this a bug.  Please report\n--1288-- 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:
'--1296-- WARNING: unhandled riscv64-linux syscall: 258\n--1296-- You may be able to write your own handler.\n--1296-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1296-- Nevertheless we consider this a bug.  Please report\n--1296-- it at http://valgrind.org/support/bug_reports.html.\n--1296-- WARNING: unhandled riscv64-linux syscall: 258\n--1296-- You may be able to write your own handler.\n--1296-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1296-- Nevertheless we consider this a bug.  Please report\n--1296-- it at http://valgrind.org/support/bug_reports.html.\n--1296-- WARNING: unhandled riscv64-linux syscall: 258\n--1296-- You may be able to write your own handler.\n--1296-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1296-- Nevertheless we consider this a bug.  Please report\n--1296-- it at http://valgrind.org/support/bug_reports.html.\n--1296-- WARNING: unhandled riscv64-linux syscall: 258\n--1296-- You may be able to write your own handler.\n--1296-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1296-- Nevertheless we consider this a bug.  Please report\n--1296-- it at http://valgrind.org/support/bug_reports.html.\n--1296-- WARNING: unhandled riscv64-linux syscall: 258\n--1296-- You may be able to write your own handler.\n--1296-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1296-- Nevertheless we consider this a bug.  Please report\n--1296-- it at http://valgrind.org/support/bug_reports.html.\n--1296-- WARNING: unhandled riscv64-linux syscall: 258\n--1296-- You may be able to write your own handler.\n--1296-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1296-- Nevertheless we consider this a bug.  Please report\n--1296-- it at http://valgrind.org/support/bug_reports.html.\n--1296-- WARNING: unhandled riscv64-linux syscall: 258\n--1296-- You may be able to write your own handler.\n--1296-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1296-- Nevertheless we consider this a bug.  Please report\n--1296-- it at http://valgrind.org/support/bug_reports.html.\n--1296-- WARNING: unhandled riscv64-linux syscall: 258\n--1296-- You may be able to write your own handler.\n--1296-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1296-- Nevertheless we consider this a bug.  Please report\n--1296-- it at http://valgrind.org/support/bug_reports.html.\n--1296-- WARNING: unhandled riscv64-linux syscall: 258\n--1296-- You may be able to write your own handler.\n--1296-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1296-- Nevertheless we consider this a bug.  Please report\n--1296-- it at http://valgrind.org/support/bug_reports.html.\n--1296-- WARNING: unhandled riscv64-linux syscall: 258\n--1296-- You may be able to write your own handler.\n--1296-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1296-- Nevertheless we consider this a bug.  Please report\n--1296-- it at http://valgrind.org/support/bug_reports.html.\n--1296-- WARNING: unhandled riscv64-linux syscall: 258\n--1296-- You may be able to write your own handler.\n--1296-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1296-- Nevertheless we consider this a bug.  Please report\n--1296-- it at http://valgrind.org/support/bug_reports.html.\n--1296-- WARNING: unhandled riscv64-linux syscall: 258\n--1296-- You may be able to write your own handler.\n--1296-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1296-- Nevertheless we consider this a bug.  Please report\n--1296-- it at http://valgrind.org/support/bug_reports.html.\n--1296-- WARNING: unhandled riscv64-linux syscall: 258\n--1296-- You may be able to write your own handler.\n--1296-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1296-- Nevertheless we consider this a bug.  Please report\n--1296-- it at http://valgrind.org/support/bug_reports.html.\n--1296-- WARNING: unhandled riscv64-linux syscall: 258\n--1296-- You may be able to write your own handler.\n--1296-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1296-- Nevertheless we consider this a bug.  Please report\n--1296-- it at http://valgrind.org/support/bug_reports.html.\n--1296-- WARNING: unhandled riscv64-linux syscall: 258\n--1296-- You may be able to write your own handler.\n--1296-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1296-- Nevertheless we consider this a bug.  Please report\n--1296-- it at http://valgrind.org/support/bug_reports.html.\n--1296-- WARNING: unhandled riscv64-linux syscall: 258\n--1296-- You may be able to write your own handler.\n--1296-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1296-- Nevertheless we consider this a bug.  Please report\n--1296-- it at http://valgrind.org/support/bug_reports.html.\n--1296-- WARNING: unhandled riscv64-linux syscall: 258\n--1296-- You may be able to write your own handler.\n--1296-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1296-- Nevertheless we consider this a bug.  Please report\n--1296-- it at http://valgrind.org/support/bug_reports.html.\n--1296-- WARNING: unhandled riscv64-linux syscall: 258\n--1296-- You may be able to write your own handler.\n--1296-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1296-- Nevertheless we consider this a bug.  Please report\n--1296-- 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:
'--1304-- WARNING: unhandled riscv64-linux syscall: 258\n--1304-- You may be able to write your own handler.\n--1304-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1304-- Nevertheless we consider this a bug.  Please report\n--1304-- it at http://valgrind.org/support/bug_reports.html.\n--1304-- WARNING: unhandled riscv64-linux syscall: 258\n--1304-- You may be able to write your own handler.\n--1304-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1304-- Nevertheless we consider this a bug.  Please report\n--1304-- it at http://valgrind.org/support/bug_reports.html.\n--1304-- WARNING: unhandled riscv64-linux syscall: 258\n--1304-- You may be able to write your own handler.\n--1304-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1304-- Nevertheless we consider this a bug.  Please report\n--1304-- it at http://valgrind.org/support/bug_reports.html.\n--1304-- WARNING: unhandled riscv64-linux syscall: 258\n--1304-- You may be able to write your own handler.\n--1304-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1304-- Nevertheless we consider this a bug.  Please report\n--1304-- it at http://valgrind.org/support/bug_reports.html.\n--1304-- WARNING: unhandled riscv64-linux syscall: 258\n--1304-- You may be able to write your own handler.\n--1304-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1304-- Nevertheless we consider this a bug.  Please report\n--1304-- it at http://valgrind.org/support/bug_reports.html.\n--1304-- WARNING: unhandled riscv64-linux syscall: 258\n--1304-- You may be able to write your own handler.\n--1304-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1304-- Nevertheless we consider this a bug.  Please report\n--1304-- it at http://valgrind.org/support/bug_reports.html.\n--1304-- WARNING: unhandled riscv64-linux syscall: 258\n--1304-- You may be able to write your own handler.\n--1304-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1304-- Nevertheless we consider this a bug.  Please report\n--1304-- it at http://valgrind.org/support/bug_reports.html.\n--1304-- WARNING: unhandled riscv64-linux syscall: 258\n--1304-- You may be able to write your own handler.\n--1304-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1304-- Nevertheless we consider this a bug.  Please report\n--1304-- it at http://valgrind.org/support/bug_reports.html.\n--1304-- WARNING: unhandled riscv64-linux syscall: 258\n--1304-- You may be able to write your own handler.\n--1304-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1304-- Nevertheless we consider this a bug.  Please report\n--1304-- it at http://valgrind.org/support/bug_reports.html.\n--1304-- WARNING: unhandled riscv64-linux syscall: 258\n--1304-- You may be able to write your own handler.\n--1304-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1304-- Nevertheless we consider this a bug.  Please report\n--1304-- it at http://valgrind.org/support/bug_reports.html.\n--1304-- WARNING: unhandled riscv64-linux syscall: 258\n--1304-- You may be able to write your own handler.\n--1304-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1304-- Nevertheless we consider this a bug.  Please report\n--1304-- it at http://valgrind.org/support/bug_reports.html.\n--1304-- WARNING: unhandled riscv64-linux syscall: 258\n--1304-- You may be able to write your own handler.\n--1304-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1304-- Nevertheless we consider this a bug.  Please report\n--1304-- it at http://valgrind.org/support/bug_reports.html.\n--1304-- WARNING: unhandled riscv64-linux syscall: 258\n--1304-- You may be able to write your own handler.\n--1304-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1304-- Nevertheless we consider this a bug.  Please report\n--1304-- it at http://valgrind.org/support/bug_reports.html.\n--1304-- WARNING: unhandled riscv64-linux syscall: 258\n--1304-- You may be able to write your own handler.\n--1304-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1304-- Nevertheless we consider this a bug.  Please report\n--1304-- it at http://valgrind.org/support/bug_reports.html.\n--1304-- WARNING: unhandled riscv64-linux syscall: 258\n--1304-- You may be able to write your own handler.\n--1304-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1304-- Nevertheless we consider this a bug.  Please report\n--1304-- it at http://valgrind.org/support/bug_reports.html.\n--1304-- WARNING: unhandled riscv64-linux syscall: 258\n--1304-- You may be able to write your own handler.\n--1304-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1304-- Nevertheless we consider this a bug.  Please report\n--1304-- it at http://valgrind.org/support/bug_reports.html.\n--1304-- WARNING: unhandled riscv64-linux syscall: 258\n--1304-- You may be able to write your own handler.\n--1304-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1304-- Nevertheless we consider this a bug.  Please report\n--1304-- it at http://valgrind.org/support/bug_reports.html.\n--1304-- WARNING: unhandled riscv64-linux syscall: 258\n--1304-- You may be able to write your own handler.\n--1304-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1304-- Nevertheless we consider this a bug.  Please report\n--1304-- it at http://valgrind.org/support/bug_reports.html.\n==1304== Conditional jump or move depends on uninitialised value(s)\n==1304==    at 0x48B7428: UnknownInlinedFun (urlapi.c:932)\n==1304==    by 0x48B7428: parseurl_and_replace.lto_priv.0 (urlapi.c:1269)\n==1304==    by 0x48BC9E5: curl_url_set (urlapi.c:1784)\n==1304==    by 0x10CB67: UnknownInlinedFun (trurl.c:1674)\n==1304==    by 0x10CB67: singleurl (trurl.c:1780)\n==1304==    by 0x109C81: main (trurl.c:2118)\n==1304== \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:
'--1312-- WARNING: unhandled riscv64-linux syscall: 258\n--1312-- You may be able to write your own handler.\n--1312-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1312-- Nevertheless we consider this a bug.  Please report\n--1312-- it at http://valgrind.org/support/bug_reports.html.\n--1312-- WARNING: unhandled riscv64-linux syscall: 258\n--1312-- You may be able to write your own handler.\n--1312-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1312-- Nevertheless we consider this a bug.  Please report\n--1312-- it at http://valgrind.org/support/bug_reports.html.\n--1312-- WARNING: unhandled riscv64-linux syscall: 258\n--1312-- You may be able to write your own handler.\n--1312-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1312-- Nevertheless we consider this a bug.  Please report\n--1312-- it at http://valgrind.org/support/bug_reports.html.\n--1312-- WARNING: unhandled riscv64-linux syscall: 258\n--1312-- You may be able to write your own handler.\n--1312-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1312-- Nevertheless we consider this a bug.  Please report\n--1312-- it at http://valgrind.org/support/bug_reports.html.\n--1312-- WARNING: unhandled riscv64-linux syscall: 258\n--1312-- You may be able to write your own handler.\n--1312-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1312-- Nevertheless we consider this a bug.  Please report\n--1312-- it at http://valgrind.org/support/bug_reports.html.\n--1312-- WARNING: unhandled riscv64-linux syscall: 258\n--1312-- You may be able to write your own handler.\n--1312-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1312-- Nevertheless we consider this a bug.  Please report\n--1312-- it at http://valgrind.org/support/bug_reports.html.\n--1312-- WARNING: unhandled riscv64-linux syscall: 258\n--1312-- You may be able to write your own handler.\n--1312-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1312-- Nevertheless we consider this a bug.  Please report\n--1312-- it at http://valgrind.org/support/bug_reports.html.\n--1312-- WARNING: unhandled riscv64-linux syscall: 258\n--1312-- You may be able to write your own handler.\n--1312-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1312-- Nevertheless we consider this a bug.  Please report\n--1312-- it at http://valgrind.org/support/bug_reports.html.\n--1312-- WARNING: unhandled riscv64-linux syscall: 258\n--1312-- You may be able to write your own handler.\n--1312-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1312-- Nevertheless we consider this a bug.  Please report\n--1312-- it at http://valgrind.org/support/bug_reports.html.\n--1312-- WARNING: unhandled riscv64-linux syscall: 258\n--1312-- You may be able to write your own handler.\n--1312-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1312-- Nevertheless we consider this a bug.  Please report\n--1312-- it at http://valgrind.org/support/bug_reports.html.\n--1312-- WARNING: unhandled riscv64-linux syscall: 258\n--1312-- You may be able to write your own handler.\n--1312-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1312-- Nevertheless we consider this a bug.  Please report\n--1312-- it at http://valgrind.org/support/bug_reports.html.\n--1312-- WARNING: unhandled riscv64-linux syscall: 258\n--1312-- You may be able to write your own handler.\n--1312-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1312-- Nevertheless we consider this a bug.  Please report\n--1312-- it at http://valgrind.org/support/bug_reports.html.\n--1312-- WARNING: unhandled riscv64-linux syscall: 258\n--1312-- You may be able to write your own handler.\n--1312-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1312-- Nevertheless we consider this a bug.  Please report\n--1312-- it at http://valgrind.org/support/bug_reports.html.\n--1312-- WARNING: unhandled riscv64-linux syscall: 258\n--1312-- You may be able to write your own handler.\n--1312-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1312-- Nevertheless we consider this a bug.  Please report\n--1312-- it at http://valgrind.org/support/bug_reports.html.\n--1312-- WARNING: unhandled riscv64-linux syscall: 258\n--1312-- You may be able to write your own handler.\n--1312-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1312-- Nevertheless we consider this a bug.  Please report\n--1312-- it at http://valgrind.org/support/bug_reports.html.\n--1312-- WARNING: unhandled riscv64-linux syscall: 258\n--1312-- You may be able to write your own handler.\n--1312-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1312-- Nevertheless we consider this a bug.  Please report\n--1312-- it at http://valgrind.org/support/bug_reports.html.\n--1312-- WARNING: unhandled riscv64-linux syscall: 258\n--1312-- You may be able to write your own handler.\n--1312-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1312-- Nevertheless we consider this a bug.  Please report\n--1312-- it at http://valgrind.org/support/bug_reports.html.\n--1312-- WARNING: unhandled riscv64-linux syscall: 258\n--1312-- You may be able to write your own handler.\n--1312-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1312-- Nevertheless we consider this a bug.  Please report\n--1312-- 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:
'--1320-- WARNING: unhandled riscv64-linux syscall: 258\n--1320-- You may be able to write your own handler.\n--1320-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1320-- Nevertheless we consider this a bug.  Please report\n--1320-- it at http://valgrind.org/support/bug_reports.html.\n--1320-- WARNING: unhandled riscv64-linux syscall: 258\n--1320-- You may be able to write your own handler.\n--1320-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1320-- Nevertheless we consider this a bug.  Please report\n--1320-- it at http://valgrind.org/support/bug_reports.html.\n--1320-- WARNING: unhandled riscv64-linux syscall: 258\n--1320-- You may be able to write your own handler.\n--1320-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1320-- Nevertheless we consider this a bug.  Please report\n--1320-- it at http://valgrind.org/support/bug_reports.html.\n--1320-- WARNING: unhandled riscv64-linux syscall: 258\n--1320-- You may be able to write your own handler.\n--1320-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1320-- Nevertheless we consider this a bug.  Please report\n--1320-- it at http://valgrind.org/support/bug_reports.html.\n--1320-- WARNING: unhandled riscv64-linux syscall: 258\n--1320-- You may be able to write your own handler.\n--1320-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1320-- Nevertheless we consider this a bug.  Please report\n--1320-- it at http://valgrind.org/support/bug_reports.html.\n--1320-- WARNING: unhandled riscv64-linux syscall: 258\n--1320-- You may be able to write your own handler.\n--1320-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1320-- Nevertheless we consider this a bug.  Please report\n--1320-- it at http://valgrind.org/support/bug_reports.html.\n--1320-- WARNING: unhandled riscv64-linux syscall: 258\n--1320-- You may be able to write your own handler.\n--1320-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1320-- Nevertheless we consider this a bug.  Please report\n--1320-- it at http://valgrind.org/support/bug_reports.html.\n--1320-- WARNING: unhandled riscv64-linux syscall: 258\n--1320-- You may be able to write your own handler.\n--1320-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1320-- Nevertheless we consider this a bug.  Please report\n--1320-- it at http://valgrind.org/support/bug_reports.html.\n--1320-- WARNING: unhandled riscv64-linux syscall: 258\n--1320-- You may be able to write your own handler.\n--1320-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1320-- Nevertheless we consider this a bug.  Please report\n--1320-- it at http://valgrind.org/support/bug_reports.html.\n--1320-- WARNING: unhandled riscv64-linux syscall: 258\n--1320-- You may be able to write your own handler.\n--1320-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1320-- Nevertheless we consider this a bug.  Please report\n--1320-- it at http://valgrind.org/support/bug_reports.html.\n--1320-- WARNING: unhandled riscv64-linux syscall: 258\n--1320-- You may be able to write your own handler.\n--1320-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1320-- Nevertheless we consider this a bug.  Please report\n--1320-- it at http://valgrind.org/support/bug_reports.html.\n--1320-- WARNING: unhandled riscv64-linux syscall: 258\n--1320-- You may be able to write your own handler.\n--1320-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1320-- Nevertheless we consider this a bug.  Please report\n--1320-- it at http://valgrind.org/support/bug_reports.html.\n--1320-- WARNING: unhandled riscv64-linux syscall: 258\n--1320-- You may be able to write your own handler.\n--1320-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1320-- Nevertheless we consider this a bug.  Please report\n--1320-- it at http://valgrind.org/support/bug_reports.html.\n--1320-- WARNING: unhandled riscv64-linux syscall: 258\n--1320-- You may be able to write your own handler.\n--1320-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1320-- Nevertheless we consider this a bug.  Please report\n--1320-- it at http://valgrind.org/support/bug_reports.html.\n--1320-- WARNING: unhandled riscv64-linux syscall: 258\n--1320-- You may be able to write your own handler.\n--1320-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1320-- Nevertheless we consider this a bug.  Please report\n--1320-- it at http://valgrind.org/support/bug_reports.html.\n--1320-- WARNING: unhandled riscv64-linux syscall: 258\n--1320-- You may be able to write your own handler.\n--1320-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1320-- Nevertheless we consider this a bug.  Please report\n--1320-- it at http://valgrind.org/support/bug_reports.html.\n--1320-- WARNING: unhandled riscv64-linux syscall: 258\n--1320-- You may be able to write your own handler.\n--1320-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1320-- Nevertheless we consider this a bug.  Please report\n--1320-- it at http://valgrind.org/support/bug_reports.html.\n--1320-- WARNING: unhandled riscv64-linux syscall: 258\n--1320-- You may be able to write your own handler.\n--1320-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1320-- Nevertheless we consider this a bug.  Please report\n--1320-- 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:
'--1328-- WARNING: unhandled riscv64-linux syscall: 258\n--1328-- You may be able to write your own handler.\n--1328-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1328-- Nevertheless we consider this a bug.  Please report\n--1328-- it at http://valgrind.org/support/bug_reports.html.\n--1328-- WARNING: unhandled riscv64-linux syscall: 258\n--1328-- You may be able to write your own handler.\n--1328-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1328-- Nevertheless we consider this a bug.  Please report\n--1328-- it at http://valgrind.org/support/bug_reports.html.\n--1328-- WARNING: unhandled riscv64-linux syscall: 258\n--1328-- You may be able to write your own handler.\n--1328-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1328-- Nevertheless we consider this a bug.  Please report\n--1328-- it at http://valgrind.org/support/bug_reports.html.\n--1328-- WARNING: unhandled riscv64-linux syscall: 258\n--1328-- You may be able to write your own handler.\n--1328-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1328-- Nevertheless we consider this a bug.  Please report\n--1328-- it at http://valgrind.org/support/bug_reports.html.\n--1328-- WARNING: unhandled riscv64-linux syscall: 258\n--1328-- You may be able to write your own handler.\n--1328-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1328-- Nevertheless we consider this a bug.  Please report\n--1328-- it at http://valgrind.org/support/bug_reports.html.\n--1328-- WARNING: unhandled riscv64-linux syscall: 258\n--1328-- You may be able to write your own handler.\n--1328-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1328-- Nevertheless we consider this a bug.  Please report\n--1328-- it at http://valgrind.org/support/bug_reports.html.\n--1328-- WARNING: unhandled riscv64-linux syscall: 258\n--1328-- You may be able to write your own handler.\n--1328-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1328-- Nevertheless we consider this a bug.  Please report\n--1328-- it at http://valgrind.org/support/bug_reports.html.\n--1328-- WARNING: unhandled riscv64-linux syscall: 258\n--1328-- You may be able to write your own handler.\n--1328-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1328-- Nevertheless we consider this a bug.  Please report\n--1328-- it at http://valgrind.org/support/bug_reports.html.\n--1328-- WARNING: unhandled riscv64-linux syscall: 258\n--1328-- You may be able to write your own handler.\n--1328-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1328-- Nevertheless we consider this a bug.  Please report\n--1328-- it at http://valgrind.org/support/bug_reports.html.\n--1328-- WARNING: unhandled riscv64-linux syscall: 258\n--1328-- You may be able to write your own handler.\n--1328-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1328-- Nevertheless we consider this a bug.  Please report\n--1328-- it at http://valgrind.org/support/bug_reports.html.\n--1328-- WARNING: unhandled riscv64-linux syscall: 258\n--1328-- You may be able to write your own handler.\n--1328-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1328-- Nevertheless we consider this a bug.  Please report\n--1328-- it at http://valgrind.org/support/bug_reports.html.\n--1328-- WARNING: unhandled riscv64-linux syscall: 258\n--1328-- You may be able to write your own handler.\n--1328-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1328-- Nevertheless we consider this a bug.  Please report\n--1328-- it at http://valgrind.org/support/bug_reports.html.\n--1328-- WARNING: unhandled riscv64-linux syscall: 258\n--1328-- You may be able to write your own handler.\n--1328-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1328-- Nevertheless we consider this a bug.  Please report\n--1328-- it at http://valgrind.org/support/bug_reports.html.\n--1328-- WARNING: unhandled riscv64-linux syscall: 258\n--1328-- You may be able to write your own handler.\n--1328-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1328-- Nevertheless we consider this a bug.  Please report\n--1328-- it at http://valgrind.org/support/bug_reports.html.\n--1328-- WARNING: unhandled riscv64-linux syscall: 258\n--1328-- You may be able to write your own handler.\n--1328-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1328-- Nevertheless we consider this a bug.  Please report\n--1328-- it at http://valgrind.org/support/bug_reports.html.\n--1328-- WARNING: unhandled riscv64-linux syscall: 258\n--1328-- You may be able to write your own handler.\n--1328-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1328-- Nevertheless we consider this a bug.  Please report\n--1328-- it at http://valgrind.org/support/bug_reports.html.\n--1328-- WARNING: unhandled riscv64-linux syscall: 258\n--1328-- You may be able to write your own handler.\n--1328-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1328-- Nevertheless we consider this a bug.  Please report\n--1328-- it at http://valgrind.org/support/bug_reports.html.\n--1328-- WARNING: unhandled riscv64-linux syscall: 258\n--1328-- You may be able to write your own handler.\n--1328-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1328-- Nevertheless we consider this a bug.  Please report\n--1328-- 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:
'--1336-- WARNING: unhandled riscv64-linux syscall: 258\n--1336-- You may be able to write your own handler.\n--1336-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1336-- Nevertheless we consider this a bug.  Please report\n--1336-- it at http://valgrind.org/support/bug_reports.html.\n--1336-- WARNING: unhandled riscv64-linux syscall: 258\n--1336-- You may be able to write your own handler.\n--1336-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1336-- Nevertheless we consider this a bug.  Please report\n--1336-- it at http://valgrind.org/support/bug_reports.html.\n--1336-- WARNING: unhandled riscv64-linux syscall: 258\n--1336-- You may be able to write your own handler.\n--1336-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1336-- Nevertheless we consider this a bug.  Please report\n--1336-- it at http://valgrind.org/support/bug_reports.html.\n--1336-- WARNING: unhandled riscv64-linux syscall: 258\n--1336-- You may be able to write your own handler.\n--1336-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1336-- Nevertheless we consider this a bug.  Please report\n--1336-- it at http://valgrind.org/support/bug_reports.html.\n--1336-- WARNING: unhandled riscv64-linux syscall: 258\n--1336-- You may be able to write your own handler.\n--1336-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1336-- Nevertheless we consider this a bug.  Please report\n--1336-- it at http://valgrind.org/support/bug_reports.html.\n--1336-- WARNING: unhandled riscv64-linux syscall: 258\n--1336-- You may be able to write your own handler.\n--1336-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1336-- Nevertheless we consider this a bug.  Please report\n--1336-- it at http://valgrind.org/support/bug_reports.html.\n--1336-- WARNING: unhandled riscv64-linux syscall: 258\n--1336-- You may be able to write your own handler.\n--1336-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1336-- Nevertheless we consider this a bug.  Please report\n--1336-- it at http://valgrind.org/support/bug_reports.html.\n--1336-- WARNING: unhandled riscv64-linux syscall: 258\n--1336-- You may be able to write your own handler.\n--1336-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1336-- Nevertheless we consider this a bug.  Please report\n--1336-- it at http://valgrind.org/support/bug_reports.html.\n--1336-- WARNING: unhandled riscv64-linux syscall: 258\n--1336-- You may be able to write your own handler.\n--1336-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1336-- Nevertheless we consider this a bug.  Please report\n--1336-- it at http://valgrind.org/support/bug_reports.html.\n--1336-- WARNING: unhandled riscv64-linux syscall: 258\n--1336-- You may be able to write your own handler.\n--1336-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1336-- Nevertheless we consider this a bug.  Please report\n--1336-- it at http://valgrind.org/support/bug_reports.html.\n--1336-- WARNING: unhandled riscv64-linux syscall: 258\n--1336-- You may be able to write your own handler.\n--1336-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1336-- Nevertheless we consider this a bug.  Please report\n--1336-- it at http://valgrind.org/support/bug_reports.html.\n--1336-- WARNING: unhandled riscv64-linux syscall: 258\n--1336-- You may be able to write your own handler.\n--1336-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1336-- Nevertheless we consider this a bug.  Please report\n--1336-- it at http://valgrind.org/support/bug_reports.html.\n--1336-- WARNING: unhandled riscv64-linux syscall: 258\n--1336-- You may be able to write your own handler.\n--1336-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1336-- Nevertheless we consider this a bug.  Please report\n--1336-- it at http://valgrind.org/support/bug_reports.html.\n--1336-- WARNING: unhandled riscv64-linux syscall: 258\n--1336-- You may be able to write your own handler.\n--1336-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1336-- Nevertheless we consider this a bug.  Please report\n--1336-- it at http://valgrind.org/support/bug_reports.html.\n--1336-- WARNING: unhandled riscv64-linux syscall: 258\n--1336-- You may be able to write your own handler.\n--1336-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1336-- Nevertheless we consider this a bug.  Please report\n--1336-- it at http://valgrind.org/support/bug_reports.html.\n--1336-- WARNING: unhandled riscv64-linux syscall: 258\n--1336-- You may be able to write your own handler.\n--1336-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1336-- Nevertheless we consider this a bug.  Please report\n--1336-- it at http://valgrind.org/support/bug_reports.html.\n--1336-- WARNING: unhandled riscv64-linux syscall: 258\n--1336-- You may be able to write your own handler.\n--1336-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1336-- Nevertheless we consider this a bug.  Please report\n--1336-- it at http://valgrind.org/support/bug_reports.html.\n--1336-- WARNING: unhandled riscv64-linux syscall: 258\n--1336-- You may be able to write your own handler.\n--1336-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1336-- Nevertheless we consider this a bug.  Please report\n--1336-- 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:
'--1344-- WARNING: unhandled riscv64-linux syscall: 258\n--1344-- You may be able to write your own handler.\n--1344-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1344-- Nevertheless we consider this a bug.  Please report\n--1344-- it at http://valgrind.org/support/bug_reports.html.\n--1344-- WARNING: unhandled riscv64-linux syscall: 258\n--1344-- You may be able to write your own handler.\n--1344-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1344-- Nevertheless we consider this a bug.  Please report\n--1344-- it at http://valgrind.org/support/bug_reports.html.\n--1344-- WARNING: unhandled riscv64-linux syscall: 258\n--1344-- You may be able to write your own handler.\n--1344-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1344-- Nevertheless we consider this a bug.  Please report\n--1344-- it at http://valgrind.org/support/bug_reports.html.\n--1344-- WARNING: unhandled riscv64-linux syscall: 258\n--1344-- You may be able to write your own handler.\n--1344-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1344-- Nevertheless we consider this a bug.  Please report\n--1344-- it at http://valgrind.org/support/bug_reports.html.\n--1344-- WARNING: unhandled riscv64-linux syscall: 258\n--1344-- You may be able to write your own handler.\n--1344-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1344-- Nevertheless we consider this a bug.  Please report\n--1344-- it at http://valgrind.org/support/bug_reports.html.\n--1344-- WARNING: unhandled riscv64-linux syscall: 258\n--1344-- You may be able to write your own handler.\n--1344-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1344-- Nevertheless we consider this a bug.  Please report\n--1344-- it at http://valgrind.org/support/bug_reports.html.\n--1344-- WARNING: unhandled riscv64-linux syscall: 258\n--1344-- You may be able to write your own handler.\n--1344-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1344-- Nevertheless we consider this a bug.  Please report\n--1344-- it at http://valgrind.org/support/bug_reports.html.\n--1344-- WARNING: unhandled riscv64-linux syscall: 258\n--1344-- You may be able to write your own handler.\n--1344-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1344-- Nevertheless we consider this a bug.  Please report\n--1344-- it at http://valgrind.org/support/bug_reports.html.\n--1344-- WARNING: unhandled riscv64-linux syscall: 258\n--1344-- You may be able to write your own handler.\n--1344-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1344-- Nevertheless we consider this a bug.  Please report\n--1344-- it at http://valgrind.org/support/bug_reports.html.\n--1344-- WARNING: unhandled riscv64-linux syscall: 258\n--1344-- You may be able to write your own handler.\n--1344-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1344-- Nevertheless we consider this a bug.  Please report\n--1344-- it at http://valgrind.org/support/bug_reports.html.\n--1344-- WARNING: unhandled riscv64-linux syscall: 258\n--1344-- You may be able to write your own handler.\n--1344-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1344-- Nevertheless we consider this a bug.  Please report\n--1344-- it at http://valgrind.org/support/bug_reports.html.\n--1344-- WARNING: unhandled riscv64-linux syscall: 258\n--1344-- You may be able to write your own handler.\n--1344-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1344-- Nevertheless we consider this a bug.  Please report\n--1344-- it at http://valgrind.org/support/bug_reports.html.\n--1344-- WARNING: unhandled riscv64-linux syscall: 258\n--1344-- You may be able to write your own handler.\n--1344-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1344-- Nevertheless we consider this a bug.  Please report\n--1344-- it at http://valgrind.org/support/bug_reports.html.\n--1344-- WARNING: unhandled riscv64-linux syscall: 258\n--1344-- You may be able to write your own handler.\n--1344-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1344-- Nevertheless we consider this a bug.  Please report\n--1344-- it at http://valgrind.org/support/bug_reports.html.\n--1344-- WARNING: unhandled riscv64-linux syscall: 258\n--1344-- You may be able to write your own handler.\n--1344-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1344-- Nevertheless we consider this a bug.  Please report\n--1344-- it at http://valgrind.org/support/bug_reports.html.\n--1344-- WARNING: unhandled riscv64-linux syscall: 258\n--1344-- You may be able to write your own handler.\n--1344-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1344-- Nevertheless we consider this a bug.  Please report\n--1344-- it at http://valgrind.org/support/bug_reports.html.\n--1344-- WARNING: unhandled riscv64-linux syscall: 258\n--1344-- You may be able to write your own handler.\n--1344-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1344-- Nevertheless we consider this a bug.  Please report\n--1344-- it at http://valgrind.org/support/bug_reports.html.\n--1344-- WARNING: unhandled riscv64-linux syscall: 258\n--1344-- You may be able to write your own handler.\n--1344-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1344-- Nevertheless we consider this a bug.  Please report\n--1344-- 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:
'--1352-- WARNING: unhandled riscv64-linux syscall: 258\n--1352-- You may be able to write your own handler.\n--1352-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1352-- Nevertheless we consider this a bug.  Please report\n--1352-- it at http://valgrind.org/support/bug_reports.html.\n--1352-- WARNING: unhandled riscv64-linux syscall: 258\n--1352-- You may be able to write your own handler.\n--1352-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1352-- Nevertheless we consider this a bug.  Please report\n--1352-- it at http://valgrind.org/support/bug_reports.html.\n--1352-- WARNING: unhandled riscv64-linux syscall: 258\n--1352-- You may be able to write your own handler.\n--1352-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1352-- Nevertheless we consider this a bug.  Please report\n--1352-- it at http://valgrind.org/support/bug_reports.html.\n--1352-- WARNING: unhandled riscv64-linux syscall: 258\n--1352-- You may be able to write your own handler.\n--1352-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1352-- Nevertheless we consider this a bug.  Please report\n--1352-- it at http://valgrind.org/support/bug_reports.html.\n--1352-- WARNING: unhandled riscv64-linux syscall: 258\n--1352-- You may be able to write your own handler.\n--1352-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1352-- Nevertheless we consider this a bug.  Please report\n--1352-- it at http://valgrind.org/support/bug_reports.html.\n--1352-- WARNING: unhandled riscv64-linux syscall: 258\n--1352-- You may be able to write your own handler.\n--1352-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1352-- Nevertheless we consider this a bug.  Please report\n--1352-- it at http://valgrind.org/support/bug_reports.html.\n--1352-- WARNING: unhandled riscv64-linux syscall: 258\n--1352-- You may be able to write your own handler.\n--1352-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1352-- Nevertheless we consider this a bug.  Please report\n--1352-- it at http://valgrind.org/support/bug_reports.html.\n--1352-- WARNING: unhandled riscv64-linux syscall: 258\n--1352-- You may be able to write your own handler.\n--1352-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1352-- Nevertheless we consider this a bug.  Please report\n--1352-- it at http://valgrind.org/support/bug_reports.html.\n--1352-- WARNING: unhandled riscv64-linux syscall: 258\n--1352-- You may be able to write your own handler.\n--1352-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1352-- Nevertheless we consider this a bug.  Please report\n--1352-- it at http://valgrind.org/support/bug_reports.html.\n--1352-- WARNING: unhandled riscv64-linux syscall: 258\n--1352-- You may be able to write your own handler.\n--1352-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1352-- Nevertheless we consider this a bug.  Please report\n--1352-- it at http://valgrind.org/support/bug_reports.html.\n--1352-- WARNING: unhandled riscv64-linux syscall: 258\n--1352-- You may be able to write your own handler.\n--1352-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1352-- Nevertheless we consider this a bug.  Please report\n--1352-- it at http://valgrind.org/support/bug_reports.html.\n--1352-- WARNING: unhandled riscv64-linux syscall: 258\n--1352-- You may be able to write your own handler.\n--1352-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1352-- Nevertheless we consider this a bug.  Please report\n--1352-- it at http://valgrind.org/support/bug_reports.html.\n--1352-- WARNING: unhandled riscv64-linux syscall: 258\n--1352-- You may be able to write your own handler.\n--1352-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1352-- Nevertheless we consider this a bug.  Please report\n--1352-- it at http://valgrind.org/support/bug_reports.html.\n--1352-- WARNING: unhandled riscv64-linux syscall: 258\n--1352-- You may be able to write your own handler.\n--1352-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1352-- Nevertheless we consider this a bug.  Please report\n--1352-- it at http://valgrind.org/support/bug_reports.html.\n--1352-- WARNING: unhandled riscv64-linux syscall: 258\n--1352-- You may be able to write your own handler.\n--1352-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1352-- Nevertheless we consider this a bug.  Please report\n--1352-- it at http://valgrind.org/support/bug_reports.html.\n--1352-- WARNING: unhandled riscv64-linux syscall: 258\n--1352-- You may be able to write your own handler.\n--1352-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1352-- Nevertheless we consider this a bug.  Please report\n--1352-- it at http://valgrind.org/support/bug_reports.html.\n--1352-- WARNING: unhandled riscv64-linux syscall: 258\n--1352-- You may be able to write your own handler.\n--1352-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1352-- Nevertheless we consider this a bug.  Please report\n--1352-- it at http://valgrind.org/support/bug_reports.html.\n--1352-- WARNING: unhandled riscv64-linux syscall: 258\n--1352-- You may be able to write your own handler.\n--1352-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1352-- Nevertheless we consider this a bug.  Please report\n--1352-- 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:
'--1360-- WARNING: unhandled riscv64-linux syscall: 258\n--1360-- You may be able to write your own handler.\n--1360-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1360-- Nevertheless we consider this a bug.  Please report\n--1360-- it at http://valgrind.org/support/bug_reports.html.\n--1360-- WARNING: unhandled riscv64-linux syscall: 258\n--1360-- You may be able to write your own handler.\n--1360-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1360-- Nevertheless we consider this a bug.  Please report\n--1360-- it at http://valgrind.org/support/bug_reports.html.\n--1360-- WARNING: unhandled riscv64-linux syscall: 258\n--1360-- You may be able to write your own handler.\n--1360-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1360-- Nevertheless we consider this a bug.  Please report\n--1360-- it at http://valgrind.org/support/bug_reports.html.\n--1360-- WARNING: unhandled riscv64-linux syscall: 258\n--1360-- You may be able to write your own handler.\n--1360-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1360-- Nevertheless we consider this a bug.  Please report\n--1360-- it at http://valgrind.org/support/bug_reports.html.\n--1360-- WARNING: unhandled riscv64-linux syscall: 258\n--1360-- You may be able to write your own handler.\n--1360-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1360-- Nevertheless we consider this a bug.  Please report\n--1360-- it at http://valgrind.org/support/bug_reports.html.\n--1360-- WARNING: unhandled riscv64-linux syscall: 258\n--1360-- You may be able to write your own handler.\n--1360-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1360-- Nevertheless we consider this a bug.  Please report\n--1360-- it at http://valgrind.org/support/bug_reports.html.\n--1360-- WARNING: unhandled riscv64-linux syscall: 258\n--1360-- You may be able to write your own handler.\n--1360-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1360-- Nevertheless we consider this a bug.  Please report\n--1360-- it at http://valgrind.org/support/bug_reports.html.\n--1360-- WARNING: unhandled riscv64-linux syscall: 258\n--1360-- You may be able to write your own handler.\n--1360-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1360-- Nevertheless we consider this a bug.  Please report\n--1360-- it at http://valgrind.org/support/bug_reports.html.\n--1360-- WARNING: unhandled riscv64-linux syscall: 258\n--1360-- You may be able to write your own handler.\n--1360-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1360-- Nevertheless we consider this a bug.  Please report\n--1360-- it at http://valgrind.org/support/bug_reports.html.\n--1360-- WARNING: unhandled riscv64-linux syscall: 258\n--1360-- You may be able to write your own handler.\n--1360-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1360-- Nevertheless we consider this a bug.  Please report\n--1360-- it at http://valgrind.org/support/bug_reports.html.\n--1360-- WARNING: unhandled riscv64-linux syscall: 258\n--1360-- You may be able to write your own handler.\n--1360-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1360-- Nevertheless we consider this a bug.  Please report\n--1360-- it at http://valgrind.org/support/bug_reports.html.\n--1360-- WARNING: unhandled riscv64-linux syscall: 258\n--1360-- You may be able to write your own handler.\n--1360-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1360-- Nevertheless we consider this a bug.  Please report\n--1360-- it at http://valgrind.org/support/bug_reports.html.\n--1360-- WARNING: unhandled riscv64-linux syscall: 258\n--1360-- You may be able to write your own handler.\n--1360-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1360-- Nevertheless we consider this a bug.  Please report\n--1360-- it at http://valgrind.org/support/bug_reports.html.\n--1360-- WARNING: unhandled riscv64-linux syscall: 258\n--1360-- You may be able to write your own handler.\n--1360-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1360-- Nevertheless we consider this a bug.  Please report\n--1360-- it at http://valgrind.org/support/bug_reports.html.\n--1360-- WARNING: unhandled riscv64-linux syscall: 258\n--1360-- You may be able to write your own handler.\n--1360-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1360-- Nevertheless we consider this a bug.  Please report\n--1360-- it at http://valgrind.org/support/bug_reports.html.\n--1360-- WARNING: unhandled riscv64-linux syscall: 258\n--1360-- You may be able to write your own handler.\n--1360-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1360-- Nevertheless we consider this a bug.  Please report\n--1360-- it at http://valgrind.org/support/bug_reports.html.\n--1360-- WARNING: unhandled riscv64-linux syscall: 258\n--1360-- You may be able to write your own handler.\n--1360-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1360-- Nevertheless we consider this a bug.  Please report\n--1360-- it at http://valgrind.org/support/bug_reports.html.\n--1360-- WARNING: unhandled riscv64-linux syscall: 258\n--1360-- You may be able to write your own handler.\n--1360-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1360-- Nevertheless we consider this a bug.  Please report\n--1360-- 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:
'--1368-- WARNING: unhandled riscv64-linux syscall: 258\n--1368-- You may be able to write your own handler.\n--1368-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1368-- Nevertheless we consider this a bug.  Please report\n--1368-- it at http://valgrind.org/support/bug_reports.html.\n--1368-- WARNING: unhandled riscv64-linux syscall: 258\n--1368-- You may be able to write your own handler.\n--1368-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1368-- Nevertheless we consider this a bug.  Please report\n--1368-- it at http://valgrind.org/support/bug_reports.html.\n--1368-- WARNING: unhandled riscv64-linux syscall: 258\n--1368-- You may be able to write your own handler.\n--1368-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1368-- Nevertheless we consider this a bug.  Please report\n--1368-- it at http://valgrind.org/support/bug_reports.html.\n--1368-- WARNING: unhandled riscv64-linux syscall: 258\n--1368-- You may be able to write your own handler.\n--1368-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1368-- Nevertheless we consider this a bug.  Please report\n--1368-- it at http://valgrind.org/support/bug_reports.html.\n--1368-- WARNING: unhandled riscv64-linux syscall: 258\n--1368-- You may be able to write your own handler.\n--1368-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1368-- Nevertheless we consider this a bug.  Please report\n--1368-- it at http://valgrind.org/support/bug_reports.html.\n--1368-- WARNING: unhandled riscv64-linux syscall: 258\n--1368-- You may be able to write your own handler.\n--1368-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1368-- Nevertheless we consider this a bug.  Please report\n--1368-- it at http://valgrind.org/support/bug_reports.html.\n--1368-- WARNING: unhandled riscv64-linux syscall: 258\n--1368-- You may be able to write your own handler.\n--1368-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1368-- Nevertheless we consider this a bug.  Please report\n--1368-- it at http://valgrind.org/support/bug_reports.html.\n--1368-- WARNING: unhandled riscv64-linux syscall: 258\n--1368-- You may be able to write your own handler.\n--1368-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1368-- Nevertheless we consider this a bug.  Please report\n--1368-- it at http://valgrind.org/support/bug_reports.html.\n--1368-- WARNING: unhandled riscv64-linux syscall: 258\n--1368-- You may be able to write your own handler.\n--1368-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1368-- Nevertheless we consider this a bug.  Please report\n--1368-- it at http://valgrind.org/support/bug_reports.html.\n--1368-- WARNING: unhandled riscv64-linux syscall: 258\n--1368-- You may be able to write your own handler.\n--1368-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1368-- Nevertheless we consider this a bug.  Please report\n--1368-- it at http://valgrind.org/support/bug_reports.html.\n--1368-- WARNING: unhandled riscv64-linux syscall: 258\n--1368-- You may be able to write your own handler.\n--1368-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1368-- Nevertheless we consider this a bug.  Please report\n--1368-- it at http://valgrind.org/support/bug_reports.html.\n--1368-- WARNING: unhandled riscv64-linux syscall: 258\n--1368-- You may be able to write your own handler.\n--1368-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1368-- Nevertheless we consider this a bug.  Please report\n--1368-- it at http://valgrind.org/support/bug_reports.html.\n--1368-- WARNING: unhandled riscv64-linux syscall: 258\n--1368-- You may be able to write your own handler.\n--1368-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1368-- Nevertheless we consider this a bug.  Please report\n--1368-- it at http://valgrind.org/support/bug_reports.html.\n--1368-- WARNING: unhandled riscv64-linux syscall: 258\n--1368-- You may be able to write your own handler.\n--1368-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1368-- Nevertheless we consider this a bug.  Please report\n--1368-- it at http://valgrind.org/support/bug_reports.html.\n--1368-- WARNING: unhandled riscv64-linux syscall: 258\n--1368-- You may be able to write your own handler.\n--1368-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1368-- Nevertheless we consider this a bug.  Please report\n--1368-- it at http://valgrind.org/support/bug_reports.html.\n--1368-- WARNING: unhandled riscv64-linux syscall: 258\n--1368-- You may be able to write your own handler.\n--1368-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1368-- Nevertheless we consider this a bug.  Please report\n--1368-- it at http://valgrind.org/support/bug_reports.html.\n--1368-- WARNING: unhandled riscv64-linux syscall: 258\n--1368-- You may be able to write your own handler.\n--1368-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1368-- Nevertheless we consider this a bug.  Please report\n--1368-- it at http://valgrind.org/support/bug_reports.html.\n--1368-- WARNING: unhandled riscv64-linux syscall: 258\n--1368-- You may be able to write your own handler.\n--1368-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1368-- Nevertheless we consider this a bug.  Please report\n--1368-- 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:
'--1376-- WARNING: unhandled riscv64-linux syscall: 258\n--1376-- You may be able to write your own handler.\n--1376-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1376-- Nevertheless we consider this a bug.  Please report\n--1376-- it at http://valgrind.org/support/bug_reports.html.\n--1376-- WARNING: unhandled riscv64-linux syscall: 258\n--1376-- You may be able to write your own handler.\n--1376-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1376-- Nevertheless we consider this a bug.  Please report\n--1376-- it at http://valgrind.org/support/bug_reports.html.\n--1376-- WARNING: unhandled riscv64-linux syscall: 258\n--1376-- You may be able to write your own handler.\n--1376-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1376-- Nevertheless we consider this a bug.  Please report\n--1376-- it at http://valgrind.org/support/bug_reports.html.\n--1376-- WARNING: unhandled riscv64-linux syscall: 258\n--1376-- You may be able to write your own handler.\n--1376-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1376-- Nevertheless we consider this a bug.  Please report\n--1376-- it at http://valgrind.org/support/bug_reports.html.\n--1376-- WARNING: unhandled riscv64-linux syscall: 258\n--1376-- You may be able to write your own handler.\n--1376-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1376-- Nevertheless we consider this a bug.  Please report\n--1376-- it at http://valgrind.org/support/bug_reports.html.\n--1376-- WARNING: unhandled riscv64-linux syscall: 258\n--1376-- You may be able to write your own handler.\n--1376-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1376-- Nevertheless we consider this a bug.  Please report\n--1376-- it at http://valgrind.org/support/bug_reports.html.\n--1376-- WARNING: unhandled riscv64-linux syscall: 258\n--1376-- You may be able to write your own handler.\n--1376-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1376-- Nevertheless we consider this a bug.  Please report\n--1376-- it at http://valgrind.org/support/bug_reports.html.\n--1376-- WARNING: unhandled riscv64-linux syscall: 258\n--1376-- You may be able to write your own handler.\n--1376-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1376-- Nevertheless we consider this a bug.  Please report\n--1376-- it at http://valgrind.org/support/bug_reports.html.\n--1376-- WARNING: unhandled riscv64-linux syscall: 258\n--1376-- You may be able to write your own handler.\n--1376-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1376-- Nevertheless we consider this a bug.  Please report\n--1376-- it at http://valgrind.org/support/bug_reports.html.\n--1376-- WARNING: unhandled riscv64-linux syscall: 258\n--1376-- You may be able to write your own handler.\n--1376-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1376-- Nevertheless we consider this a bug.  Please report\n--1376-- it at http://valgrind.org/support/bug_reports.html.\n--1376-- WARNING: unhandled riscv64-linux syscall: 258\n--1376-- You may be able to write your own handler.\n--1376-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1376-- Nevertheless we consider this a bug.  Please report\n--1376-- it at http://valgrind.org/support/bug_reports.html.\n--1376-- WARNING: unhandled riscv64-linux syscall: 258\n--1376-- You may be able to write your own handler.\n--1376-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1376-- Nevertheless we consider this a bug.  Please report\n--1376-- it at http://valgrind.org/support/bug_reports.html.\n--1376-- WARNING: unhandled riscv64-linux syscall: 258\n--1376-- You may be able to write your own handler.\n--1376-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1376-- Nevertheless we consider this a bug.  Please report\n--1376-- it at http://valgrind.org/support/bug_reports.html.\n--1376-- WARNING: unhandled riscv64-linux syscall: 258\n--1376-- You may be able to write your own handler.\n--1376-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1376-- Nevertheless we consider this a bug.  Please report\n--1376-- it at http://valgrind.org/support/bug_reports.html.\n--1376-- WARNING: unhandled riscv64-linux syscall: 258\n--1376-- You may be able to write your own handler.\n--1376-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1376-- Nevertheless we consider this a bug.  Please report\n--1376-- it at http://valgrind.org/support/bug_reports.html.\n--1376-- WARNING: unhandled riscv64-linux syscall: 258\n--1376-- You may be able to write your own handler.\n--1376-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1376-- Nevertheless we consider this a bug.  Please report\n--1376-- it at http://valgrind.org/support/bug_reports.html.\n--1376-- WARNING: unhandled riscv64-linux syscall: 258\n--1376-- You may be able to write your own handler.\n--1376-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1376-- Nevertheless we consider this a bug.  Please report\n--1376-- it at http://valgrind.org/support/bug_reports.html.\n--1376-- WARNING: unhandled riscv64-linux syscall: 258\n--1376-- You may be able to write your own handler.\n--1376-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1376-- Nevertheless we consider this a bug.  Please report\n--1376-- 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:
'--1384-- WARNING: unhandled riscv64-linux syscall: 258\n--1384-- You may be able to write your own handler.\n--1384-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1384-- Nevertheless we consider this a bug.  Please report\n--1384-- it at http://valgrind.org/support/bug_reports.html.\n--1384-- WARNING: unhandled riscv64-linux syscall: 258\n--1384-- You may be able to write your own handler.\n--1384-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1384-- Nevertheless we consider this a bug.  Please report\n--1384-- it at http://valgrind.org/support/bug_reports.html.\n--1384-- WARNING: unhandled riscv64-linux syscall: 258\n--1384-- You may be able to write your own handler.\n--1384-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1384-- Nevertheless we consider this a bug.  Please report\n--1384-- it at http://valgrind.org/support/bug_reports.html.\n--1384-- WARNING: unhandled riscv64-linux syscall: 258\n--1384-- You may be able to write your own handler.\n--1384-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1384-- Nevertheless we consider this a bug.  Please report\n--1384-- it at http://valgrind.org/support/bug_reports.html.\n--1384-- WARNING: unhandled riscv64-linux syscall: 258\n--1384-- You may be able to write your own handler.\n--1384-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1384-- Nevertheless we consider this a bug.  Please report\n--1384-- it at http://valgrind.org/support/bug_reports.html.\n--1384-- WARNING: unhandled riscv64-linux syscall: 258\n--1384-- You may be able to write your own handler.\n--1384-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1384-- Nevertheless we consider this a bug.  Please report\n--1384-- it at http://valgrind.org/support/bug_reports.html.\n--1384-- WARNING: unhandled riscv64-linux syscall: 258\n--1384-- You may be able to write your own handler.\n--1384-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1384-- Nevertheless we consider this a bug.  Please report\n--1384-- it at http://valgrind.org/support/bug_reports.html.\n--1384-- WARNING: unhandled riscv64-linux syscall: 258\n--1384-- You may be able to write your own handler.\n--1384-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1384-- Nevertheless we consider this a bug.  Please report\n--1384-- it at http://valgrind.org/support/bug_reports.html.\n--1384-- WARNING: unhandled riscv64-linux syscall: 258\n--1384-- You may be able to write your own handler.\n--1384-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1384-- Nevertheless we consider this a bug.  Please report\n--1384-- it at http://valgrind.org/support/bug_reports.html.\n--1384-- WARNING: unhandled riscv64-linux syscall: 258\n--1384-- You may be able to write your own handler.\n--1384-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1384-- Nevertheless we consider this a bug.  Please report\n--1384-- it at http://valgrind.org/support/bug_reports.html.\n--1384-- WARNING: unhandled riscv64-linux syscall: 258\n--1384-- You may be able to write your own handler.\n--1384-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1384-- Nevertheless we consider this a bug.  Please report\n--1384-- it at http://valgrind.org/support/bug_reports.html.\n--1384-- WARNING: unhandled riscv64-linux syscall: 258\n--1384-- You may be able to write your own handler.\n--1384-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1384-- Nevertheless we consider this a bug.  Please report\n--1384-- it at http://valgrind.org/support/bug_reports.html.\n--1384-- WARNING: unhandled riscv64-linux syscall: 258\n--1384-- You may be able to write your own handler.\n--1384-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1384-- Nevertheless we consider this a bug.  Please report\n--1384-- it at http://valgrind.org/support/bug_reports.html.\n--1384-- WARNING: unhandled riscv64-linux syscall: 258\n--1384-- You may be able to write your own handler.\n--1384-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1384-- Nevertheless we consider this a bug.  Please report\n--1384-- it at http://valgrind.org/support/bug_reports.html.\n--1384-- WARNING: unhandled riscv64-linux syscall: 258\n--1384-- You may be able to write your own handler.\n--1384-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1384-- Nevertheless we consider this a bug.  Please report\n--1384-- it at http://valgrind.org/support/bug_reports.html.\n--1384-- WARNING: unhandled riscv64-linux syscall: 258\n--1384-- You may be able to write your own handler.\n--1384-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1384-- Nevertheless we consider this a bug.  Please report\n--1384-- it at http://valgrind.org/support/bug_reports.html.\n--1384-- WARNING: unhandled riscv64-linux syscall: 258\n--1384-- You may be able to write your own handler.\n--1384-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1384-- Nevertheless we consider this a bug.  Please report\n--1384-- it at http://valgrind.org/support/bug_reports.html.\n--1384-- WARNING: unhandled riscv64-linux syscall: 258\n--1384-- You may be able to write your own handler.\n--1384-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1384-- Nevertheless we consider this a bug.  Please report\n--1384-- 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:
'--1392-- WARNING: unhandled riscv64-linux syscall: 258\n--1392-- You may be able to write your own handler.\n--1392-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1392-- Nevertheless we consider this a bug.  Please report\n--1392-- it at http://valgrind.org/support/bug_reports.html.\n--1392-- WARNING: unhandled riscv64-linux syscall: 258\n--1392-- You may be able to write your own handler.\n--1392-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1392-- Nevertheless we consider this a bug.  Please report\n--1392-- it at http://valgrind.org/support/bug_reports.html.\n--1392-- WARNING: unhandled riscv64-linux syscall: 258\n--1392-- You may be able to write your own handler.\n--1392-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1392-- Nevertheless we consider this a bug.  Please report\n--1392-- it at http://valgrind.org/support/bug_reports.html.\n--1392-- WARNING: unhandled riscv64-linux syscall: 258\n--1392-- You may be able to write your own handler.\n--1392-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1392-- Nevertheless we consider this a bug.  Please report\n--1392-- it at http://valgrind.org/support/bug_reports.html.\n--1392-- WARNING: unhandled riscv64-linux syscall: 258\n--1392-- You may be able to write your own handler.\n--1392-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1392-- Nevertheless we consider this a bug.  Please report\n--1392-- it at http://valgrind.org/support/bug_reports.html.\n--1392-- WARNING: unhandled riscv64-linux syscall: 258\n--1392-- You may be able to write your own handler.\n--1392-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1392-- Nevertheless we consider this a bug.  Please report\n--1392-- it at http://valgrind.org/support/bug_reports.html.\n--1392-- WARNING: unhandled riscv64-linux syscall: 258\n--1392-- You may be able to write your own handler.\n--1392-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1392-- Nevertheless we consider this a bug.  Please report\n--1392-- it at http://valgrind.org/support/bug_reports.html.\n--1392-- WARNING: unhandled riscv64-linux syscall: 258\n--1392-- You may be able to write your own handler.\n--1392-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1392-- Nevertheless we consider this a bug.  Please report\n--1392-- it at http://valgrind.org/support/bug_reports.html.\n--1392-- WARNING: unhandled riscv64-linux syscall: 258\n--1392-- You may be able to write your own handler.\n--1392-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1392-- Nevertheless we consider this a bug.  Please report\n--1392-- it at http://valgrind.org/support/bug_reports.html.\n--1392-- WARNING: unhandled riscv64-linux syscall: 258\n--1392-- You may be able to write your own handler.\n--1392-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1392-- Nevertheless we consider this a bug.  Please report\n--1392-- it at http://valgrind.org/support/bug_reports.html.\n--1392-- WARNING: unhandled riscv64-linux syscall: 258\n--1392-- You may be able to write your own handler.\n--1392-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1392-- Nevertheless we consider this a bug.  Please report\n--1392-- it at http://valgrind.org/support/bug_reports.html.\n--1392-- WARNING: unhandled riscv64-linux syscall: 258\n--1392-- You may be able to write your own handler.\n--1392-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1392-- Nevertheless we consider this a bug.  Please report\n--1392-- it at http://valgrind.org/support/bug_reports.html.\n--1392-- WARNING: unhandled riscv64-linux syscall: 258\n--1392-- You may be able to write your own handler.\n--1392-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1392-- Nevertheless we consider this a bug.  Please report\n--1392-- it at http://valgrind.org/support/bug_reports.html.\n--1392-- WARNING: unhandled riscv64-linux syscall: 258\n--1392-- You may be able to write your own handler.\n--1392-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1392-- Nevertheless we consider this a bug.  Please report\n--1392-- it at http://valgrind.org/support/bug_reports.html.\n--1392-- WARNING: unhandled riscv64-linux syscall: 258\n--1392-- You may be able to write your own handler.\n--1392-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1392-- Nevertheless we consider this a bug.  Please report\n--1392-- it at http://valgrind.org/support/bug_reports.html.\n--1392-- WARNING: unhandled riscv64-linux syscall: 258\n--1392-- You may be able to write your own handler.\n--1392-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1392-- Nevertheless we consider this a bug.  Please report\n--1392-- it at http://valgrind.org/support/bug_reports.html.\n--1392-- WARNING: unhandled riscv64-linux syscall: 258\n--1392-- You may be able to write your own handler.\n--1392-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1392-- Nevertheless we consider this a bug.  Please report\n--1392-- it at http://valgrind.org/support/bug_reports.html.\n--1392-- WARNING: unhandled riscv64-linux syscall: 258\n--1392-- You may be able to write your own handler.\n--1392-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1392-- Nevertheless we consider this a bug.  Please report\n--1392-- 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:
'--1400-- WARNING: unhandled riscv64-linux syscall: 258\n--1400-- You may be able to write your own handler.\n--1400-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1400-- Nevertheless we consider this a bug.  Please report\n--1400-- it at http://valgrind.org/support/bug_reports.html.\n--1400-- WARNING: unhandled riscv64-linux syscall: 258\n--1400-- You may be able to write your own handler.\n--1400-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1400-- Nevertheless we consider this a bug.  Please report\n--1400-- it at http://valgrind.org/support/bug_reports.html.\n--1400-- WARNING: unhandled riscv64-linux syscall: 258\n--1400-- You may be able to write your own handler.\n--1400-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1400-- Nevertheless we consider this a bug.  Please report\n--1400-- it at http://valgrind.org/support/bug_reports.html.\n--1400-- WARNING: unhandled riscv64-linux syscall: 258\n--1400-- You may be able to write your own handler.\n--1400-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1400-- Nevertheless we consider this a bug.  Please report\n--1400-- it at http://valgrind.org/support/bug_reports.html.\n--1400-- WARNING: unhandled riscv64-linux syscall: 258\n--1400-- You may be able to write your own handler.\n--1400-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1400-- Nevertheless we consider this a bug.  Please report\n--1400-- it at http://valgrind.org/support/bug_reports.html.\n--1400-- WARNING: unhandled riscv64-linux syscall: 258\n--1400-- You may be able to write your own handler.\n--1400-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1400-- Nevertheless we consider this a bug.  Please report\n--1400-- it at http://valgrind.org/support/bug_reports.html.\n--1400-- WARNING: unhandled riscv64-linux syscall: 258\n--1400-- You may be able to write your own handler.\n--1400-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1400-- Nevertheless we consider this a bug.  Please report\n--1400-- it at http://valgrind.org/support/bug_reports.html.\n--1400-- WARNING: unhandled riscv64-linux syscall: 258\n--1400-- You may be able to write your own handler.\n--1400-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1400-- Nevertheless we consider this a bug.  Please report\n--1400-- it at http://valgrind.org/support/bug_reports.html.\n--1400-- WARNING: unhandled riscv64-linux syscall: 258\n--1400-- You may be able to write your own handler.\n--1400-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1400-- Nevertheless we consider this a bug.  Please report\n--1400-- it at http://valgrind.org/support/bug_reports.html.\n--1400-- WARNING: unhandled riscv64-linux syscall: 258\n--1400-- You may be able to write your own handler.\n--1400-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1400-- Nevertheless we consider this a bug.  Please report\n--1400-- it at http://valgrind.org/support/bug_reports.html.\n--1400-- WARNING: unhandled riscv64-linux syscall: 258\n--1400-- You may be able to write your own handler.\n--1400-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1400-- Nevertheless we consider this a bug.  Please report\n--1400-- it at http://valgrind.org/support/bug_reports.html.\n--1400-- WARNING: unhandled riscv64-linux syscall: 258\n--1400-- You may be able to write your own handler.\n--1400-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1400-- Nevertheless we consider this a bug.  Please report\n--1400-- it at http://valgrind.org/support/bug_reports.html.\n--1400-- WARNING: unhandled riscv64-linux syscall: 258\n--1400-- You may be able to write your own handler.\n--1400-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1400-- Nevertheless we consider this a bug.  Please report\n--1400-- it at http://valgrind.org/support/bug_reports.html.\n--1400-- WARNING: unhandled riscv64-linux syscall: 258\n--1400-- You may be able to write your own handler.\n--1400-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1400-- Nevertheless we consider this a bug.  Please report\n--1400-- it at http://valgrind.org/support/bug_reports.html.\n--1400-- WARNING: unhandled riscv64-linux syscall: 258\n--1400-- You may be able to write your own handler.\n--1400-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1400-- Nevertheless we consider this a bug.  Please report\n--1400-- it at http://valgrind.org/support/bug_reports.html.\n--1400-- WARNING: unhandled riscv64-linux syscall: 258\n--1400-- You may be able to write your own handler.\n--1400-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1400-- Nevertheless we consider this a bug.  Please report\n--1400-- it at http://valgrind.org/support/bug_reports.html.\n--1400-- WARNING: unhandled riscv64-linux syscall: 258\n--1400-- You may be able to write your own handler.\n--1400-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1400-- Nevertheless we consider this a bug.  Please report\n--1400-- it at http://valgrind.org/support/bug_reports.html.\n--1400-- WARNING: unhandled riscv64-linux syscall: 258\n--1400-- You may be able to write your own handler.\n--1400-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1400-- Nevertheless we consider this a bug.  Please report\n--1400-- 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:
'--1408-- WARNING: unhandled riscv64-linux syscall: 258\n--1408-- You may be able to write your own handler.\n--1408-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1408-- Nevertheless we consider this a bug.  Please report\n--1408-- it at http://valgrind.org/support/bug_reports.html.\n--1408-- WARNING: unhandled riscv64-linux syscall: 258\n--1408-- You may be able to write your own handler.\n--1408-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1408-- Nevertheless we consider this a bug.  Please report\n--1408-- it at http://valgrind.org/support/bug_reports.html.\n--1408-- WARNING: unhandled riscv64-linux syscall: 258\n--1408-- You may be able to write your own handler.\n--1408-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1408-- Nevertheless we consider this a bug.  Please report\n--1408-- it at http://valgrind.org/support/bug_reports.html.\n--1408-- WARNING: unhandled riscv64-linux syscall: 258\n--1408-- You may be able to write your own handler.\n--1408-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1408-- Nevertheless we consider this a bug.  Please report\n--1408-- it at http://valgrind.org/support/bug_reports.html.\n--1408-- WARNING: unhandled riscv64-linux syscall: 258\n--1408-- You may be able to write your own handler.\n--1408-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1408-- Nevertheless we consider this a bug.  Please report\n--1408-- it at http://valgrind.org/support/bug_reports.html.\n--1408-- WARNING: unhandled riscv64-linux syscall: 258\n--1408-- You may be able to write your own handler.\n--1408-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1408-- Nevertheless we consider this a bug.  Please report\n--1408-- it at http://valgrind.org/support/bug_reports.html.\n--1408-- WARNING: unhandled riscv64-linux syscall: 258\n--1408-- You may be able to write your own handler.\n--1408-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1408-- Nevertheless we consider this a bug.  Please report\n--1408-- it at http://valgrind.org/support/bug_reports.html.\n--1408-- WARNING: unhandled riscv64-linux syscall: 258\n--1408-- You may be able to write your own handler.\n--1408-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1408-- Nevertheless we consider this a bug.  Please report\n--1408-- it at http://valgrind.org/support/bug_reports.html.\n--1408-- WARNING: unhandled riscv64-linux syscall: 258\n--1408-- You may be able to write your own handler.\n--1408-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1408-- Nevertheless we consider this a bug.  Please report\n--1408-- it at http://valgrind.org/support/bug_reports.html.\n--1408-- WARNING: unhandled riscv64-linux syscall: 258\n--1408-- You may be able to write your own handler.\n--1408-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1408-- Nevertheless we consider this a bug.  Please report\n--1408-- it at http://valgrind.org/support/bug_reports.html.\n--1408-- WARNING: unhandled riscv64-linux syscall: 258\n--1408-- You may be able to write your own handler.\n--1408-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1408-- Nevertheless we consider this a bug.  Please report\n--1408-- it at http://valgrind.org/support/bug_reports.html.\n--1408-- WARNING: unhandled riscv64-linux syscall: 258\n--1408-- You may be able to write your own handler.\n--1408-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1408-- Nevertheless we consider this a bug.  Please report\n--1408-- it at http://valgrind.org/support/bug_reports.html.\n--1408-- WARNING: unhandled riscv64-linux syscall: 258\n--1408-- You may be able to write your own handler.\n--1408-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1408-- Nevertheless we consider this a bug.  Please report\n--1408-- it at http://valgrind.org/support/bug_reports.html.\n--1408-- WARNING: unhandled riscv64-linux syscall: 258\n--1408-- You may be able to write your own handler.\n--1408-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1408-- Nevertheless we consider this a bug.  Please report\n--1408-- it at http://valgrind.org/support/bug_reports.html.\n--1408-- WARNING: unhandled riscv64-linux syscall: 258\n--1408-- You may be able to write your own handler.\n--1408-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1408-- Nevertheless we consider this a bug.  Please report\n--1408-- it at http://valgrind.org/support/bug_reports.html.\n--1408-- WARNING: unhandled riscv64-linux syscall: 258\n--1408-- You may be able to write your own handler.\n--1408-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1408-- Nevertheless we consider this a bug.  Please report\n--1408-- it at http://valgrind.org/support/bug_reports.html.\n--1408-- WARNING: unhandled riscv64-linux syscall: 258\n--1408-- You may be able to write your own handler.\n--1408-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1408-- Nevertheless we consider this a bug.  Please report\n--1408-- it at http://valgrind.org/support/bug_reports.html.\n--1408-- WARNING: unhandled riscv64-linux syscall: 258\n--1408-- You may be able to write your own handler.\n--1408-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1408-- Nevertheless we consider this a bug.  Please report\n--1408-- 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:
'--1416-- WARNING: unhandled riscv64-linux syscall: 258\n--1416-- You may be able to write your own handler.\n--1416-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1416-- Nevertheless we consider this a bug.  Please report\n--1416-- it at http://valgrind.org/support/bug_reports.html.\n--1416-- WARNING: unhandled riscv64-linux syscall: 258\n--1416-- You may be able to write your own handler.\n--1416-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1416-- Nevertheless we consider this a bug.  Please report\n--1416-- it at http://valgrind.org/support/bug_reports.html.\n--1416-- WARNING: unhandled riscv64-linux syscall: 258\n--1416-- You may be able to write your own handler.\n--1416-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1416-- Nevertheless we consider this a bug.  Please report\n--1416-- it at http://valgrind.org/support/bug_reports.html.\n--1416-- WARNING: unhandled riscv64-linux syscall: 258\n--1416-- You may be able to write your own handler.\n--1416-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1416-- Nevertheless we consider this a bug.  Please report\n--1416-- it at http://valgrind.org/support/bug_reports.html.\n--1416-- WARNING: unhandled riscv64-linux syscall: 258\n--1416-- You may be able to write your own handler.\n--1416-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1416-- Nevertheless we consider this a bug.  Please report\n--1416-- it at http://valgrind.org/support/bug_reports.html.\n--1416-- WARNING: unhandled riscv64-linux syscall: 258\n--1416-- You may be able to write your own handler.\n--1416-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1416-- Nevertheless we consider this a bug.  Please report\n--1416-- it at http://valgrind.org/support/bug_reports.html.\n--1416-- WARNING: unhandled riscv64-linux syscall: 258\n--1416-- You may be able to write your own handler.\n--1416-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1416-- Nevertheless we consider this a bug.  Please report\n--1416-- it at http://valgrind.org/support/bug_reports.html.\n--1416-- WARNING: unhandled riscv64-linux syscall: 258\n--1416-- You may be able to write your own handler.\n--1416-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1416-- Nevertheless we consider this a bug.  Please report\n--1416-- it at http://valgrind.org/support/bug_reports.html.\n--1416-- WARNING: unhandled riscv64-linux syscall: 258\n--1416-- You may be able to write your own handler.\n--1416-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1416-- Nevertheless we consider this a bug.  Please report\n--1416-- it at http://valgrind.org/support/bug_reports.html.\n--1416-- WARNING: unhandled riscv64-linux syscall: 258\n--1416-- You may be able to write your own handler.\n--1416-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1416-- Nevertheless we consider this a bug.  Please report\n--1416-- it at http://valgrind.org/support/bug_reports.html.\n--1416-- WARNING: unhandled riscv64-linux syscall: 258\n--1416-- You may be able to write your own handler.\n--1416-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1416-- Nevertheless we consider this a bug.  Please report\n--1416-- it at http://valgrind.org/support/bug_reports.html.\n--1416-- WARNING: unhandled riscv64-linux syscall: 258\n--1416-- You may be able to write your own handler.\n--1416-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1416-- Nevertheless we consider this a bug.  Please report\n--1416-- it at http://valgrind.org/support/bug_reports.html.\n--1416-- WARNING: unhandled riscv64-linux syscall: 258\n--1416-- You may be able to write your own handler.\n--1416-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1416-- Nevertheless we consider this a bug.  Please report\n--1416-- it at http://valgrind.org/support/bug_reports.html.\n--1416-- WARNING: unhandled riscv64-linux syscall: 258\n--1416-- You may be able to write your own handler.\n--1416-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1416-- Nevertheless we consider this a bug.  Please report\n--1416-- it at http://valgrind.org/support/bug_reports.html.\n--1416-- WARNING: unhandled riscv64-linux syscall: 258\n--1416-- You may be able to write your own handler.\n--1416-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1416-- Nevertheless we consider this a bug.  Please report\n--1416-- it at http://valgrind.org/support/bug_reports.html.\n--1416-- WARNING: unhandled riscv64-linux syscall: 258\n--1416-- You may be able to write your own handler.\n--1416-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1416-- Nevertheless we consider this a bug.  Please report\n--1416-- it at http://valgrind.org/support/bug_reports.html.\n--1416-- WARNING: unhandled riscv64-linux syscall: 258\n--1416-- You may be able to write your own handler.\n--1416-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1416-- Nevertheless we consider this a bug.  Please report\n--1416-- it at http://valgrind.org/support/bug_reports.html.\n--1416-- WARNING: unhandled riscv64-linux syscall: 258\n--1416-- You may be able to write your own handler.\n--1416-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1416-- Nevertheless we consider this a bug.  Please report\n--1416-- 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:
'--1424-- WARNING: unhandled riscv64-linux syscall: 258\n--1424-- You may be able to write your own handler.\n--1424-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1424-- Nevertheless we consider this a bug.  Please report\n--1424-- it at http://valgrind.org/support/bug_reports.html.\n--1424-- WARNING: unhandled riscv64-linux syscall: 258\n--1424-- You may be able to write your own handler.\n--1424-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1424-- Nevertheless we consider this a bug.  Please report\n--1424-- it at http://valgrind.org/support/bug_reports.html.\n--1424-- WARNING: unhandled riscv64-linux syscall: 258\n--1424-- You may be able to write your own handler.\n--1424-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1424-- Nevertheless we consider this a bug.  Please report\n--1424-- it at http://valgrind.org/support/bug_reports.html.\n--1424-- WARNING: unhandled riscv64-linux syscall: 258\n--1424-- You may be able to write your own handler.\n--1424-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1424-- Nevertheless we consider this a bug.  Please report\n--1424-- it at http://valgrind.org/support/bug_reports.html.\n--1424-- WARNING: unhandled riscv64-linux syscall: 258\n--1424-- You may be able to write your own handler.\n--1424-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1424-- Nevertheless we consider this a bug.  Please report\n--1424-- it at http://valgrind.org/support/bug_reports.html.\n--1424-- WARNING: unhandled riscv64-linux syscall: 258\n--1424-- You may be able to write your own handler.\n--1424-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1424-- Nevertheless we consider this a bug.  Please report\n--1424-- it at http://valgrind.org/support/bug_reports.html.\n--1424-- WARNING: unhandled riscv64-linux syscall: 258\n--1424-- You may be able to write your own handler.\n--1424-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1424-- Nevertheless we consider this a bug.  Please report\n--1424-- it at http://valgrind.org/support/bug_reports.html.\n--1424-- WARNING: unhandled riscv64-linux syscall: 258\n--1424-- You may be able to write your own handler.\n--1424-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1424-- Nevertheless we consider this a bug.  Please report\n--1424-- it at http://valgrind.org/support/bug_reports.html.\n--1424-- WARNING: unhandled riscv64-linux syscall: 258\n--1424-- You may be able to write your own handler.\n--1424-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1424-- Nevertheless we consider this a bug.  Please report\n--1424-- it at http://valgrind.org/support/bug_reports.html.\n--1424-- WARNING: unhandled riscv64-linux syscall: 258\n--1424-- You may be able to write your own handler.\n--1424-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1424-- Nevertheless we consider this a bug.  Please report\n--1424-- it at http://valgrind.org/support/bug_reports.html.\n--1424-- WARNING: unhandled riscv64-linux syscall: 258\n--1424-- You may be able to write your own handler.\n--1424-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1424-- Nevertheless we consider this a bug.  Please report\n--1424-- it at http://valgrind.org/support/bug_reports.html.\n--1424-- WARNING: unhandled riscv64-linux syscall: 258\n--1424-- You may be able to write your own handler.\n--1424-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1424-- Nevertheless we consider this a bug.  Please report\n--1424-- it at http://valgrind.org/support/bug_reports.html.\n--1424-- WARNING: unhandled riscv64-linux syscall: 258\n--1424-- You may be able to write your own handler.\n--1424-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1424-- Nevertheless we consider this a bug.  Please report\n--1424-- it at http://valgrind.org/support/bug_reports.html.\n--1424-- WARNING: unhandled riscv64-linux syscall: 258\n--1424-- You may be able to write your own handler.\n--1424-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1424-- Nevertheless we consider this a bug.  Please report\n--1424-- it at http://valgrind.org/support/bug_reports.html.\n--1424-- WARNING: unhandled riscv64-linux syscall: 258\n--1424-- You may be able to write your own handler.\n--1424-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1424-- Nevertheless we consider this a bug.  Please report\n--1424-- it at http://valgrind.org/support/bug_reports.html.\n--1424-- WARNING: unhandled riscv64-linux syscall: 258\n--1424-- You may be able to write your own handler.\n--1424-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1424-- Nevertheless we consider this a bug.  Please report\n--1424-- it at http://valgrind.org/support/bug_reports.html.\n--1424-- WARNING: unhandled riscv64-linux syscall: 258\n--1424-- You may be able to write your own handler.\n--1424-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1424-- Nevertheless we consider this a bug.  Please report\n--1424-- it at http://valgrind.org/support/bug_reports.html.\n--1424-- WARNING: unhandled riscv64-linux syscall: 258\n--1424-- You may be able to write your own handler.\n--1424-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1424-- Nevertheless we consider this a bug.  Please report\n--1424-- 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:
'--1432-- WARNING: unhandled riscv64-linux syscall: 258\n--1432-- You may be able to write your own handler.\n--1432-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1432-- Nevertheless we consider this a bug.  Please report\n--1432-- it at http://valgrind.org/support/bug_reports.html.\n--1432-- WARNING: unhandled riscv64-linux syscall: 258\n--1432-- You may be able to write your own handler.\n--1432-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1432-- Nevertheless we consider this a bug.  Please report\n--1432-- it at http://valgrind.org/support/bug_reports.html.\n--1432-- WARNING: unhandled riscv64-linux syscall: 258\n--1432-- You may be able to write your own handler.\n--1432-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1432-- Nevertheless we consider this a bug.  Please report\n--1432-- it at http://valgrind.org/support/bug_reports.html.\n--1432-- WARNING: unhandled riscv64-linux syscall: 258\n--1432-- You may be able to write your own handler.\n--1432-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1432-- Nevertheless we consider this a bug.  Please report\n--1432-- it at http://valgrind.org/support/bug_reports.html.\n--1432-- WARNING: unhandled riscv64-linux syscall: 258\n--1432-- You may be able to write your own handler.\n--1432-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1432-- Nevertheless we consider this a bug.  Please report\n--1432-- it at http://valgrind.org/support/bug_reports.html.\n--1432-- WARNING: unhandled riscv64-linux syscall: 258\n--1432-- You may be able to write your own handler.\n--1432-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1432-- Nevertheless we consider this a bug.  Please report\n--1432-- it at http://valgrind.org/support/bug_reports.html.\n--1432-- WARNING: unhandled riscv64-linux syscall: 258\n--1432-- You may be able to write your own handler.\n--1432-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1432-- Nevertheless we consider this a bug.  Please report\n--1432-- it at http://valgrind.org/support/bug_reports.html.\n--1432-- WARNING: unhandled riscv64-linux syscall: 258\n--1432-- You may be able to write your own handler.\n--1432-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1432-- Nevertheless we consider this a bug.  Please report\n--1432-- it at http://valgrind.org/support/bug_reports.html.\n--1432-- WARNING: unhandled riscv64-linux syscall: 258\n--1432-- You may be able to write your own handler.\n--1432-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1432-- Nevertheless we consider this a bug.  Please report\n--1432-- it at http://valgrind.org/support/bug_reports.html.\n--1432-- WARNING: unhandled riscv64-linux syscall: 258\n--1432-- You may be able to write your own handler.\n--1432-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1432-- Nevertheless we consider this a bug.  Please report\n--1432-- it at http://valgrind.org/support/bug_reports.html.\n--1432-- WARNING: unhandled riscv64-linux syscall: 258\n--1432-- You may be able to write your own handler.\n--1432-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1432-- Nevertheless we consider this a bug.  Please report\n--1432-- it at http://valgrind.org/support/bug_reports.html.\n--1432-- WARNING: unhandled riscv64-linux syscall: 258\n--1432-- You may be able to write your own handler.\n--1432-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1432-- Nevertheless we consider this a bug.  Please report\n--1432-- it at http://valgrind.org/support/bug_reports.html.\n--1432-- WARNING: unhandled riscv64-linux syscall: 258\n--1432-- You may be able to write your own handler.\n--1432-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1432-- Nevertheless we consider this a bug.  Please report\n--1432-- it at http://valgrind.org/support/bug_reports.html.\n--1432-- WARNING: unhandled riscv64-linux syscall: 258\n--1432-- You may be able to write your own handler.\n--1432-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1432-- Nevertheless we consider this a bug.  Please report\n--1432-- it at http://valgrind.org/support/bug_reports.html.\n--1432-- WARNING: unhandled riscv64-linux syscall: 258\n--1432-- You may be able to write your own handler.\n--1432-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1432-- Nevertheless we consider this a bug.  Please report\n--1432-- it at http://valgrind.org/support/bug_reports.html.\n--1432-- WARNING: unhandled riscv64-linux syscall: 258\n--1432-- You may be able to write your own handler.\n--1432-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1432-- Nevertheless we consider this a bug.  Please report\n--1432-- it at http://valgrind.org/support/bug_reports.html.\n--1432-- WARNING: unhandled riscv64-linux syscall: 258\n--1432-- You may be able to write your own handler.\n--1432-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1432-- Nevertheless we consider this a bug.  Please report\n--1432-- it at http://valgrind.org/support/bug_reports.html.\n--1432-- WARNING: unhandled riscv64-linux syscall: 258\n--1432-- You may be able to write your own handler.\n--1432-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1432-- Nevertheless we consider this a bug.  Please report\n--1432-- 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:
'--1440-- WARNING: unhandled riscv64-linux syscall: 258\n--1440-- You may be able to write your own handler.\n--1440-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1440-- Nevertheless we consider this a bug.  Please report\n--1440-- it at http://valgrind.org/support/bug_reports.html.\n--1440-- WARNING: unhandled riscv64-linux syscall: 258\n--1440-- You may be able to write your own handler.\n--1440-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1440-- Nevertheless we consider this a bug.  Please report\n--1440-- it at http://valgrind.org/support/bug_reports.html.\n--1440-- WARNING: unhandled riscv64-linux syscall: 258\n--1440-- You may be able to write your own handler.\n--1440-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1440-- Nevertheless we consider this a bug.  Please report\n--1440-- it at http://valgrind.org/support/bug_reports.html.\n--1440-- WARNING: unhandled riscv64-linux syscall: 258\n--1440-- You may be able to write your own handler.\n--1440-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1440-- Nevertheless we consider this a bug.  Please report\n--1440-- it at http://valgrind.org/support/bug_reports.html.\n--1440-- WARNING: unhandled riscv64-linux syscall: 258\n--1440-- You may be able to write your own handler.\n--1440-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1440-- Nevertheless we consider this a bug.  Please report\n--1440-- it at http://valgrind.org/support/bug_reports.html.\n--1440-- WARNING: unhandled riscv64-linux syscall: 258\n--1440-- You may be able to write your own handler.\n--1440-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1440-- Nevertheless we consider this a bug.  Please report\n--1440-- it at http://valgrind.org/support/bug_reports.html.\n--1440-- WARNING: unhandled riscv64-linux syscall: 258\n--1440-- You may be able to write your own handler.\n--1440-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1440-- Nevertheless we consider this a bug.  Please report\n--1440-- it at http://valgrind.org/support/bug_reports.html.\n--1440-- WARNING: unhandled riscv64-linux syscall: 258\n--1440-- You may be able to write your own handler.\n--1440-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1440-- Nevertheless we consider this a bug.  Please report\n--1440-- it at http://valgrind.org/support/bug_reports.html.\n--1440-- WARNING: unhandled riscv64-linux syscall: 258\n--1440-- You may be able to write your own handler.\n--1440-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1440-- Nevertheless we consider this a bug.  Please report\n--1440-- it at http://valgrind.org/support/bug_reports.html.\n--1440-- WARNING: unhandled riscv64-linux syscall: 258\n--1440-- You may be able to write your own handler.\n--1440-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1440-- Nevertheless we consider this a bug.  Please report\n--1440-- it at http://valgrind.org/support/bug_reports.html.\n--1440-- WARNING: unhandled riscv64-linux syscall: 258\n--1440-- You may be able to write your own handler.\n--1440-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1440-- Nevertheless we consider this a bug.  Please report\n--1440-- it at http://valgrind.org/support/bug_reports.html.\n--1440-- WARNING: unhandled riscv64-linux syscall: 258\n--1440-- You may be able to write your own handler.\n--1440-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1440-- Nevertheless we consider this a bug.  Please report\n--1440-- it at http://valgrind.org/support/bug_reports.html.\n--1440-- WARNING: unhandled riscv64-linux syscall: 258\n--1440-- You may be able to write your own handler.\n--1440-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1440-- Nevertheless we consider this a bug.  Please report\n--1440-- it at http://valgrind.org/support/bug_reports.html.\n--1440-- WARNING: unhandled riscv64-linux syscall: 258\n--1440-- You may be able to write your own handler.\n--1440-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1440-- Nevertheless we consider this a bug.  Please report\n--1440-- it at http://valgrind.org/support/bug_reports.html.\n--1440-- WARNING: unhandled riscv64-linux syscall: 258\n--1440-- You may be able to write your own handler.\n--1440-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1440-- Nevertheless we consider this a bug.  Please report\n--1440-- it at http://valgrind.org/support/bug_reports.html.\n--1440-- WARNING: unhandled riscv64-linux syscall: 258\n--1440-- You may be able to write your own handler.\n--1440-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1440-- Nevertheless we consider this a bug.  Please report\n--1440-- it at http://valgrind.org/support/bug_reports.html.\n--1440-- WARNING: unhandled riscv64-linux syscall: 258\n--1440-- You may be able to write your own handler.\n--1440-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1440-- Nevertheless we consider this a bug.  Please report\n--1440-- it at http://valgrind.org/support/bug_reports.html.\n--1440-- WARNING: unhandled riscv64-linux syscall: 258\n--1440-- You may be able to write your own handler.\n--1440-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1440-- Nevertheless we consider this a bug.  Please report\n--1440-- 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:
'--1448-- WARNING: unhandled riscv64-linux syscall: 258\n--1448-- You may be able to write your own handler.\n--1448-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1448-- Nevertheless we consider this a bug.  Please report\n--1448-- it at http://valgrind.org/support/bug_reports.html.\n--1448-- WARNING: unhandled riscv64-linux syscall: 258\n--1448-- You may be able to write your own handler.\n--1448-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1448-- Nevertheless we consider this a bug.  Please report\n--1448-- it at http://valgrind.org/support/bug_reports.html.\n--1448-- WARNING: unhandled riscv64-linux syscall: 258\n--1448-- You may be able to write your own handler.\n--1448-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1448-- Nevertheless we consider this a bug.  Please report\n--1448-- it at http://valgrind.org/support/bug_reports.html.\n--1448-- WARNING: unhandled riscv64-linux syscall: 258\n--1448-- You may be able to write your own handler.\n--1448-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1448-- Nevertheless we consider this a bug.  Please report\n--1448-- it at http://valgrind.org/support/bug_reports.html.\n--1448-- WARNING: unhandled riscv64-linux syscall: 258\n--1448-- You may be able to write your own handler.\n--1448-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1448-- Nevertheless we consider this a bug.  Please report\n--1448-- it at http://valgrind.org/support/bug_reports.html.\n--1448-- WARNING: unhandled riscv64-linux syscall: 258\n--1448-- You may be able to write your own handler.\n--1448-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1448-- Nevertheless we consider this a bug.  Please report\n--1448-- it at http://valgrind.org/support/bug_reports.html.\n--1448-- WARNING: unhandled riscv64-linux syscall: 258\n--1448-- You may be able to write your own handler.\n--1448-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1448-- Nevertheless we consider this a bug.  Please report\n--1448-- it at http://valgrind.org/support/bug_reports.html.\n--1448-- WARNING: unhandled riscv64-linux syscall: 258\n--1448-- You may be able to write your own handler.\n--1448-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1448-- Nevertheless we consider this a bug.  Please report\n--1448-- it at http://valgrind.org/support/bug_reports.html.\n--1448-- WARNING: unhandled riscv64-linux syscall: 258\n--1448-- You may be able to write your own handler.\n--1448-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1448-- Nevertheless we consider this a bug.  Please report\n--1448-- it at http://valgrind.org/support/bug_reports.html.\n--1448-- WARNING: unhandled riscv64-linux syscall: 258\n--1448-- You may be able to write your own handler.\n--1448-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1448-- Nevertheless we consider this a bug.  Please report\n--1448-- it at http://valgrind.org/support/bug_reports.html.\n--1448-- WARNING: unhandled riscv64-linux syscall: 258\n--1448-- You may be able to write your own handler.\n--1448-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1448-- Nevertheless we consider this a bug.  Please report\n--1448-- it at http://valgrind.org/support/bug_reports.html.\n--1448-- WARNING: unhandled riscv64-linux syscall: 258\n--1448-- You may be able to write your own handler.\n--1448-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1448-- Nevertheless we consider this a bug.  Please report\n--1448-- it at http://valgrind.org/support/bug_reports.html.\n--1448-- WARNING: unhandled riscv64-linux syscall: 258\n--1448-- You may be able to write your own handler.\n--1448-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1448-- Nevertheless we consider this a bug.  Please report\n--1448-- it at http://valgrind.org/support/bug_reports.html.\n--1448-- WARNING: unhandled riscv64-linux syscall: 258\n--1448-- You may be able to write your own handler.\n--1448-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1448-- Nevertheless we consider this a bug.  Please report\n--1448-- it at http://valgrind.org/support/bug_reports.html.\n--1448-- WARNING: unhandled riscv64-linux syscall: 258\n--1448-- You may be able to write your own handler.\n--1448-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1448-- Nevertheless we consider this a bug.  Please report\n--1448-- it at http://valgrind.org/support/bug_reports.html.\n--1448-- WARNING: unhandled riscv64-linux syscall: 258\n--1448-- You may be able to write your own handler.\n--1448-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1448-- Nevertheless we consider this a bug.  Please report\n--1448-- it at http://valgrind.org/support/bug_reports.html.\n--1448-- WARNING: unhandled riscv64-linux syscall: 258\n--1448-- You may be able to write your own handler.\n--1448-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1448-- Nevertheless we consider this a bug.  Please report\n--1448-- it at http://valgrind.org/support/bug_reports.html.\n--1448-- WARNING: unhandled riscv64-linux syscall: 258\n--1448-- You may be able to write your own handler.\n--1448-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1448-- Nevertheless we consider this a bug.  Please report\n--1448-- 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:
'--1456-- WARNING: unhandled riscv64-linux syscall: 258\n--1456-- You may be able to write your own handler.\n--1456-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1456-- Nevertheless we consider this a bug.  Please report\n--1456-- it at http://valgrind.org/support/bug_reports.html.\n--1456-- WARNING: unhandled riscv64-linux syscall: 258\n--1456-- You may be able to write your own handler.\n--1456-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1456-- Nevertheless we consider this a bug.  Please report\n--1456-- it at http://valgrind.org/support/bug_reports.html.\n--1456-- WARNING: unhandled riscv64-linux syscall: 258\n--1456-- You may be able to write your own handler.\n--1456-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1456-- Nevertheless we consider this a bug.  Please report\n--1456-- it at http://valgrind.org/support/bug_reports.html.\n--1456-- WARNING: unhandled riscv64-linux syscall: 258\n--1456-- You may be able to write your own handler.\n--1456-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1456-- Nevertheless we consider this a bug.  Please report\n--1456-- it at http://valgrind.org/support/bug_reports.html.\n--1456-- WARNING: unhandled riscv64-linux syscall: 258\n--1456-- You may be able to write your own handler.\n--1456-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1456-- Nevertheless we consider this a bug.  Please report\n--1456-- it at http://valgrind.org/support/bug_reports.html.\n--1456-- WARNING: unhandled riscv64-linux syscall: 258\n--1456-- You may be able to write your own handler.\n--1456-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1456-- Nevertheless we consider this a bug.  Please report\n--1456-- it at http://valgrind.org/support/bug_reports.html.\n--1456-- WARNING: unhandled riscv64-linux syscall: 258\n--1456-- You may be able to write your own handler.\n--1456-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1456-- Nevertheless we consider this a bug.  Please report\n--1456-- it at http://valgrind.org/support/bug_reports.html.\n--1456-- WARNING: unhandled riscv64-linux syscall: 258\n--1456-- You may be able to write your own handler.\n--1456-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1456-- Nevertheless we consider this a bug.  Please report\n--1456-- it at http://valgrind.org/support/bug_reports.html.\n--1456-- WARNING: unhandled riscv64-linux syscall: 258\n--1456-- You may be able to write your own handler.\n--1456-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1456-- Nevertheless we consider this a bug.  Please report\n--1456-- it at http://valgrind.org/support/bug_reports.html.\n--1456-- WARNING: unhandled riscv64-linux syscall: 258\n--1456-- You may be able to write your own handler.\n--1456-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1456-- Nevertheless we consider this a bug.  Please report\n--1456-- it at http://valgrind.org/support/bug_reports.html.\n--1456-- WARNING: unhandled riscv64-linux syscall: 258\n--1456-- You may be able to write your own handler.\n--1456-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1456-- Nevertheless we consider this a bug.  Please report\n--1456-- it at http://valgrind.org/support/bug_reports.html.\n--1456-- WARNING: unhandled riscv64-linux syscall: 258\n--1456-- You may be able to write your own handler.\n--1456-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1456-- Nevertheless we consider this a bug.  Please report\n--1456-- it at http://valgrind.org/support/bug_reports.html.\n--1456-- WARNING: unhandled riscv64-linux syscall: 258\n--1456-- You may be able to write your own handler.\n--1456-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1456-- Nevertheless we consider this a bug.  Please report\n--1456-- it at http://valgrind.org/support/bug_reports.html.\n--1456-- WARNING: unhandled riscv64-linux syscall: 258\n--1456-- You may be able to write your own handler.\n--1456-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1456-- Nevertheless we consider this a bug.  Please report\n--1456-- it at http://valgrind.org/support/bug_reports.html.\n--1456-- WARNING: unhandled riscv64-linux syscall: 258\n--1456-- You may be able to write your own handler.\n--1456-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1456-- Nevertheless we consider this a bug.  Please report\n--1456-- it at http://valgrind.org/support/bug_reports.html.\n--1456-- WARNING: unhandled riscv64-linux syscall: 258\n--1456-- You may be able to write your own handler.\n--1456-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1456-- Nevertheless we consider this a bug.  Please report\n--1456-- it at http://valgrind.org/support/bug_reports.html.\n--1456-- WARNING: unhandled riscv64-linux syscall: 258\n--1456-- You may be able to write your own handler.\n--1456-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1456-- Nevertheless we consider this a bug.  Please report\n--1456-- it at http://valgrind.org/support/bug_reports.html.\n--1456-- WARNING: unhandled riscv64-linux syscall: 258\n--1456-- You may be able to write your own handler.\n--1456-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1456-- Nevertheless we consider this a bug.  Please report\n--1456-- 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:
'--1464-- WARNING: unhandled riscv64-linux syscall: 258\n--1464-- You may be able to write your own handler.\n--1464-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1464-- Nevertheless we consider this a bug.  Please report\n--1464-- it at http://valgrind.org/support/bug_reports.html.\n--1464-- WARNING: unhandled riscv64-linux syscall: 258\n--1464-- You may be able to write your own handler.\n--1464-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1464-- Nevertheless we consider this a bug.  Please report\n--1464-- it at http://valgrind.org/support/bug_reports.html.\n--1464-- WARNING: unhandled riscv64-linux syscall: 258\n--1464-- You may be able to write your own handler.\n--1464-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1464-- Nevertheless we consider this a bug.  Please report\n--1464-- it at http://valgrind.org/support/bug_reports.html.\n--1464-- WARNING: unhandled riscv64-linux syscall: 258\n--1464-- You may be able to write your own handler.\n--1464-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1464-- Nevertheless we consider this a bug.  Please report\n--1464-- it at http://valgrind.org/support/bug_reports.html.\n--1464-- WARNING: unhandled riscv64-linux syscall: 258\n--1464-- You may be able to write your own handler.\n--1464-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1464-- Nevertheless we consider this a bug.  Please report\n--1464-- it at http://valgrind.org/support/bug_reports.html.\n--1464-- WARNING: unhandled riscv64-linux syscall: 258\n--1464-- You may be able to write your own handler.\n--1464-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1464-- Nevertheless we consider this a bug.  Please report\n--1464-- it at http://valgrind.org/support/bug_reports.html.\n--1464-- WARNING: unhandled riscv64-linux syscall: 258\n--1464-- You may be able to write your own handler.\n--1464-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1464-- Nevertheless we consider this a bug.  Please report\n--1464-- it at http://valgrind.org/support/bug_reports.html.\n--1464-- WARNING: unhandled riscv64-linux syscall: 258\n--1464-- You may be able to write your own handler.\n--1464-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1464-- Nevertheless we consider this a bug.  Please report\n--1464-- it at http://valgrind.org/support/bug_reports.html.\n--1464-- WARNING: unhandled riscv64-linux syscall: 258\n--1464-- You may be able to write your own handler.\n--1464-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1464-- Nevertheless we consider this a bug.  Please report\n--1464-- it at http://valgrind.org/support/bug_reports.html.\n--1464-- WARNING: unhandled riscv64-linux syscall: 258\n--1464-- You may be able to write your own handler.\n--1464-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1464-- Nevertheless we consider this a bug.  Please report\n--1464-- it at http://valgrind.org/support/bug_reports.html.\n--1464-- WARNING: unhandled riscv64-linux syscall: 258\n--1464-- You may be able to write your own handler.\n--1464-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1464-- Nevertheless we consider this a bug.  Please report\n--1464-- it at http://valgrind.org/support/bug_reports.html.\n--1464-- WARNING: unhandled riscv64-linux syscall: 258\n--1464-- You may be able to write your own handler.\n--1464-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1464-- Nevertheless we consider this a bug.  Please report\n--1464-- it at http://valgrind.org/support/bug_reports.html.\n--1464-- WARNING: unhandled riscv64-linux syscall: 258\n--1464-- You may be able to write your own handler.\n--1464-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1464-- Nevertheless we consider this a bug.  Please report\n--1464-- it at http://valgrind.org/support/bug_reports.html.\n--1464-- WARNING: unhandled riscv64-linux syscall: 258\n--1464-- You may be able to write your own handler.\n--1464-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1464-- Nevertheless we consider this a bug.  Please report\n--1464-- it at http://valgrind.org/support/bug_reports.html.\n--1464-- WARNING: unhandled riscv64-linux syscall: 258\n--1464-- You may be able to write your own handler.\n--1464-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1464-- Nevertheless we consider this a bug.  Please report\n--1464-- it at http://valgrind.org/support/bug_reports.html.\n--1464-- WARNING: unhandled riscv64-linux syscall: 258\n--1464-- You may be able to write your own handler.\n--1464-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1464-- Nevertheless we consider this a bug.  Please report\n--1464-- it at http://valgrind.org/support/bug_reports.html.\n--1464-- WARNING: unhandled riscv64-linux syscall: 258\n--1464-- You may be able to write your own handler.\n--1464-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1464-- Nevertheless we consider this a bug.  Please report\n--1464-- it at http://valgrind.org/support/bug_reports.html.\n--1464-- WARNING: unhandled riscv64-linux syscall: 258\n--1464-- You may be able to write your own handler.\n--1464-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1464-- Nevertheless we consider this a bug.  Please report\n--1464-- 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:
'--1472-- WARNING: unhandled riscv64-linux syscall: 258\n--1472-- You may be able to write your own handler.\n--1472-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1472-- Nevertheless we consider this a bug.  Please report\n--1472-- it at http://valgrind.org/support/bug_reports.html.\n--1472-- WARNING: unhandled riscv64-linux syscall: 258\n--1472-- You may be able to write your own handler.\n--1472-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1472-- Nevertheless we consider this a bug.  Please report\n--1472-- it at http://valgrind.org/support/bug_reports.html.\n--1472-- WARNING: unhandled riscv64-linux syscall: 258\n--1472-- You may be able to write your own handler.\n--1472-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1472-- Nevertheless we consider this a bug.  Please report\n--1472-- it at http://valgrind.org/support/bug_reports.html.\n--1472-- WARNING: unhandled riscv64-linux syscall: 258\n--1472-- You may be able to write your own handler.\n--1472-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1472-- Nevertheless we consider this a bug.  Please report\n--1472-- it at http://valgrind.org/support/bug_reports.html.\n--1472-- WARNING: unhandled riscv64-linux syscall: 258\n--1472-- You may be able to write your own handler.\n--1472-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1472-- Nevertheless we consider this a bug.  Please report\n--1472-- it at http://valgrind.org/support/bug_reports.html.\n--1472-- WARNING: unhandled riscv64-linux syscall: 258\n--1472-- You may be able to write your own handler.\n--1472-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1472-- Nevertheless we consider this a bug.  Please report\n--1472-- it at http://valgrind.org/support/bug_reports.html.\n--1472-- WARNING: unhandled riscv64-linux syscall: 258\n--1472-- You may be able to write your own handler.\n--1472-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1472-- Nevertheless we consider this a bug.  Please report\n--1472-- it at http://valgrind.org/support/bug_reports.html.\n--1472-- WARNING: unhandled riscv64-linux syscall: 258\n--1472-- You may be able to write your own handler.\n--1472-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1472-- Nevertheless we consider this a bug.  Please report\n--1472-- it at http://valgrind.org/support/bug_reports.html.\n--1472-- WARNING: unhandled riscv64-linux syscall: 258\n--1472-- You may be able to write your own handler.\n--1472-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1472-- Nevertheless we consider this a bug.  Please report\n--1472-- it at http://valgrind.org/support/bug_reports.html.\n--1472-- WARNING: unhandled riscv64-linux syscall: 258\n--1472-- You may be able to write your own handler.\n--1472-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1472-- Nevertheless we consider this a bug.  Please report\n--1472-- it at http://valgrind.org/support/bug_reports.html.\n--1472-- WARNING: unhandled riscv64-linux syscall: 258\n--1472-- You may be able to write your own handler.\n--1472-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1472-- Nevertheless we consider this a bug.  Please report\n--1472-- it at http://valgrind.org/support/bug_reports.html.\n--1472-- WARNING: unhandled riscv64-linux syscall: 258\n--1472-- You may be able to write your own handler.\n--1472-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1472-- Nevertheless we consider this a bug.  Please report\n--1472-- it at http://valgrind.org/support/bug_reports.html.\n--1472-- WARNING: unhandled riscv64-linux syscall: 258\n--1472-- You may be able to write your own handler.\n--1472-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1472-- Nevertheless we consider this a bug.  Please report\n--1472-- it at http://valgrind.org/support/bug_reports.html.\n--1472-- WARNING: unhandled riscv64-linux syscall: 258\n--1472-- You may be able to write your own handler.\n--1472-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1472-- Nevertheless we consider this a bug.  Please report\n--1472-- it at http://valgrind.org/support/bug_reports.html.\n--1472-- WARNING: unhandled riscv64-linux syscall: 258\n--1472-- You may be able to write your own handler.\n--1472-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1472-- Nevertheless we consider this a bug.  Please report\n--1472-- it at http://valgrind.org/support/bug_reports.html.\n--1472-- WARNING: unhandled riscv64-linux syscall: 258\n--1472-- You may be able to write your own handler.\n--1472-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1472-- Nevertheless we consider this a bug.  Please report\n--1472-- it at http://valgrind.org/support/bug_reports.html.\n--1472-- WARNING: unhandled riscv64-linux syscall: 258\n--1472-- You may be able to write your own handler.\n--1472-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1472-- Nevertheless we consider this a bug.  Please report\n--1472-- it at http://valgrind.org/support/bug_reports.html.\n--1472-- WARNING: unhandled riscv64-linux syscall: 258\n--1472-- You may be able to write your own handler.\n--1472-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1472-- Nevertheless we consider this a bug.  Please report\n--1472-- 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:
'--1480-- WARNING: unhandled riscv64-linux syscall: 258\n--1480-- You may be able to write your own handler.\n--1480-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1480-- Nevertheless we consider this a bug.  Please report\n--1480-- it at http://valgrind.org/support/bug_reports.html.\n--1480-- WARNING: unhandled riscv64-linux syscall: 258\n--1480-- You may be able to write your own handler.\n--1480-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1480-- Nevertheless we consider this a bug.  Please report\n--1480-- it at http://valgrind.org/support/bug_reports.html.\n--1480-- WARNING: unhandled riscv64-linux syscall: 258\n--1480-- You may be able to write your own handler.\n--1480-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1480-- Nevertheless we consider this a bug.  Please report\n--1480-- it at http://valgrind.org/support/bug_reports.html.\n--1480-- WARNING: unhandled riscv64-linux syscall: 258\n--1480-- You may be able to write your own handler.\n--1480-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1480-- Nevertheless we consider this a bug.  Please report\n--1480-- it at http://valgrind.org/support/bug_reports.html.\n--1480-- WARNING: unhandled riscv64-linux syscall: 258\n--1480-- You may be able to write your own handler.\n--1480-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1480-- Nevertheless we consider this a bug.  Please report\n--1480-- it at http://valgrind.org/support/bug_reports.html.\n--1480-- WARNING: unhandled riscv64-linux syscall: 258\n--1480-- You may be able to write your own handler.\n--1480-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1480-- Nevertheless we consider this a bug.  Please report\n--1480-- it at http://valgrind.org/support/bug_reports.html.\n--1480-- WARNING: unhandled riscv64-linux syscall: 258\n--1480-- You may be able to write your own handler.\n--1480-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1480-- Nevertheless we consider this a bug.  Please report\n--1480-- it at http://valgrind.org/support/bug_reports.html.\n--1480-- WARNING: unhandled riscv64-linux syscall: 258\n--1480-- You may be able to write your own handler.\n--1480-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1480-- Nevertheless we consider this a bug.  Please report\n--1480-- it at http://valgrind.org/support/bug_reports.html.\n--1480-- WARNING: unhandled riscv64-linux syscall: 258\n--1480-- You may be able to write your own handler.\n--1480-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1480-- Nevertheless we consider this a bug.  Please report\n--1480-- it at http://valgrind.org/support/bug_reports.html.\n--1480-- WARNING: unhandled riscv64-linux syscall: 258\n--1480-- You may be able to write your own handler.\n--1480-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1480-- Nevertheless we consider this a bug.  Please report\n--1480-- it at http://valgrind.org/support/bug_reports.html.\n--1480-- WARNING: unhandled riscv64-linux syscall: 258\n--1480-- You may be able to write your own handler.\n--1480-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1480-- Nevertheless we consider this a bug.  Please report\n--1480-- it at http://valgrind.org/support/bug_reports.html.\n--1480-- WARNING: unhandled riscv64-linux syscall: 258\n--1480-- You may be able to write your own handler.\n--1480-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1480-- Nevertheless we consider this a bug.  Please report\n--1480-- it at http://valgrind.org/support/bug_reports.html.\n--1480-- WARNING: unhandled riscv64-linux syscall: 258\n--1480-- You may be able to write your own handler.\n--1480-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1480-- Nevertheless we consider this a bug.  Please report\n--1480-- it at http://valgrind.org/support/bug_reports.html.\n--1480-- WARNING: unhandled riscv64-linux syscall: 258\n--1480-- You may be able to write your own handler.\n--1480-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1480-- Nevertheless we consider this a bug.  Please report\n--1480-- it at http://valgrind.org/support/bug_reports.html.\n--1480-- WARNING: unhandled riscv64-linux syscall: 258\n--1480-- You may be able to write your own handler.\n--1480-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1480-- Nevertheless we consider this a bug.  Please report\n--1480-- it at http://valgrind.org/support/bug_reports.html.\n--1480-- WARNING: unhandled riscv64-linux syscall: 258\n--1480-- You may be able to write your own handler.\n--1480-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1480-- Nevertheless we consider this a bug.  Please report\n--1480-- it at http://valgrind.org/support/bug_reports.html.\n--1480-- WARNING: unhandled riscv64-linux syscall: 258\n--1480-- You may be able to write your own handler.\n--1480-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1480-- Nevertheless we consider this a bug.  Please report\n--1480-- it at http://valgrind.org/support/bug_reports.html.\n--1480-- WARNING: unhandled riscv64-linux syscall: 258\n--1480-- You may be able to write your own handler.\n--1480-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1480-- Nevertheless we consider this a bug.  Please report\n--1480-- 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:
'--1488-- WARNING: unhandled riscv64-linux syscall: 258\n--1488-- You may be able to write your own handler.\n--1488-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1488-- Nevertheless we consider this a bug.  Please report\n--1488-- it at http://valgrind.org/support/bug_reports.html.\n--1488-- WARNING: unhandled riscv64-linux syscall: 258\n--1488-- You may be able to write your own handler.\n--1488-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1488-- Nevertheless we consider this a bug.  Please report\n--1488-- it at http://valgrind.org/support/bug_reports.html.\n--1488-- WARNING: unhandled riscv64-linux syscall: 258\n--1488-- You may be able to write your own handler.\n--1488-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1488-- Nevertheless we consider this a bug.  Please report\n--1488-- it at http://valgrind.org/support/bug_reports.html.\n--1488-- WARNING: unhandled riscv64-linux syscall: 258\n--1488-- You may be able to write your own handler.\n--1488-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1488-- Nevertheless we consider this a bug.  Please report\n--1488-- it at http://valgrind.org/support/bug_reports.html.\n--1488-- WARNING: unhandled riscv64-linux syscall: 258\n--1488-- You may be able to write your own handler.\n--1488-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1488-- Nevertheless we consider this a bug.  Please report\n--1488-- it at http://valgrind.org/support/bug_reports.html.\n--1488-- WARNING: unhandled riscv64-linux syscall: 258\n--1488-- You may be able to write your own handler.\n--1488-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1488-- Nevertheless we consider this a bug.  Please report\n--1488-- it at http://valgrind.org/support/bug_reports.html.\n--1488-- WARNING: unhandled riscv64-linux syscall: 258\n--1488-- You may be able to write your own handler.\n--1488-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1488-- Nevertheless we consider this a bug.  Please report\n--1488-- it at http://valgrind.org/support/bug_reports.html.\n--1488-- WARNING: unhandled riscv64-linux syscall: 258\n--1488-- You may be able to write your own handler.\n--1488-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1488-- Nevertheless we consider this a bug.  Please report\n--1488-- it at http://valgrind.org/support/bug_reports.html.\n--1488-- WARNING: unhandled riscv64-linux syscall: 258\n--1488-- You may be able to write your own handler.\n--1488-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1488-- Nevertheless we consider this a bug.  Please report\n--1488-- it at http://valgrind.org/support/bug_reports.html.\n--1488-- WARNING: unhandled riscv64-linux syscall: 258\n--1488-- You may be able to write your own handler.\n--1488-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1488-- Nevertheless we consider this a bug.  Please report\n--1488-- it at http://valgrind.org/support/bug_reports.html.\n--1488-- WARNING: unhandled riscv64-linux syscall: 258\n--1488-- You may be able to write your own handler.\n--1488-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1488-- Nevertheless we consider this a bug.  Please report\n--1488-- it at http://valgrind.org/support/bug_reports.html.\n--1488-- WARNING: unhandled riscv64-linux syscall: 258\n--1488-- You may be able to write your own handler.\n--1488-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1488-- Nevertheless we consider this a bug.  Please report\n--1488-- it at http://valgrind.org/support/bug_reports.html.\n--1488-- WARNING: unhandled riscv64-linux syscall: 258\n--1488-- You may be able to write your own handler.\n--1488-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1488-- Nevertheless we consider this a bug.  Please report\n--1488-- it at http://valgrind.org/support/bug_reports.html.\n--1488-- WARNING: unhandled riscv64-linux syscall: 258\n--1488-- You may be able to write your own handler.\n--1488-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1488-- Nevertheless we consider this a bug.  Please report\n--1488-- it at http://valgrind.org/support/bug_reports.html.\n--1488-- WARNING: unhandled riscv64-linux syscall: 258\n--1488-- You may be able to write your own handler.\n--1488-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1488-- Nevertheless we consider this a bug.  Please report\n--1488-- it at http://valgrind.org/support/bug_reports.html.\n--1488-- WARNING: unhandled riscv64-linux syscall: 258\n--1488-- You may be able to write your own handler.\n--1488-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1488-- Nevertheless we consider this a bug.  Please report\n--1488-- it at http://valgrind.org/support/bug_reports.html.\n--1488-- WARNING: unhandled riscv64-linux syscall: 258\n--1488-- You may be able to write your own handler.\n--1488-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1488-- Nevertheless we consider this a bug.  Please report\n--1488-- it at http://valgrind.org/support/bug_reports.html.\n--1488-- WARNING: unhandled riscv64-linux syscall: 258\n--1488-- You may be able to write your own handler.\n--1488-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1488-- Nevertheless we consider this a bug.  Please report\n--1488-- 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:
'--1496-- WARNING: unhandled riscv64-linux syscall: 258\n--1496-- You may be able to write your own handler.\n--1496-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1496-- Nevertheless we consider this a bug.  Please report\n--1496-- it at http://valgrind.org/support/bug_reports.html.\n--1496-- WARNING: unhandled riscv64-linux syscall: 258\n--1496-- You may be able to write your own handler.\n--1496-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1496-- Nevertheless we consider this a bug.  Please report\n--1496-- it at http://valgrind.org/support/bug_reports.html.\n--1496-- WARNING: unhandled riscv64-linux syscall: 258\n--1496-- You may be able to write your own handler.\n--1496-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1496-- Nevertheless we consider this a bug.  Please report\n--1496-- it at http://valgrind.org/support/bug_reports.html.\n--1496-- WARNING: unhandled riscv64-linux syscall: 258\n--1496-- You may be able to write your own handler.\n--1496-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1496-- Nevertheless we consider this a bug.  Please report\n--1496-- it at http://valgrind.org/support/bug_reports.html.\n--1496-- WARNING: unhandled riscv64-linux syscall: 258\n--1496-- You may be able to write your own handler.\n--1496-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1496-- Nevertheless we consider this a bug.  Please report\n--1496-- it at http://valgrind.org/support/bug_reports.html.\n--1496-- WARNING: unhandled riscv64-linux syscall: 258\n--1496-- You may be able to write your own handler.\n--1496-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1496-- Nevertheless we consider this a bug.  Please report\n--1496-- it at http://valgrind.org/support/bug_reports.html.\n--1496-- WARNING: unhandled riscv64-linux syscall: 258\n--1496-- You may be able to write your own handler.\n--1496-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1496-- Nevertheless we consider this a bug.  Please report\n--1496-- it at http://valgrind.org/support/bug_reports.html.\n--1496-- WARNING: unhandled riscv64-linux syscall: 258\n--1496-- You may be able to write your own handler.\n--1496-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1496-- Nevertheless we consider this a bug.  Please report\n--1496-- it at http://valgrind.org/support/bug_reports.html.\n--1496-- WARNING: unhandled riscv64-linux syscall: 258\n--1496-- You may be able to write your own handler.\n--1496-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1496-- Nevertheless we consider this a bug.  Please report\n--1496-- it at http://valgrind.org/support/bug_reports.html.\n--1496-- WARNING: unhandled riscv64-linux syscall: 258\n--1496-- You may be able to write your own handler.\n--1496-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1496-- Nevertheless we consider this a bug.  Please report\n--1496-- it at http://valgrind.org/support/bug_reports.html.\n--1496-- WARNING: unhandled riscv64-linux syscall: 258\n--1496-- You may be able to write your own handler.\n--1496-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1496-- Nevertheless we consider this a bug.  Please report\n--1496-- it at http://valgrind.org/support/bug_reports.html.\n--1496-- WARNING: unhandled riscv64-linux syscall: 258\n--1496-- You may be able to write your own handler.\n--1496-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1496-- Nevertheless we consider this a bug.  Please report\n--1496-- it at http://valgrind.org/support/bug_reports.html.\n--1496-- WARNING: unhandled riscv64-linux syscall: 258\n--1496-- You may be able to write your own handler.\n--1496-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1496-- Nevertheless we consider this a bug.  Please report\n--1496-- it at http://valgrind.org/support/bug_reports.html.\n--1496-- WARNING: unhandled riscv64-linux syscall: 258\n--1496-- You may be able to write your own handler.\n--1496-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1496-- Nevertheless we consider this a bug.  Please report\n--1496-- it at http://valgrind.org/support/bug_reports.html.\n--1496-- WARNING: unhandled riscv64-linux syscall: 258\n--1496-- You may be able to write your own handler.\n--1496-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1496-- Nevertheless we consider this a bug.  Please report\n--1496-- it at http://valgrind.org/support/bug_reports.html.\n--1496-- WARNING: unhandled riscv64-linux syscall: 258\n--1496-- You may be able to write your own handler.\n--1496-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1496-- Nevertheless we consider this a bug.  Please report\n--1496-- it at http://valgrind.org/support/bug_reports.html.\n--1496-- WARNING: unhandled riscv64-linux syscall: 258\n--1496-- You may be able to write your own handler.\n--1496-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1496-- Nevertheless we consider this a bug.  Please report\n--1496-- it at http://valgrind.org/support/bug_reports.html.\n--1496-- WARNING: unhandled riscv64-linux syscall: 258\n--1496-- You may be able to write your own handler.\n--1496-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1496-- Nevertheless we consider this a bug.  Please report\n--1496-- 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:
'--1504-- WARNING: unhandled riscv64-linux syscall: 258\n--1504-- You may be able to write your own handler.\n--1504-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1504-- Nevertheless we consider this a bug.  Please report\n--1504-- it at http://valgrind.org/support/bug_reports.html.\n--1504-- WARNING: unhandled riscv64-linux syscall: 258\n--1504-- You may be able to write your own handler.\n--1504-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1504-- Nevertheless we consider this a bug.  Please report\n--1504-- it at http://valgrind.org/support/bug_reports.html.\n--1504-- WARNING: unhandled riscv64-linux syscall: 258\n--1504-- You may be able to write your own handler.\n--1504-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1504-- Nevertheless we consider this a bug.  Please report\n--1504-- it at http://valgrind.org/support/bug_reports.html.\n--1504-- WARNING: unhandled riscv64-linux syscall: 258\n--1504-- You may be able to write your own handler.\n--1504-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1504-- Nevertheless we consider this a bug.  Please report\n--1504-- it at http://valgrind.org/support/bug_reports.html.\n--1504-- WARNING: unhandled riscv64-linux syscall: 258\n--1504-- You may be able to write your own handler.\n--1504-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1504-- Nevertheless we consider this a bug.  Please report\n--1504-- it at http://valgrind.org/support/bug_reports.html.\n--1504-- WARNING: unhandled riscv64-linux syscall: 258\n--1504-- You may be able to write your own handler.\n--1504-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1504-- Nevertheless we consider this a bug.  Please report\n--1504-- it at http://valgrind.org/support/bug_reports.html.\n--1504-- WARNING: unhandled riscv64-linux syscall: 258\n--1504-- You may be able to write your own handler.\n--1504-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1504-- Nevertheless we consider this a bug.  Please report\n--1504-- it at http://valgrind.org/support/bug_reports.html.\n--1504-- WARNING: unhandled riscv64-linux syscall: 258\n--1504-- You may be able to write your own handler.\n--1504-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1504-- Nevertheless we consider this a bug.  Please report\n--1504-- it at http://valgrind.org/support/bug_reports.html.\n--1504-- WARNING: unhandled riscv64-linux syscall: 258\n--1504-- You may be able to write your own handler.\n--1504-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1504-- Nevertheless we consider this a bug.  Please report\n--1504-- it at http://valgrind.org/support/bug_reports.html.\n--1504-- WARNING: unhandled riscv64-linux syscall: 258\n--1504-- You may be able to write your own handler.\n--1504-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1504-- Nevertheless we consider this a bug.  Please report\n--1504-- it at http://valgrind.org/support/bug_reports.html.\n--1504-- WARNING: unhandled riscv64-linux syscall: 258\n--1504-- You may be able to write your own handler.\n--1504-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1504-- Nevertheless we consider this a bug.  Please report\n--1504-- it at http://valgrind.org/support/bug_reports.html.\n--1504-- WARNING: unhandled riscv64-linux syscall: 258\n--1504-- You may be able to write your own handler.\n--1504-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1504-- Nevertheless we consider this a bug.  Please report\n--1504-- it at http://valgrind.org/support/bug_reports.html.\n--1504-- WARNING: unhandled riscv64-linux syscall: 258\n--1504-- You may be able to write your own handler.\n--1504-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1504-- Nevertheless we consider this a bug.  Please report\n--1504-- it at http://valgrind.org/support/bug_reports.html.\n--1504-- WARNING: unhandled riscv64-linux syscall: 258\n--1504-- You may be able to write your own handler.\n--1504-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1504-- Nevertheless we consider this a bug.  Please report\n--1504-- it at http://valgrind.org/support/bug_reports.html.\n--1504-- WARNING: unhandled riscv64-linux syscall: 258\n--1504-- You may be able to write your own handler.\n--1504-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1504-- Nevertheless we consider this a bug.  Please report\n--1504-- it at http://valgrind.org/support/bug_reports.html.\n--1504-- WARNING: unhandled riscv64-linux syscall: 258\n--1504-- You may be able to write your own handler.\n--1504-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1504-- Nevertheless we consider this a bug.  Please report\n--1504-- it at http://valgrind.org/support/bug_reports.html.\n--1504-- WARNING: unhandled riscv64-linux syscall: 258\n--1504-- You may be able to write your own handler.\n--1504-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1504-- Nevertheless we consider this a bug.  Please report\n--1504-- it at http://valgrind.org/support/bug_reports.html.\n--1504-- WARNING: unhandled riscv64-linux syscall: 258\n--1504-- You may be able to write your own handler.\n--1504-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1504-- Nevertheless we consider this a bug.  Please report\n--1504-- 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:
'--1512-- WARNING: unhandled riscv64-linux syscall: 258\n--1512-- You may be able to write your own handler.\n--1512-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1512-- Nevertheless we consider this a bug.  Please report\n--1512-- it at http://valgrind.org/support/bug_reports.html.\n--1512-- WARNING: unhandled riscv64-linux syscall: 258\n--1512-- You may be able to write your own handler.\n--1512-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1512-- Nevertheless we consider this a bug.  Please report\n--1512-- it at http://valgrind.org/support/bug_reports.html.\n--1512-- WARNING: unhandled riscv64-linux syscall: 258\n--1512-- You may be able to write your own handler.\n--1512-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1512-- Nevertheless we consider this a bug.  Please report\n--1512-- it at http://valgrind.org/support/bug_reports.html.\n--1512-- WARNING: unhandled riscv64-linux syscall: 258\n--1512-- You may be able to write your own handler.\n--1512-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1512-- Nevertheless we consider this a bug.  Please report\n--1512-- it at http://valgrind.org/support/bug_reports.html.\n--1512-- WARNING: unhandled riscv64-linux syscall: 258\n--1512-- You may be able to write your own handler.\n--1512-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1512-- Nevertheless we consider this a bug.  Please report\n--1512-- it at http://valgrind.org/support/bug_reports.html.\n--1512-- WARNING: unhandled riscv64-linux syscall: 258\n--1512-- You may be able to write your own handler.\n--1512-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1512-- Nevertheless we consider this a bug.  Please report\n--1512-- it at http://valgrind.org/support/bug_reports.html.\n--1512-- WARNING: unhandled riscv64-linux syscall: 258\n--1512-- You may be able to write your own handler.\n--1512-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1512-- Nevertheless we consider this a bug.  Please report\n--1512-- it at http://valgrind.org/support/bug_reports.html.\n--1512-- WARNING: unhandled riscv64-linux syscall: 258\n--1512-- You may be able to write your own handler.\n--1512-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1512-- Nevertheless we consider this a bug.  Please report\n--1512-- it at http://valgrind.org/support/bug_reports.html.\n--1512-- WARNING: unhandled riscv64-linux syscall: 258\n--1512-- You may be able to write your own handler.\n--1512-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1512-- Nevertheless we consider this a bug.  Please report\n--1512-- it at http://valgrind.org/support/bug_reports.html.\n--1512-- WARNING: unhandled riscv64-linux syscall: 258\n--1512-- You may be able to write your own handler.\n--1512-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1512-- Nevertheless we consider this a bug.  Please report\n--1512-- it at http://valgrind.org/support/bug_reports.html.\n--1512-- WARNING: unhandled riscv64-linux syscall: 258\n--1512-- You may be able to write your own handler.\n--1512-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1512-- Nevertheless we consider this a bug.  Please report\n--1512-- it at http://valgrind.org/support/bug_reports.html.\n--1512-- WARNING: unhandled riscv64-linux syscall: 258\n--1512-- You may be able to write your own handler.\n--1512-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1512-- Nevertheless we consider this a bug.  Please report\n--1512-- it at http://valgrind.org/support/bug_reports.html.\n--1512-- WARNING: unhandled riscv64-linux syscall: 258\n--1512-- You may be able to write your own handler.\n--1512-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1512-- Nevertheless we consider this a bug.  Please report\n--1512-- it at http://valgrind.org/support/bug_reports.html.\n--1512-- WARNING: unhandled riscv64-linux syscall: 258\n--1512-- You may be able to write your own handler.\n--1512-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1512-- Nevertheless we consider this a bug.  Please report\n--1512-- it at http://valgrind.org/support/bug_reports.html.\n--1512-- WARNING: unhandled riscv64-linux syscall: 258\n--1512-- You may be able to write your own handler.\n--1512-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1512-- Nevertheless we consider this a bug.  Please report\n--1512-- it at http://valgrind.org/support/bug_reports.html.\n--1512-- WARNING: unhandled riscv64-linux syscall: 258\n--1512-- You may be able to write your own handler.\n--1512-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1512-- Nevertheless we consider this a bug.  Please report\n--1512-- it at http://valgrind.org/support/bug_reports.html.\n--1512-- WARNING: unhandled riscv64-linux syscall: 258\n--1512-- You may be able to write your own handler.\n--1512-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1512-- Nevertheless we consider this a bug.  Please report\n--1512-- it at http://valgrind.org/support/bug_reports.html.\n--1512-- WARNING: unhandled riscv64-linux syscall: 258\n--1512-- You may be able to write your own handler.\n--1512-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1512-- Nevertheless we consider this a bug.  Please report\n--1512-- 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:
'--1520-- WARNING: unhandled riscv64-linux syscall: 258\n--1520-- You may be able to write your own handler.\n--1520-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1520-- Nevertheless we consider this a bug.  Please report\n--1520-- it at http://valgrind.org/support/bug_reports.html.\n--1520-- WARNING: unhandled riscv64-linux syscall: 258\n--1520-- You may be able to write your own handler.\n--1520-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1520-- Nevertheless we consider this a bug.  Please report\n--1520-- it at http://valgrind.org/support/bug_reports.html.\n--1520-- WARNING: unhandled riscv64-linux syscall: 258\n--1520-- You may be able to write your own handler.\n--1520-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1520-- Nevertheless we consider this a bug.  Please report\n--1520-- it at http://valgrind.org/support/bug_reports.html.\n--1520-- WARNING: unhandled riscv64-linux syscall: 258\n--1520-- You may be able to write your own handler.\n--1520-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1520-- Nevertheless we consider this a bug.  Please report\n--1520-- it at http://valgrind.org/support/bug_reports.html.\n--1520-- WARNING: unhandled riscv64-linux syscall: 258\n--1520-- You may be able to write your own handler.\n--1520-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1520-- Nevertheless we consider this a bug.  Please report\n--1520-- it at http://valgrind.org/support/bug_reports.html.\n--1520-- WARNING: unhandled riscv64-linux syscall: 258\n--1520-- You may be able to write your own handler.\n--1520-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1520-- Nevertheless we consider this a bug.  Please report\n--1520-- it at http://valgrind.org/support/bug_reports.html.\n--1520-- WARNING: unhandled riscv64-linux syscall: 258\n--1520-- You may be able to write your own handler.\n--1520-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1520-- Nevertheless we consider this a bug.  Please report\n--1520-- it at http://valgrind.org/support/bug_reports.html.\n--1520-- WARNING: unhandled riscv64-linux syscall: 258\n--1520-- You may be able to write your own handler.\n--1520-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1520-- Nevertheless we consider this a bug.  Please report\n--1520-- it at http://valgrind.org/support/bug_reports.html.\n--1520-- WARNING: unhandled riscv64-linux syscall: 258\n--1520-- You may be able to write your own handler.\n--1520-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1520-- Nevertheless we consider this a bug.  Please report\n--1520-- it at http://valgrind.org/support/bug_reports.html.\n--1520-- WARNING: unhandled riscv64-linux syscall: 258\n--1520-- You may be able to write your own handler.\n--1520-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1520-- Nevertheless we consider this a bug.  Please report\n--1520-- it at http://valgrind.org/support/bug_reports.html.\n--1520-- WARNING: unhandled riscv64-linux syscall: 258\n--1520-- You may be able to write your own handler.\n--1520-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1520-- Nevertheless we consider this a bug.  Please report\n--1520-- it at http://valgrind.org/support/bug_reports.html.\n--1520-- WARNING: unhandled riscv64-linux syscall: 258\n--1520-- You may be able to write your own handler.\n--1520-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1520-- Nevertheless we consider this a bug.  Please report\n--1520-- it at http://valgrind.org/support/bug_reports.html.\n--1520-- WARNING: unhandled riscv64-linux syscall: 258\n--1520-- You may be able to write your own handler.\n--1520-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1520-- Nevertheless we consider this a bug.  Please report\n--1520-- it at http://valgrind.org/support/bug_reports.html.\n--1520-- WARNING: unhandled riscv64-linux syscall: 258\n--1520-- You may be able to write your own handler.\n--1520-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1520-- Nevertheless we consider this a bug.  Please report\n--1520-- it at http://valgrind.org/support/bug_reports.html.\n--1520-- WARNING: unhandled riscv64-linux syscall: 258\n--1520-- You may be able to write your own handler.\n--1520-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1520-- Nevertheless we consider this a bug.  Please report\n--1520-- it at http://valgrind.org/support/bug_reports.html.\n--1520-- WARNING: unhandled riscv64-linux syscall: 258\n--1520-- You may be able to write your own handler.\n--1520-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1520-- Nevertheless we consider this a bug.  Please report\n--1520-- it at http://valgrind.org/support/bug_reports.html.\n--1520-- WARNING: unhandled riscv64-linux syscall: 258\n--1520-- You may be able to write your own handler.\n--1520-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1520-- Nevertheless we consider this a bug.  Please report\n--1520-- it at http://valgrind.org/support/bug_reports.html.\n--1520-- WARNING: unhandled riscv64-linux syscall: 258\n--1520-- You may be able to write your own handler.\n--1520-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1520-- Nevertheless we consider this a bug.  Please report\n--1520-- 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:
'--1528-- WARNING: unhandled riscv64-linux syscall: 258\n--1528-- You may be able to write your own handler.\n--1528-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1528-- Nevertheless we consider this a bug.  Please report\n--1528-- it at http://valgrind.org/support/bug_reports.html.\n--1528-- WARNING: unhandled riscv64-linux syscall: 258\n--1528-- You may be able to write your own handler.\n--1528-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1528-- Nevertheless we consider this a bug.  Please report\n--1528-- it at http://valgrind.org/support/bug_reports.html.\n--1528-- WARNING: unhandled riscv64-linux syscall: 258\n--1528-- You may be able to write your own handler.\n--1528-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1528-- Nevertheless we consider this a bug.  Please report\n--1528-- it at http://valgrind.org/support/bug_reports.html.\n--1528-- WARNING: unhandled riscv64-linux syscall: 258\n--1528-- You may be able to write your own handler.\n--1528-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1528-- Nevertheless we consider this a bug.  Please report\n--1528-- it at http://valgrind.org/support/bug_reports.html.\n--1528-- WARNING: unhandled riscv64-linux syscall: 258\n--1528-- You may be able to write your own handler.\n--1528-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1528-- Nevertheless we consider this a bug.  Please report\n--1528-- it at http://valgrind.org/support/bug_reports.html.\n--1528-- WARNING: unhandled riscv64-linux syscall: 258\n--1528-- You may be able to write your own handler.\n--1528-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1528-- Nevertheless we consider this a bug.  Please report\n--1528-- it at http://valgrind.org/support/bug_reports.html.\n--1528-- WARNING: unhandled riscv64-linux syscall: 258\n--1528-- You may be able to write your own handler.\n--1528-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1528-- Nevertheless we consider this a bug.  Please report\n--1528-- it at http://valgrind.org/support/bug_reports.html.\n--1528-- WARNING: unhandled riscv64-linux syscall: 258\n--1528-- You may be able to write your own handler.\n--1528-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1528-- Nevertheless we consider this a bug.  Please report\n--1528-- it at http://valgrind.org/support/bug_reports.html.\n--1528-- WARNING: unhandled riscv64-linux syscall: 258\n--1528-- You may be able to write your own handler.\n--1528-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1528-- Nevertheless we consider this a bug.  Please report\n--1528-- it at http://valgrind.org/support/bug_reports.html.\n--1528-- WARNING: unhandled riscv64-linux syscall: 258\n--1528-- You may be able to write your own handler.\n--1528-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1528-- Nevertheless we consider this a bug.  Please report\n--1528-- it at http://valgrind.org/support/bug_reports.html.\n--1528-- WARNING: unhandled riscv64-linux syscall: 258\n--1528-- You may be able to write your own handler.\n--1528-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1528-- Nevertheless we consider this a bug.  Please report\n--1528-- it at http://valgrind.org/support/bug_reports.html.\n--1528-- WARNING: unhandled riscv64-linux syscall: 258\n--1528-- You may be able to write your own handler.\n--1528-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1528-- Nevertheless we consider this a bug.  Please report\n--1528-- it at http://valgrind.org/support/bug_reports.html.\n--1528-- WARNING: unhandled riscv64-linux syscall: 258\n--1528-- You may be able to write your own handler.\n--1528-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1528-- Nevertheless we consider this a bug.  Please report\n--1528-- it at http://valgrind.org/support/bug_reports.html.\n--1528-- WARNING: unhandled riscv64-linux syscall: 258\n--1528-- You may be able to write your own handler.\n--1528-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1528-- Nevertheless we consider this a bug.  Please report\n--1528-- it at http://valgrind.org/support/bug_reports.html.\n--1528-- WARNING: unhandled riscv64-linux syscall: 258\n--1528-- You may be able to write your own handler.\n--1528-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1528-- Nevertheless we consider this a bug.  Please report\n--1528-- it at http://valgrind.org/support/bug_reports.html.\n--1528-- WARNING: unhandled riscv64-linux syscall: 258\n--1528-- You may be able to write your own handler.\n--1528-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1528-- Nevertheless we consider this a bug.  Please report\n--1528-- it at http://valgrind.org/support/bug_reports.html.\n--1528-- WARNING: unhandled riscv64-linux syscall: 258\n--1528-- You may be able to write your own handler.\n--1528-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1528-- Nevertheless we consider this a bug.  Please report\n--1528-- it at http://valgrind.org/support/bug_reports.html.\n--1528-- WARNING: unhandled riscv64-linux syscall: 258\n--1528-- You may be able to write your own handler.\n--1528-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1528-- Nevertheless we consider this a bug.  Please report\n--1528-- 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:
'--1536-- WARNING: unhandled riscv64-linux syscall: 258\n--1536-- You may be able to write your own handler.\n--1536-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1536-- Nevertheless we consider this a bug.  Please report\n--1536-- it at http://valgrind.org/support/bug_reports.html.\n--1536-- WARNING: unhandled riscv64-linux syscall: 258\n--1536-- You may be able to write your own handler.\n--1536-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1536-- Nevertheless we consider this a bug.  Please report\n--1536-- it at http://valgrind.org/support/bug_reports.html.\n--1536-- WARNING: unhandled riscv64-linux syscall: 258\n--1536-- You may be able to write your own handler.\n--1536-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1536-- Nevertheless we consider this a bug.  Please report\n--1536-- it at http://valgrind.org/support/bug_reports.html.\n--1536-- WARNING: unhandled riscv64-linux syscall: 258\n--1536-- You may be able to write your own handler.\n--1536-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1536-- Nevertheless we consider this a bug.  Please report\n--1536-- it at http://valgrind.org/support/bug_reports.html.\n--1536-- WARNING: unhandled riscv64-linux syscall: 258\n--1536-- You may be able to write your own handler.\n--1536-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1536-- Nevertheless we consider this a bug.  Please report\n--1536-- it at http://valgrind.org/support/bug_reports.html.\n--1536-- WARNING: unhandled riscv64-linux syscall: 258\n--1536-- You may be able to write your own handler.\n--1536-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1536-- Nevertheless we consider this a bug.  Please report\n--1536-- it at http://valgrind.org/support/bug_reports.html.\n--1536-- WARNING: unhandled riscv64-linux syscall: 258\n--1536-- You may be able to write your own handler.\n--1536-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1536-- Nevertheless we consider this a bug.  Please report\n--1536-- it at http://valgrind.org/support/bug_reports.html.\n--1536-- WARNING: unhandled riscv64-linux syscall: 258\n--1536-- You may be able to write your own handler.\n--1536-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1536-- Nevertheless we consider this a bug.  Please report\n--1536-- it at http://valgrind.org/support/bug_reports.html.\n--1536-- WARNING: unhandled riscv64-linux syscall: 258\n--1536-- You may be able to write your own handler.\n--1536-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1536-- Nevertheless we consider this a bug.  Please report\n--1536-- it at http://valgrind.org/support/bug_reports.html.\n--1536-- WARNING: unhandled riscv64-linux syscall: 258\n--1536-- You may be able to write your own handler.\n--1536-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1536-- Nevertheless we consider this a bug.  Please report\n--1536-- it at http://valgrind.org/support/bug_reports.html.\n--1536-- WARNING: unhandled riscv64-linux syscall: 258\n--1536-- You may be able to write your own handler.\n--1536-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1536-- Nevertheless we consider this a bug.  Please report\n--1536-- it at http://valgrind.org/support/bug_reports.html.\n--1536-- WARNING: unhandled riscv64-linux syscall: 258\n--1536-- You may be able to write your own handler.\n--1536-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1536-- Nevertheless we consider this a bug.  Please report\n--1536-- it at http://valgrind.org/support/bug_reports.html.\n--1536-- WARNING: unhandled riscv64-linux syscall: 258\n--1536-- You may be able to write your own handler.\n--1536-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1536-- Nevertheless we consider this a bug.  Please report\n--1536-- it at http://valgrind.org/support/bug_reports.html.\n--1536-- WARNING: unhandled riscv64-linux syscall: 258\n--1536-- You may be able to write your own handler.\n--1536-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1536-- Nevertheless we consider this a bug.  Please report\n--1536-- it at http://valgrind.org/support/bug_reports.html.\n--1536-- WARNING: unhandled riscv64-linux syscall: 258\n--1536-- You may be able to write your own handler.\n--1536-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1536-- Nevertheless we consider this a bug.  Please report\n--1536-- it at http://valgrind.org/support/bug_reports.html.\n--1536-- WARNING: unhandled riscv64-linux syscall: 258\n--1536-- You may be able to write your own handler.\n--1536-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1536-- Nevertheless we consider this a bug.  Please report\n--1536-- it at http://valgrind.org/support/bug_reports.html.\n--1536-- WARNING: unhandled riscv64-linux syscall: 258\n--1536-- You may be able to write your own handler.\n--1536-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1536-- Nevertheless we consider this a bug.  Please report\n--1536-- it at http://valgrind.org/support/bug_reports.html.\n--1536-- WARNING: unhandled riscv64-linux syscall: 258\n--1536-- You may be able to write your own handler.\n--1536-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1536-- Nevertheless we consider this a bug.  Please report\n--1536-- 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:
'--1544-- WARNING: unhandled riscv64-linux syscall: 258\n--1544-- You may be able to write your own handler.\n--1544-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1544-- Nevertheless we consider this a bug.  Please report\n--1544-- it at http://valgrind.org/support/bug_reports.html.\n--1544-- WARNING: unhandled riscv64-linux syscall: 258\n--1544-- You may be able to write your own handler.\n--1544-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1544-- Nevertheless we consider this a bug.  Please report\n--1544-- it at http://valgrind.org/support/bug_reports.html.\n--1544-- WARNING: unhandled riscv64-linux syscall: 258\n--1544-- You may be able to write your own handler.\n--1544-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1544-- Nevertheless we consider this a bug.  Please report\n--1544-- it at http://valgrind.org/support/bug_reports.html.\n--1544-- WARNING: unhandled riscv64-linux syscall: 258\n--1544-- You may be able to write your own handler.\n--1544-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1544-- Nevertheless we consider this a bug.  Please report\n--1544-- it at http://valgrind.org/support/bug_reports.html.\n--1544-- WARNING: unhandled riscv64-linux syscall: 258\n--1544-- You may be able to write your own handler.\n--1544-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1544-- Nevertheless we consider this a bug.  Please report\n--1544-- it at http://valgrind.org/support/bug_reports.html.\n--1544-- WARNING: unhandled riscv64-linux syscall: 258\n--1544-- You may be able to write your own handler.\n--1544-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1544-- Nevertheless we consider this a bug.  Please report\n--1544-- it at http://valgrind.org/support/bug_reports.html.\n--1544-- WARNING: unhandled riscv64-linux syscall: 258\n--1544-- You may be able to write your own handler.\n--1544-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1544-- Nevertheless we consider this a bug.  Please report\n--1544-- it at http://valgrind.org/support/bug_reports.html.\n--1544-- WARNING: unhandled riscv64-linux syscall: 258\n--1544-- You may be able to write your own handler.\n--1544-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1544-- Nevertheless we consider this a bug.  Please report\n--1544-- it at http://valgrind.org/support/bug_reports.html.\n--1544-- WARNING: unhandled riscv64-linux syscall: 258\n--1544-- You may be able to write your own handler.\n--1544-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1544-- Nevertheless we consider this a bug.  Please report\n--1544-- it at http://valgrind.org/support/bug_reports.html.\n--1544-- WARNING: unhandled riscv64-linux syscall: 258\n--1544-- You may be able to write your own handler.\n--1544-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1544-- Nevertheless we consider this a bug.  Please report\n--1544-- it at http://valgrind.org/support/bug_reports.html.\n--1544-- WARNING: unhandled riscv64-linux syscall: 258\n--1544-- You may be able to write your own handler.\n--1544-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1544-- Nevertheless we consider this a bug.  Please report\n--1544-- it at http://valgrind.org/support/bug_reports.html.\n--1544-- WARNING: unhandled riscv64-linux syscall: 258\n--1544-- You may be able to write your own handler.\n--1544-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1544-- Nevertheless we consider this a bug.  Please report\n--1544-- it at http://valgrind.org/support/bug_reports.html.\n--1544-- WARNING: unhandled riscv64-linux syscall: 258\n--1544-- You may be able to write your own handler.\n--1544-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1544-- Nevertheless we consider this a bug.  Please report\n--1544-- it at http://valgrind.org/support/bug_reports.html.\n--1544-- WARNING: unhandled riscv64-linux syscall: 258\n--1544-- You may be able to write your own handler.\n--1544-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1544-- Nevertheless we consider this a bug.  Please report\n--1544-- it at http://valgrind.org/support/bug_reports.html.\n--1544-- WARNING: unhandled riscv64-linux syscall: 258\n--1544-- You may be able to write your own handler.\n--1544-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1544-- Nevertheless we consider this a bug.  Please report\n--1544-- it at http://valgrind.org/support/bug_reports.html.\n--1544-- WARNING: unhandled riscv64-linux syscall: 258\n--1544-- You may be able to write your own handler.\n--1544-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1544-- Nevertheless we consider this a bug.  Please report\n--1544-- it at http://valgrind.org/support/bug_reports.html.\n--1544-- WARNING: unhandled riscv64-linux syscall: 258\n--1544-- You may be able to write your own handler.\n--1544-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1544-- Nevertheless we consider this a bug.  Please report\n--1544-- it at http://valgrind.org/support/bug_reports.html.\n--1544-- WARNING: unhandled riscv64-linux syscall: 258\n--1544-- You may be able to write your own handler.\n--1544-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1544-- Nevertheless we consider this a bug.  Please report\n--1544-- 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:
'--1552-- WARNING: unhandled riscv64-linux syscall: 258\n--1552-- You may be able to write your own handler.\n--1552-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1552-- Nevertheless we consider this a bug.  Please report\n--1552-- it at http://valgrind.org/support/bug_reports.html.\n--1552-- WARNING: unhandled riscv64-linux syscall: 258\n--1552-- You may be able to write your own handler.\n--1552-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1552-- Nevertheless we consider this a bug.  Please report\n--1552-- it at http://valgrind.org/support/bug_reports.html.\n--1552-- WARNING: unhandled riscv64-linux syscall: 258\n--1552-- You may be able to write your own handler.\n--1552-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1552-- Nevertheless we consider this a bug.  Please report\n--1552-- it at http://valgrind.org/support/bug_reports.html.\n--1552-- WARNING: unhandled riscv64-linux syscall: 258\n--1552-- You may be able to write your own handler.\n--1552-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1552-- Nevertheless we consider this a bug.  Please report\n--1552-- it at http://valgrind.org/support/bug_reports.html.\n--1552-- WARNING: unhandled riscv64-linux syscall: 258\n--1552-- You may be able to write your own handler.\n--1552-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1552-- Nevertheless we consider this a bug.  Please report\n--1552-- it at http://valgrind.org/support/bug_reports.html.\n--1552-- WARNING: unhandled riscv64-linux syscall: 258\n--1552-- You may be able to write your own handler.\n--1552-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1552-- Nevertheless we consider this a bug.  Please report\n--1552-- it at http://valgrind.org/support/bug_reports.html.\n--1552-- WARNING: unhandled riscv64-linux syscall: 258\n--1552-- You may be able to write your own handler.\n--1552-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1552-- Nevertheless we consider this a bug.  Please report\n--1552-- it at http://valgrind.org/support/bug_reports.html.\n--1552-- WARNING: unhandled riscv64-linux syscall: 258\n--1552-- You may be able to write your own handler.\n--1552-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1552-- Nevertheless we consider this a bug.  Please report\n--1552-- it at http://valgrind.org/support/bug_reports.html.\n--1552-- WARNING: unhandled riscv64-linux syscall: 258\n--1552-- You may be able to write your own handler.\n--1552-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1552-- Nevertheless we consider this a bug.  Please report\n--1552-- it at http://valgrind.org/support/bug_reports.html.\n--1552-- WARNING: unhandled riscv64-linux syscall: 258\n--1552-- You may be able to write your own handler.\n--1552-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1552-- Nevertheless we consider this a bug.  Please report\n--1552-- it at http://valgrind.org/support/bug_reports.html.\n--1552-- WARNING: unhandled riscv64-linux syscall: 258\n--1552-- You may be able to write your own handler.\n--1552-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1552-- Nevertheless we consider this a bug.  Please report\n--1552-- it at http://valgrind.org/support/bug_reports.html.\n--1552-- WARNING: unhandled riscv64-linux syscall: 258\n--1552-- You may be able to write your own handler.\n--1552-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1552-- Nevertheless we consider this a bug.  Please report\n--1552-- it at http://valgrind.org/support/bug_reports.html.\n--1552-- WARNING: unhandled riscv64-linux syscall: 258\n--1552-- You may be able to write your own handler.\n--1552-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1552-- Nevertheless we consider this a bug.  Please report\n--1552-- it at http://valgrind.org/support/bug_reports.html.\n--1552-- WARNING: unhandled riscv64-linux syscall: 258\n--1552-- You may be able to write your own handler.\n--1552-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1552-- Nevertheless we consider this a bug.  Please report\n--1552-- it at http://valgrind.org/support/bug_reports.html.\n--1552-- WARNING: unhandled riscv64-linux syscall: 258\n--1552-- You may be able to write your own handler.\n--1552-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1552-- Nevertheless we consider this a bug.  Please report\n--1552-- it at http://valgrind.org/support/bug_reports.html.\n--1552-- WARNING: unhandled riscv64-linux syscall: 258\n--1552-- You may be able to write your own handler.\n--1552-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1552-- Nevertheless we consider this a bug.  Please report\n--1552-- it at http://valgrind.org/support/bug_reports.html.\n--1552-- WARNING: unhandled riscv64-linux syscall: 258\n--1552-- You may be able to write your own handler.\n--1552-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1552-- Nevertheless we consider this a bug.  Please report\n--1552-- it at http://valgrind.org/support/bug_reports.html.\n--1552-- WARNING: unhandled riscv64-linux syscall: 258\n--1552-- You may be able to write your own handler.\n--1552-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1552-- Nevertheless we consider this a bug.  Please report\n--1552-- 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:
'--1560-- WARNING: unhandled riscv64-linux syscall: 258\n--1560-- You may be able to write your own handler.\n--1560-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1560-- Nevertheless we consider this a bug.  Please report\n--1560-- it at http://valgrind.org/support/bug_reports.html.\n--1560-- WARNING: unhandled riscv64-linux syscall: 258\n--1560-- You may be able to write your own handler.\n--1560-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1560-- Nevertheless we consider this a bug.  Please report\n--1560-- it at http://valgrind.org/support/bug_reports.html.\n--1560-- WARNING: unhandled riscv64-linux syscall: 258\n--1560-- You may be able to write your own handler.\n--1560-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1560-- Nevertheless we consider this a bug.  Please report\n--1560-- it at http://valgrind.org/support/bug_reports.html.\n--1560-- WARNING: unhandled riscv64-linux syscall: 258\n--1560-- You may be able to write your own handler.\n--1560-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1560-- Nevertheless we consider this a bug.  Please report\n--1560-- it at http://valgrind.org/support/bug_reports.html.\n--1560-- WARNING: unhandled riscv64-linux syscall: 258\n--1560-- You may be able to write your own handler.\n--1560-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1560-- Nevertheless we consider this a bug.  Please report\n--1560-- it at http://valgrind.org/support/bug_reports.html.\n--1560-- WARNING: unhandled riscv64-linux syscall: 258\n--1560-- You may be able to write your own handler.\n--1560-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1560-- Nevertheless we consider this a bug.  Please report\n--1560-- it at http://valgrind.org/support/bug_reports.html.\n--1560-- WARNING: unhandled riscv64-linux syscall: 258\n--1560-- You may be able to write your own handler.\n--1560-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1560-- Nevertheless we consider this a bug.  Please report\n--1560-- it at http://valgrind.org/support/bug_reports.html.\n--1560-- WARNING: unhandled riscv64-linux syscall: 258\n--1560-- You may be able to write your own handler.\n--1560-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1560-- Nevertheless we consider this a bug.  Please report\n--1560-- it at http://valgrind.org/support/bug_reports.html.\n--1560-- WARNING: unhandled riscv64-linux syscall: 258\n--1560-- You may be able to write your own handler.\n--1560-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1560-- Nevertheless we consider this a bug.  Please report\n--1560-- it at http://valgrind.org/support/bug_reports.html.\n--1560-- WARNING: unhandled riscv64-linux syscall: 258\n--1560-- You may be able to write your own handler.\n--1560-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1560-- Nevertheless we consider this a bug.  Please report\n--1560-- it at http://valgrind.org/support/bug_reports.html.\n--1560-- WARNING: unhandled riscv64-linux syscall: 258\n--1560-- You may be able to write your own handler.\n--1560-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1560-- Nevertheless we consider this a bug.  Please report\n--1560-- it at http://valgrind.org/support/bug_reports.html.\n--1560-- WARNING: unhandled riscv64-linux syscall: 258\n--1560-- You may be able to write your own handler.\n--1560-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1560-- Nevertheless we consider this a bug.  Please report\n--1560-- it at http://valgrind.org/support/bug_reports.html.\n--1560-- WARNING: unhandled riscv64-linux syscall: 258\n--1560-- You may be able to write your own handler.\n--1560-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1560-- Nevertheless we consider this a bug.  Please report\n--1560-- it at http://valgrind.org/support/bug_reports.html.\n--1560-- WARNING: unhandled riscv64-linux syscall: 258\n--1560-- You may be able to write your own handler.\n--1560-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1560-- Nevertheless we consider this a bug.  Please report\n--1560-- it at http://valgrind.org/support/bug_reports.html.\n--1560-- WARNING: unhandled riscv64-linux syscall: 258\n--1560-- You may be able to write your own handler.\n--1560-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1560-- Nevertheless we consider this a bug.  Please report\n--1560-- it at http://valgrind.org/support/bug_reports.html.\n--1560-- WARNING: unhandled riscv64-linux syscall: 258\n--1560-- You may be able to write your own handler.\n--1560-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1560-- Nevertheless we consider this a bug.  Please report\n--1560-- it at http://valgrind.org/support/bug_reports.html.\n--1560-- WARNING: unhandled riscv64-linux syscall: 258\n--1560-- You may be able to write your own handler.\n--1560-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1560-- Nevertheless we consider this a bug.  Please report\n--1560-- it at http://valgrind.org/support/bug_reports.html.\n--1560-- WARNING: unhandled riscv64-linux syscall: 258\n--1560-- You may be able to write your own handler.\n--1560-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1560-- Nevertheless we consider this a bug.  Please report\n--1560-- 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:
'--1568-- WARNING: unhandled riscv64-linux syscall: 258\n--1568-- You may be able to write your own handler.\n--1568-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1568-- Nevertheless we consider this a bug.  Please report\n--1568-- it at http://valgrind.org/support/bug_reports.html.\n--1568-- WARNING: unhandled riscv64-linux syscall: 258\n--1568-- You may be able to write your own handler.\n--1568-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1568-- Nevertheless we consider this a bug.  Please report\n--1568-- it at http://valgrind.org/support/bug_reports.html.\n--1568-- WARNING: unhandled riscv64-linux syscall: 258\n--1568-- You may be able to write your own handler.\n--1568-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1568-- Nevertheless we consider this a bug.  Please report\n--1568-- it at http://valgrind.org/support/bug_reports.html.\n--1568-- WARNING: unhandled riscv64-linux syscall: 258\n--1568-- You may be able to write your own handler.\n--1568-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1568-- Nevertheless we consider this a bug.  Please report\n--1568-- it at http://valgrind.org/support/bug_reports.html.\n--1568-- WARNING: unhandled riscv64-linux syscall: 258\n--1568-- You may be able to write your own handler.\n--1568-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1568-- Nevertheless we consider this a bug.  Please report\n--1568-- it at http://valgrind.org/support/bug_reports.html.\n--1568-- WARNING: unhandled riscv64-linux syscall: 258\n--1568-- You may be able to write your own handler.\n--1568-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1568-- Nevertheless we consider this a bug.  Please report\n--1568-- it at http://valgrind.org/support/bug_reports.html.\n--1568-- WARNING: unhandled riscv64-linux syscall: 258\n--1568-- You may be able to write your own handler.\n--1568-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1568-- Nevertheless we consider this a bug.  Please report\n--1568-- it at http://valgrind.org/support/bug_reports.html.\n--1568-- WARNING: unhandled riscv64-linux syscall: 258\n--1568-- You may be able to write your own handler.\n--1568-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1568-- Nevertheless we consider this a bug.  Please report\n--1568-- it at http://valgrind.org/support/bug_reports.html.\n--1568-- WARNING: unhandled riscv64-linux syscall: 258\n--1568-- You may be able to write your own handler.\n--1568-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1568-- Nevertheless we consider this a bug.  Please report\n--1568-- it at http://valgrind.org/support/bug_reports.html.\n--1568-- WARNING: unhandled riscv64-linux syscall: 258\n--1568-- You may be able to write your own handler.\n--1568-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1568-- Nevertheless we consider this a bug.  Please report\n--1568-- it at http://valgrind.org/support/bug_reports.html.\n--1568-- WARNING: unhandled riscv64-linux syscall: 258\n--1568-- You may be able to write your own handler.\n--1568-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1568-- Nevertheless we consider this a bug.  Please report\n--1568-- it at http://valgrind.org/support/bug_reports.html.\n--1568-- WARNING: unhandled riscv64-linux syscall: 258\n--1568-- You may be able to write your own handler.\n--1568-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1568-- Nevertheless we consider this a bug.  Please report\n--1568-- it at http://valgrind.org/support/bug_reports.html.\n--1568-- WARNING: unhandled riscv64-linux syscall: 258\n--1568-- You may be able to write your own handler.\n--1568-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1568-- Nevertheless we consider this a bug.  Please report\n--1568-- it at http://valgrind.org/support/bug_reports.html.\n--1568-- WARNING: unhandled riscv64-linux syscall: 258\n--1568-- You may be able to write your own handler.\n--1568-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1568-- Nevertheless we consider this a bug.  Please report\n--1568-- it at http://valgrind.org/support/bug_reports.html.\n--1568-- WARNING: unhandled riscv64-linux syscall: 258\n--1568-- You may be able to write your own handler.\n--1568-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1568-- Nevertheless we consider this a bug.  Please report\n--1568-- it at http://valgrind.org/support/bug_reports.html.\n--1568-- WARNING: unhandled riscv64-linux syscall: 258\n--1568-- You may be able to write your own handler.\n--1568-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1568-- Nevertheless we consider this a bug.  Please report\n--1568-- it at http://valgrind.org/support/bug_reports.html.\n--1568-- WARNING: unhandled riscv64-linux syscall: 258\n--1568-- You may be able to write your own handler.\n--1568-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1568-- Nevertheless we consider this a bug.  Please report\n--1568-- it at http://valgrind.org/support/bug_reports.html.\n--1568-- WARNING: unhandled riscv64-linux syscall: 258\n--1568-- You may be able to write your own handler.\n--1568-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1568-- Nevertheless we consider this a bug.  Please report\n--1568-- 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:
'--1576-- WARNING: unhandled riscv64-linux syscall: 258\n--1576-- You may be able to write your own handler.\n--1576-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1576-- Nevertheless we consider this a bug.  Please report\n--1576-- it at http://valgrind.org/support/bug_reports.html.\n--1576-- WARNING: unhandled riscv64-linux syscall: 258\n--1576-- You may be able to write your own handler.\n--1576-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1576-- Nevertheless we consider this a bug.  Please report\n--1576-- it at http://valgrind.org/support/bug_reports.html.\n--1576-- WARNING: unhandled riscv64-linux syscall: 258\n--1576-- You may be able to write your own handler.\n--1576-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1576-- Nevertheless we consider this a bug.  Please report\n--1576-- it at http://valgrind.org/support/bug_reports.html.\n--1576-- WARNING: unhandled riscv64-linux syscall: 258\n--1576-- You may be able to write your own handler.\n--1576-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1576-- Nevertheless we consider this a bug.  Please report\n--1576-- it at http://valgrind.org/support/bug_reports.html.\n--1576-- WARNING: unhandled riscv64-linux syscall: 258\n--1576-- You may be able to write your own handler.\n--1576-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1576-- Nevertheless we consider this a bug.  Please report\n--1576-- it at http://valgrind.org/support/bug_reports.html.\n--1576-- WARNING: unhandled riscv64-linux syscall: 258\n--1576-- You may be able to write your own handler.\n--1576-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1576-- Nevertheless we consider this a bug.  Please report\n--1576-- it at http://valgrind.org/support/bug_reports.html.\n--1576-- WARNING: unhandled riscv64-linux syscall: 258\n--1576-- You may be able to write your own handler.\n--1576-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1576-- Nevertheless we consider this a bug.  Please report\n--1576-- it at http://valgrind.org/support/bug_reports.html.\n--1576-- WARNING: unhandled riscv64-linux syscall: 258\n--1576-- You may be able to write your own handler.\n--1576-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1576-- Nevertheless we consider this a bug.  Please report\n--1576-- it at http://valgrind.org/support/bug_reports.html.\n--1576-- WARNING: unhandled riscv64-linux syscall: 258\n--1576-- You may be able to write your own handler.\n--1576-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1576-- Nevertheless we consider this a bug.  Please report\n--1576-- it at http://valgrind.org/support/bug_reports.html.\n--1576-- WARNING: unhandled riscv64-linux syscall: 258\n--1576-- You may be able to write your own handler.\n--1576-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1576-- Nevertheless we consider this a bug.  Please report\n--1576-- it at http://valgrind.org/support/bug_reports.html.\n--1576-- WARNING: unhandled riscv64-linux syscall: 258\n--1576-- You may be able to write your own handler.\n--1576-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1576-- Nevertheless we consider this a bug.  Please report\n--1576-- it at http://valgrind.org/support/bug_reports.html.\n--1576-- WARNING: unhandled riscv64-linux syscall: 258\n--1576-- You may be able to write your own handler.\n--1576-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1576-- Nevertheless we consider this a bug.  Please report\n--1576-- it at http://valgrind.org/support/bug_reports.html.\n--1576-- WARNING: unhandled riscv64-linux syscall: 258\n--1576-- You may be able to write your own handler.\n--1576-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1576-- Nevertheless we consider this a bug.  Please report\n--1576-- it at http://valgrind.org/support/bug_reports.html.\n--1576-- WARNING: unhandled riscv64-linux syscall: 258\n--1576-- You may be able to write your own handler.\n--1576-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1576-- Nevertheless we consider this a bug.  Please report\n--1576-- it at http://valgrind.org/support/bug_reports.html.\n--1576-- WARNING: unhandled riscv64-linux syscall: 258\n--1576-- You may be able to write your own handler.\n--1576-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1576-- Nevertheless we consider this a bug.  Please report\n--1576-- it at http://valgrind.org/support/bug_reports.html.\n--1576-- WARNING: unhandled riscv64-linux syscall: 258\n--1576-- You may be able to write your own handler.\n--1576-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1576-- Nevertheless we consider this a bug.  Please report\n--1576-- it at http://valgrind.org/support/bug_reports.html.\n--1576-- WARNING: unhandled riscv64-linux syscall: 258\n--1576-- You may be able to write your own handler.\n--1576-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1576-- Nevertheless we consider this a bug.  Please report\n--1576-- it at http://valgrind.org/support/bug_reports.html.\n--1576-- WARNING: unhandled riscv64-linux syscall: 258\n--1576-- You may be able to write your own handler.\n--1576-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1576-- Nevertheless we consider this a bug.  Please report\n--1576-- 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:
'--1584-- WARNING: unhandled riscv64-linux syscall: 258\n--1584-- You may be able to write your own handler.\n--1584-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1584-- Nevertheless we consider this a bug.  Please report\n--1584-- it at http://valgrind.org/support/bug_reports.html.\n--1584-- WARNING: unhandled riscv64-linux syscall: 258\n--1584-- You may be able to write your own handler.\n--1584-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1584-- Nevertheless we consider this a bug.  Please report\n--1584-- it at http://valgrind.org/support/bug_reports.html.\n--1584-- WARNING: unhandled riscv64-linux syscall: 258\n--1584-- You may be able to write your own handler.\n--1584-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1584-- Nevertheless we consider this a bug.  Please report\n--1584-- it at http://valgrind.org/support/bug_reports.html.\n--1584-- WARNING: unhandled riscv64-linux syscall: 258\n--1584-- You may be able to write your own handler.\n--1584-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1584-- Nevertheless we consider this a bug.  Please report\n--1584-- it at http://valgrind.org/support/bug_reports.html.\n--1584-- WARNING: unhandled riscv64-linux syscall: 258\n--1584-- You may be able to write your own handler.\n--1584-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1584-- Nevertheless we consider this a bug.  Please report\n--1584-- it at http://valgrind.org/support/bug_reports.html.\n--1584-- WARNING: unhandled riscv64-linux syscall: 258\n--1584-- You may be able to write your own handler.\n--1584-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1584-- Nevertheless we consider this a bug.  Please report\n--1584-- it at http://valgrind.org/support/bug_reports.html.\n--1584-- WARNING: unhandled riscv64-linux syscall: 258\n--1584-- You may be able to write your own handler.\n--1584-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1584-- Nevertheless we consider this a bug.  Please report\n--1584-- it at http://valgrind.org/support/bug_reports.html.\n--1584-- WARNING: unhandled riscv64-linux syscall: 258\n--1584-- You may be able to write your own handler.\n--1584-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1584-- Nevertheless we consider this a bug.  Please report\n--1584-- it at http://valgrind.org/support/bug_reports.html.\n--1584-- WARNING: unhandled riscv64-linux syscall: 258\n--1584-- You may be able to write your own handler.\n--1584-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1584-- Nevertheless we consider this a bug.  Please report\n--1584-- it at http://valgrind.org/support/bug_reports.html.\n--1584-- WARNING: unhandled riscv64-linux syscall: 258\n--1584-- You may be able to write your own handler.\n--1584-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1584-- Nevertheless we consider this a bug.  Please report\n--1584-- it at http://valgrind.org/support/bug_reports.html.\n--1584-- WARNING: unhandled riscv64-linux syscall: 258\n--1584-- You may be able to write your own handler.\n--1584-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1584-- Nevertheless we consider this a bug.  Please report\n--1584-- it at http://valgrind.org/support/bug_reports.html.\n--1584-- WARNING: unhandled riscv64-linux syscall: 258\n--1584-- You may be able to write your own handler.\n--1584-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1584-- Nevertheless we consider this a bug.  Please report\n--1584-- it at http://valgrind.org/support/bug_reports.html.\n--1584-- WARNING: unhandled riscv64-linux syscall: 258\n--1584-- You may be able to write your own handler.\n--1584-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1584-- Nevertheless we consider this a bug.  Please report\n--1584-- it at http://valgrind.org/support/bug_reports.html.\n--1584-- WARNING: unhandled riscv64-linux syscall: 258\n--1584-- You may be able to write your own handler.\n--1584-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1584-- Nevertheless we consider this a bug.  Please report\n--1584-- it at http://valgrind.org/support/bug_reports.html.\n--1584-- WARNING: unhandled riscv64-linux syscall: 258\n--1584-- You may be able to write your own handler.\n--1584-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1584-- Nevertheless we consider this a bug.  Please report\n--1584-- it at http://valgrind.org/support/bug_reports.html.\n--1584-- WARNING: unhandled riscv64-linux syscall: 258\n--1584-- You may be able to write your own handler.\n--1584-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1584-- Nevertheless we consider this a bug.  Please report\n--1584-- it at http://valgrind.org/support/bug_reports.html.\n--1584-- WARNING: unhandled riscv64-linux syscall: 258\n--1584-- You may be able to write your own handler.\n--1584-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1584-- Nevertheless we consider this a bug.  Please report\n--1584-- it at http://valgrind.org/support/bug_reports.html.\n--1584-- WARNING: unhandled riscv64-linux syscall: 258\n--1584-- You may be able to write your own handler.\n--1584-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1584-- Nevertheless we consider this a bug.  Please report\n--1584-- 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:
'--1592-- WARNING: unhandled riscv64-linux syscall: 258\n--1592-- You may be able to write your own handler.\n--1592-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1592-- Nevertheless we consider this a bug.  Please report\n--1592-- it at http://valgrind.org/support/bug_reports.html.\n--1592-- WARNING: unhandled riscv64-linux syscall: 258\n--1592-- You may be able to write your own handler.\n--1592-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1592-- Nevertheless we consider this a bug.  Please report\n--1592-- it at http://valgrind.org/support/bug_reports.html.\n--1592-- WARNING: unhandled riscv64-linux syscall: 258\n--1592-- You may be able to write your own handler.\n--1592-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1592-- Nevertheless we consider this a bug.  Please report\n--1592-- it at http://valgrind.org/support/bug_reports.html.\n--1592-- WARNING: unhandled riscv64-linux syscall: 258\n--1592-- You may be able to write your own handler.\n--1592-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1592-- Nevertheless we consider this a bug.  Please report\n--1592-- it at http://valgrind.org/support/bug_reports.html.\n--1592-- WARNING: unhandled riscv64-linux syscall: 258\n--1592-- You may be able to write your own handler.\n--1592-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1592-- Nevertheless we consider this a bug.  Please report\n--1592-- it at http://valgrind.org/support/bug_reports.html.\n--1592-- WARNING: unhandled riscv64-linux syscall: 258\n--1592-- You may be able to write your own handler.\n--1592-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1592-- Nevertheless we consider this a bug.  Please report\n--1592-- it at http://valgrind.org/support/bug_reports.html.\n--1592-- WARNING: unhandled riscv64-linux syscall: 258\n--1592-- You may be able to write your own handler.\n--1592-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1592-- Nevertheless we consider this a bug.  Please report\n--1592-- it at http://valgrind.org/support/bug_reports.html.\n--1592-- WARNING: unhandled riscv64-linux syscall: 258\n--1592-- You may be able to write your own handler.\n--1592-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1592-- Nevertheless we consider this a bug.  Please report\n--1592-- it at http://valgrind.org/support/bug_reports.html.\n--1592-- WARNING: unhandled riscv64-linux syscall: 258\n--1592-- You may be able to write your own handler.\n--1592-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1592-- Nevertheless we consider this a bug.  Please report\n--1592-- it at http://valgrind.org/support/bug_reports.html.\n--1592-- WARNING: unhandled riscv64-linux syscall: 258\n--1592-- You may be able to write your own handler.\n--1592-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1592-- Nevertheless we consider this a bug.  Please report\n--1592-- it at http://valgrind.org/support/bug_reports.html.\n--1592-- WARNING: unhandled riscv64-linux syscall: 258\n--1592-- You may be able to write your own handler.\n--1592-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1592-- Nevertheless we consider this a bug.  Please report\n--1592-- it at http://valgrind.org/support/bug_reports.html.\n--1592-- WARNING: unhandled riscv64-linux syscall: 258\n--1592-- You may be able to write your own handler.\n--1592-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1592-- Nevertheless we consider this a bug.  Please report\n--1592-- it at http://valgrind.org/support/bug_reports.html.\n--1592-- WARNING: unhandled riscv64-linux syscall: 258\n--1592-- You may be able to write your own handler.\n--1592-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1592-- Nevertheless we consider this a bug.  Please report\n--1592-- it at http://valgrind.org/support/bug_reports.html.\n--1592-- WARNING: unhandled riscv64-linux syscall: 258\n--1592-- You may be able to write your own handler.\n--1592-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1592-- Nevertheless we consider this a bug.  Please report\n--1592-- it at http://valgrind.org/support/bug_reports.html.\n--1592-- WARNING: unhandled riscv64-linux syscall: 258\n--1592-- You may be able to write your own handler.\n--1592-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1592-- Nevertheless we consider this a bug.  Please report\n--1592-- it at http://valgrind.org/support/bug_reports.html.\n--1592-- WARNING: unhandled riscv64-linux syscall: 258\n--1592-- You may be able to write your own handler.\n--1592-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1592-- Nevertheless we consider this a bug.  Please report\n--1592-- it at http://valgrind.org/support/bug_reports.html.\n--1592-- WARNING: unhandled riscv64-linux syscall: 258\n--1592-- You may be able to write your own handler.\n--1592-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1592-- Nevertheless we consider this a bug.  Please report\n--1592-- it at http://valgrind.org/support/bug_reports.html.\n--1592-- WARNING: unhandled riscv64-linux syscall: 258\n--1592-- You may be able to write your own handler.\n--1592-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1592-- Nevertheless we consider this a bug.  Please report\n--1592-- 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:
'--1600-- WARNING: unhandled riscv64-linux syscall: 258\n--1600-- You may be able to write your own handler.\n--1600-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1600-- Nevertheless we consider this a bug.  Please report\n--1600-- it at http://valgrind.org/support/bug_reports.html.\n--1600-- WARNING: unhandled riscv64-linux syscall: 258\n--1600-- You may be able to write your own handler.\n--1600-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1600-- Nevertheless we consider this a bug.  Please report\n--1600-- it at http://valgrind.org/support/bug_reports.html.\n--1600-- WARNING: unhandled riscv64-linux syscall: 258\n--1600-- You may be able to write your own handler.\n--1600-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1600-- Nevertheless we consider this a bug.  Please report\n--1600-- it at http://valgrind.org/support/bug_reports.html.\n--1600-- WARNING: unhandled riscv64-linux syscall: 258\n--1600-- You may be able to write your own handler.\n--1600-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1600-- Nevertheless we consider this a bug.  Please report\n--1600-- it at http://valgrind.org/support/bug_reports.html.\n--1600-- WARNING: unhandled riscv64-linux syscall: 258\n--1600-- You may be able to write your own handler.\n--1600-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1600-- Nevertheless we consider this a bug.  Please report\n--1600-- it at http://valgrind.org/support/bug_reports.html.\n--1600-- WARNING: unhandled riscv64-linux syscall: 258\n--1600-- You may be able to write your own handler.\n--1600-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1600-- Nevertheless we consider this a bug.  Please report\n--1600-- it at http://valgrind.org/support/bug_reports.html.\n--1600-- WARNING: unhandled riscv64-linux syscall: 258\n--1600-- You may be able to write your own handler.\n--1600-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1600-- Nevertheless we consider this a bug.  Please report\n--1600-- it at http://valgrind.org/support/bug_reports.html.\n--1600-- WARNING: unhandled riscv64-linux syscall: 258\n--1600-- You may be able to write your own handler.\n--1600-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1600-- Nevertheless we consider this a bug.  Please report\n--1600-- it at http://valgrind.org/support/bug_reports.html.\n--1600-- WARNING: unhandled riscv64-linux syscall: 258\n--1600-- You may be able to write your own handler.\n--1600-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1600-- Nevertheless we consider this a bug.  Please report\n--1600-- it at http://valgrind.org/support/bug_reports.html.\n--1600-- WARNING: unhandled riscv64-linux syscall: 258\n--1600-- You may be able to write your own handler.\n--1600-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1600-- Nevertheless we consider this a bug.  Please report\n--1600-- it at http://valgrind.org/support/bug_reports.html.\n--1600-- WARNING: unhandled riscv64-linux syscall: 258\n--1600-- You may be able to write your own handler.\n--1600-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1600-- Nevertheless we consider this a bug.  Please report\n--1600-- it at http://valgrind.org/support/bug_reports.html.\n--1600-- WARNING: unhandled riscv64-linux syscall: 258\n--1600-- You may be able to write your own handler.\n--1600-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1600-- Nevertheless we consider this a bug.  Please report\n--1600-- it at http://valgrind.org/support/bug_reports.html.\n--1600-- WARNING: unhandled riscv64-linux syscall: 258\n--1600-- You may be able to write your own handler.\n--1600-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1600-- Nevertheless we consider this a bug.  Please report\n--1600-- it at http://valgrind.org/support/bug_reports.html.\n--1600-- WARNING: unhandled riscv64-linux syscall: 258\n--1600-- You may be able to write your own handler.\n--1600-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1600-- Nevertheless we consider this a bug.  Please report\n--1600-- it at http://valgrind.org/support/bug_reports.html.\n--1600-- WARNING: unhandled riscv64-linux syscall: 258\n--1600-- You may be able to write your own handler.\n--1600-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1600-- Nevertheless we consider this a bug.  Please report\n--1600-- it at http://valgrind.org/support/bug_reports.html.\n--1600-- WARNING: unhandled riscv64-linux syscall: 258\n--1600-- You may be able to write your own handler.\n--1600-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1600-- Nevertheless we consider this a bug.  Please report\n--1600-- it at http://valgrind.org/support/bug_reports.html.\n--1600-- WARNING: unhandled riscv64-linux syscall: 258\n--1600-- You may be able to write your own handler.\n--1600-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1600-- Nevertheless we consider this a bug.  Please report\n--1600-- it at http://valgrind.org/support/bug_reports.html.\n--1600-- WARNING: unhandled riscv64-linux syscall: 258\n--1600-- You may be able to write your own handler.\n--1600-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1600-- Nevertheless we consider this a bug.  Please report\n--1600-- 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:
'--1608-- WARNING: unhandled riscv64-linux syscall: 258\n--1608-- You may be able to write your own handler.\n--1608-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1608-- Nevertheless we consider this a bug.  Please report\n--1608-- it at http://valgrind.org/support/bug_reports.html.\n--1608-- WARNING: unhandled riscv64-linux syscall: 258\n--1608-- You may be able to write your own handler.\n--1608-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1608-- Nevertheless we consider this a bug.  Please report\n--1608-- it at http://valgrind.org/support/bug_reports.html.\n--1608-- WARNING: unhandled riscv64-linux syscall: 258\n--1608-- You may be able to write your own handler.\n--1608-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1608-- Nevertheless we consider this a bug.  Please report\n--1608-- it at http://valgrind.org/support/bug_reports.html.\n--1608-- WARNING: unhandled riscv64-linux syscall: 258\n--1608-- You may be able to write your own handler.\n--1608-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1608-- Nevertheless we consider this a bug.  Please report\n--1608-- it at http://valgrind.org/support/bug_reports.html.\n--1608-- WARNING: unhandled riscv64-linux syscall: 258\n--1608-- You may be able to write your own handler.\n--1608-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1608-- Nevertheless we consider this a bug.  Please report\n--1608-- it at http://valgrind.org/support/bug_reports.html.\n--1608-- WARNING: unhandled riscv64-linux syscall: 258\n--1608-- You may be able to write your own handler.\n--1608-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1608-- Nevertheless we consider this a bug.  Please report\n--1608-- it at http://valgrind.org/support/bug_reports.html.\n--1608-- WARNING: unhandled riscv64-linux syscall: 258\n--1608-- You may be able to write your own handler.\n--1608-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1608-- Nevertheless we consider this a bug.  Please report\n--1608-- it at http://valgrind.org/support/bug_reports.html.\n--1608-- WARNING: unhandled riscv64-linux syscall: 258\n--1608-- You may be able to write your own handler.\n--1608-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1608-- Nevertheless we consider this a bug.  Please report\n--1608-- it at http://valgrind.org/support/bug_reports.html.\n--1608-- WARNING: unhandled riscv64-linux syscall: 258\n--1608-- You may be able to write your own handler.\n--1608-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1608-- Nevertheless we consider this a bug.  Please report\n--1608-- it at http://valgrind.org/support/bug_reports.html.\n--1608-- WARNING: unhandled riscv64-linux syscall: 258\n--1608-- You may be able to write your own handler.\n--1608-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1608-- Nevertheless we consider this a bug.  Please report\n--1608-- it at http://valgrind.org/support/bug_reports.html.\n--1608-- WARNING: unhandled riscv64-linux syscall: 258\n--1608-- You may be able to write your own handler.\n--1608-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1608-- Nevertheless we consider this a bug.  Please report\n--1608-- it at http://valgrind.org/support/bug_reports.html.\n--1608-- WARNING: unhandled riscv64-linux syscall: 258\n--1608-- You may be able to write your own handler.\n--1608-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1608-- Nevertheless we consider this a bug.  Please report\n--1608-- it at http://valgrind.org/support/bug_reports.html.\n--1608-- WARNING: unhandled riscv64-linux syscall: 258\n--1608-- You may be able to write your own handler.\n--1608-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1608-- Nevertheless we consider this a bug.  Please report\n--1608-- it at http://valgrind.org/support/bug_reports.html.\n--1608-- WARNING: unhandled riscv64-linux syscall: 258\n--1608-- You may be able to write your own handler.\n--1608-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1608-- Nevertheless we consider this a bug.  Please report\n--1608-- it at http://valgrind.org/support/bug_reports.html.\n--1608-- WARNING: unhandled riscv64-linux syscall: 258\n--1608-- You may be able to write your own handler.\n--1608-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1608-- Nevertheless we consider this a bug.  Please report\n--1608-- it at http://valgrind.org/support/bug_reports.html.\n--1608-- WARNING: unhandled riscv64-linux syscall: 258\n--1608-- You may be able to write your own handler.\n--1608-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1608-- Nevertheless we consider this a bug.  Please report\n--1608-- it at http://valgrind.org/support/bug_reports.html.\n--1608-- WARNING: unhandled riscv64-linux syscall: 258\n--1608-- You may be able to write your own handler.\n--1608-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1608-- Nevertheless we consider this a bug.  Please report\n--1608-- it at http://valgrind.org/support/bug_reports.html.\n--1608-- WARNING: unhandled riscv64-linux syscall: 258\n--1608-- You may be able to write your own handler.\n--1608-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1608-- Nevertheless we consider this a bug.  Please report\n--1608-- 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:
'--1616-- WARNING: unhandled riscv64-linux syscall: 258\n--1616-- You may be able to write your own handler.\n--1616-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1616-- Nevertheless we consider this a bug.  Please report\n--1616-- it at http://valgrind.org/support/bug_reports.html.\n--1616-- WARNING: unhandled riscv64-linux syscall: 258\n--1616-- You may be able to write your own handler.\n--1616-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1616-- Nevertheless we consider this a bug.  Please report\n--1616-- it at http://valgrind.org/support/bug_reports.html.\n--1616-- WARNING: unhandled riscv64-linux syscall: 258\n--1616-- You may be able to write your own handler.\n--1616-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1616-- Nevertheless we consider this a bug.  Please report\n--1616-- it at http://valgrind.org/support/bug_reports.html.\n--1616-- WARNING: unhandled riscv64-linux syscall: 258\n--1616-- You may be able to write your own handler.\n--1616-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1616-- Nevertheless we consider this a bug.  Please report\n--1616-- it at http://valgrind.org/support/bug_reports.html.\n--1616-- WARNING: unhandled riscv64-linux syscall: 258\n--1616-- You may be able to write your own handler.\n--1616-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1616-- Nevertheless we consider this a bug.  Please report\n--1616-- it at http://valgrind.org/support/bug_reports.html.\n--1616-- WARNING: unhandled riscv64-linux syscall: 258\n--1616-- You may be able to write your own handler.\n--1616-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1616-- Nevertheless we consider this a bug.  Please report\n--1616-- it at http://valgrind.org/support/bug_reports.html.\n--1616-- WARNING: unhandled riscv64-linux syscall: 258\n--1616-- You may be able to write your own handler.\n--1616-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1616-- Nevertheless we consider this a bug.  Please report\n--1616-- it at http://valgrind.org/support/bug_reports.html.\n--1616-- WARNING: unhandled riscv64-linux syscall: 258\n--1616-- You may be able to write your own handler.\n--1616-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1616-- Nevertheless we consider this a bug.  Please report\n--1616-- it at http://valgrind.org/support/bug_reports.html.\n--1616-- WARNING: unhandled riscv64-linux syscall: 258\n--1616-- You may be able to write your own handler.\n--1616-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1616-- Nevertheless we consider this a bug.  Please report\n--1616-- it at http://valgrind.org/support/bug_reports.html.\n--1616-- WARNING: unhandled riscv64-linux syscall: 258\n--1616-- You may be able to write your own handler.\n--1616-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1616-- Nevertheless we consider this a bug.  Please report\n--1616-- it at http://valgrind.org/support/bug_reports.html.\n--1616-- WARNING: unhandled riscv64-linux syscall: 258\n--1616-- You may be able to write your own handler.\n--1616-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1616-- Nevertheless we consider this a bug.  Please report\n--1616-- it at http://valgrind.org/support/bug_reports.html.\n--1616-- WARNING: unhandled riscv64-linux syscall: 258\n--1616-- You may be able to write your own handler.\n--1616-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1616-- Nevertheless we consider this a bug.  Please report\n--1616-- it at http://valgrind.org/support/bug_reports.html.\n--1616-- WARNING: unhandled riscv64-linux syscall: 258\n--1616-- You may be able to write your own handler.\n--1616-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1616-- Nevertheless we consider this a bug.  Please report\n--1616-- it at http://valgrind.org/support/bug_reports.html.\n--1616-- WARNING: unhandled riscv64-linux syscall: 258\n--1616-- You may be able to write your own handler.\n--1616-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1616-- Nevertheless we consider this a bug.  Please report\n--1616-- it at http://valgrind.org/support/bug_reports.html.\n--1616-- WARNING: unhandled riscv64-linux syscall: 258\n--1616-- You may be able to write your own handler.\n--1616-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1616-- Nevertheless we consider this a bug.  Please report\n--1616-- it at http://valgrind.org/support/bug_reports.html.\n--1616-- WARNING: unhandled riscv64-linux syscall: 258\n--1616-- You may be able to write your own handler.\n--1616-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1616-- Nevertheless we consider this a bug.  Please report\n--1616-- it at http://valgrind.org/support/bug_reports.html.\n--1616-- WARNING: unhandled riscv64-linux syscall: 258\n--1616-- You may be able to write your own handler.\n--1616-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1616-- Nevertheless we consider this a bug.  Please report\n--1616-- it at http://valgrind.org/support/bug_reports.html.\n--1616-- WARNING: unhandled riscv64-linux syscall: 258\n--1616-- You may be able to write your own handler.\n--1616-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1616-- Nevertheless we consider this a bug.  Please report\n--1616-- 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:
'--1624-- WARNING: unhandled riscv64-linux syscall: 258\n--1624-- You may be able to write your own handler.\n--1624-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1624-- Nevertheless we consider this a bug.  Please report\n--1624-- it at http://valgrind.org/support/bug_reports.html.\n--1624-- WARNING: unhandled riscv64-linux syscall: 258\n--1624-- You may be able to write your own handler.\n--1624-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1624-- Nevertheless we consider this a bug.  Please report\n--1624-- it at http://valgrind.org/support/bug_reports.html.\n--1624-- WARNING: unhandled riscv64-linux syscall: 258\n--1624-- You may be able to write your own handler.\n--1624-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1624-- Nevertheless we consider this a bug.  Please report\n--1624-- it at http://valgrind.org/support/bug_reports.html.\n--1624-- WARNING: unhandled riscv64-linux syscall: 258\n--1624-- You may be able to write your own handler.\n--1624-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1624-- Nevertheless we consider this a bug.  Please report\n--1624-- it at http://valgrind.org/support/bug_reports.html.\n--1624-- WARNING: unhandled riscv64-linux syscall: 258\n--1624-- You may be able to write your own handler.\n--1624-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1624-- Nevertheless we consider this a bug.  Please report\n--1624-- it at http://valgrind.org/support/bug_reports.html.\n--1624-- WARNING: unhandled riscv64-linux syscall: 258\n--1624-- You may be able to write your own handler.\n--1624-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1624-- Nevertheless we consider this a bug.  Please report\n--1624-- it at http://valgrind.org/support/bug_reports.html.\n--1624-- WARNING: unhandled riscv64-linux syscall: 258\n--1624-- You may be able to write your own handler.\n--1624-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1624-- Nevertheless we consider this a bug.  Please report\n--1624-- it at http://valgrind.org/support/bug_reports.html.\n--1624-- WARNING: unhandled riscv64-linux syscall: 258\n--1624-- You may be able to write your own handler.\n--1624-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1624-- Nevertheless we consider this a bug.  Please report\n--1624-- it at http://valgrind.org/support/bug_reports.html.\n--1624-- WARNING: unhandled riscv64-linux syscall: 258\n--1624-- You may be able to write your own handler.\n--1624-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1624-- Nevertheless we consider this a bug.  Please report\n--1624-- it at http://valgrind.org/support/bug_reports.html.\n--1624-- WARNING: unhandled riscv64-linux syscall: 258\n--1624-- You may be able to write your own handler.\n--1624-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1624-- Nevertheless we consider this a bug.  Please report\n--1624-- it at http://valgrind.org/support/bug_reports.html.\n--1624-- WARNING: unhandled riscv64-linux syscall: 258\n--1624-- You may be able to write your own handler.\n--1624-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1624-- Nevertheless we consider this a bug.  Please report\n--1624-- it at http://valgrind.org/support/bug_reports.html.\n--1624-- WARNING: unhandled riscv64-linux syscall: 258\n--1624-- You may be able to write your own handler.\n--1624-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1624-- Nevertheless we consider this a bug.  Please report\n--1624-- it at http://valgrind.org/support/bug_reports.html.\n--1624-- WARNING: unhandled riscv64-linux syscall: 258\n--1624-- You may be able to write your own handler.\n--1624-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1624-- Nevertheless we consider this a bug.  Please report\n--1624-- it at http://valgrind.org/support/bug_reports.html.\n--1624-- WARNING: unhandled riscv64-linux syscall: 258\n--1624-- You may be able to write your own handler.\n--1624-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1624-- Nevertheless we consider this a bug.  Please report\n--1624-- it at http://valgrind.org/support/bug_reports.html.\n--1624-- WARNING: unhandled riscv64-linux syscall: 258\n--1624-- You may be able to write your own handler.\n--1624-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1624-- Nevertheless we consider this a bug.  Please report\n--1624-- it at http://valgrind.org/support/bug_reports.html.\n--1624-- WARNING: unhandled riscv64-linux syscall: 258\n--1624-- You may be able to write your own handler.\n--1624-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1624-- Nevertheless we consider this a bug.  Please report\n--1624-- it at http://valgrind.org/support/bug_reports.html.\n--1624-- WARNING: unhandled riscv64-linux syscall: 258\n--1624-- You may be able to write your own handler.\n--1624-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1624-- Nevertheless we consider this a bug.  Please report\n--1624-- it at http://valgrind.org/support/bug_reports.html.\n--1624-- WARNING: unhandled riscv64-linux syscall: 258\n--1624-- You may be able to write your own handler.\n--1624-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1624-- Nevertheless we consider this a bug.  Please report\n--1624-- 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:
'--1632-- WARNING: unhandled riscv64-linux syscall: 258\n--1632-- You may be able to write your own handler.\n--1632-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1632-- Nevertheless we consider this a bug.  Please report\n--1632-- it at http://valgrind.org/support/bug_reports.html.\n--1632-- WARNING: unhandled riscv64-linux syscall: 258\n--1632-- You may be able to write your own handler.\n--1632-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1632-- Nevertheless we consider this a bug.  Please report\n--1632-- it at http://valgrind.org/support/bug_reports.html.\n--1632-- WARNING: unhandled riscv64-linux syscall: 258\n--1632-- You may be able to write your own handler.\n--1632-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1632-- Nevertheless we consider this a bug.  Please report\n--1632-- it at http://valgrind.org/support/bug_reports.html.\n--1632-- WARNING: unhandled riscv64-linux syscall: 258\n--1632-- You may be able to write your own handler.\n--1632-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1632-- Nevertheless we consider this a bug.  Please report\n--1632-- it at http://valgrind.org/support/bug_reports.html.\n--1632-- WARNING: unhandled riscv64-linux syscall: 258\n--1632-- You may be able to write your own handler.\n--1632-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1632-- Nevertheless we consider this a bug.  Please report\n--1632-- it at http://valgrind.org/support/bug_reports.html.\n--1632-- WARNING: unhandled riscv64-linux syscall: 258\n--1632-- You may be able to write your own handler.\n--1632-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1632-- Nevertheless we consider this a bug.  Please report\n--1632-- it at http://valgrind.org/support/bug_reports.html.\n--1632-- WARNING: unhandled riscv64-linux syscall: 258\n--1632-- You may be able to write your own handler.\n--1632-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1632-- Nevertheless we consider this a bug.  Please report\n--1632-- it at http://valgrind.org/support/bug_reports.html.\n--1632-- WARNING: unhandled riscv64-linux syscall: 258\n--1632-- You may be able to write your own handler.\n--1632-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1632-- Nevertheless we consider this a bug.  Please report\n--1632-- it at http://valgrind.org/support/bug_reports.html.\n--1632-- WARNING: unhandled riscv64-linux syscall: 258\n--1632-- You may be able to write your own handler.\n--1632-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1632-- Nevertheless we consider this a bug.  Please report\n--1632-- it at http://valgrind.org/support/bug_reports.html.\n--1632-- WARNING: unhandled riscv64-linux syscall: 258\n--1632-- You may be able to write your own handler.\n--1632-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1632-- Nevertheless we consider this a bug.  Please report\n--1632-- it at http://valgrind.org/support/bug_reports.html.\n--1632-- WARNING: unhandled riscv64-linux syscall: 258\n--1632-- You may be able to write your own handler.\n--1632-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1632-- Nevertheless we consider this a bug.  Please report\n--1632-- it at http://valgrind.org/support/bug_reports.html.\n--1632-- WARNING: unhandled riscv64-linux syscall: 258\n--1632-- You may be able to write your own handler.\n--1632-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1632-- Nevertheless we consider this a bug.  Please report\n--1632-- it at http://valgrind.org/support/bug_reports.html.\n--1632-- WARNING: unhandled riscv64-linux syscall: 258\n--1632-- You may be able to write your own handler.\n--1632-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1632-- Nevertheless we consider this a bug.  Please report\n--1632-- it at http://valgrind.org/support/bug_reports.html.\n--1632-- WARNING: unhandled riscv64-linux syscall: 258\n--1632-- You may be able to write your own handler.\n--1632-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1632-- Nevertheless we consider this a bug.  Please report\n--1632-- it at http://valgrind.org/support/bug_reports.html.\n--1632-- WARNING: unhandled riscv64-linux syscall: 258\n--1632-- You may be able to write your own handler.\n--1632-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1632-- Nevertheless we consider this a bug.  Please report\n--1632-- it at http://valgrind.org/support/bug_reports.html.\n--1632-- WARNING: unhandled riscv64-linux syscall: 258\n--1632-- You may be able to write your own handler.\n--1632-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1632-- Nevertheless we consider this a bug.  Please report\n--1632-- it at http://valgrind.org/support/bug_reports.html.\n--1632-- WARNING: unhandled riscv64-linux syscall: 258\n--1632-- You may be able to write your own handler.\n--1632-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1632-- Nevertheless we consider this a bug.  Please report\n--1632-- it at http://valgrind.org/support/bug_reports.html.\n--1632-- WARNING: unhandled riscv64-linux syscall: 258\n--1632-- You may be able to write your own handler.\n--1632-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1632-- Nevertheless we consider this a bug.  Please report\n--1632-- 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:
'--1640-- WARNING: unhandled riscv64-linux syscall: 258\n--1640-- You may be able to write your own handler.\n--1640-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1640-- Nevertheless we consider this a bug.  Please report\n--1640-- it at http://valgrind.org/support/bug_reports.html.\n--1640-- WARNING: unhandled riscv64-linux syscall: 258\n--1640-- You may be able to write your own handler.\n--1640-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1640-- Nevertheless we consider this a bug.  Please report\n--1640-- it at http://valgrind.org/support/bug_reports.html.\n--1640-- WARNING: unhandled riscv64-linux syscall: 258\n--1640-- You may be able to write your own handler.\n--1640-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1640-- Nevertheless we consider this a bug.  Please report\n--1640-- it at http://valgrind.org/support/bug_reports.html.\n--1640-- WARNING: unhandled riscv64-linux syscall: 258\n--1640-- You may be able to write your own handler.\n--1640-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1640-- Nevertheless we consider this a bug.  Please report\n--1640-- it at http://valgrind.org/support/bug_reports.html.\n--1640-- WARNING: unhandled riscv64-linux syscall: 258\n--1640-- You may be able to write your own handler.\n--1640-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1640-- Nevertheless we consider this a bug.  Please report\n--1640-- it at http://valgrind.org/support/bug_reports.html.\n--1640-- WARNING: unhandled riscv64-linux syscall: 258\n--1640-- You may be able to write your own handler.\n--1640-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1640-- Nevertheless we consider this a bug.  Please report\n--1640-- it at http://valgrind.org/support/bug_reports.html.\n--1640-- WARNING: unhandled riscv64-linux syscall: 258\n--1640-- You may be able to write your own handler.\n--1640-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1640-- Nevertheless we consider this a bug.  Please report\n--1640-- it at http://valgrind.org/support/bug_reports.html.\n--1640-- WARNING: unhandled riscv64-linux syscall: 258\n--1640-- You may be able to write your own handler.\n--1640-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1640-- Nevertheless we consider this a bug.  Please report\n--1640-- it at http://valgrind.org/support/bug_reports.html.\n--1640-- WARNING: unhandled riscv64-linux syscall: 258\n--1640-- You may be able to write your own handler.\n--1640-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1640-- Nevertheless we consider this a bug.  Please report\n--1640-- it at http://valgrind.org/support/bug_reports.html.\n--1640-- WARNING: unhandled riscv64-linux syscall: 258\n--1640-- You may be able to write your own handler.\n--1640-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1640-- Nevertheless we consider this a bug.  Please report\n--1640-- it at http://valgrind.org/support/bug_reports.html.\n--1640-- WARNING: unhandled riscv64-linux syscall: 258\n--1640-- You may be able to write your own handler.\n--1640-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1640-- Nevertheless we consider this a bug.  Please report\n--1640-- it at http://valgrind.org/support/bug_reports.html.\n--1640-- WARNING: unhandled riscv64-linux syscall: 258\n--1640-- You may be able to write your own handler.\n--1640-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1640-- Nevertheless we consider this a bug.  Please report\n--1640-- it at http://valgrind.org/support/bug_reports.html.\n--1640-- WARNING: unhandled riscv64-linux syscall: 258\n--1640-- You may be able to write your own handler.\n--1640-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1640-- Nevertheless we consider this a bug.  Please report\n--1640-- it at http://valgrind.org/support/bug_reports.html.\n--1640-- WARNING: unhandled riscv64-linux syscall: 258\n--1640-- You may be able to write your own handler.\n--1640-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1640-- Nevertheless we consider this a bug.  Please report\n--1640-- it at http://valgrind.org/support/bug_reports.html.\n--1640-- WARNING: unhandled riscv64-linux syscall: 258\n--1640-- You may be able to write your own handler.\n--1640-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1640-- Nevertheless we consider this a bug.  Please report\n--1640-- it at http://valgrind.org/support/bug_reports.html.\n--1640-- WARNING: unhandled riscv64-linux syscall: 258\n--1640-- You may be able to write your own handler.\n--1640-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1640-- Nevertheless we consider this a bug.  Please report\n--1640-- it at http://valgrind.org/support/bug_reports.html.\n--1640-- WARNING: unhandled riscv64-linux syscall: 258\n--1640-- You may be able to write your own handler.\n--1640-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1640-- Nevertheless we consider this a bug.  Please report\n--1640-- it at http://valgrind.org/support/bug_reports.html.\n--1640-- WARNING: unhandled riscv64-linux syscall: 258\n--1640-- You may be able to write your own handler.\n--1640-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1640-- Nevertheless we consider this a bug.  Please report\n--1640-- 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:
'--1648-- WARNING: unhandled riscv64-linux syscall: 258\n--1648-- You may be able to write your own handler.\n--1648-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1648-- Nevertheless we consider this a bug.  Please report\n--1648-- it at http://valgrind.org/support/bug_reports.html.\n--1648-- WARNING: unhandled riscv64-linux syscall: 258\n--1648-- You may be able to write your own handler.\n--1648-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1648-- Nevertheless we consider this a bug.  Please report\n--1648-- it at http://valgrind.org/support/bug_reports.html.\n--1648-- WARNING: unhandled riscv64-linux syscall: 258\n--1648-- You may be able to write your own handler.\n--1648-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1648-- Nevertheless we consider this a bug.  Please report\n--1648-- it at http://valgrind.org/support/bug_reports.html.\n--1648-- WARNING: unhandled riscv64-linux syscall: 258\n--1648-- You may be able to write your own handler.\n--1648-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1648-- Nevertheless we consider this a bug.  Please report\n--1648-- it at http://valgrind.org/support/bug_reports.html.\n--1648-- WARNING: unhandled riscv64-linux syscall: 258\n--1648-- You may be able to write your own handler.\n--1648-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1648-- Nevertheless we consider this a bug.  Please report\n--1648-- it at http://valgrind.org/support/bug_reports.html.\n--1648-- WARNING: unhandled riscv64-linux syscall: 258\n--1648-- You may be able to write your own handler.\n--1648-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1648-- Nevertheless we consider this a bug.  Please report\n--1648-- it at http://valgrind.org/support/bug_reports.html.\n--1648-- WARNING: unhandled riscv64-linux syscall: 258\n--1648-- You may be able to write your own handler.\n--1648-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1648-- Nevertheless we consider this a bug.  Please report\n--1648-- it at http://valgrind.org/support/bug_reports.html.\n--1648-- WARNING: unhandled riscv64-linux syscall: 258\n--1648-- You may be able to write your own handler.\n--1648-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1648-- Nevertheless we consider this a bug.  Please report\n--1648-- it at http://valgrind.org/support/bug_reports.html.\n--1648-- WARNING: unhandled riscv64-linux syscall: 258\n--1648-- You may be able to write your own handler.\n--1648-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1648-- Nevertheless we consider this a bug.  Please report\n--1648-- it at http://valgrind.org/support/bug_reports.html.\n--1648-- WARNING: unhandled riscv64-linux syscall: 258\n--1648-- You may be able to write your own handler.\n--1648-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1648-- Nevertheless we consider this a bug.  Please report\n--1648-- it at http://valgrind.org/support/bug_reports.html.\n--1648-- WARNING: unhandled riscv64-linux syscall: 258\n--1648-- You may be able to write your own handler.\n--1648-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1648-- Nevertheless we consider this a bug.  Please report\n--1648-- it at http://valgrind.org/support/bug_reports.html.\n--1648-- WARNING: unhandled riscv64-linux syscall: 258\n--1648-- You may be able to write your own handler.\n--1648-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1648-- Nevertheless we consider this a bug.  Please report\n--1648-- it at http://valgrind.org/support/bug_reports.html.\n--1648-- WARNING: unhandled riscv64-linux syscall: 258\n--1648-- You may be able to write your own handler.\n--1648-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1648-- Nevertheless we consider this a bug.  Please report\n--1648-- it at http://valgrind.org/support/bug_reports.html.\n--1648-- WARNING: unhandled riscv64-linux syscall: 258\n--1648-- You may be able to write your own handler.\n--1648-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1648-- Nevertheless we consider this a bug.  Please report\n--1648-- it at http://valgrind.org/support/bug_reports.html.\n--1648-- WARNING: unhandled riscv64-linux syscall: 258\n--1648-- You may be able to write your own handler.\n--1648-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1648-- Nevertheless we consider this a bug.  Please report\n--1648-- it at http://valgrind.org/support/bug_reports.html.\n--1648-- WARNING: unhandled riscv64-linux syscall: 258\n--1648-- You may be able to write your own handler.\n--1648-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1648-- Nevertheless we consider this a bug.  Please report\n--1648-- it at http://valgrind.org/support/bug_reports.html.\n--1648-- WARNING: unhandled riscv64-linux syscall: 258\n--1648-- You may be able to write your own handler.\n--1648-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1648-- Nevertheless we consider this a bug.  Please report\n--1648-- it at http://valgrind.org/support/bug_reports.html.\n--1648-- WARNING: unhandled riscv64-linux syscall: 258\n--1648-- You may be able to write your own handler.\n--1648-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1648-- Nevertheless we consider this a bug.  Please report\n--1648-- 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:
'--1656-- WARNING: unhandled riscv64-linux syscall: 258\n--1656-- You may be able to write your own handler.\n--1656-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1656-- Nevertheless we consider this a bug.  Please report\n--1656-- it at http://valgrind.org/support/bug_reports.html.\n--1656-- WARNING: unhandled riscv64-linux syscall: 258\n--1656-- You may be able to write your own handler.\n--1656-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1656-- Nevertheless we consider this a bug.  Please report\n--1656-- it at http://valgrind.org/support/bug_reports.html.\n--1656-- WARNING: unhandled riscv64-linux syscall: 258\n--1656-- You may be able to write your own handler.\n--1656-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1656-- Nevertheless we consider this a bug.  Please report\n--1656-- it at http://valgrind.org/support/bug_reports.html.\n--1656-- WARNING: unhandled riscv64-linux syscall: 258\n--1656-- You may be able to write your own handler.\n--1656-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1656-- Nevertheless we consider this a bug.  Please report\n--1656-- it at http://valgrind.org/support/bug_reports.html.\n--1656-- WARNING: unhandled riscv64-linux syscall: 258\n--1656-- You may be able to write your own handler.\n--1656-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1656-- Nevertheless we consider this a bug.  Please report\n--1656-- it at http://valgrind.org/support/bug_reports.html.\n--1656-- WARNING: unhandled riscv64-linux syscall: 258\n--1656-- You may be able to write your own handler.\n--1656-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1656-- Nevertheless we consider this a bug.  Please report\n--1656-- it at http://valgrind.org/support/bug_reports.html.\n--1656-- WARNING: unhandled riscv64-linux syscall: 258\n--1656-- You may be able to write your own handler.\n--1656-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1656-- Nevertheless we consider this a bug.  Please report\n--1656-- it at http://valgrind.org/support/bug_reports.html.\n--1656-- WARNING: unhandled riscv64-linux syscall: 258\n--1656-- You may be able to write your own handler.\n--1656-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1656-- Nevertheless we consider this a bug.  Please report\n--1656-- it at http://valgrind.org/support/bug_reports.html.\n--1656-- WARNING: unhandled riscv64-linux syscall: 258\n--1656-- You may be able to write your own handler.\n--1656-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1656-- Nevertheless we consider this a bug.  Please report\n--1656-- it at http://valgrind.org/support/bug_reports.html.\n--1656-- WARNING: unhandled riscv64-linux syscall: 258\n--1656-- You may be able to write your own handler.\n--1656-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1656-- Nevertheless we consider this a bug.  Please report\n--1656-- it at http://valgrind.org/support/bug_reports.html.\n--1656-- WARNING: unhandled riscv64-linux syscall: 258\n--1656-- You may be able to write your own handler.\n--1656-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1656-- Nevertheless we consider this a bug.  Please report\n--1656-- it at http://valgrind.org/support/bug_reports.html.\n--1656-- WARNING: unhandled riscv64-linux syscall: 258\n--1656-- You may be able to write your own handler.\n--1656-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1656-- Nevertheless we consider this a bug.  Please report\n--1656-- it at http://valgrind.org/support/bug_reports.html.\n--1656-- WARNING: unhandled riscv64-linux syscall: 258\n--1656-- You may be able to write your own handler.\n--1656-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1656-- Nevertheless we consider this a bug.  Please report\n--1656-- it at http://valgrind.org/support/bug_reports.html.\n--1656-- WARNING: unhandled riscv64-linux syscall: 258\n--1656-- You may be able to write your own handler.\n--1656-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1656-- Nevertheless we consider this a bug.  Please report\n--1656-- it at http://valgrind.org/support/bug_reports.html.\n--1656-- WARNING: unhandled riscv64-linux syscall: 258\n--1656-- You may be able to write your own handler.\n--1656-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1656-- Nevertheless we consider this a bug.  Please report\n--1656-- it at http://valgrind.org/support/bug_reports.html.\n--1656-- WARNING: unhandled riscv64-linux syscall: 258\n--1656-- You may be able to write your own handler.\n--1656-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1656-- Nevertheless we consider this a bug.  Please report\n--1656-- it at http://valgrind.org/support/bug_reports.html.\n--1656-- WARNING: unhandled riscv64-linux syscall: 258\n--1656-- You may be able to write your own handler.\n--1656-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1656-- Nevertheless we consider this a bug.  Please report\n--1656-- it at http://valgrind.org/support/bug_reports.html.\n--1656-- WARNING: unhandled riscv64-linux syscall: 258\n--1656-- You may be able to write your own handler.\n--1656-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1656-- Nevertheless we consider this a bug.  Please report\n--1656-- 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:
'--1664-- WARNING: unhandled riscv64-linux syscall: 258\n--1664-- You may be able to write your own handler.\n--1664-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1664-- Nevertheless we consider this a bug.  Please report\n--1664-- it at http://valgrind.org/support/bug_reports.html.\n--1664-- WARNING: unhandled riscv64-linux syscall: 258\n--1664-- You may be able to write your own handler.\n--1664-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1664-- Nevertheless we consider this a bug.  Please report\n--1664-- it at http://valgrind.org/support/bug_reports.html.\n--1664-- WARNING: unhandled riscv64-linux syscall: 258\n--1664-- You may be able to write your own handler.\n--1664-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1664-- Nevertheless we consider this a bug.  Please report\n--1664-- it at http://valgrind.org/support/bug_reports.html.\n--1664-- WARNING: unhandled riscv64-linux syscall: 258\n--1664-- You may be able to write your own handler.\n--1664-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1664-- Nevertheless we consider this a bug.  Please report\n--1664-- it at http://valgrind.org/support/bug_reports.html.\n--1664-- WARNING: unhandled riscv64-linux syscall: 258\n--1664-- You may be able to write your own handler.\n--1664-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1664-- Nevertheless we consider this a bug.  Please report\n--1664-- it at http://valgrind.org/support/bug_reports.html.\n--1664-- WARNING: unhandled riscv64-linux syscall: 258\n--1664-- You may be able to write your own handler.\n--1664-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1664-- Nevertheless we consider this a bug.  Please report\n--1664-- it at http://valgrind.org/support/bug_reports.html.\n--1664-- WARNING: unhandled riscv64-linux syscall: 258\n--1664-- You may be able to write your own handler.\n--1664-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1664-- Nevertheless we consider this a bug.  Please report\n--1664-- it at http://valgrind.org/support/bug_reports.html.\n--1664-- WARNING: unhandled riscv64-linux syscall: 258\n--1664-- You may be able to write your own handler.\n--1664-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1664-- Nevertheless we consider this a bug.  Please report\n--1664-- it at http://valgrind.org/support/bug_reports.html.\n--1664-- WARNING: unhandled riscv64-linux syscall: 258\n--1664-- You may be able to write your own handler.\n--1664-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1664-- Nevertheless we consider this a bug.  Please report\n--1664-- it at http://valgrind.org/support/bug_reports.html.\n--1664-- WARNING: unhandled riscv64-linux syscall: 258\n--1664-- You may be able to write your own handler.\n--1664-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1664-- Nevertheless we consider this a bug.  Please report\n--1664-- it at http://valgrind.org/support/bug_reports.html.\n--1664-- WARNING: unhandled riscv64-linux syscall: 258\n--1664-- You may be able to write your own handler.\n--1664-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1664-- Nevertheless we consider this a bug.  Please report\n--1664-- it at http://valgrind.org/support/bug_reports.html.\n--1664-- WARNING: unhandled riscv64-linux syscall: 258\n--1664-- You may be able to write your own handler.\n--1664-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1664-- Nevertheless we consider this a bug.  Please report\n--1664-- it at http://valgrind.org/support/bug_reports.html.\n--1664-- WARNING: unhandled riscv64-linux syscall: 258\n--1664-- You may be able to write your own handler.\n--1664-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1664-- Nevertheless we consider this a bug.  Please report\n--1664-- it at http://valgrind.org/support/bug_reports.html.\n--1664-- WARNING: unhandled riscv64-linux syscall: 258\n--1664-- You may be able to write your own handler.\n--1664-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1664-- Nevertheless we consider this a bug.  Please report\n--1664-- it at http://valgrind.org/support/bug_reports.html.\n--1664-- WARNING: unhandled riscv64-linux syscall: 258\n--1664-- You may be able to write your own handler.\n--1664-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1664-- Nevertheless we consider this a bug.  Please report\n--1664-- it at http://valgrind.org/support/bug_reports.html.\n--1664-- WARNING: unhandled riscv64-linux syscall: 258\n--1664-- You may be able to write your own handler.\n--1664-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1664-- Nevertheless we consider this a bug.  Please report\n--1664-- it at http://valgrind.org/support/bug_reports.html.\n--1664-- WARNING: unhandled riscv64-linux syscall: 258\n--1664-- You may be able to write your own handler.\n--1664-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1664-- Nevertheless we consider this a bug.  Please report\n--1664-- it at http://valgrind.org/support/bug_reports.html.\n--1664-- WARNING: unhandled riscv64-linux syscall: 258\n--1664-- You may be able to write your own handler.\n--1664-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1664-- Nevertheless we consider this a bug.  Please report\n--1664-- 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:
'--1672-- WARNING: unhandled riscv64-linux syscall: 258\n--1672-- You may be able to write your own handler.\n--1672-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1672-- Nevertheless we consider this a bug.  Please report\n--1672-- it at http://valgrind.org/support/bug_reports.html.\n--1672-- WARNING: unhandled riscv64-linux syscall: 258\n--1672-- You may be able to write your own handler.\n--1672-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1672-- Nevertheless we consider this a bug.  Please report\n--1672-- it at http://valgrind.org/support/bug_reports.html.\n--1672-- WARNING: unhandled riscv64-linux syscall: 258\n--1672-- You may be able to write your own handler.\n--1672-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1672-- Nevertheless we consider this a bug.  Please report\n--1672-- it at http://valgrind.org/support/bug_reports.html.\n--1672-- WARNING: unhandled riscv64-linux syscall: 258\n--1672-- You may be able to write your own handler.\n--1672-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1672-- Nevertheless we consider this a bug.  Please report\n--1672-- it at http://valgrind.org/support/bug_reports.html.\n--1672-- WARNING: unhandled riscv64-linux syscall: 258\n--1672-- You may be able to write your own handler.\n--1672-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1672-- Nevertheless we consider this a bug.  Please report\n--1672-- it at http://valgrind.org/support/bug_reports.html.\n--1672-- WARNING: unhandled riscv64-linux syscall: 258\n--1672-- You may be able to write your own handler.\n--1672-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1672-- Nevertheless we consider this a bug.  Please report\n--1672-- it at http://valgrind.org/support/bug_reports.html.\n--1672-- WARNING: unhandled riscv64-linux syscall: 258\n--1672-- You may be able to write your own handler.\n--1672-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1672-- Nevertheless we consider this a bug.  Please report\n--1672-- it at http://valgrind.org/support/bug_reports.html.\n--1672-- WARNING: unhandled riscv64-linux syscall: 258\n--1672-- You may be able to write your own handler.\n--1672-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1672-- Nevertheless we consider this a bug.  Please report\n--1672-- it at http://valgrind.org/support/bug_reports.html.\n--1672-- WARNING: unhandled riscv64-linux syscall: 258\n--1672-- You may be able to write your own handler.\n--1672-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1672-- Nevertheless we consider this a bug.  Please report\n--1672-- it at http://valgrind.org/support/bug_reports.html.\n--1672-- WARNING: unhandled riscv64-linux syscall: 258\n--1672-- You may be able to write your own handler.\n--1672-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1672-- Nevertheless we consider this a bug.  Please report\n--1672-- it at http://valgrind.org/support/bug_reports.html.\n--1672-- WARNING: unhandled riscv64-linux syscall: 258\n--1672-- You may be able to write your own handler.\n--1672-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1672-- Nevertheless we consider this a bug.  Please report\n--1672-- it at http://valgrind.org/support/bug_reports.html.\n--1672-- WARNING: unhandled riscv64-linux syscall: 258\n--1672-- You may be able to write your own handler.\n--1672-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1672-- Nevertheless we consider this a bug.  Please report\n--1672-- it at http://valgrind.org/support/bug_reports.html.\n--1672-- WARNING: unhandled riscv64-linux syscall: 258\n--1672-- You may be able to write your own handler.\n--1672-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1672-- Nevertheless we consider this a bug.  Please report\n--1672-- it at http://valgrind.org/support/bug_reports.html.\n--1672-- WARNING: unhandled riscv64-linux syscall: 258\n--1672-- You may be able to write your own handler.\n--1672-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1672-- Nevertheless we consider this a bug.  Please report\n--1672-- it at http://valgrind.org/support/bug_reports.html.\n--1672-- WARNING: unhandled riscv64-linux syscall: 258\n--1672-- You may be able to write your own handler.\n--1672-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1672-- Nevertheless we consider this a bug.  Please report\n--1672-- it at http://valgrind.org/support/bug_reports.html.\n--1672-- WARNING: unhandled riscv64-linux syscall: 258\n--1672-- You may be able to write your own handler.\n--1672-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1672-- Nevertheless we consider this a bug.  Please report\n--1672-- it at http://valgrind.org/support/bug_reports.html.\n--1672-- WARNING: unhandled riscv64-linux syscall: 258\n--1672-- You may be able to write your own handler.\n--1672-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1672-- Nevertheless we consider this a bug.  Please report\n--1672-- it at http://valgrind.org/support/bug_reports.html.\n--1672-- WARNING: unhandled riscv64-linux syscall: 258\n--1672-- You may be able to write your own handler.\n--1672-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1672-- Nevertheless we consider this a bug.  Please report\n--1672-- 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:
'--1680-- WARNING: unhandled riscv64-linux syscall: 258\n--1680-- You may be able to write your own handler.\n--1680-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1680-- Nevertheless we consider this a bug.  Please report\n--1680-- it at http://valgrind.org/support/bug_reports.html.\n--1680-- WARNING: unhandled riscv64-linux syscall: 258\n--1680-- You may be able to write your own handler.\n--1680-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1680-- Nevertheless we consider this a bug.  Please report\n--1680-- it at http://valgrind.org/support/bug_reports.html.\n--1680-- WARNING: unhandled riscv64-linux syscall: 258\n--1680-- You may be able to write your own handler.\n--1680-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1680-- Nevertheless we consider this a bug.  Please report\n--1680-- it at http://valgrind.org/support/bug_reports.html.\n--1680-- WARNING: unhandled riscv64-linux syscall: 258\n--1680-- You may be able to write your own handler.\n--1680-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1680-- Nevertheless we consider this a bug.  Please report\n--1680-- it at http://valgrind.org/support/bug_reports.html.\n--1680-- WARNING: unhandled riscv64-linux syscall: 258\n--1680-- You may be able to write your own handler.\n--1680-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1680-- Nevertheless we consider this a bug.  Please report\n--1680-- it at http://valgrind.org/support/bug_reports.html.\n--1680-- WARNING: unhandled riscv64-linux syscall: 258\n--1680-- You may be able to write your own handler.\n--1680-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1680-- Nevertheless we consider this a bug.  Please report\n--1680-- it at http://valgrind.org/support/bug_reports.html.\n--1680-- WARNING: unhandled riscv64-linux syscall: 258\n--1680-- You may be able to write your own handler.\n--1680-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1680-- Nevertheless we consider this a bug.  Please report\n--1680-- it at http://valgrind.org/support/bug_reports.html.\n--1680-- WARNING: unhandled riscv64-linux syscall: 258\n--1680-- You may be able to write your own handler.\n--1680-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1680-- Nevertheless we consider this a bug.  Please report\n--1680-- it at http://valgrind.org/support/bug_reports.html.\n--1680-- WARNING: unhandled riscv64-linux syscall: 258\n--1680-- You may be able to write your own handler.\n--1680-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1680-- Nevertheless we consider this a bug.  Please report\n--1680-- it at http://valgrind.org/support/bug_reports.html.\n--1680-- WARNING: unhandled riscv64-linux syscall: 258\n--1680-- You may be able to write your own handler.\n--1680-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1680-- Nevertheless we consider this a bug.  Please report\n--1680-- it at http://valgrind.org/support/bug_reports.html.\n--1680-- WARNING: unhandled riscv64-linux syscall: 258\n--1680-- You may be able to write your own handler.\n--1680-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1680-- Nevertheless we consider this a bug.  Please report\n--1680-- it at http://valgrind.org/support/bug_reports.html.\n--1680-- WARNING: unhandled riscv64-linux syscall: 258\n--1680-- You may be able to write your own handler.\n--1680-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1680-- Nevertheless we consider this a bug.  Please report\n--1680-- it at http://valgrind.org/support/bug_reports.html.\n--1680-- WARNING: unhandled riscv64-linux syscall: 258\n--1680-- You may be able to write your own handler.\n--1680-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1680-- Nevertheless we consider this a bug.  Please report\n--1680-- it at http://valgrind.org/support/bug_reports.html.\n--1680-- WARNING: unhandled riscv64-linux syscall: 258\n--1680-- You may be able to write your own handler.\n--1680-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1680-- Nevertheless we consider this a bug.  Please report\n--1680-- it at http://valgrind.org/support/bug_reports.html.\n--1680-- WARNING: unhandled riscv64-linux syscall: 258\n--1680-- You may be able to write your own handler.\n--1680-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1680-- Nevertheless we consider this a bug.  Please report\n--1680-- it at http://valgrind.org/support/bug_reports.html.\n--1680-- WARNING: unhandled riscv64-linux syscall: 258\n--1680-- You may be able to write your own handler.\n--1680-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1680-- Nevertheless we consider this a bug.  Please report\n--1680-- it at http://valgrind.org/support/bug_reports.html.\n--1680-- WARNING: unhandled riscv64-linux syscall: 258\n--1680-- You may be able to write your own handler.\n--1680-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1680-- Nevertheless we consider this a bug.  Please report\n--1680-- it at http://valgrind.org/support/bug_reports.html.\n--1680-- WARNING: unhandled riscv64-linux syscall: 258\n--1680-- You may be able to write your own handler.\n--1680-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1680-- Nevertheless we consider this a bug.  Please report\n--1680-- 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:
'--1688-- WARNING: unhandled riscv64-linux syscall: 258\n--1688-- You may be able to write your own handler.\n--1688-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1688-- Nevertheless we consider this a bug.  Please report\n--1688-- it at http://valgrind.org/support/bug_reports.html.\n--1688-- WARNING: unhandled riscv64-linux syscall: 258\n--1688-- You may be able to write your own handler.\n--1688-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1688-- Nevertheless we consider this a bug.  Please report\n--1688-- it at http://valgrind.org/support/bug_reports.html.\n--1688-- WARNING: unhandled riscv64-linux syscall: 258\n--1688-- You may be able to write your own handler.\n--1688-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1688-- Nevertheless we consider this a bug.  Please report\n--1688-- it at http://valgrind.org/support/bug_reports.html.\n--1688-- WARNING: unhandled riscv64-linux syscall: 258\n--1688-- You may be able to write your own handler.\n--1688-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1688-- Nevertheless we consider this a bug.  Please report\n--1688-- it at http://valgrind.org/support/bug_reports.html.\n--1688-- WARNING: unhandled riscv64-linux syscall: 258\n--1688-- You may be able to write your own handler.\n--1688-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1688-- Nevertheless we consider this a bug.  Please report\n--1688-- it at http://valgrind.org/support/bug_reports.html.\n--1688-- WARNING: unhandled riscv64-linux syscall: 258\n--1688-- You may be able to write your own handler.\n--1688-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1688-- Nevertheless we consider this a bug.  Please report\n--1688-- it at http://valgrind.org/support/bug_reports.html.\n--1688-- WARNING: unhandled riscv64-linux syscall: 258\n--1688-- You may be able to write your own handler.\n--1688-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1688-- Nevertheless we consider this a bug.  Please report\n--1688-- it at http://valgrind.org/support/bug_reports.html.\n--1688-- WARNING: unhandled riscv64-linux syscall: 258\n--1688-- You may be able to write your own handler.\n--1688-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1688-- Nevertheless we consider this a bug.  Please report\n--1688-- it at http://valgrind.org/support/bug_reports.html.\n--1688-- WARNING: unhandled riscv64-linux syscall: 258\n--1688-- You may be able to write your own handler.\n--1688-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1688-- Nevertheless we consider this a bug.  Please report\n--1688-- it at http://valgrind.org/support/bug_reports.html.\n--1688-- WARNING: unhandled riscv64-linux syscall: 258\n--1688-- You may be able to write your own handler.\n--1688-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1688-- Nevertheless we consider this a bug.  Please report\n--1688-- it at http://valgrind.org/support/bug_reports.html.\n--1688-- WARNING: unhandled riscv64-linux syscall: 258\n--1688-- You may be able to write your own handler.\n--1688-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1688-- Nevertheless we consider this a bug.  Please report\n--1688-- it at http://valgrind.org/support/bug_reports.html.\n--1688-- WARNING: unhandled riscv64-linux syscall: 258\n--1688-- You may be able to write your own handler.\n--1688-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1688-- Nevertheless we consider this a bug.  Please report\n--1688-- it at http://valgrind.org/support/bug_reports.html.\n--1688-- WARNING: unhandled riscv64-linux syscall: 258\n--1688-- You may be able to write your own handler.\n--1688-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1688-- Nevertheless we consider this a bug.  Please report\n--1688-- it at http://valgrind.org/support/bug_reports.html.\n--1688-- WARNING: unhandled riscv64-linux syscall: 258\n--1688-- You may be able to write your own handler.\n--1688-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1688-- Nevertheless we consider this a bug.  Please report\n--1688-- it at http://valgrind.org/support/bug_reports.html.\n--1688-- WARNING: unhandled riscv64-linux syscall: 258\n--1688-- You may be able to write your own handler.\n--1688-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1688-- Nevertheless we consider this a bug.  Please report\n--1688-- it at http://valgrind.org/support/bug_reports.html.\n--1688-- WARNING: unhandled riscv64-linux syscall: 258\n--1688-- You may be able to write your own handler.\n--1688-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1688-- Nevertheless we consider this a bug.  Please report\n--1688-- it at http://valgrind.org/support/bug_reports.html.\n--1688-- WARNING: unhandled riscv64-linux syscall: 258\n--1688-- You may be able to write your own handler.\n--1688-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1688-- Nevertheless we consider this a bug.  Please report\n--1688-- it at http://valgrind.org/support/bug_reports.html.\n--1688-- WARNING: unhandled riscv64-linux syscall: 258\n--1688-- You may be able to write your own handler.\n--1688-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1688-- Nevertheless we consider this a bug.  Please report\n--1688-- 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:
'--1696-- WARNING: unhandled riscv64-linux syscall: 258\n--1696-- You may be able to write your own handler.\n--1696-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1696-- Nevertheless we consider this a bug.  Please report\n--1696-- it at http://valgrind.org/support/bug_reports.html.\n--1696-- WARNING: unhandled riscv64-linux syscall: 258\n--1696-- You may be able to write your own handler.\n--1696-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1696-- Nevertheless we consider this a bug.  Please report\n--1696-- it at http://valgrind.org/support/bug_reports.html.\n--1696-- WARNING: unhandled riscv64-linux syscall: 258\n--1696-- You may be able to write your own handler.\n--1696-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1696-- Nevertheless we consider this a bug.  Please report\n--1696-- it at http://valgrind.org/support/bug_reports.html.\n--1696-- WARNING: unhandled riscv64-linux syscall: 258\n--1696-- You may be able to write your own handler.\n--1696-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1696-- Nevertheless we consider this a bug.  Please report\n--1696-- it at http://valgrind.org/support/bug_reports.html.\n--1696-- WARNING: unhandled riscv64-linux syscall: 258\n--1696-- You may be able to write your own handler.\n--1696-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1696-- Nevertheless we consider this a bug.  Please report\n--1696-- it at http://valgrind.org/support/bug_reports.html.\n--1696-- WARNING: unhandled riscv64-linux syscall: 258\n--1696-- You may be able to write your own handler.\n--1696-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1696-- Nevertheless we consider this a bug.  Please report\n--1696-- it at http://valgrind.org/support/bug_reports.html.\n--1696-- WARNING: unhandled riscv64-linux syscall: 258\n--1696-- You may be able to write your own handler.\n--1696-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1696-- Nevertheless we consider this a bug.  Please report\n--1696-- it at http://valgrind.org/support/bug_reports.html.\n--1696-- WARNING: unhandled riscv64-linux syscall: 258\n--1696-- You may be able to write your own handler.\n--1696-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1696-- Nevertheless we consider this a bug.  Please report\n--1696-- it at http://valgrind.org/support/bug_reports.html.\n--1696-- WARNING: unhandled riscv64-linux syscall: 258\n--1696-- You may be able to write your own handler.\n--1696-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1696-- Nevertheless we consider this a bug.  Please report\n--1696-- it at http://valgrind.org/support/bug_reports.html.\n--1696-- WARNING: unhandled riscv64-linux syscall: 258\n--1696-- You may be able to write your own handler.\n--1696-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1696-- Nevertheless we consider this a bug.  Please report\n--1696-- it at http://valgrind.org/support/bug_reports.html.\n--1696-- WARNING: unhandled riscv64-linux syscall: 258\n--1696-- You may be able to write your own handler.\n--1696-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1696-- Nevertheless we consider this a bug.  Please report\n--1696-- it at http://valgrind.org/support/bug_reports.html.\n--1696-- WARNING: unhandled riscv64-linux syscall: 258\n--1696-- You may be able to write your own handler.\n--1696-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1696-- Nevertheless we consider this a bug.  Please report\n--1696-- it at http://valgrind.org/support/bug_reports.html.\n--1696-- WARNING: unhandled riscv64-linux syscall: 258\n--1696-- You may be able to write your own handler.\n--1696-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1696-- Nevertheless we consider this a bug.  Please report\n--1696-- it at http://valgrind.org/support/bug_reports.html.\n--1696-- WARNING: unhandled riscv64-linux syscall: 258\n--1696-- You may be able to write your own handler.\n--1696-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1696-- Nevertheless we consider this a bug.  Please report\n--1696-- it at http://valgrind.org/support/bug_reports.html.\n--1696-- WARNING: unhandled riscv64-linux syscall: 258\n--1696-- You may be able to write your own handler.\n--1696-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1696-- Nevertheless we consider this a bug.  Please report\n--1696-- it at http://valgrind.org/support/bug_reports.html.\n--1696-- WARNING: unhandled riscv64-linux syscall: 258\n--1696-- You may be able to write your own handler.\n--1696-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1696-- Nevertheless we consider this a bug.  Please report\n--1696-- it at http://valgrind.org/support/bug_reports.html.\n--1696-- WARNING: unhandled riscv64-linux syscall: 258\n--1696-- You may be able to write your own handler.\n--1696-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1696-- Nevertheless we consider this a bug.  Please report\n--1696-- it at http://valgrind.org/support/bug_reports.html.\n--1696-- WARNING: unhandled riscv64-linux syscall: 258\n--1696-- You may be able to write your own handler.\n--1696-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1696-- Nevertheless we consider this a bug.  Please report\n--1696-- 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:
'--1704-- WARNING: unhandled riscv64-linux syscall: 258\n--1704-- You may be able to write your own handler.\n--1704-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1704-- Nevertheless we consider this a bug.  Please report\n--1704-- it at http://valgrind.org/support/bug_reports.html.\n--1704-- WARNING: unhandled riscv64-linux syscall: 258\n--1704-- You may be able to write your own handler.\n--1704-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1704-- Nevertheless we consider this a bug.  Please report\n--1704-- it at http://valgrind.org/support/bug_reports.html.\n--1704-- WARNING: unhandled riscv64-linux syscall: 258\n--1704-- You may be able to write your own handler.\n--1704-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1704-- Nevertheless we consider this a bug.  Please report\n--1704-- it at http://valgrind.org/support/bug_reports.html.\n--1704-- WARNING: unhandled riscv64-linux syscall: 258\n--1704-- You may be able to write your own handler.\n--1704-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1704-- Nevertheless we consider this a bug.  Please report\n--1704-- it at http://valgrind.org/support/bug_reports.html.\n--1704-- WARNING: unhandled riscv64-linux syscall: 258\n--1704-- You may be able to write your own handler.\n--1704-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1704-- Nevertheless we consider this a bug.  Please report\n--1704-- it at http://valgrind.org/support/bug_reports.html.\n--1704-- WARNING: unhandled riscv64-linux syscall: 258\n--1704-- You may be able to write your own handler.\n--1704-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1704-- Nevertheless we consider this a bug.  Please report\n--1704-- it at http://valgrind.org/support/bug_reports.html.\n--1704-- WARNING: unhandled riscv64-linux syscall: 258\n--1704-- You may be able to write your own handler.\n--1704-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1704-- Nevertheless we consider this a bug.  Please report\n--1704-- it at http://valgrind.org/support/bug_reports.html.\n--1704-- WARNING: unhandled riscv64-linux syscall: 258\n--1704-- You may be able to write your own handler.\n--1704-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1704-- Nevertheless we consider this a bug.  Please report\n--1704-- it at http://valgrind.org/support/bug_reports.html.\n--1704-- WARNING: unhandled riscv64-linux syscall: 258\n--1704-- You may be able to write your own handler.\n--1704-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1704-- Nevertheless we consider this a bug.  Please report\n--1704-- it at http://valgrind.org/support/bug_reports.html.\n--1704-- WARNING: unhandled riscv64-linux syscall: 258\n--1704-- You may be able to write your own handler.\n--1704-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1704-- Nevertheless we consider this a bug.  Please report\n--1704-- it at http://valgrind.org/support/bug_reports.html.\n--1704-- WARNING: unhandled riscv64-linux syscall: 258\n--1704-- You may be able to write your own handler.\n--1704-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1704-- Nevertheless we consider this a bug.  Please report\n--1704-- it at http://valgrind.org/support/bug_reports.html.\n--1704-- WARNING: unhandled riscv64-linux syscall: 258\n--1704-- You may be able to write your own handler.\n--1704-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1704-- Nevertheless we consider this a bug.  Please report\n--1704-- it at http://valgrind.org/support/bug_reports.html.\n--1704-- WARNING: unhandled riscv64-linux syscall: 258\n--1704-- You may be able to write your own handler.\n--1704-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1704-- Nevertheless we consider this a bug.  Please report\n--1704-- it at http://valgrind.org/support/bug_reports.html.\n--1704-- WARNING: unhandled riscv64-linux syscall: 258\n--1704-- You may be able to write your own handler.\n--1704-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1704-- Nevertheless we consider this a bug.  Please report\n--1704-- it at http://valgrind.org/support/bug_reports.html.\n--1704-- WARNING: unhandled riscv64-linux syscall: 258\n--1704-- You may be able to write your own handler.\n--1704-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1704-- Nevertheless we consider this a bug.  Please report\n--1704-- it at http://valgrind.org/support/bug_reports.html.\n--1704-- WARNING: unhandled riscv64-linux syscall: 258\n--1704-- You may be able to write your own handler.\n--1704-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1704-- Nevertheless we consider this a bug.  Please report\n--1704-- it at http://valgrind.org/support/bug_reports.html.\n--1704-- WARNING: unhandled riscv64-linux syscall: 258\n--1704-- You may be able to write your own handler.\n--1704-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1704-- Nevertheless we consider this a bug.  Please report\n--1704-- it at http://valgrind.org/support/bug_reports.html.\n--1704-- WARNING: unhandled riscv64-linux syscall: 258\n--1704-- You may be able to write your own handler.\n--1704-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1704-- Nevertheless we consider this a bug.  Please report\n--1704-- 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:
'--1712-- WARNING: unhandled riscv64-linux syscall: 258\n--1712-- You may be able to write your own handler.\n--1712-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1712-- Nevertheless we consider this a bug.  Please report\n--1712-- it at http://valgrind.org/support/bug_reports.html.\n--1712-- WARNING: unhandled riscv64-linux syscall: 258\n--1712-- You may be able to write your own handler.\n--1712-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1712-- Nevertheless we consider this a bug.  Please report\n--1712-- it at http://valgrind.org/support/bug_reports.html.\n--1712-- WARNING: unhandled riscv64-linux syscall: 258\n--1712-- You may be able to write your own handler.\n--1712-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1712-- Nevertheless we consider this a bug.  Please report\n--1712-- it at http://valgrind.org/support/bug_reports.html.\n--1712-- WARNING: unhandled riscv64-linux syscall: 258\n--1712-- You may be able to write your own handler.\n--1712-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1712-- Nevertheless we consider this a bug.  Please report\n--1712-- it at http://valgrind.org/support/bug_reports.html.\n--1712-- WARNING: unhandled riscv64-linux syscall: 258\n--1712-- You may be able to write your own handler.\n--1712-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1712-- Nevertheless we consider this a bug.  Please report\n--1712-- it at http://valgrind.org/support/bug_reports.html.\n--1712-- WARNING: unhandled riscv64-linux syscall: 258\n--1712-- You may be able to write your own handler.\n--1712-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1712-- Nevertheless we consider this a bug.  Please report\n--1712-- it at http://valgrind.org/support/bug_reports.html.\n--1712-- WARNING: unhandled riscv64-linux syscall: 258\n--1712-- You may be able to write your own handler.\n--1712-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1712-- Nevertheless we consider this a bug.  Please report\n--1712-- it at http://valgrind.org/support/bug_reports.html.\n--1712-- WARNING: unhandled riscv64-linux syscall: 258\n--1712-- You may be able to write your own handler.\n--1712-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1712-- Nevertheless we consider this a bug.  Please report\n--1712-- it at http://valgrind.org/support/bug_reports.html.\n--1712-- WARNING: unhandled riscv64-linux syscall: 258\n--1712-- You may be able to write your own handler.\n--1712-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1712-- Nevertheless we consider this a bug.  Please report\n--1712-- it at http://valgrind.org/support/bug_reports.html.\n--1712-- WARNING: unhandled riscv64-linux syscall: 258\n--1712-- You may be able to write your own handler.\n--1712-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1712-- Nevertheless we consider this a bug.  Please report\n--1712-- it at http://valgrind.org/support/bug_reports.html.\n--1712-- WARNING: unhandled riscv64-linux syscall: 258\n--1712-- You may be able to write your own handler.\n--1712-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1712-- Nevertheless we consider this a bug.  Please report\n--1712-- it at http://valgrind.org/support/bug_reports.html.\n--1712-- WARNING: unhandled riscv64-linux syscall: 258\n--1712-- You may be able to write your own handler.\n--1712-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1712-- Nevertheless we consider this a bug.  Please report\n--1712-- it at http://valgrind.org/support/bug_reports.html.\n--1712-- WARNING: unhandled riscv64-linux syscall: 258\n--1712-- You may be able to write your own handler.\n--1712-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1712-- Nevertheless we consider this a bug.  Please report\n--1712-- it at http://valgrind.org/support/bug_reports.html.\n--1712-- WARNING: unhandled riscv64-linux syscall: 258\n--1712-- You may be able to write your own handler.\n--1712-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1712-- Nevertheless we consider this a bug.  Please report\n--1712-- it at http://valgrind.org/support/bug_reports.html.\n--1712-- WARNING: unhandled riscv64-linux syscall: 258\n--1712-- You may be able to write your own handler.\n--1712-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1712-- Nevertheless we consider this a bug.  Please report\n--1712-- it at http://valgrind.org/support/bug_reports.html.\n--1712-- WARNING: unhandled riscv64-linux syscall: 258\n--1712-- You may be able to write your own handler.\n--1712-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1712-- Nevertheless we consider this a bug.  Please report\n--1712-- it at http://valgrind.org/support/bug_reports.html.\n--1712-- WARNING: unhandled riscv64-linux syscall: 258\n--1712-- You may be able to write your own handler.\n--1712-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1712-- Nevertheless we consider this a bug.  Please report\n--1712-- it at http://valgrind.org/support/bug_reports.html.\n--1712-- WARNING: unhandled riscv64-linux syscall: 258\n--1712-- You may be able to write your own handler.\n--1712-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1712-- Nevertheless we consider this a bug.  Please report\n--1712-- 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:
'--1720-- WARNING: unhandled riscv64-linux syscall: 258\n--1720-- You may be able to write your own handler.\n--1720-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1720-- Nevertheless we consider this a bug.  Please report\n--1720-- it at http://valgrind.org/support/bug_reports.html.\n--1720-- WARNING: unhandled riscv64-linux syscall: 258\n--1720-- You may be able to write your own handler.\n--1720-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1720-- Nevertheless we consider this a bug.  Please report\n--1720-- it at http://valgrind.org/support/bug_reports.html.\n--1720-- WARNING: unhandled riscv64-linux syscall: 258\n--1720-- You may be able to write your own handler.\n--1720-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1720-- Nevertheless we consider this a bug.  Please report\n--1720-- it at http://valgrind.org/support/bug_reports.html.\n--1720-- WARNING: unhandled riscv64-linux syscall: 258\n--1720-- You may be able to write your own handler.\n--1720-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1720-- Nevertheless we consider this a bug.  Please report\n--1720-- it at http://valgrind.org/support/bug_reports.html.\n--1720-- WARNING: unhandled riscv64-linux syscall: 258\n--1720-- You may be able to write your own handler.\n--1720-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1720-- Nevertheless we consider this a bug.  Please report\n--1720-- it at http://valgrind.org/support/bug_reports.html.\n--1720-- WARNING: unhandled riscv64-linux syscall: 258\n--1720-- You may be able to write your own handler.\n--1720-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1720-- Nevertheless we consider this a bug.  Please report\n--1720-- it at http://valgrind.org/support/bug_reports.html.\n--1720-- WARNING: unhandled riscv64-linux syscall: 258\n--1720-- You may be able to write your own handler.\n--1720-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1720-- Nevertheless we consider this a bug.  Please report\n--1720-- it at http://valgrind.org/support/bug_reports.html.\n--1720-- WARNING: unhandled riscv64-linux syscall: 258\n--1720-- You may be able to write your own handler.\n--1720-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1720-- Nevertheless we consider this a bug.  Please report\n--1720-- it at http://valgrind.org/support/bug_reports.html.\n--1720-- WARNING: unhandled riscv64-linux syscall: 258\n--1720-- You may be able to write your own handler.\n--1720-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1720-- Nevertheless we consider this a bug.  Please report\n--1720-- it at http://valgrind.org/support/bug_reports.html.\n--1720-- WARNING: unhandled riscv64-linux syscall: 258\n--1720-- You may be able to write your own handler.\n--1720-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1720-- Nevertheless we consider this a bug.  Please report\n--1720-- it at http://valgrind.org/support/bug_reports.html.\n--1720-- WARNING: unhandled riscv64-linux syscall: 258\n--1720-- You may be able to write your own handler.\n--1720-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1720-- Nevertheless we consider this a bug.  Please report\n--1720-- it at http://valgrind.org/support/bug_reports.html.\n--1720-- WARNING: unhandled riscv64-linux syscall: 258\n--1720-- You may be able to write your own handler.\n--1720-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1720-- Nevertheless we consider this a bug.  Please report\n--1720-- it at http://valgrind.org/support/bug_reports.html.\n--1720-- WARNING: unhandled riscv64-linux syscall: 258\n--1720-- You may be able to write your own handler.\n--1720-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1720-- Nevertheless we consider this a bug.  Please report\n--1720-- it at http://valgrind.org/support/bug_reports.html.\n--1720-- WARNING: unhandled riscv64-linux syscall: 258\n--1720-- You may be able to write your own handler.\n--1720-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1720-- Nevertheless we consider this a bug.  Please report\n--1720-- it at http://valgrind.org/support/bug_reports.html.\n--1720-- WARNING: unhandled riscv64-linux syscall: 258\n--1720-- You may be able to write your own handler.\n--1720-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1720-- Nevertheless we consider this a bug.  Please report\n--1720-- it at http://valgrind.org/support/bug_reports.html.\n--1720-- WARNING: unhandled riscv64-linux syscall: 258\n--1720-- You may be able to write your own handler.\n--1720-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1720-- Nevertheless we consider this a bug.  Please report\n--1720-- it at http://valgrind.org/support/bug_reports.html.\n--1720-- WARNING: unhandled riscv64-linux syscall: 258\n--1720-- You may be able to write your own handler.\n--1720-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1720-- Nevertheless we consider this a bug.  Please report\n--1720-- it at http://valgrind.org/support/bug_reports.html.\n--1720-- WARNING: unhandled riscv64-linux syscall: 258\n--1720-- You may be able to write your own handler.\n--1720-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1720-- Nevertheless we consider this a bug.  Please report\n--1720-- 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:
'--1728-- WARNING: unhandled riscv64-linux syscall: 258\n--1728-- You may be able to write your own handler.\n--1728-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1728-- Nevertheless we consider this a bug.  Please report\n--1728-- it at http://valgrind.org/support/bug_reports.html.\n--1728-- WARNING: unhandled riscv64-linux syscall: 258\n--1728-- You may be able to write your own handler.\n--1728-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1728-- Nevertheless we consider this a bug.  Please report\n--1728-- it at http://valgrind.org/support/bug_reports.html.\n--1728-- WARNING: unhandled riscv64-linux syscall: 258\n--1728-- You may be able to write your own handler.\n--1728-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1728-- Nevertheless we consider this a bug.  Please report\n--1728-- it at http://valgrind.org/support/bug_reports.html.\n--1728-- WARNING: unhandled riscv64-linux syscall: 258\n--1728-- You may be able to write your own handler.\n--1728-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1728-- Nevertheless we consider this a bug.  Please report\n--1728-- it at http://valgrind.org/support/bug_reports.html.\n--1728-- WARNING: unhandled riscv64-linux syscall: 258\n--1728-- You may be able to write your own handler.\n--1728-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1728-- Nevertheless we consider this a bug.  Please report\n--1728-- it at http://valgrind.org/support/bug_reports.html.\n--1728-- WARNING: unhandled riscv64-linux syscall: 258\n--1728-- You may be able to write your own handler.\n--1728-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1728-- Nevertheless we consider this a bug.  Please report\n--1728-- it at http://valgrind.org/support/bug_reports.html.\n--1728-- WARNING: unhandled riscv64-linux syscall: 258\n--1728-- You may be able to write your own handler.\n--1728-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1728-- Nevertheless we consider this a bug.  Please report\n--1728-- it at http://valgrind.org/support/bug_reports.html.\n--1728-- WARNING: unhandled riscv64-linux syscall: 258\n--1728-- You may be able to write your own handler.\n--1728-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1728-- Nevertheless we consider this a bug.  Please report\n--1728-- it at http://valgrind.org/support/bug_reports.html.\n--1728-- WARNING: unhandled riscv64-linux syscall: 258\n--1728-- You may be able to write your own handler.\n--1728-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1728-- Nevertheless we consider this a bug.  Please report\n--1728-- it at http://valgrind.org/support/bug_reports.html.\n--1728-- WARNING: unhandled riscv64-linux syscall: 258\n--1728-- You may be able to write your own handler.\n--1728-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1728-- Nevertheless we consider this a bug.  Please report\n--1728-- it at http://valgrind.org/support/bug_reports.html.\n--1728-- WARNING: unhandled riscv64-linux syscall: 258\n--1728-- You may be able to write your own handler.\n--1728-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1728-- Nevertheless we consider this a bug.  Please report\n--1728-- it at http://valgrind.org/support/bug_reports.html.\n--1728-- WARNING: unhandled riscv64-linux syscall: 258\n--1728-- You may be able to write your own handler.\n--1728-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1728-- Nevertheless we consider this a bug.  Please report\n--1728-- it at http://valgrind.org/support/bug_reports.html.\n--1728-- WARNING: unhandled riscv64-linux syscall: 258\n--1728-- You may be able to write your own handler.\n--1728-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1728-- Nevertheless we consider this a bug.  Please report\n--1728-- it at http://valgrind.org/support/bug_reports.html.\n--1728-- WARNING: unhandled riscv64-linux syscall: 258\n--1728-- You may be able to write your own handler.\n--1728-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1728-- Nevertheless we consider this a bug.  Please report\n--1728-- it at http://valgrind.org/support/bug_reports.html.\n--1728-- WARNING: unhandled riscv64-linux syscall: 258\n--1728-- You may be able to write your own handler.\n--1728-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1728-- Nevertheless we consider this a bug.  Please report\n--1728-- it at http://valgrind.org/support/bug_reports.html.\n--1728-- WARNING: unhandled riscv64-linux syscall: 258\n--1728-- You may be able to write your own handler.\n--1728-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1728-- Nevertheless we consider this a bug.  Please report\n--1728-- it at http://valgrind.org/support/bug_reports.html.\n--1728-- WARNING: unhandled riscv64-linux syscall: 258\n--1728-- You may be able to write your own handler.\n--1728-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1728-- Nevertheless we consider this a bug.  Please report\n--1728-- it at http://valgrind.org/support/bug_reports.html.\n--1728-- WARNING: unhandled riscv64-linux syscall: 258\n--1728-- You may be able to write your own handler.\n--1728-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1728-- Nevertheless we consider this a bug.  Please report\n--1728-- 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:
'--1736-- WARNING: unhandled riscv64-linux syscall: 258\n--1736-- You may be able to write your own handler.\n--1736-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1736-- Nevertheless we consider this a bug.  Please report\n--1736-- it at http://valgrind.org/support/bug_reports.html.\n--1736-- WARNING: unhandled riscv64-linux syscall: 258\n--1736-- You may be able to write your own handler.\n--1736-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1736-- Nevertheless we consider this a bug.  Please report\n--1736-- it at http://valgrind.org/support/bug_reports.html.\n--1736-- WARNING: unhandled riscv64-linux syscall: 258\n--1736-- You may be able to write your own handler.\n--1736-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1736-- Nevertheless we consider this a bug.  Please report\n--1736-- it at http://valgrind.org/support/bug_reports.html.\n--1736-- WARNING: unhandled riscv64-linux syscall: 258\n--1736-- You may be able to write your own handler.\n--1736-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1736-- Nevertheless we consider this a bug.  Please report\n--1736-- it at http://valgrind.org/support/bug_reports.html.\n--1736-- WARNING: unhandled riscv64-linux syscall: 258\n--1736-- You may be able to write your own handler.\n--1736-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1736-- Nevertheless we consider this a bug.  Please report\n--1736-- it at http://valgrind.org/support/bug_reports.html.\n--1736-- WARNING: unhandled riscv64-linux syscall: 258\n--1736-- You may be able to write your own handler.\n--1736-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1736-- Nevertheless we consider this a bug.  Please report\n--1736-- it at http://valgrind.org/support/bug_reports.html.\n--1736-- WARNING: unhandled riscv64-linux syscall: 258\n--1736-- You may be able to write your own handler.\n--1736-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1736-- Nevertheless we consider this a bug.  Please report\n--1736-- it at http://valgrind.org/support/bug_reports.html.\n--1736-- WARNING: unhandled riscv64-linux syscall: 258\n--1736-- You may be able to write your own handler.\n--1736-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1736-- Nevertheless we consider this a bug.  Please report\n--1736-- it at http://valgrind.org/support/bug_reports.html.\n--1736-- WARNING: unhandled riscv64-linux syscall: 258\n--1736-- You may be able to write your own handler.\n--1736-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1736-- Nevertheless we consider this a bug.  Please report\n--1736-- it at http://valgrind.org/support/bug_reports.html.\n--1736-- WARNING: unhandled riscv64-linux syscall: 258\n--1736-- You may be able to write your own handler.\n--1736-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1736-- Nevertheless we consider this a bug.  Please report\n--1736-- it at http://valgrind.org/support/bug_reports.html.\n--1736-- WARNING: unhandled riscv64-linux syscall: 258\n--1736-- You may be able to write your own handler.\n--1736-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1736-- Nevertheless we consider this a bug.  Please report\n--1736-- it at http://valgrind.org/support/bug_reports.html.\n--1736-- WARNING: unhandled riscv64-linux syscall: 258\n--1736-- You may be able to write your own handler.\n--1736-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1736-- Nevertheless we consider this a bug.  Please report\n--1736-- it at http://valgrind.org/support/bug_reports.html.\n--1736-- WARNING: unhandled riscv64-linux syscall: 258\n--1736-- You may be able to write your own handler.\n--1736-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1736-- Nevertheless we consider this a bug.  Please report\n--1736-- it at http://valgrind.org/support/bug_reports.html.\n--1736-- WARNING: unhandled riscv64-linux syscall: 258\n--1736-- You may be able to write your own handler.\n--1736-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1736-- Nevertheless we consider this a bug.  Please report\n--1736-- it at http://valgrind.org/support/bug_reports.html.\n--1736-- WARNING: unhandled riscv64-linux syscall: 258\n--1736-- You may be able to write your own handler.\n--1736-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1736-- Nevertheless we consider this a bug.  Please report\n--1736-- it at http://valgrind.org/support/bug_reports.html.\n--1736-- WARNING: unhandled riscv64-linux syscall: 258\n--1736-- You may be able to write your own handler.\n--1736-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1736-- Nevertheless we consider this a bug.  Please report\n--1736-- it at http://valgrind.org/support/bug_reports.html.\n--1736-- WARNING: unhandled riscv64-linux syscall: 258\n--1736-- You may be able to write your own handler.\n--1736-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1736-- Nevertheless we consider this a bug.  Please report\n--1736-- it at http://valgrind.org/support/bug_reports.html.\n--1736-- WARNING: unhandled riscv64-linux syscall: 258\n--1736-- You may be able to write your own handler.\n--1736-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1736-- Nevertheless we consider this a bug.  Please report\n--1736-- 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:
'--1744-- WARNING: unhandled riscv64-linux syscall: 258\n--1744-- You may be able to write your own handler.\n--1744-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1744-- Nevertheless we consider this a bug.  Please report\n--1744-- it at http://valgrind.org/support/bug_reports.html.\n--1744-- WARNING: unhandled riscv64-linux syscall: 258\n--1744-- You may be able to write your own handler.\n--1744-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1744-- Nevertheless we consider this a bug.  Please report\n--1744-- it at http://valgrind.org/support/bug_reports.html.\n--1744-- WARNING: unhandled riscv64-linux syscall: 258\n--1744-- You may be able to write your own handler.\n--1744-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1744-- Nevertheless we consider this a bug.  Please report\n--1744-- it at http://valgrind.org/support/bug_reports.html.\n--1744-- WARNING: unhandled riscv64-linux syscall: 258\n--1744-- You may be able to write your own handler.\n--1744-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1744-- Nevertheless we consider this a bug.  Please report\n--1744-- it at http://valgrind.org/support/bug_reports.html.\n--1744-- WARNING: unhandled riscv64-linux syscall: 258\n--1744-- You may be able to write your own handler.\n--1744-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1744-- Nevertheless we consider this a bug.  Please report\n--1744-- it at http://valgrind.org/support/bug_reports.html.\n--1744-- WARNING: unhandled riscv64-linux syscall: 258\n--1744-- You may be able to write your own handler.\n--1744-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1744-- Nevertheless we consider this a bug.  Please report\n--1744-- it at http://valgrind.org/support/bug_reports.html.\n--1744-- WARNING: unhandled riscv64-linux syscall: 258\n--1744-- You may be able to write your own handler.\n--1744-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1744-- Nevertheless we consider this a bug.  Please report\n--1744-- it at http://valgrind.org/support/bug_reports.html.\n--1744-- WARNING: unhandled riscv64-linux syscall: 258\n--1744-- You may be able to write your own handler.\n--1744-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1744-- Nevertheless we consider this a bug.  Please report\n--1744-- it at http://valgrind.org/support/bug_reports.html.\n--1744-- WARNING: unhandled riscv64-linux syscall: 258\n--1744-- You may be able to write your own handler.\n--1744-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1744-- Nevertheless we consider this a bug.  Please report\n--1744-- it at http://valgrind.org/support/bug_reports.html.\n--1744-- WARNING: unhandled riscv64-linux syscall: 258\n--1744-- You may be able to write your own handler.\n--1744-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1744-- Nevertheless we consider this a bug.  Please report\n--1744-- it at http://valgrind.org/support/bug_reports.html.\n--1744-- WARNING: unhandled riscv64-linux syscall: 258\n--1744-- You may be able to write your own handler.\n--1744-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1744-- Nevertheless we consider this a bug.  Please report\n--1744-- it at http://valgrind.org/support/bug_reports.html.\n--1744-- WARNING: unhandled riscv64-linux syscall: 258\n--1744-- You may be able to write your own handler.\n--1744-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1744-- Nevertheless we consider this a bug.  Please report\n--1744-- it at http://valgrind.org/support/bug_reports.html.\n--1744-- WARNING: unhandled riscv64-linux syscall: 258\n--1744-- You may be able to write your own handler.\n--1744-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1744-- Nevertheless we consider this a bug.  Please report\n--1744-- it at http://valgrind.org/support/bug_reports.html.\n--1744-- WARNING: unhandled riscv64-linux syscall: 258\n--1744-- You may be able to write your own handler.\n--1744-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1744-- Nevertheless we consider this a bug.  Please report\n--1744-- it at http://valgrind.org/support/bug_reports.html.\n--1744-- WARNING: unhandled riscv64-linux syscall: 258\n--1744-- You may be able to write your own handler.\n--1744-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1744-- Nevertheless we consider this a bug.  Please report\n--1744-- it at http://valgrind.org/support/bug_reports.html.\n--1744-- WARNING: unhandled riscv64-linux syscall: 258\n--1744-- You may be able to write your own handler.\n--1744-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1744-- Nevertheless we consider this a bug.  Please report\n--1744-- it at http://valgrind.org/support/bug_reports.html.\n--1744-- WARNING: unhandled riscv64-linux syscall: 258\n--1744-- You may be able to write your own handler.\n--1744-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1744-- Nevertheless we consider this a bug.  Please report\n--1744-- it at http://valgrind.org/support/bug_reports.html.\n--1744-- WARNING: unhandled riscv64-linux syscall: 258\n--1744-- You may be able to write your own handler.\n--1744-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1744-- Nevertheless we consider this a bug.  Please report\n--1744-- 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:
'--1752-- WARNING: unhandled riscv64-linux syscall: 258\n--1752-- You may be able to write your own handler.\n--1752-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1752-- Nevertheless we consider this a bug.  Please report\n--1752-- it at http://valgrind.org/support/bug_reports.html.\n--1752-- WARNING: unhandled riscv64-linux syscall: 258\n--1752-- You may be able to write your own handler.\n--1752-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1752-- Nevertheless we consider this a bug.  Please report\n--1752-- it at http://valgrind.org/support/bug_reports.html.\n--1752-- WARNING: unhandled riscv64-linux syscall: 258\n--1752-- You may be able to write your own handler.\n--1752-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1752-- Nevertheless we consider this a bug.  Please report\n--1752-- it at http://valgrind.org/support/bug_reports.html.\n--1752-- WARNING: unhandled riscv64-linux syscall: 258\n--1752-- You may be able to write your own handler.\n--1752-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1752-- Nevertheless we consider this a bug.  Please report\n--1752-- it at http://valgrind.org/support/bug_reports.html.\n--1752-- WARNING: unhandled riscv64-linux syscall: 258\n--1752-- You may be able to write your own handler.\n--1752-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1752-- Nevertheless we consider this a bug.  Please report\n--1752-- it at http://valgrind.org/support/bug_reports.html.\n--1752-- WARNING: unhandled riscv64-linux syscall: 258\n--1752-- You may be able to write your own handler.\n--1752-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1752-- Nevertheless we consider this a bug.  Please report\n--1752-- it at http://valgrind.org/support/bug_reports.html.\n--1752-- WARNING: unhandled riscv64-linux syscall: 258\n--1752-- You may be able to write your own handler.\n--1752-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1752-- Nevertheless we consider this a bug.  Please report\n--1752-- it at http://valgrind.org/support/bug_reports.html.\n--1752-- WARNING: unhandled riscv64-linux syscall: 258\n--1752-- You may be able to write your own handler.\n--1752-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1752-- Nevertheless we consider this a bug.  Please report\n--1752-- it at http://valgrind.org/support/bug_reports.html.\n--1752-- WARNING: unhandled riscv64-linux syscall: 258\n--1752-- You may be able to write your own handler.\n--1752-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1752-- Nevertheless we consider this a bug.  Please report\n--1752-- it at http://valgrind.org/support/bug_reports.html.\n--1752-- WARNING: unhandled riscv64-linux syscall: 258\n--1752-- You may be able to write your own handler.\n--1752-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1752-- Nevertheless we consider this a bug.  Please report\n--1752-- it at http://valgrind.org/support/bug_reports.html.\n--1752-- WARNING: unhandled riscv64-linux syscall: 258\n--1752-- You may be able to write your own handler.\n--1752-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1752-- Nevertheless we consider this a bug.  Please report\n--1752-- it at http://valgrind.org/support/bug_reports.html.\n--1752-- WARNING: unhandled riscv64-linux syscall: 258\n--1752-- You may be able to write your own handler.\n--1752-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1752-- Nevertheless we consider this a bug.  Please report\n--1752-- it at http://valgrind.org/support/bug_reports.html.\n--1752-- WARNING: unhandled riscv64-linux syscall: 258\n--1752-- You may be able to write your own handler.\n--1752-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1752-- Nevertheless we consider this a bug.  Please report\n--1752-- it at http://valgrind.org/support/bug_reports.html.\n--1752-- WARNING: unhandled riscv64-linux syscall: 258\n--1752-- You may be able to write your own handler.\n--1752-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1752-- Nevertheless we consider this a bug.  Please report\n--1752-- it at http://valgrind.org/support/bug_reports.html.\n--1752-- WARNING: unhandled riscv64-linux syscall: 258\n--1752-- You may be able to write your own handler.\n--1752-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1752-- Nevertheless we consider this a bug.  Please report\n--1752-- it at http://valgrind.org/support/bug_reports.html.\n--1752-- WARNING: unhandled riscv64-linux syscall: 258\n--1752-- You may be able to write your own handler.\n--1752-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1752-- Nevertheless we consider this a bug.  Please report\n--1752-- it at http://valgrind.org/support/bug_reports.html.\n--1752-- WARNING: unhandled riscv64-linux syscall: 258\n--1752-- You may be able to write your own handler.\n--1752-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1752-- Nevertheless we consider this a bug.  Please report\n--1752-- it at http://valgrind.org/support/bug_reports.html.\n--1752-- WARNING: unhandled riscv64-linux syscall: 258\n--1752-- You may be able to write your own handler.\n--1752-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1752-- Nevertheless we consider this a bug.  Please report\n--1752-- 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:
'--1760-- WARNING: unhandled riscv64-linux syscall: 258\n--1760-- You may be able to write your own handler.\n--1760-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1760-- Nevertheless we consider this a bug.  Please report\n--1760-- it at http://valgrind.org/support/bug_reports.html.\n--1760-- WARNING: unhandled riscv64-linux syscall: 258\n--1760-- You may be able to write your own handler.\n--1760-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1760-- Nevertheless we consider this a bug.  Please report\n--1760-- it at http://valgrind.org/support/bug_reports.html.\n--1760-- WARNING: unhandled riscv64-linux syscall: 258\n--1760-- You may be able to write your own handler.\n--1760-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1760-- Nevertheless we consider this a bug.  Please report\n--1760-- it at http://valgrind.org/support/bug_reports.html.\n--1760-- WARNING: unhandled riscv64-linux syscall: 258\n--1760-- You may be able to write your own handler.\n--1760-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1760-- Nevertheless we consider this a bug.  Please report\n--1760-- it at http://valgrind.org/support/bug_reports.html.\n--1760-- WARNING: unhandled riscv64-linux syscall: 258\n--1760-- You may be able to write your own handler.\n--1760-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1760-- Nevertheless we consider this a bug.  Please report\n--1760-- it at http://valgrind.org/support/bug_reports.html.\n--1760-- WARNING: unhandled riscv64-linux syscall: 258\n--1760-- You may be able to write your own handler.\n--1760-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1760-- Nevertheless we consider this a bug.  Please report\n--1760-- it at http://valgrind.org/support/bug_reports.html.\n--1760-- WARNING: unhandled riscv64-linux syscall: 258\n--1760-- You may be able to write your own handler.\n--1760-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1760-- Nevertheless we consider this a bug.  Please report\n--1760-- it at http://valgrind.org/support/bug_reports.html.\n--1760-- WARNING: unhandled riscv64-linux syscall: 258\n--1760-- You may be able to write your own handler.\n--1760-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1760-- Nevertheless we consider this a bug.  Please report\n--1760-- it at http://valgrind.org/support/bug_reports.html.\n--1760-- WARNING: unhandled riscv64-linux syscall: 258\n--1760-- You may be able to write your own handler.\n--1760-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1760-- Nevertheless we consider this a bug.  Please report\n--1760-- it at http://valgrind.org/support/bug_reports.html.\n--1760-- WARNING: unhandled riscv64-linux syscall: 258\n--1760-- You may be able to write your own handler.\n--1760-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1760-- Nevertheless we consider this a bug.  Please report\n--1760-- it at http://valgrind.org/support/bug_reports.html.\n--1760-- WARNING: unhandled riscv64-linux syscall: 258\n--1760-- You may be able to write your own handler.\n--1760-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1760-- Nevertheless we consider this a bug.  Please report\n--1760-- it at http://valgrind.org/support/bug_reports.html.\n--1760-- WARNING: unhandled riscv64-linux syscall: 258\n--1760-- You may be able to write your own handler.\n--1760-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1760-- Nevertheless we consider this a bug.  Please report\n--1760-- it at http://valgrind.org/support/bug_reports.html.\n--1760-- WARNING: unhandled riscv64-linux syscall: 258\n--1760-- You may be able to write your own handler.\n--1760-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1760-- Nevertheless we consider this a bug.  Please report\n--1760-- it at http://valgrind.org/support/bug_reports.html.\n--1760-- WARNING: unhandled riscv64-linux syscall: 258\n--1760-- You may be able to write your own handler.\n--1760-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1760-- Nevertheless we consider this a bug.  Please report\n--1760-- it at http://valgrind.org/support/bug_reports.html.\n--1760-- WARNING: unhandled riscv64-linux syscall: 258\n--1760-- You may be able to write your own handler.\n--1760-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1760-- Nevertheless we consider this a bug.  Please report\n--1760-- it at http://valgrind.org/support/bug_reports.html.\n--1760-- WARNING: unhandled riscv64-linux syscall: 258\n--1760-- You may be able to write your own handler.\n--1760-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1760-- Nevertheless we consider this a bug.  Please report\n--1760-- it at http://valgrind.org/support/bug_reports.html.\n--1760-- WARNING: unhandled riscv64-linux syscall: 258\n--1760-- You may be able to write your own handler.\n--1760-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1760-- Nevertheless we consider this a bug.  Please report\n--1760-- it at http://valgrind.org/support/bug_reports.html.\n--1760-- WARNING: unhandled riscv64-linux syscall: 258\n--1760-- You may be able to write your own handler.\n--1760-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1760-- Nevertheless we consider this a bug.  Please report\n--1760-- 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:
'--1768-- WARNING: unhandled riscv64-linux syscall: 258\n--1768-- You may be able to write your own handler.\n--1768-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1768-- Nevertheless we consider this a bug.  Please report\n--1768-- it at http://valgrind.org/support/bug_reports.html.\n--1768-- WARNING: unhandled riscv64-linux syscall: 258\n--1768-- You may be able to write your own handler.\n--1768-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1768-- Nevertheless we consider this a bug.  Please report\n--1768-- it at http://valgrind.org/support/bug_reports.html.\n--1768-- WARNING: unhandled riscv64-linux syscall: 258\n--1768-- You may be able to write your own handler.\n--1768-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1768-- Nevertheless we consider this a bug.  Please report\n--1768-- it at http://valgrind.org/support/bug_reports.html.\n--1768-- WARNING: unhandled riscv64-linux syscall: 258\n--1768-- You may be able to write your own handler.\n--1768-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1768-- Nevertheless we consider this a bug.  Please report\n--1768-- it at http://valgrind.org/support/bug_reports.html.\n--1768-- WARNING: unhandled riscv64-linux syscall: 258\n--1768-- You may be able to write your own handler.\n--1768-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1768-- Nevertheless we consider this a bug.  Please report\n--1768-- it at http://valgrind.org/support/bug_reports.html.\n--1768-- WARNING: unhandled riscv64-linux syscall: 258\n--1768-- You may be able to write your own handler.\n--1768-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1768-- Nevertheless we consider this a bug.  Please report\n--1768-- it at http://valgrind.org/support/bug_reports.html.\n--1768-- WARNING: unhandled riscv64-linux syscall: 258\n--1768-- You may be able to write your own handler.\n--1768-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1768-- Nevertheless we consider this a bug.  Please report\n--1768-- it at http://valgrind.org/support/bug_reports.html.\n--1768-- WARNING: unhandled riscv64-linux syscall: 258\n--1768-- You may be able to write your own handler.\n--1768-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1768-- Nevertheless we consider this a bug.  Please report\n--1768-- it at http://valgrind.org/support/bug_reports.html.\n--1768-- WARNING: unhandled riscv64-linux syscall: 258\n--1768-- You may be able to write your own handler.\n--1768-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1768-- Nevertheless we consider this a bug.  Please report\n--1768-- it at http://valgrind.org/support/bug_reports.html.\n--1768-- WARNING: unhandled riscv64-linux syscall: 258\n--1768-- You may be able to write your own handler.\n--1768-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1768-- Nevertheless we consider this a bug.  Please report\n--1768-- it at http://valgrind.org/support/bug_reports.html.\n--1768-- WARNING: unhandled riscv64-linux syscall: 258\n--1768-- You may be able to write your own handler.\n--1768-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1768-- Nevertheless we consider this a bug.  Please report\n--1768-- it at http://valgrind.org/support/bug_reports.html.\n--1768-- WARNING: unhandled riscv64-linux syscall: 258\n--1768-- You may be able to write your own handler.\n--1768-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1768-- Nevertheless we consider this a bug.  Please report\n--1768-- it at http://valgrind.org/support/bug_reports.html.\n--1768-- WARNING: unhandled riscv64-linux syscall: 258\n--1768-- You may be able to write your own handler.\n--1768-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1768-- Nevertheless we consider this a bug.  Please report\n--1768-- it at http://valgrind.org/support/bug_reports.html.\n--1768-- WARNING: unhandled riscv64-linux syscall: 258\n--1768-- You may be able to write your own handler.\n--1768-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1768-- Nevertheless we consider this a bug.  Please report\n--1768-- it at http://valgrind.org/support/bug_reports.html.\n--1768-- WARNING: unhandled riscv64-linux syscall: 258\n--1768-- You may be able to write your own handler.\n--1768-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1768-- Nevertheless we consider this a bug.  Please report\n--1768-- it at http://valgrind.org/support/bug_reports.html.\n--1768-- WARNING: unhandled riscv64-linux syscall: 258\n--1768-- You may be able to write your own handler.\n--1768-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1768-- Nevertheless we consider this a bug.  Please report\n--1768-- it at http://valgrind.org/support/bug_reports.html.\n--1768-- WARNING: unhandled riscv64-linux syscall: 258\n--1768-- You may be able to write your own handler.\n--1768-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1768-- Nevertheless we consider this a bug.  Please report\n--1768-- it at http://valgrind.org/support/bug_reports.html.\n--1768-- WARNING: unhandled riscv64-linux syscall: 258\n--1768-- You may be able to write your own handler.\n--1768-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1768-- Nevertheless we consider this a bug.  Please report\n--1768-- 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:
'--1776-- WARNING: unhandled riscv64-linux syscall: 258\n--1776-- You may be able to write your own handler.\n--1776-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1776-- Nevertheless we consider this a bug.  Please report\n--1776-- it at http://valgrind.org/support/bug_reports.html.\n--1776-- WARNING: unhandled riscv64-linux syscall: 258\n--1776-- You may be able to write your own handler.\n--1776-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1776-- Nevertheless we consider this a bug.  Please report\n--1776-- it at http://valgrind.org/support/bug_reports.html.\n--1776-- WARNING: unhandled riscv64-linux syscall: 258\n--1776-- You may be able to write your own handler.\n--1776-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1776-- Nevertheless we consider this a bug.  Please report\n--1776-- it at http://valgrind.org/support/bug_reports.html.\n--1776-- WARNING: unhandled riscv64-linux syscall: 258\n--1776-- You may be able to write your own handler.\n--1776-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1776-- Nevertheless we consider this a bug.  Please report\n--1776-- it at http://valgrind.org/support/bug_reports.html.\n--1776-- WARNING: unhandled riscv64-linux syscall: 258\n--1776-- You may be able to write your own handler.\n--1776-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1776-- Nevertheless we consider this a bug.  Please report\n--1776-- it at http://valgrind.org/support/bug_reports.html.\n--1776-- WARNING: unhandled riscv64-linux syscall: 258\n--1776-- You may be able to write your own handler.\n--1776-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1776-- Nevertheless we consider this a bug.  Please report\n--1776-- it at http://valgrind.org/support/bug_reports.html.\n--1776-- WARNING: unhandled riscv64-linux syscall: 258\n--1776-- You may be able to write your own handler.\n--1776-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1776-- Nevertheless we consider this a bug.  Please report\n--1776-- it at http://valgrind.org/support/bug_reports.html.\n--1776-- WARNING: unhandled riscv64-linux syscall: 258\n--1776-- You may be able to write your own handler.\n--1776-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1776-- Nevertheless we consider this a bug.  Please report\n--1776-- it at http://valgrind.org/support/bug_reports.html.\n--1776-- WARNING: unhandled riscv64-linux syscall: 258\n--1776-- You may be able to write your own handler.\n--1776-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1776-- Nevertheless we consider this a bug.  Please report\n--1776-- it at http://valgrind.org/support/bug_reports.html.\n--1776-- WARNING: unhandled riscv64-linux syscall: 258\n--1776-- You may be able to write your own handler.\n--1776-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1776-- Nevertheless we consider this a bug.  Please report\n--1776-- it at http://valgrind.org/support/bug_reports.html.\n--1776-- WARNING: unhandled riscv64-linux syscall: 258\n--1776-- You may be able to write your own handler.\n--1776-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1776-- Nevertheless we consider this a bug.  Please report\n--1776-- it at http://valgrind.org/support/bug_reports.html.\n--1776-- WARNING: unhandled riscv64-linux syscall: 258\n--1776-- You may be able to write your own handler.\n--1776-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1776-- Nevertheless we consider this a bug.  Please report\n--1776-- it at http://valgrind.org/support/bug_reports.html.\n--1776-- WARNING: unhandled riscv64-linux syscall: 258\n--1776-- You may be able to write your own handler.\n--1776-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1776-- Nevertheless we consider this a bug.  Please report\n--1776-- it at http://valgrind.org/support/bug_reports.html.\n--1776-- WARNING: unhandled riscv64-linux syscall: 258\n--1776-- You may be able to write your own handler.\n--1776-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1776-- Nevertheless we consider this a bug.  Please report\n--1776-- it at http://valgrind.org/support/bug_reports.html.\n--1776-- WARNING: unhandled riscv64-linux syscall: 258\n--1776-- You may be able to write your own handler.\n--1776-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1776-- Nevertheless we consider this a bug.  Please report\n--1776-- it at http://valgrind.org/support/bug_reports.html.\n--1776-- WARNING: unhandled riscv64-linux syscall: 258\n--1776-- You may be able to write your own handler.\n--1776-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1776-- Nevertheless we consider this a bug.  Please report\n--1776-- it at http://valgrind.org/support/bug_reports.html.\n--1776-- WARNING: unhandled riscv64-linux syscall: 258\n--1776-- You may be able to write your own handler.\n--1776-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1776-- Nevertheless we consider this a bug.  Please report\n--1776-- it at http://valgrind.org/support/bug_reports.html.\n--1776-- WARNING: unhandled riscv64-linux syscall: 258\n--1776-- You may be able to write your own handler.\n--1776-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1776-- Nevertheless we consider this a bug.  Please report\n--1776-- 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:
'--1784-- WARNING: unhandled riscv64-linux syscall: 258\n--1784-- You may be able to write your own handler.\n--1784-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1784-- Nevertheless we consider this a bug.  Please report\n--1784-- it at http://valgrind.org/support/bug_reports.html.\n--1784-- WARNING: unhandled riscv64-linux syscall: 258\n--1784-- You may be able to write your own handler.\n--1784-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1784-- Nevertheless we consider this a bug.  Please report\n--1784-- it at http://valgrind.org/support/bug_reports.html.\n--1784-- WARNING: unhandled riscv64-linux syscall: 258\n--1784-- You may be able to write your own handler.\n--1784-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1784-- Nevertheless we consider this a bug.  Please report\n--1784-- it at http://valgrind.org/support/bug_reports.html.\n--1784-- WARNING: unhandled riscv64-linux syscall: 258\n--1784-- You may be able to write your own handler.\n--1784-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1784-- Nevertheless we consider this a bug.  Please report\n--1784-- it at http://valgrind.org/support/bug_reports.html.\n--1784-- WARNING: unhandled riscv64-linux syscall: 258\n--1784-- You may be able to write your own handler.\n--1784-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1784-- Nevertheless we consider this a bug.  Please report\n--1784-- it at http://valgrind.org/support/bug_reports.html.\n--1784-- WARNING: unhandled riscv64-linux syscall: 258\n--1784-- You may be able to write your own handler.\n--1784-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1784-- Nevertheless we consider this a bug.  Please report\n--1784-- it at http://valgrind.org/support/bug_reports.html.\n--1784-- WARNING: unhandled riscv64-linux syscall: 258\n--1784-- You may be able to write your own handler.\n--1784-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1784-- Nevertheless we consider this a bug.  Please report\n--1784-- it at http://valgrind.org/support/bug_reports.html.\n--1784-- WARNING: unhandled riscv64-linux syscall: 258\n--1784-- You may be able to write your own handler.\n--1784-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1784-- Nevertheless we consider this a bug.  Please report\n--1784-- it at http://valgrind.org/support/bug_reports.html.\n--1784-- WARNING: unhandled riscv64-linux syscall: 258\n--1784-- You may be able to write your own handler.\n--1784-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1784-- Nevertheless we consider this a bug.  Please report\n--1784-- it at http://valgrind.org/support/bug_reports.html.\n--1784-- WARNING: unhandled riscv64-linux syscall: 258\n--1784-- You may be able to write your own handler.\n--1784-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1784-- Nevertheless we consider this a bug.  Please report\n--1784-- it at http://valgrind.org/support/bug_reports.html.\n--1784-- WARNING: unhandled riscv64-linux syscall: 258\n--1784-- You may be able to write your own handler.\n--1784-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1784-- Nevertheless we consider this a bug.  Please report\n--1784-- it at http://valgrind.org/support/bug_reports.html.\n--1784-- WARNING: unhandled riscv64-linux syscall: 258\n--1784-- You may be able to write your own handler.\n--1784-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1784-- Nevertheless we consider this a bug.  Please report\n--1784-- it at http://valgrind.org/support/bug_reports.html.\n--1784-- WARNING: unhandled riscv64-linux syscall: 258\n--1784-- You may be able to write your own handler.\n--1784-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1784-- Nevertheless we consider this a bug.  Please report\n--1784-- it at http://valgrind.org/support/bug_reports.html.\n--1784-- WARNING: unhandled riscv64-linux syscall: 258\n--1784-- You may be able to write your own handler.\n--1784-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1784-- Nevertheless we consider this a bug.  Please report\n--1784-- it at http://valgrind.org/support/bug_reports.html.\n--1784-- WARNING: unhandled riscv64-linux syscall: 258\n--1784-- You may be able to write your own handler.\n--1784-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1784-- Nevertheless we consider this a bug.  Please report\n--1784-- it at http://valgrind.org/support/bug_reports.html.\n--1784-- WARNING: unhandled riscv64-linux syscall: 258\n--1784-- You may be able to write your own handler.\n--1784-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1784-- Nevertheless we consider this a bug.  Please report\n--1784-- it at http://valgrind.org/support/bug_reports.html.\n--1784-- WARNING: unhandled riscv64-linux syscall: 258\n--1784-- You may be able to write your own handler.\n--1784-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1784-- Nevertheless we consider this a bug.  Please report\n--1784-- it at http://valgrind.org/support/bug_reports.html.\n--1784-- WARNING: unhandled riscv64-linux syscall: 258\n--1784-- You may be able to write your own handler.\n--1784-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1784-- Nevertheless we consider this a bug.  Please report\n--1784-- 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:
'--1792-- WARNING: unhandled riscv64-linux syscall: 258\n--1792-- You may be able to write your own handler.\n--1792-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1792-- Nevertheless we consider this a bug.  Please report\n--1792-- it at http://valgrind.org/support/bug_reports.html.\n--1792-- WARNING: unhandled riscv64-linux syscall: 258\n--1792-- You may be able to write your own handler.\n--1792-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1792-- Nevertheless we consider this a bug.  Please report\n--1792-- it at http://valgrind.org/support/bug_reports.html.\n--1792-- WARNING: unhandled riscv64-linux syscall: 258\n--1792-- You may be able to write your own handler.\n--1792-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1792-- Nevertheless we consider this a bug.  Please report\n--1792-- it at http://valgrind.org/support/bug_reports.html.\n--1792-- WARNING: unhandled riscv64-linux syscall: 258\n--1792-- You may be able to write your own handler.\n--1792-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1792-- Nevertheless we consider this a bug.  Please report\n--1792-- it at http://valgrind.org/support/bug_reports.html.\n--1792-- WARNING: unhandled riscv64-linux syscall: 258\n--1792-- You may be able to write your own handler.\n--1792-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1792-- Nevertheless we consider this a bug.  Please report\n--1792-- it at http://valgrind.org/support/bug_reports.html.\n--1792-- WARNING: unhandled riscv64-linux syscall: 258\n--1792-- You may be able to write your own handler.\n--1792-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1792-- Nevertheless we consider this a bug.  Please report\n--1792-- it at http://valgrind.org/support/bug_reports.html.\n--1792-- WARNING: unhandled riscv64-linux syscall: 258\n--1792-- You may be able to write your own handler.\n--1792-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1792-- Nevertheless we consider this a bug.  Please report\n--1792-- it at http://valgrind.org/support/bug_reports.html.\n--1792-- WARNING: unhandled riscv64-linux syscall: 258\n--1792-- You may be able to write your own handler.\n--1792-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1792-- Nevertheless we consider this a bug.  Please report\n--1792-- it at http://valgrind.org/support/bug_reports.html.\n--1792-- WARNING: unhandled riscv64-linux syscall: 258\n--1792-- You may be able to write your own handler.\n--1792-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1792-- Nevertheless we consider this a bug.  Please report\n--1792-- it at http://valgrind.org/support/bug_reports.html.\n--1792-- WARNING: unhandled riscv64-linux syscall: 258\n--1792-- You may be able to write your own handler.\n--1792-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1792-- Nevertheless we consider this a bug.  Please report\n--1792-- it at http://valgrind.org/support/bug_reports.html.\n--1792-- WARNING: unhandled riscv64-linux syscall: 258\n--1792-- You may be able to write your own handler.\n--1792-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1792-- Nevertheless we consider this a bug.  Please report\n--1792-- it at http://valgrind.org/support/bug_reports.html.\n--1792-- WARNING: unhandled riscv64-linux syscall: 258\n--1792-- You may be able to write your own handler.\n--1792-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1792-- Nevertheless we consider this a bug.  Please report\n--1792-- it at http://valgrind.org/support/bug_reports.html.\n--1792-- WARNING: unhandled riscv64-linux syscall: 258\n--1792-- You may be able to write your own handler.\n--1792-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1792-- Nevertheless we consider this a bug.  Please report\n--1792-- it at http://valgrind.org/support/bug_reports.html.\n--1792-- WARNING: unhandled riscv64-linux syscall: 258\n--1792-- You may be able to write your own handler.\n--1792-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1792-- Nevertheless we consider this a bug.  Please report\n--1792-- it at http://valgrind.org/support/bug_reports.html.\n--1792-- WARNING: unhandled riscv64-linux syscall: 258\n--1792-- You may be able to write your own handler.\n--1792-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1792-- Nevertheless we consider this a bug.  Please report\n--1792-- it at http://valgrind.org/support/bug_reports.html.\n--1792-- WARNING: unhandled riscv64-linux syscall: 258\n--1792-- You may be able to write your own handler.\n--1792-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1792-- Nevertheless we consider this a bug.  Please report\n--1792-- it at http://valgrind.org/support/bug_reports.html.\n--1792-- WARNING: unhandled riscv64-linux syscall: 258\n--1792-- You may be able to write your own handler.\n--1792-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1792-- Nevertheless we consider this a bug.  Please report\n--1792-- it at http://valgrind.org/support/bug_reports.html.\n--1792-- WARNING: unhandled riscv64-linux syscall: 258\n--1792-- You may be able to write your own handler.\n--1792-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1792-- Nevertheless we consider this a bug.  Please report\n--1792-- 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:
'--1800-- WARNING: unhandled riscv64-linux syscall: 258\n--1800-- You may be able to write your own handler.\n--1800-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1800-- Nevertheless we consider this a bug.  Please report\n--1800-- it at http://valgrind.org/support/bug_reports.html.\n--1800-- WARNING: unhandled riscv64-linux syscall: 258\n--1800-- You may be able to write your own handler.\n--1800-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1800-- Nevertheless we consider this a bug.  Please report\n--1800-- it at http://valgrind.org/support/bug_reports.html.\n--1800-- WARNING: unhandled riscv64-linux syscall: 258\n--1800-- You may be able to write your own handler.\n--1800-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1800-- Nevertheless we consider this a bug.  Please report\n--1800-- it at http://valgrind.org/support/bug_reports.html.\n--1800-- WARNING: unhandled riscv64-linux syscall: 258\n--1800-- You may be able to write your own handler.\n--1800-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1800-- Nevertheless we consider this a bug.  Please report\n--1800-- it at http://valgrind.org/support/bug_reports.html.\n--1800-- WARNING: unhandled riscv64-linux syscall: 258\n--1800-- You may be able to write your own handler.\n--1800-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1800-- Nevertheless we consider this a bug.  Please report\n--1800-- it at http://valgrind.org/support/bug_reports.html.\n--1800-- WARNING: unhandled riscv64-linux syscall: 258\n--1800-- You may be able to write your own handler.\n--1800-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1800-- Nevertheless we consider this a bug.  Please report\n--1800-- it at http://valgrind.org/support/bug_reports.html.\n--1800-- WARNING: unhandled riscv64-linux syscall: 258\n--1800-- You may be able to write your own handler.\n--1800-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1800-- Nevertheless we consider this a bug.  Please report\n--1800-- it at http://valgrind.org/support/bug_reports.html.\n--1800-- WARNING: unhandled riscv64-linux syscall: 258\n--1800-- You may be able to write your own handler.\n--1800-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1800-- Nevertheless we consider this a bug.  Please report\n--1800-- it at http://valgrind.org/support/bug_reports.html.\n--1800-- WARNING: unhandled riscv64-linux syscall: 258\n--1800-- You may be able to write your own handler.\n--1800-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1800-- Nevertheless we consider this a bug.  Please report\n--1800-- it at http://valgrind.org/support/bug_reports.html.\n--1800-- WARNING: unhandled riscv64-linux syscall: 258\n--1800-- You may be able to write your own handler.\n--1800-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1800-- Nevertheless we consider this a bug.  Please report\n--1800-- it at http://valgrind.org/support/bug_reports.html.\n--1800-- WARNING: unhandled riscv64-linux syscall: 258\n--1800-- You may be able to write your own handler.\n--1800-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1800-- Nevertheless we consider this a bug.  Please report\n--1800-- it at http://valgrind.org/support/bug_reports.html.\n--1800-- WARNING: unhandled riscv64-linux syscall: 258\n--1800-- You may be able to write your own handler.\n--1800-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1800-- Nevertheless we consider this a bug.  Please report\n--1800-- it at http://valgrind.org/support/bug_reports.html.\n--1800-- WARNING: unhandled riscv64-linux syscall: 258\n--1800-- You may be able to write your own handler.\n--1800-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1800-- Nevertheless we consider this a bug.  Please report\n--1800-- it at http://valgrind.org/support/bug_reports.html.\n--1800-- WARNING: unhandled riscv64-linux syscall: 258\n--1800-- You may be able to write your own handler.\n--1800-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1800-- Nevertheless we consider this a bug.  Please report\n--1800-- it at http://valgrind.org/support/bug_reports.html.\n--1800-- WARNING: unhandled riscv64-linux syscall: 258\n--1800-- You may be able to write your own handler.\n--1800-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1800-- Nevertheless we consider this a bug.  Please report\n--1800-- it at http://valgrind.org/support/bug_reports.html.\n--1800-- WARNING: unhandled riscv64-linux syscall: 258\n--1800-- You may be able to write your own handler.\n--1800-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1800-- Nevertheless we consider this a bug.  Please report\n--1800-- it at http://valgrind.org/support/bug_reports.html.\n--1800-- WARNING: unhandled riscv64-linux syscall: 258\n--1800-- You may be able to write your own handler.\n--1800-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1800-- Nevertheless we consider this a bug.  Please report\n--1800-- it at http://valgrind.org/support/bug_reports.html.\n--1800-- WARNING: unhandled riscv64-linux syscall: 258\n--1800-- You may be able to write your own handler.\n--1800-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1800-- Nevertheless we consider this a bug.  Please report\n--1800-- 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:
'--1808-- WARNING: unhandled riscv64-linux syscall: 258\n--1808-- You may be able to write your own handler.\n--1808-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1808-- Nevertheless we consider this a bug.  Please report\n--1808-- it at http://valgrind.org/support/bug_reports.html.\n--1808-- WARNING: unhandled riscv64-linux syscall: 258\n--1808-- You may be able to write your own handler.\n--1808-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1808-- Nevertheless we consider this a bug.  Please report\n--1808-- it at http://valgrind.org/support/bug_reports.html.\n--1808-- WARNING: unhandled riscv64-linux syscall: 258\n--1808-- You may be able to write your own handler.\n--1808-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1808-- Nevertheless we consider this a bug.  Please report\n--1808-- it at http://valgrind.org/support/bug_reports.html.\n--1808-- WARNING: unhandled riscv64-linux syscall: 258\n--1808-- You may be able to write your own handler.\n--1808-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1808-- Nevertheless we consider this a bug.  Please report\n--1808-- it at http://valgrind.org/support/bug_reports.html.\n--1808-- WARNING: unhandled riscv64-linux syscall: 258\n--1808-- You may be able to write your own handler.\n--1808-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1808-- Nevertheless we consider this a bug.  Please report\n--1808-- it at http://valgrind.org/support/bug_reports.html.\n--1808-- WARNING: unhandled riscv64-linux syscall: 258\n--1808-- You may be able to write your own handler.\n--1808-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1808-- Nevertheless we consider this a bug.  Please report\n--1808-- it at http://valgrind.org/support/bug_reports.html.\n--1808-- WARNING: unhandled riscv64-linux syscall: 258\n--1808-- You may be able to write your own handler.\n--1808-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1808-- Nevertheless we consider this a bug.  Please report\n--1808-- it at http://valgrind.org/support/bug_reports.html.\n--1808-- WARNING: unhandled riscv64-linux syscall: 258\n--1808-- You may be able to write your own handler.\n--1808-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1808-- Nevertheless we consider this a bug.  Please report\n--1808-- it at http://valgrind.org/support/bug_reports.html.\n--1808-- WARNING: unhandled riscv64-linux syscall: 258\n--1808-- You may be able to write your own handler.\n--1808-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1808-- Nevertheless we consider this a bug.  Please report\n--1808-- it at http://valgrind.org/support/bug_reports.html.\n--1808-- WARNING: unhandled riscv64-linux syscall: 258\n--1808-- You may be able to write your own handler.\n--1808-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1808-- Nevertheless we consider this a bug.  Please report\n--1808-- it at http://valgrind.org/support/bug_reports.html.\n--1808-- WARNING: unhandled riscv64-linux syscall: 258\n--1808-- You may be able to write your own handler.\n--1808-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1808-- Nevertheless we consider this a bug.  Please report\n--1808-- it at http://valgrind.org/support/bug_reports.html.\n--1808-- WARNING: unhandled riscv64-linux syscall: 258\n--1808-- You may be able to write your own handler.\n--1808-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1808-- Nevertheless we consider this a bug.  Please report\n--1808-- it at http://valgrind.org/support/bug_reports.html.\n--1808-- WARNING: unhandled riscv64-linux syscall: 258\n--1808-- You may be able to write your own handler.\n--1808-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1808-- Nevertheless we consider this a bug.  Please report\n--1808-- it at http://valgrind.org/support/bug_reports.html.\n--1808-- WARNING: unhandled riscv64-linux syscall: 258\n--1808-- You may be able to write your own handler.\n--1808-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1808-- Nevertheless we consider this a bug.  Please report\n--1808-- it at http://valgrind.org/support/bug_reports.html.\n--1808-- WARNING: unhandled riscv64-linux syscall: 258\n--1808-- You may be able to write your own handler.\n--1808-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1808-- Nevertheless we consider this a bug.  Please report\n--1808-- it at http://valgrind.org/support/bug_reports.html.\n--1808-- WARNING: unhandled riscv64-linux syscall: 258\n--1808-- You may be able to write your own handler.\n--1808-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1808-- Nevertheless we consider this a bug.  Please report\n--1808-- it at http://valgrind.org/support/bug_reports.html.\n--1808-- WARNING: unhandled riscv64-linux syscall: 258\n--1808-- You may be able to write your own handler.\n--1808-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1808-- Nevertheless we consider this a bug.  Please report\n--1808-- it at http://valgrind.org/support/bug_reports.html.\n--1808-- WARNING: unhandled riscv64-linux syscall: 258\n--1808-- You may be able to write your own handler.\n--1808-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1808-- Nevertheless we consider this a bug.  Please report\n--1808-- 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:
'--1816-- WARNING: unhandled riscv64-linux syscall: 258\n--1816-- You may be able to write your own handler.\n--1816-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1816-- Nevertheless we consider this a bug.  Please report\n--1816-- it at http://valgrind.org/support/bug_reports.html.\n--1816-- WARNING: unhandled riscv64-linux syscall: 258\n--1816-- You may be able to write your own handler.\n--1816-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1816-- Nevertheless we consider this a bug.  Please report\n--1816-- it at http://valgrind.org/support/bug_reports.html.\n--1816-- WARNING: unhandled riscv64-linux syscall: 258\n--1816-- You may be able to write your own handler.\n--1816-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1816-- Nevertheless we consider this a bug.  Please report\n--1816-- it at http://valgrind.org/support/bug_reports.html.\n--1816-- WARNING: unhandled riscv64-linux syscall: 258\n--1816-- You may be able to write your own handler.\n--1816-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1816-- Nevertheless we consider this a bug.  Please report\n--1816-- it at http://valgrind.org/support/bug_reports.html.\n--1816-- WARNING: unhandled riscv64-linux syscall: 258\n--1816-- You may be able to write your own handler.\n--1816-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1816-- Nevertheless we consider this a bug.  Please report\n--1816-- it at http://valgrind.org/support/bug_reports.html.\n--1816-- WARNING: unhandled riscv64-linux syscall: 258\n--1816-- You may be able to write your own handler.\n--1816-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1816-- Nevertheless we consider this a bug.  Please report\n--1816-- it at http://valgrind.org/support/bug_reports.html.\n--1816-- WARNING: unhandled riscv64-linux syscall: 258\n--1816-- You may be able to write your own handler.\n--1816-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1816-- Nevertheless we consider this a bug.  Please report\n--1816-- it at http://valgrind.org/support/bug_reports.html.\n--1816-- WARNING: unhandled riscv64-linux syscall: 258\n--1816-- You may be able to write your own handler.\n--1816-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1816-- Nevertheless we consider this a bug.  Please report\n--1816-- it at http://valgrind.org/support/bug_reports.html.\n--1816-- WARNING: unhandled riscv64-linux syscall: 258\n--1816-- You may be able to write your own handler.\n--1816-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1816-- Nevertheless we consider this a bug.  Please report\n--1816-- it at http://valgrind.org/support/bug_reports.html.\n--1816-- WARNING: unhandled riscv64-linux syscall: 258\n--1816-- You may be able to write your own handler.\n--1816-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1816-- Nevertheless we consider this a bug.  Please report\n--1816-- it at http://valgrind.org/support/bug_reports.html.\n--1816-- WARNING: unhandled riscv64-linux syscall: 258\n--1816-- You may be able to write your own handler.\n--1816-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1816-- Nevertheless we consider this a bug.  Please report\n--1816-- it at http://valgrind.org/support/bug_reports.html.\n--1816-- WARNING: unhandled riscv64-linux syscall: 258\n--1816-- You may be able to write your own handler.\n--1816-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1816-- Nevertheless we consider this a bug.  Please report\n--1816-- it at http://valgrind.org/support/bug_reports.html.\n--1816-- WARNING: unhandled riscv64-linux syscall: 258\n--1816-- You may be able to write your own handler.\n--1816-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1816-- Nevertheless we consider this a bug.  Please report\n--1816-- it at http://valgrind.org/support/bug_reports.html.\n--1816-- WARNING: unhandled riscv64-linux syscall: 258\n--1816-- You may be able to write your own handler.\n--1816-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1816-- Nevertheless we consider this a bug.  Please report\n--1816-- it at http://valgrind.org/support/bug_reports.html.\n--1816-- WARNING: unhandled riscv64-linux syscall: 258\n--1816-- You may be able to write your own handler.\n--1816-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1816-- Nevertheless we consider this a bug.  Please report\n--1816-- it at http://valgrind.org/support/bug_reports.html.\n--1816-- WARNING: unhandled riscv64-linux syscall: 258\n--1816-- You may be able to write your own handler.\n--1816-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1816-- Nevertheless we consider this a bug.  Please report\n--1816-- it at http://valgrind.org/support/bug_reports.html.\n--1816-- WARNING: unhandled riscv64-linux syscall: 258\n--1816-- You may be able to write your own handler.\n--1816-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1816-- Nevertheless we consider this a bug.  Please report\n--1816-- it at http://valgrind.org/support/bug_reports.html.\n--1816-- WARNING: unhandled riscv64-linux syscall: 258\n--1816-- You may be able to write your own handler.\n--1816-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1816-- Nevertheless we consider this a bug.  Please report\n--1816-- 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:
'--1824-- WARNING: unhandled riscv64-linux syscall: 258\n--1824-- You may be able to write your own handler.\n--1824-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1824-- Nevertheless we consider this a bug.  Please report\n--1824-- it at http://valgrind.org/support/bug_reports.html.\n--1824-- WARNING: unhandled riscv64-linux syscall: 258\n--1824-- You may be able to write your own handler.\n--1824-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1824-- Nevertheless we consider this a bug.  Please report\n--1824-- it at http://valgrind.org/support/bug_reports.html.\n--1824-- WARNING: unhandled riscv64-linux syscall: 258\n--1824-- You may be able to write your own handler.\n--1824-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1824-- Nevertheless we consider this a bug.  Please report\n--1824-- it at http://valgrind.org/support/bug_reports.html.\n--1824-- WARNING: unhandled riscv64-linux syscall: 258\n--1824-- You may be able to write your own handler.\n--1824-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1824-- Nevertheless we consider this a bug.  Please report\n--1824-- it at http://valgrind.org/support/bug_reports.html.\n--1824-- WARNING: unhandled riscv64-linux syscall: 258\n--1824-- You may be able to write your own handler.\n--1824-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1824-- Nevertheless we consider this a bug.  Please report\n--1824-- it at http://valgrind.org/support/bug_reports.html.\n--1824-- WARNING: unhandled riscv64-linux syscall: 258\n--1824-- You may be able to write your own handler.\n--1824-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1824-- Nevertheless we consider this a bug.  Please report\n--1824-- it at http://valgrind.org/support/bug_reports.html.\n--1824-- WARNING: unhandled riscv64-linux syscall: 258\n--1824-- You may be able to write your own handler.\n--1824-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1824-- Nevertheless we consider this a bug.  Please report\n--1824-- it at http://valgrind.org/support/bug_reports.html.\n--1824-- WARNING: unhandled riscv64-linux syscall: 258\n--1824-- You may be able to write your own handler.\n--1824-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1824-- Nevertheless we consider this a bug.  Please report\n--1824-- it at http://valgrind.org/support/bug_reports.html.\n--1824-- WARNING: unhandled riscv64-linux syscall: 258\n--1824-- You may be able to write your own handler.\n--1824-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1824-- Nevertheless we consider this a bug.  Please report\n--1824-- it at http://valgrind.org/support/bug_reports.html.\n--1824-- WARNING: unhandled riscv64-linux syscall: 258\n--1824-- You may be able to write your own handler.\n--1824-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1824-- Nevertheless we consider this a bug.  Please report\n--1824-- it at http://valgrind.org/support/bug_reports.html.\n--1824-- WARNING: unhandled riscv64-linux syscall: 258\n--1824-- You may be able to write your own handler.\n--1824-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1824-- Nevertheless we consider this a bug.  Please report\n--1824-- it at http://valgrind.org/support/bug_reports.html.\n--1824-- WARNING: unhandled riscv64-linux syscall: 258\n--1824-- You may be able to write your own handler.\n--1824-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1824-- Nevertheless we consider this a bug.  Please report\n--1824-- it at http://valgrind.org/support/bug_reports.html.\n--1824-- WARNING: unhandled riscv64-linux syscall: 258\n--1824-- You may be able to write your own handler.\n--1824-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1824-- Nevertheless we consider this a bug.  Please report\n--1824-- it at http://valgrind.org/support/bug_reports.html.\n--1824-- WARNING: unhandled riscv64-linux syscall: 258\n--1824-- You may be able to write your own handler.\n--1824-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1824-- Nevertheless we consider this a bug.  Please report\n--1824-- it at http://valgrind.org/support/bug_reports.html.\n--1824-- WARNING: unhandled riscv64-linux syscall: 258\n--1824-- You may be able to write your own handler.\n--1824-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1824-- Nevertheless we consider this a bug.  Please report\n--1824-- it at http://valgrind.org/support/bug_reports.html.\n--1824-- WARNING: unhandled riscv64-linux syscall: 258\n--1824-- You may be able to write your own handler.\n--1824-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1824-- Nevertheless we consider this a bug.  Please report\n--1824-- it at http://valgrind.org/support/bug_reports.html.\n--1824-- WARNING: unhandled riscv64-linux syscall: 258\n--1824-- You may be able to write your own handler.\n--1824-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1824-- Nevertheless we consider this a bug.  Please report\n--1824-- it at http://valgrind.org/support/bug_reports.html.\n--1824-- WARNING: unhandled riscv64-linux syscall: 258\n--1824-- You may be able to write your own handler.\n--1824-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1824-- Nevertheless we consider this a bug.  Please report\n--1824-- 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:
'--1832-- WARNING: unhandled riscv64-linux syscall: 258\n--1832-- You may be able to write your own handler.\n--1832-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1832-- Nevertheless we consider this a bug.  Please report\n--1832-- it at http://valgrind.org/support/bug_reports.html.\n--1832-- WARNING: unhandled riscv64-linux syscall: 258\n--1832-- You may be able to write your own handler.\n--1832-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1832-- Nevertheless we consider this a bug.  Please report\n--1832-- it at http://valgrind.org/support/bug_reports.html.\n--1832-- WARNING: unhandled riscv64-linux syscall: 258\n--1832-- You may be able to write your own handler.\n--1832-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1832-- Nevertheless we consider this a bug.  Please report\n--1832-- it at http://valgrind.org/support/bug_reports.html.\n--1832-- WARNING: unhandled riscv64-linux syscall: 258\n--1832-- You may be able to write your own handler.\n--1832-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1832-- Nevertheless we consider this a bug.  Please report\n--1832-- it at http://valgrind.org/support/bug_reports.html.\n--1832-- WARNING: unhandled riscv64-linux syscall: 258\n--1832-- You may be able to write your own handler.\n--1832-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1832-- Nevertheless we consider this a bug.  Please report\n--1832-- it at http://valgrind.org/support/bug_reports.html.\n--1832-- WARNING: unhandled riscv64-linux syscall: 258\n--1832-- You may be able to write your own handler.\n--1832-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1832-- Nevertheless we consider this a bug.  Please report\n--1832-- it at http://valgrind.org/support/bug_reports.html.\n--1832-- WARNING: unhandled riscv64-linux syscall: 258\n--1832-- You may be able to write your own handler.\n--1832-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1832-- Nevertheless we consider this a bug.  Please report\n--1832-- it at http://valgrind.org/support/bug_reports.html.\n--1832-- WARNING: unhandled riscv64-linux syscall: 258\n--1832-- You may be able to write your own handler.\n--1832-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1832-- Nevertheless we consider this a bug.  Please report\n--1832-- it at http://valgrind.org/support/bug_reports.html.\n--1832-- WARNING: unhandled riscv64-linux syscall: 258\n--1832-- You may be able to write your own handler.\n--1832-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1832-- Nevertheless we consider this a bug.  Please report\n--1832-- it at http://valgrind.org/support/bug_reports.html.\n--1832-- WARNING: unhandled riscv64-linux syscall: 258\n--1832-- You may be able to write your own handler.\n--1832-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1832-- Nevertheless we consider this a bug.  Please report\n--1832-- it at http://valgrind.org/support/bug_reports.html.\n--1832-- WARNING: unhandled riscv64-linux syscall: 258\n--1832-- You may be able to write your own handler.\n--1832-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1832-- Nevertheless we consider this a bug.  Please report\n--1832-- it at http://valgrind.org/support/bug_reports.html.\n--1832-- WARNING: unhandled riscv64-linux syscall: 258\n--1832-- You may be able to write your own handler.\n--1832-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1832-- Nevertheless we consider this a bug.  Please report\n--1832-- it at http://valgrind.org/support/bug_reports.html.\n--1832-- WARNING: unhandled riscv64-linux syscall: 258\n--1832-- You may be able to write your own handler.\n--1832-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1832-- Nevertheless we consider this a bug.  Please report\n--1832-- it at http://valgrind.org/support/bug_reports.html.\n--1832-- WARNING: unhandled riscv64-linux syscall: 258\n--1832-- You may be able to write your own handler.\n--1832-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1832-- Nevertheless we consider this a bug.  Please report\n--1832-- it at http://valgrind.org/support/bug_reports.html.\n--1832-- WARNING: unhandled riscv64-linux syscall: 258\n--1832-- You may be able to write your own handler.\n--1832-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1832-- Nevertheless we consider this a bug.  Please report\n--1832-- it at http://valgrind.org/support/bug_reports.html.\n--1832-- WARNING: unhandled riscv64-linux syscall: 258\n--1832-- You may be able to write your own handler.\n--1832-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1832-- Nevertheless we consider this a bug.  Please report\n--1832-- it at http://valgrind.org/support/bug_reports.html.\n--1832-- WARNING: unhandled riscv64-linux syscall: 258\n--1832-- You may be able to write your own handler.\n--1832-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1832-- Nevertheless we consider this a bug.  Please report\n--1832-- it at http://valgrind.org/support/bug_reports.html.\n--1832-- WARNING: unhandled riscv64-linux syscall: 258\n--1832-- You may be able to write your own handler.\n--1832-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1832-- Nevertheless we consider this a bug.  Please report\n--1832-- 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:
'--1840-- WARNING: unhandled riscv64-linux syscall: 258\n--1840-- You may be able to write your own handler.\n--1840-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1840-- Nevertheless we consider this a bug.  Please report\n--1840-- it at http://valgrind.org/support/bug_reports.html.\n--1840-- WARNING: unhandled riscv64-linux syscall: 258\n--1840-- You may be able to write your own handler.\n--1840-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1840-- Nevertheless we consider this a bug.  Please report\n--1840-- it at http://valgrind.org/support/bug_reports.html.\n--1840-- WARNING: unhandled riscv64-linux syscall: 258\n--1840-- You may be able to write your own handler.\n--1840-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1840-- Nevertheless we consider this a bug.  Please report\n--1840-- it at http://valgrind.org/support/bug_reports.html.\n--1840-- WARNING: unhandled riscv64-linux syscall: 258\n--1840-- You may be able to write your own handler.\n--1840-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1840-- Nevertheless we consider this a bug.  Please report\n--1840-- it at http://valgrind.org/support/bug_reports.html.\n--1840-- WARNING: unhandled riscv64-linux syscall: 258\n--1840-- You may be able to write your own handler.\n--1840-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1840-- Nevertheless we consider this a bug.  Please report\n--1840-- it at http://valgrind.org/support/bug_reports.html.\n--1840-- WARNING: unhandled riscv64-linux syscall: 258\n--1840-- You may be able to write your own handler.\n--1840-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1840-- Nevertheless we consider this a bug.  Please report\n--1840-- it at http://valgrind.org/support/bug_reports.html.\n--1840-- WARNING: unhandled riscv64-linux syscall: 258\n--1840-- You may be able to write your own handler.\n--1840-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1840-- Nevertheless we consider this a bug.  Please report\n--1840-- it at http://valgrind.org/support/bug_reports.html.\n--1840-- WARNING: unhandled riscv64-linux syscall: 258\n--1840-- You may be able to write your own handler.\n--1840-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1840-- Nevertheless we consider this a bug.  Please report\n--1840-- it at http://valgrind.org/support/bug_reports.html.\n--1840-- WARNING: unhandled riscv64-linux syscall: 258\n--1840-- You may be able to write your own handler.\n--1840-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1840-- Nevertheless we consider this a bug.  Please report\n--1840-- it at http://valgrind.org/support/bug_reports.html.\n--1840-- WARNING: unhandled riscv64-linux syscall: 258\n--1840-- You may be able to write your own handler.\n--1840-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1840-- Nevertheless we consider this a bug.  Please report\n--1840-- it at http://valgrind.org/support/bug_reports.html.\n--1840-- WARNING: unhandled riscv64-linux syscall: 258\n--1840-- You may be able to write your own handler.\n--1840-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1840-- Nevertheless we consider this a bug.  Please report\n--1840-- it at http://valgrind.org/support/bug_reports.html.\n--1840-- WARNING: unhandled riscv64-linux syscall: 258\n--1840-- You may be able to write your own handler.\n--1840-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1840-- Nevertheless we consider this a bug.  Please report\n--1840-- it at http://valgrind.org/support/bug_reports.html.\n--1840-- WARNING: unhandled riscv64-linux syscall: 258\n--1840-- You may be able to write your own handler.\n--1840-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1840-- Nevertheless we consider this a bug.  Please report\n--1840-- it at http://valgrind.org/support/bug_reports.html.\n--1840-- WARNING: unhandled riscv64-linux syscall: 258\n--1840-- You may be able to write your own handler.\n--1840-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1840-- Nevertheless we consider this a bug.  Please report\n--1840-- it at http://valgrind.org/support/bug_reports.html.\n--1840-- WARNING: unhandled riscv64-linux syscall: 258\n--1840-- You may be able to write your own handler.\n--1840-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1840-- Nevertheless we consider this a bug.  Please report\n--1840-- it at http://valgrind.org/support/bug_reports.html.\n--1840-- WARNING: unhandled riscv64-linux syscall: 258\n--1840-- You may be able to write your own handler.\n--1840-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1840-- Nevertheless we consider this a bug.  Please report\n--1840-- it at http://valgrind.org/support/bug_reports.html.\n--1840-- WARNING: unhandled riscv64-linux syscall: 258\n--1840-- You may be able to write your own handler.\n--1840-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1840-- Nevertheless we consider this a bug.  Please report\n--1840-- it at http://valgrind.org/support/bug_reports.html.\n--1840-- WARNING: unhandled riscv64-linux syscall: 258\n--1840-- You may be able to write your own handler.\n--1840-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1840-- Nevertheless we consider this a bug.  Please report\n--1840-- 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:
'--1848-- WARNING: unhandled riscv64-linux syscall: 258\n--1848-- You may be able to write your own handler.\n--1848-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1848-- Nevertheless we consider this a bug.  Please report\n--1848-- it at http://valgrind.org/support/bug_reports.html.\n--1848-- WARNING: unhandled riscv64-linux syscall: 258\n--1848-- You may be able to write your own handler.\n--1848-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1848-- Nevertheless we consider this a bug.  Please report\n--1848-- it at http://valgrind.org/support/bug_reports.html.\n--1848-- WARNING: unhandled riscv64-linux syscall: 258\n--1848-- You may be able to write your own handler.\n--1848-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1848-- Nevertheless we consider this a bug.  Please report\n--1848-- it at http://valgrind.org/support/bug_reports.html.\n--1848-- WARNING: unhandled riscv64-linux syscall: 258\n--1848-- You may be able to write your own handler.\n--1848-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1848-- Nevertheless we consider this a bug.  Please report\n--1848-- it at http://valgrind.org/support/bug_reports.html.\n--1848-- WARNING: unhandled riscv64-linux syscall: 258\n--1848-- You may be able to write your own handler.\n--1848-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1848-- Nevertheless we consider this a bug.  Please report\n--1848-- it at http://valgrind.org/support/bug_reports.html.\n--1848-- WARNING: unhandled riscv64-linux syscall: 258\n--1848-- You may be able to write your own handler.\n--1848-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1848-- Nevertheless we consider this a bug.  Please report\n--1848-- it at http://valgrind.org/support/bug_reports.html.\n--1848-- WARNING: unhandled riscv64-linux syscall: 258\n--1848-- You may be able to write your own handler.\n--1848-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1848-- Nevertheless we consider this a bug.  Please report\n--1848-- it at http://valgrind.org/support/bug_reports.html.\n--1848-- WARNING: unhandled riscv64-linux syscall: 258\n--1848-- You may be able to write your own handler.\n--1848-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1848-- Nevertheless we consider this a bug.  Please report\n--1848-- it at http://valgrind.org/support/bug_reports.html.\n--1848-- WARNING: unhandled riscv64-linux syscall: 258\n--1848-- You may be able to write your own handler.\n--1848-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1848-- Nevertheless we consider this a bug.  Please report\n--1848-- it at http://valgrind.org/support/bug_reports.html.\n--1848-- WARNING: unhandled riscv64-linux syscall: 258\n--1848-- You may be able to write your own handler.\n--1848-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1848-- Nevertheless we consider this a bug.  Please report\n--1848-- it at http://valgrind.org/support/bug_reports.html.\n--1848-- WARNING: unhandled riscv64-linux syscall: 258\n--1848-- You may be able to write your own handler.\n--1848-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1848-- Nevertheless we consider this a bug.  Please report\n--1848-- it at http://valgrind.org/support/bug_reports.html.\n--1848-- WARNING: unhandled riscv64-linux syscall: 258\n--1848-- You may be able to write your own handler.\n--1848-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1848-- Nevertheless we consider this a bug.  Please report\n--1848-- it at http://valgrind.org/support/bug_reports.html.\n--1848-- WARNING: unhandled riscv64-linux syscall: 258\n--1848-- You may be able to write your own handler.\n--1848-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1848-- Nevertheless we consider this a bug.  Please report\n--1848-- it at http://valgrind.org/support/bug_reports.html.\n--1848-- WARNING: unhandled riscv64-linux syscall: 258\n--1848-- You may be able to write your own handler.\n--1848-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1848-- Nevertheless we consider this a bug.  Please report\n--1848-- it at http://valgrind.org/support/bug_reports.html.\n--1848-- WARNING: unhandled riscv64-linux syscall: 258\n--1848-- You may be able to write your own handler.\n--1848-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1848-- Nevertheless we consider this a bug.  Please report\n--1848-- it at http://valgrind.org/support/bug_reports.html.\n--1848-- WARNING: unhandled riscv64-linux syscall: 258\n--1848-- You may be able to write your own handler.\n--1848-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1848-- Nevertheless we consider this a bug.  Please report\n--1848-- it at http://valgrind.org/support/bug_reports.html.\n--1848-- WARNING: unhandled riscv64-linux syscall: 258\n--1848-- You may be able to write your own handler.\n--1848-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1848-- Nevertheless we consider this a bug.  Please report\n--1848-- it at http://valgrind.org/support/bug_reports.html.\n--1848-- WARNING: unhandled riscv64-linux syscall: 258\n--1848-- You may be able to write your own handler.\n--1848-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1848-- Nevertheless we consider this a bug.  Please report\n--1848-- 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:
'--1856-- WARNING: unhandled riscv64-linux syscall: 258\n--1856-- You may be able to write your own handler.\n--1856-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1856-- Nevertheless we consider this a bug.  Please report\n--1856-- it at http://valgrind.org/support/bug_reports.html.\n--1856-- WARNING: unhandled riscv64-linux syscall: 258\n--1856-- You may be able to write your own handler.\n--1856-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1856-- Nevertheless we consider this a bug.  Please report\n--1856-- it at http://valgrind.org/support/bug_reports.html.\n--1856-- WARNING: unhandled riscv64-linux syscall: 258\n--1856-- You may be able to write your own handler.\n--1856-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1856-- Nevertheless we consider this a bug.  Please report\n--1856-- it at http://valgrind.org/support/bug_reports.html.\n--1856-- WARNING: unhandled riscv64-linux syscall: 258\n--1856-- You may be able to write your own handler.\n--1856-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1856-- Nevertheless we consider this a bug.  Please report\n--1856-- it at http://valgrind.org/support/bug_reports.html.\n--1856-- WARNING: unhandled riscv64-linux syscall: 258\n--1856-- You may be able to write your own handler.\n--1856-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1856-- Nevertheless we consider this a bug.  Please report\n--1856-- it at http://valgrind.org/support/bug_reports.html.\n--1856-- WARNING: unhandled riscv64-linux syscall: 258\n--1856-- You may be able to write your own handler.\n--1856-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1856-- Nevertheless we consider this a bug.  Please report\n--1856-- it at http://valgrind.org/support/bug_reports.html.\n--1856-- WARNING: unhandled riscv64-linux syscall: 258\n--1856-- You may be able to write your own handler.\n--1856-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1856-- Nevertheless we consider this a bug.  Please report\n--1856-- it at http://valgrind.org/support/bug_reports.html.\n--1856-- WARNING: unhandled riscv64-linux syscall: 258\n--1856-- You may be able to write your own handler.\n--1856-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1856-- Nevertheless we consider this a bug.  Please report\n--1856-- it at http://valgrind.org/support/bug_reports.html.\n--1856-- WARNING: unhandled riscv64-linux syscall: 258\n--1856-- You may be able to write your own handler.\n--1856-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1856-- Nevertheless we consider this a bug.  Please report\n--1856-- it at http://valgrind.org/support/bug_reports.html.\n--1856-- WARNING: unhandled riscv64-linux syscall: 258\n--1856-- You may be able to write your own handler.\n--1856-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1856-- Nevertheless we consider this a bug.  Please report\n--1856-- it at http://valgrind.org/support/bug_reports.html.\n--1856-- WARNING: unhandled riscv64-linux syscall: 258\n--1856-- You may be able to write your own handler.\n--1856-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1856-- Nevertheless we consider this a bug.  Please report\n--1856-- it at http://valgrind.org/support/bug_reports.html.\n--1856-- WARNING: unhandled riscv64-linux syscall: 258\n--1856-- You may be able to write your own handler.\n--1856-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1856-- Nevertheless we consider this a bug.  Please report\n--1856-- it at http://valgrind.org/support/bug_reports.html.\n--1856-- WARNING: unhandled riscv64-linux syscall: 258\n--1856-- You may be able to write your own handler.\n--1856-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1856-- Nevertheless we consider this a bug.  Please report\n--1856-- it at http://valgrind.org/support/bug_reports.html.\n--1856-- WARNING: unhandled riscv64-linux syscall: 258\n--1856-- You may be able to write your own handler.\n--1856-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1856-- Nevertheless we consider this a bug.  Please report\n--1856-- it at http://valgrind.org/support/bug_reports.html.\n--1856-- WARNING: unhandled riscv64-linux syscall: 258\n--1856-- You may be able to write your own handler.\n--1856-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1856-- Nevertheless we consider this a bug.  Please report\n--1856-- it at http://valgrind.org/support/bug_reports.html.\n--1856-- WARNING: unhandled riscv64-linux syscall: 258\n--1856-- You may be able to write your own handler.\n--1856-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1856-- Nevertheless we consider this a bug.  Please report\n--1856-- it at http://valgrind.org/support/bug_reports.html.\n--1856-- WARNING: unhandled riscv64-linux syscall: 258\n--1856-- You may be able to write your own handler.\n--1856-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1856-- Nevertheless we consider this a bug.  Please report\n--1856-- it at http://valgrind.org/support/bug_reports.html.\n--1856-- WARNING: unhandled riscv64-linux syscall: 258\n--1856-- You may be able to write your own handler.\n--1856-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1856-- Nevertheless we consider this a bug.  Please report\n--1856-- 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:
'--1864-- WARNING: unhandled riscv64-linux syscall: 258\n--1864-- You may be able to write your own handler.\n--1864-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1864-- Nevertheless we consider this a bug.  Please report\n--1864-- it at http://valgrind.org/support/bug_reports.html.\n--1864-- WARNING: unhandled riscv64-linux syscall: 258\n--1864-- You may be able to write your own handler.\n--1864-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1864-- Nevertheless we consider this a bug.  Please report\n--1864-- it at http://valgrind.org/support/bug_reports.html.\n--1864-- WARNING: unhandled riscv64-linux syscall: 258\n--1864-- You may be able to write your own handler.\n--1864-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1864-- Nevertheless we consider this a bug.  Please report\n--1864-- it at http://valgrind.org/support/bug_reports.html.\n--1864-- WARNING: unhandled riscv64-linux syscall: 258\n--1864-- You may be able to write your own handler.\n--1864-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1864-- Nevertheless we consider this a bug.  Please report\n--1864-- it at http://valgrind.org/support/bug_reports.html.\n--1864-- WARNING: unhandled riscv64-linux syscall: 258\n--1864-- You may be able to write your own handler.\n--1864-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1864-- Nevertheless we consider this a bug.  Please report\n--1864-- it at http://valgrind.org/support/bug_reports.html.\n--1864-- WARNING: unhandled riscv64-linux syscall: 258\n--1864-- You may be able to write your own handler.\n--1864-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1864-- Nevertheless we consider this a bug.  Please report\n--1864-- it at http://valgrind.org/support/bug_reports.html.\n--1864-- WARNING: unhandled riscv64-linux syscall: 258\n--1864-- You may be able to write your own handler.\n--1864-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1864-- Nevertheless we consider this a bug.  Please report\n--1864-- it at http://valgrind.org/support/bug_reports.html.\n--1864-- WARNING: unhandled riscv64-linux syscall: 258\n--1864-- You may be able to write your own handler.\n--1864-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1864-- Nevertheless we consider this a bug.  Please report\n--1864-- it at http://valgrind.org/support/bug_reports.html.\n--1864-- WARNING: unhandled riscv64-linux syscall: 258\n--1864-- You may be able to write your own handler.\n--1864-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1864-- Nevertheless we consider this a bug.  Please report\n--1864-- it at http://valgrind.org/support/bug_reports.html.\n--1864-- WARNING: unhandled riscv64-linux syscall: 258\n--1864-- You may be able to write your own handler.\n--1864-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1864-- Nevertheless we consider this a bug.  Please report\n--1864-- it at http://valgrind.org/support/bug_reports.html.\n--1864-- WARNING: unhandled riscv64-linux syscall: 258\n--1864-- You may be able to write your own handler.\n--1864-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1864-- Nevertheless we consider this a bug.  Please report\n--1864-- it at http://valgrind.org/support/bug_reports.html.\n--1864-- WARNING: unhandled riscv64-linux syscall: 258\n--1864-- You may be able to write your own handler.\n--1864-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1864-- Nevertheless we consider this a bug.  Please report\n--1864-- it at http://valgrind.org/support/bug_reports.html.\n--1864-- WARNING: unhandled riscv64-linux syscall: 258\n--1864-- You may be able to write your own handler.\n--1864-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1864-- Nevertheless we consider this a bug.  Please report\n--1864-- it at http://valgrind.org/support/bug_reports.html.\n--1864-- WARNING: unhandled riscv64-linux syscall: 258\n--1864-- You may be able to write your own handler.\n--1864-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1864-- Nevertheless we consider this a bug.  Please report\n--1864-- it at http://valgrind.org/support/bug_reports.html.\n--1864-- WARNING: unhandled riscv64-linux syscall: 258\n--1864-- You may be able to write your own handler.\n--1864-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1864-- Nevertheless we consider this a bug.  Please report\n--1864-- it at http://valgrind.org/support/bug_reports.html.\n--1864-- WARNING: unhandled riscv64-linux syscall: 258\n--1864-- You may be able to write your own handler.\n--1864-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1864-- Nevertheless we consider this a bug.  Please report\n--1864-- it at http://valgrind.org/support/bug_reports.html.\n--1864-- WARNING: unhandled riscv64-linux syscall: 258\n--1864-- You may be able to write your own handler.\n--1864-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1864-- Nevertheless we consider this a bug.  Please report\n--1864-- it at http://valgrind.org/support/bug_reports.html.\n--1864-- WARNING: unhandled riscv64-linux syscall: 258\n--1864-- You may be able to write your own handler.\n--1864-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1864-- Nevertheless we consider this a bug.  Please report\n--1864-- 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:
'--1872-- WARNING: unhandled riscv64-linux syscall: 258\n--1872-- You may be able to write your own handler.\n--1872-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1872-- Nevertheless we consider this a bug.  Please report\n--1872-- it at http://valgrind.org/support/bug_reports.html.\n--1872-- WARNING: unhandled riscv64-linux syscall: 258\n--1872-- You may be able to write your own handler.\n--1872-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1872-- Nevertheless we consider this a bug.  Please report\n--1872-- it at http://valgrind.org/support/bug_reports.html.\n--1872-- WARNING: unhandled riscv64-linux syscall: 258\n--1872-- You may be able to write your own handler.\n--1872-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1872-- Nevertheless we consider this a bug.  Please report\n--1872-- it at http://valgrind.org/support/bug_reports.html.\n--1872-- WARNING: unhandled riscv64-linux syscall: 258\n--1872-- You may be able to write your own handler.\n--1872-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1872-- Nevertheless we consider this a bug.  Please report\n--1872-- it at http://valgrind.org/support/bug_reports.html.\n--1872-- WARNING: unhandled riscv64-linux syscall: 258\n--1872-- You may be able to write your own handler.\n--1872-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1872-- Nevertheless we consider this a bug.  Please report\n--1872-- it at http://valgrind.org/support/bug_reports.html.\n--1872-- WARNING: unhandled riscv64-linux syscall: 258\n--1872-- You may be able to write your own handler.\n--1872-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1872-- Nevertheless we consider this a bug.  Please report\n--1872-- it at http://valgrind.org/support/bug_reports.html.\n--1872-- WARNING: unhandled riscv64-linux syscall: 258\n--1872-- You may be able to write your own handler.\n--1872-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1872-- Nevertheless we consider this a bug.  Please report\n--1872-- it at http://valgrind.org/support/bug_reports.html.\n--1872-- WARNING: unhandled riscv64-linux syscall: 258\n--1872-- You may be able to write your own handler.\n--1872-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1872-- Nevertheless we consider this a bug.  Please report\n--1872-- it at http://valgrind.org/support/bug_reports.html.\n--1872-- WARNING: unhandled riscv64-linux syscall: 258\n--1872-- You may be able to write your own handler.\n--1872-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1872-- Nevertheless we consider this a bug.  Please report\n--1872-- it at http://valgrind.org/support/bug_reports.html.\n--1872-- WARNING: unhandled riscv64-linux syscall: 258\n--1872-- You may be able to write your own handler.\n--1872-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1872-- Nevertheless we consider this a bug.  Please report\n--1872-- it at http://valgrind.org/support/bug_reports.html.\n--1872-- WARNING: unhandled riscv64-linux syscall: 258\n--1872-- You may be able to write your own handler.\n--1872-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1872-- Nevertheless we consider this a bug.  Please report\n--1872-- it at http://valgrind.org/support/bug_reports.html.\n--1872-- WARNING: unhandled riscv64-linux syscall: 258\n--1872-- You may be able to write your own handler.\n--1872-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1872-- Nevertheless we consider this a bug.  Please report\n--1872-- it at http://valgrind.org/support/bug_reports.html.\n--1872-- WARNING: unhandled riscv64-linux syscall: 258\n--1872-- You may be able to write your own handler.\n--1872-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1872-- Nevertheless we consider this a bug.  Please report\n--1872-- it at http://valgrind.org/support/bug_reports.html.\n--1872-- WARNING: unhandled riscv64-linux syscall: 258\n--1872-- You may be able to write your own handler.\n--1872-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1872-- Nevertheless we consider this a bug.  Please report\n--1872-- it at http://valgrind.org/support/bug_reports.html.\n--1872-- WARNING: unhandled riscv64-linux syscall: 258\n--1872-- You may be able to write your own handler.\n--1872-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1872-- Nevertheless we consider this a bug.  Please report\n--1872-- it at http://valgrind.org/support/bug_reports.html.\n--1872-- WARNING: unhandled riscv64-linux syscall: 258\n--1872-- You may be able to write your own handler.\n--1872-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1872-- Nevertheless we consider this a bug.  Please report\n--1872-- it at http://valgrind.org/support/bug_reports.html.\n--1872-- WARNING: unhandled riscv64-linux syscall: 258\n--1872-- You may be able to write your own handler.\n--1872-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1872-- Nevertheless we consider this a bug.  Please report\n--1872-- it at http://valgrind.org/support/bug_reports.html.\n--1872-- WARNING: unhandled riscv64-linux syscall: 258\n--1872-- You may be able to write your own handler.\n--1872-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1872-- Nevertheless we consider this a bug.  Please report\n--1872-- 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:
'--1880-- WARNING: unhandled riscv64-linux syscall: 258\n--1880-- You may be able to write your own handler.\n--1880-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1880-- Nevertheless we consider this a bug.  Please report\n--1880-- it at http://valgrind.org/support/bug_reports.html.\n--1880-- WARNING: unhandled riscv64-linux syscall: 258\n--1880-- You may be able to write your own handler.\n--1880-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1880-- Nevertheless we consider this a bug.  Please report\n--1880-- it at http://valgrind.org/support/bug_reports.html.\n--1880-- WARNING: unhandled riscv64-linux syscall: 258\n--1880-- You may be able to write your own handler.\n--1880-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1880-- Nevertheless we consider this a bug.  Please report\n--1880-- it at http://valgrind.org/support/bug_reports.html.\n--1880-- WARNING: unhandled riscv64-linux syscall: 258\n--1880-- You may be able to write your own handler.\n--1880-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1880-- Nevertheless we consider this a bug.  Please report\n--1880-- it at http://valgrind.org/support/bug_reports.html.\n--1880-- WARNING: unhandled riscv64-linux syscall: 258\n--1880-- You may be able to write your own handler.\n--1880-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1880-- Nevertheless we consider this a bug.  Please report\n--1880-- it at http://valgrind.org/support/bug_reports.html.\n--1880-- WARNING: unhandled riscv64-linux syscall: 258\n--1880-- You may be able to write your own handler.\n--1880-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1880-- Nevertheless we consider this a bug.  Please report\n--1880-- it at http://valgrind.org/support/bug_reports.html.\n--1880-- WARNING: unhandled riscv64-linux syscall: 258\n--1880-- You may be able to write your own handler.\n--1880-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1880-- Nevertheless we consider this a bug.  Please report\n--1880-- it at http://valgrind.org/support/bug_reports.html.\n--1880-- WARNING: unhandled riscv64-linux syscall: 258\n--1880-- You may be able to write your own handler.\n--1880-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1880-- Nevertheless we consider this a bug.  Please report\n--1880-- it at http://valgrind.org/support/bug_reports.html.\n--1880-- WARNING: unhandled riscv64-linux syscall: 258\n--1880-- You may be able to write your own handler.\n--1880-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1880-- Nevertheless we consider this a bug.  Please report\n--1880-- it at http://valgrind.org/support/bug_reports.html.\n--1880-- WARNING: unhandled riscv64-linux syscall: 258\n--1880-- You may be able to write your own handler.\n--1880-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1880-- Nevertheless we consider this a bug.  Please report\n--1880-- it at http://valgrind.org/support/bug_reports.html.\n--1880-- WARNING: unhandled riscv64-linux syscall: 258\n--1880-- You may be able to write your own handler.\n--1880-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1880-- Nevertheless we consider this a bug.  Please report\n--1880-- it at http://valgrind.org/support/bug_reports.html.\n--1880-- WARNING: unhandled riscv64-linux syscall: 258\n--1880-- You may be able to write your own handler.\n--1880-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1880-- Nevertheless we consider this a bug.  Please report\n--1880-- it at http://valgrind.org/support/bug_reports.html.\n--1880-- WARNING: unhandled riscv64-linux syscall: 258\n--1880-- You may be able to write your own handler.\n--1880-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1880-- Nevertheless we consider this a bug.  Please report\n--1880-- it at http://valgrind.org/support/bug_reports.html.\n--1880-- WARNING: unhandled riscv64-linux syscall: 258\n--1880-- You may be able to write your own handler.\n--1880-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1880-- Nevertheless we consider this a bug.  Please report\n--1880-- it at http://valgrind.org/support/bug_reports.html.\n--1880-- WARNING: unhandled riscv64-linux syscall: 258\n--1880-- You may be able to write your own handler.\n--1880-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1880-- Nevertheless we consider this a bug.  Please report\n--1880-- it at http://valgrind.org/support/bug_reports.html.\n--1880-- WARNING: unhandled riscv64-linux syscall: 258\n--1880-- You may be able to write your own handler.\n--1880-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1880-- Nevertheless we consider this a bug.  Please report\n--1880-- it at http://valgrind.org/support/bug_reports.html.\n--1880-- WARNING: unhandled riscv64-linux syscall: 258\n--1880-- You may be able to write your own handler.\n--1880-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1880-- Nevertheless we consider this a bug.  Please report\n--1880-- it at http://valgrind.org/support/bug_reports.html.\n--1880-- WARNING: unhandled riscv64-linux syscall: 258\n--1880-- You may be able to write your own handler.\n--1880-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1880-- Nevertheless we consider this a bug.  Please report\n--1880-- 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:
'--1888-- WARNING: unhandled riscv64-linux syscall: 258\n--1888-- You may be able to write your own handler.\n--1888-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1888-- Nevertheless we consider this a bug.  Please report\n--1888-- it at http://valgrind.org/support/bug_reports.html.\n--1888-- WARNING: unhandled riscv64-linux syscall: 258\n--1888-- You may be able to write your own handler.\n--1888-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1888-- Nevertheless we consider this a bug.  Please report\n--1888-- it at http://valgrind.org/support/bug_reports.html.\n--1888-- WARNING: unhandled riscv64-linux syscall: 258\n--1888-- You may be able to write your own handler.\n--1888-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1888-- Nevertheless we consider this a bug.  Please report\n--1888-- it at http://valgrind.org/support/bug_reports.html.\n--1888-- WARNING: unhandled riscv64-linux syscall: 258\n--1888-- You may be able to write your own handler.\n--1888-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1888-- Nevertheless we consider this a bug.  Please report\n--1888-- it at http://valgrind.org/support/bug_reports.html.\n--1888-- WARNING: unhandled riscv64-linux syscall: 258\n--1888-- You may be able to write your own handler.\n--1888-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1888-- Nevertheless we consider this a bug.  Please report\n--1888-- it at http://valgrind.org/support/bug_reports.html.\n--1888-- WARNING: unhandled riscv64-linux syscall: 258\n--1888-- You may be able to write your own handler.\n--1888-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1888-- Nevertheless we consider this a bug.  Please report\n--1888-- it at http://valgrind.org/support/bug_reports.html.\n--1888-- WARNING: unhandled riscv64-linux syscall: 258\n--1888-- You may be able to write your own handler.\n--1888-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1888-- Nevertheless we consider this a bug.  Please report\n--1888-- it at http://valgrind.org/support/bug_reports.html.\n--1888-- WARNING: unhandled riscv64-linux syscall: 258\n--1888-- You may be able to write your own handler.\n--1888-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1888-- Nevertheless we consider this a bug.  Please report\n--1888-- it at http://valgrind.org/support/bug_reports.html.\n--1888-- WARNING: unhandled riscv64-linux syscall: 258\n--1888-- You may be able to write your own handler.\n--1888-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1888-- Nevertheless we consider this a bug.  Please report\n--1888-- it at http://valgrind.org/support/bug_reports.html.\n--1888-- WARNING: unhandled riscv64-linux syscall: 258\n--1888-- You may be able to write your own handler.\n--1888-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1888-- Nevertheless we consider this a bug.  Please report\n--1888-- it at http://valgrind.org/support/bug_reports.html.\n--1888-- WARNING: unhandled riscv64-linux syscall: 258\n--1888-- You may be able to write your own handler.\n--1888-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1888-- Nevertheless we consider this a bug.  Please report\n--1888-- it at http://valgrind.org/support/bug_reports.html.\n--1888-- WARNING: unhandled riscv64-linux syscall: 258\n--1888-- You may be able to write your own handler.\n--1888-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1888-- Nevertheless we consider this a bug.  Please report\n--1888-- it at http://valgrind.org/support/bug_reports.html.\n--1888-- WARNING: unhandled riscv64-linux syscall: 258\n--1888-- You may be able to write your own handler.\n--1888-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1888-- Nevertheless we consider this a bug.  Please report\n--1888-- it at http://valgrind.org/support/bug_reports.html.\n--1888-- WARNING: unhandled riscv64-linux syscall: 258\n--1888-- You may be able to write your own handler.\n--1888-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1888-- Nevertheless we consider this a bug.  Please report\n--1888-- it at http://valgrind.org/support/bug_reports.html.\n--1888-- WARNING: unhandled riscv64-linux syscall: 258\n--1888-- You may be able to write your own handler.\n--1888-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1888-- Nevertheless we consider this a bug.  Please report\n--1888-- it at http://valgrind.org/support/bug_reports.html.\n--1888-- WARNING: unhandled riscv64-linux syscall: 258\n--1888-- You may be able to write your own handler.\n--1888-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1888-- Nevertheless we consider this a bug.  Please report\n--1888-- it at http://valgrind.org/support/bug_reports.html.\n--1888-- WARNING: unhandled riscv64-linux syscall: 258\n--1888-- You may be able to write your own handler.\n--1888-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1888-- Nevertheless we consider this a bug.  Please report\n--1888-- it at http://valgrind.org/support/bug_reports.html.\n--1888-- WARNING: unhandled riscv64-linux syscall: 258\n--1888-- You may be able to write your own handler.\n--1888-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1888-- Nevertheless we consider this a bug.  Please report\n--1888-- 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:
'--1896-- WARNING: unhandled riscv64-linux syscall: 258\n--1896-- You may be able to write your own handler.\n--1896-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1896-- Nevertheless we consider this a bug.  Please report\n--1896-- it at http://valgrind.org/support/bug_reports.html.\n--1896-- WARNING: unhandled riscv64-linux syscall: 258\n--1896-- You may be able to write your own handler.\n--1896-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1896-- Nevertheless we consider this a bug.  Please report\n--1896-- it at http://valgrind.org/support/bug_reports.html.\n--1896-- WARNING: unhandled riscv64-linux syscall: 258\n--1896-- You may be able to write your own handler.\n--1896-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1896-- Nevertheless we consider this a bug.  Please report\n--1896-- it at http://valgrind.org/support/bug_reports.html.\n--1896-- WARNING: unhandled riscv64-linux syscall: 258\n--1896-- You may be able to write your own handler.\n--1896-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1896-- Nevertheless we consider this a bug.  Please report\n--1896-- it at http://valgrind.org/support/bug_reports.html.\n--1896-- WARNING: unhandled riscv64-linux syscall: 258\n--1896-- You may be able to write your own handler.\n--1896-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1896-- Nevertheless we consider this a bug.  Please report\n--1896-- it at http://valgrind.org/support/bug_reports.html.\n--1896-- WARNING: unhandled riscv64-linux syscall: 258\n--1896-- You may be able to write your own handler.\n--1896-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1896-- Nevertheless we consider this a bug.  Please report\n--1896-- it at http://valgrind.org/support/bug_reports.html.\n--1896-- WARNING: unhandled riscv64-linux syscall: 258\n--1896-- You may be able to write your own handler.\n--1896-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1896-- Nevertheless we consider this a bug.  Please report\n--1896-- it at http://valgrind.org/support/bug_reports.html.\n--1896-- WARNING: unhandled riscv64-linux syscall: 258\n--1896-- You may be able to write your own handler.\n--1896-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1896-- Nevertheless we consider this a bug.  Please report\n--1896-- it at http://valgrind.org/support/bug_reports.html.\n--1896-- WARNING: unhandled riscv64-linux syscall: 258\n--1896-- You may be able to write your own handler.\n--1896-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1896-- Nevertheless we consider this a bug.  Please report\n--1896-- it at http://valgrind.org/support/bug_reports.html.\n--1896-- WARNING: unhandled riscv64-linux syscall: 258\n--1896-- You may be able to write your own handler.\n--1896-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1896-- Nevertheless we consider this a bug.  Please report\n--1896-- it at http://valgrind.org/support/bug_reports.html.\n--1896-- WARNING: unhandled riscv64-linux syscall: 258\n--1896-- You may be able to write your own handler.\n--1896-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1896-- Nevertheless we consider this a bug.  Please report\n--1896-- it at http://valgrind.org/support/bug_reports.html.\n--1896-- WARNING: unhandled riscv64-linux syscall: 258\n--1896-- You may be able to write your own handler.\n--1896-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1896-- Nevertheless we consider this a bug.  Please report\n--1896-- it at http://valgrind.org/support/bug_reports.html.\n--1896-- WARNING: unhandled riscv64-linux syscall: 258\n--1896-- You may be able to write your own handler.\n--1896-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1896-- Nevertheless we consider this a bug.  Please report\n--1896-- it at http://valgrind.org/support/bug_reports.html.\n--1896-- WARNING: unhandled riscv64-linux syscall: 258\n--1896-- You may be able to write your own handler.\n--1896-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1896-- Nevertheless we consider this a bug.  Please report\n--1896-- it at http://valgrind.org/support/bug_reports.html.\n--1896-- WARNING: unhandled riscv64-linux syscall: 258\n--1896-- You may be able to write your own handler.\n--1896-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1896-- Nevertheless we consider this a bug.  Please report\n--1896-- it at http://valgrind.org/support/bug_reports.html.\n--1896-- WARNING: unhandled riscv64-linux syscall: 258\n--1896-- You may be able to write your own handler.\n--1896-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1896-- Nevertheless we consider this a bug.  Please report\n--1896-- it at http://valgrind.org/support/bug_reports.html.\n--1896-- WARNING: unhandled riscv64-linux syscall: 258\n--1896-- You may be able to write your own handler.\n--1896-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1896-- Nevertheless we consider this a bug.  Please report\n--1896-- it at http://valgrind.org/support/bug_reports.html.\n--1896-- WARNING: unhandled riscv64-linux syscall: 258\n--1896-- You may be able to write your own handler.\n--1896-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1896-- Nevertheless we consider this a bug.  Please report\n--1896-- 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:
'--1904-- WARNING: unhandled riscv64-linux syscall: 258\n--1904-- You may be able to write your own handler.\n--1904-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1904-- Nevertheless we consider this a bug.  Please report\n--1904-- it at http://valgrind.org/support/bug_reports.html.\n--1904-- WARNING: unhandled riscv64-linux syscall: 258\n--1904-- You may be able to write your own handler.\n--1904-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1904-- Nevertheless we consider this a bug.  Please report\n--1904-- it at http://valgrind.org/support/bug_reports.html.\n--1904-- WARNING: unhandled riscv64-linux syscall: 258\n--1904-- You may be able to write your own handler.\n--1904-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1904-- Nevertheless we consider this a bug.  Please report\n--1904-- it at http://valgrind.org/support/bug_reports.html.\n--1904-- WARNING: unhandled riscv64-linux syscall: 258\n--1904-- You may be able to write your own handler.\n--1904-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1904-- Nevertheless we consider this a bug.  Please report\n--1904-- it at http://valgrind.org/support/bug_reports.html.\n--1904-- WARNING: unhandled riscv64-linux syscall: 258\n--1904-- You may be able to write your own handler.\n--1904-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1904-- Nevertheless we consider this a bug.  Please report\n--1904-- it at http://valgrind.org/support/bug_reports.html.\n--1904-- WARNING: unhandled riscv64-linux syscall: 258\n--1904-- You may be able to write your own handler.\n--1904-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1904-- Nevertheless we consider this a bug.  Please report\n--1904-- it at http://valgrind.org/support/bug_reports.html.\n--1904-- WARNING: unhandled riscv64-linux syscall: 258\n--1904-- You may be able to write your own handler.\n--1904-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1904-- Nevertheless we consider this a bug.  Please report\n--1904-- it at http://valgrind.org/support/bug_reports.html.\n--1904-- WARNING: unhandled riscv64-linux syscall: 258\n--1904-- You may be able to write your own handler.\n--1904-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1904-- Nevertheless we consider this a bug.  Please report\n--1904-- it at http://valgrind.org/support/bug_reports.html.\n--1904-- WARNING: unhandled riscv64-linux syscall: 258\n--1904-- You may be able to write your own handler.\n--1904-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1904-- Nevertheless we consider this a bug.  Please report\n--1904-- it at http://valgrind.org/support/bug_reports.html.\n--1904-- WARNING: unhandled riscv64-linux syscall: 258\n--1904-- You may be able to write your own handler.\n--1904-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1904-- Nevertheless we consider this a bug.  Please report\n--1904-- it at http://valgrind.org/support/bug_reports.html.\n--1904-- WARNING: unhandled riscv64-linux syscall: 258\n--1904-- You may be able to write your own handler.\n--1904-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1904-- Nevertheless we consider this a bug.  Please report\n--1904-- it at http://valgrind.org/support/bug_reports.html.\n--1904-- WARNING: unhandled riscv64-linux syscall: 258\n--1904-- You may be able to write your own handler.\n--1904-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1904-- Nevertheless we consider this a bug.  Please report\n--1904-- it at http://valgrind.org/support/bug_reports.html.\n--1904-- WARNING: unhandled riscv64-linux syscall: 258\n--1904-- You may be able to write your own handler.\n--1904-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1904-- Nevertheless we consider this a bug.  Please report\n--1904-- it at http://valgrind.org/support/bug_reports.html.\n--1904-- WARNING: unhandled riscv64-linux syscall: 258\n--1904-- You may be able to write your own handler.\n--1904-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1904-- Nevertheless we consider this a bug.  Please report\n--1904-- it at http://valgrind.org/support/bug_reports.html.\n--1904-- WARNING: unhandled riscv64-linux syscall: 258\n--1904-- You may be able to write your own handler.\n--1904-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1904-- Nevertheless we consider this a bug.  Please report\n--1904-- it at http://valgrind.org/support/bug_reports.html.\n--1904-- WARNING: unhandled riscv64-linux syscall: 258\n--1904-- You may be able to write your own handler.\n--1904-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1904-- Nevertheless we consider this a bug.  Please report\n--1904-- it at http://valgrind.org/support/bug_reports.html.\n--1904-- WARNING: unhandled riscv64-linux syscall: 258\n--1904-- You may be able to write your own handler.\n--1904-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1904-- Nevertheless we consider this a bug.  Please report\n--1904-- it at http://valgrind.org/support/bug_reports.html.\n--1904-- WARNING: unhandled riscv64-linux syscall: 258\n--1904-- You may be able to write your own handler.\n--1904-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1904-- Nevertheless we consider this a bug.  Please report\n--1904-- 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:
'--1912-- WARNING: unhandled riscv64-linux syscall: 258\n--1912-- You may be able to write your own handler.\n--1912-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1912-- Nevertheless we consider this a bug.  Please report\n--1912-- it at http://valgrind.org/support/bug_reports.html.\n--1912-- WARNING: unhandled riscv64-linux syscall: 258\n--1912-- You may be able to write your own handler.\n--1912-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1912-- Nevertheless we consider this a bug.  Please report\n--1912-- it at http://valgrind.org/support/bug_reports.html.\n--1912-- WARNING: unhandled riscv64-linux syscall: 258\n--1912-- You may be able to write your own handler.\n--1912-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1912-- Nevertheless we consider this a bug.  Please report\n--1912-- it at http://valgrind.org/support/bug_reports.html.\n--1912-- WARNING: unhandled riscv64-linux syscall: 258\n--1912-- You may be able to write your own handler.\n--1912-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1912-- Nevertheless we consider this a bug.  Please report\n--1912-- it at http://valgrind.org/support/bug_reports.html.\n--1912-- WARNING: unhandled riscv64-linux syscall: 258\n--1912-- You may be able to write your own handler.\n--1912-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1912-- Nevertheless we consider this a bug.  Please report\n--1912-- it at http://valgrind.org/support/bug_reports.html.\n--1912-- WARNING: unhandled riscv64-linux syscall: 258\n--1912-- You may be able to write your own handler.\n--1912-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1912-- Nevertheless we consider this a bug.  Please report\n--1912-- it at http://valgrind.org/support/bug_reports.html.\n--1912-- WARNING: unhandled riscv64-linux syscall: 258\n--1912-- You may be able to write your own handler.\n--1912-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1912-- Nevertheless we consider this a bug.  Please report\n--1912-- it at http://valgrind.org/support/bug_reports.html.\n--1912-- WARNING: unhandled riscv64-linux syscall: 258\n--1912-- You may be able to write your own handler.\n--1912-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1912-- Nevertheless we consider this a bug.  Please report\n--1912-- it at http://valgrind.org/support/bug_reports.html.\n--1912-- WARNING: unhandled riscv64-linux syscall: 258\n--1912-- You may be able to write your own handler.\n--1912-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1912-- Nevertheless we consider this a bug.  Please report\n--1912-- it at http://valgrind.org/support/bug_reports.html.\n--1912-- WARNING: unhandled riscv64-linux syscall: 258\n--1912-- You may be able to write your own handler.\n--1912-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1912-- Nevertheless we consider this a bug.  Please report\n--1912-- it at http://valgrind.org/support/bug_reports.html.\n--1912-- WARNING: unhandled riscv64-linux syscall: 258\n--1912-- You may be able to write your own handler.\n--1912-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1912-- Nevertheless we consider this a bug.  Please report\n--1912-- it at http://valgrind.org/support/bug_reports.html.\n--1912-- WARNING: unhandled riscv64-linux syscall: 258\n--1912-- You may be able to write your own handler.\n--1912-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1912-- Nevertheless we consider this a bug.  Please report\n--1912-- it at http://valgrind.org/support/bug_reports.html.\n--1912-- WARNING: unhandled riscv64-linux syscall: 258\n--1912-- You may be able to write your own handler.\n--1912-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1912-- Nevertheless we consider this a bug.  Please report\n--1912-- it at http://valgrind.org/support/bug_reports.html.\n--1912-- WARNING: unhandled riscv64-linux syscall: 258\n--1912-- You may be able to write your own handler.\n--1912-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1912-- Nevertheless we consider this a bug.  Please report\n--1912-- it at http://valgrind.org/support/bug_reports.html.\n--1912-- WARNING: unhandled riscv64-linux syscall: 258\n--1912-- You may be able to write your own handler.\n--1912-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1912-- Nevertheless we consider this a bug.  Please report\n--1912-- it at http://valgrind.org/support/bug_reports.html.\n--1912-- WARNING: unhandled riscv64-linux syscall: 258\n--1912-- You may be able to write your own handler.\n--1912-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1912-- Nevertheless we consider this a bug.  Please report\n--1912-- it at http://valgrind.org/support/bug_reports.html.\n--1912-- WARNING: unhandled riscv64-linux syscall: 258\n--1912-- You may be able to write your own handler.\n--1912-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1912-- Nevertheless we consider this a bug.  Please report\n--1912-- it at http://valgrind.org/support/bug_reports.html.\n--1912-- WARNING: unhandled riscv64-linux syscall: 258\n--1912-- You may be able to write your own handler.\n--1912-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1912-- Nevertheless we consider this a bug.  Please report\n--1912-- 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:
'--1920-- WARNING: unhandled riscv64-linux syscall: 258\n--1920-- You may be able to write your own handler.\n--1920-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1920-- Nevertheless we consider this a bug.  Please report\n--1920-- it at http://valgrind.org/support/bug_reports.html.\n--1920-- WARNING: unhandled riscv64-linux syscall: 258\n--1920-- You may be able to write your own handler.\n--1920-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1920-- Nevertheless we consider this a bug.  Please report\n--1920-- it at http://valgrind.org/support/bug_reports.html.\n--1920-- WARNING: unhandled riscv64-linux syscall: 258\n--1920-- You may be able to write your own handler.\n--1920-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1920-- Nevertheless we consider this a bug.  Please report\n--1920-- it at http://valgrind.org/support/bug_reports.html.\n--1920-- WARNING: unhandled riscv64-linux syscall: 258\n--1920-- You may be able to write your own handler.\n--1920-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1920-- Nevertheless we consider this a bug.  Please report\n--1920-- it at http://valgrind.org/support/bug_reports.html.\n--1920-- WARNING: unhandled riscv64-linux syscall: 258\n--1920-- You may be able to write your own handler.\n--1920-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1920-- Nevertheless we consider this a bug.  Please report\n--1920-- it at http://valgrind.org/support/bug_reports.html.\n--1920-- WARNING: unhandled riscv64-linux syscall: 258\n--1920-- You may be able to write your own handler.\n--1920-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1920-- Nevertheless we consider this a bug.  Please report\n--1920-- it at http://valgrind.org/support/bug_reports.html.\n--1920-- WARNING: unhandled riscv64-linux syscall: 258\n--1920-- You may be able to write your own handler.\n--1920-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1920-- Nevertheless we consider this a bug.  Please report\n--1920-- it at http://valgrind.org/support/bug_reports.html.\n--1920-- WARNING: unhandled riscv64-linux syscall: 258\n--1920-- You may be able to write your own handler.\n--1920-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1920-- Nevertheless we consider this a bug.  Please report\n--1920-- it at http://valgrind.org/support/bug_reports.html.\n--1920-- WARNING: unhandled riscv64-linux syscall: 258\n--1920-- You may be able to write your own handler.\n--1920-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1920-- Nevertheless we consider this a bug.  Please report\n--1920-- it at http://valgrind.org/support/bug_reports.html.\n--1920-- WARNING: unhandled riscv64-linux syscall: 258\n--1920-- You may be able to write your own handler.\n--1920-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1920-- Nevertheless we consider this a bug.  Please report\n--1920-- it at http://valgrind.org/support/bug_reports.html.\n--1920-- WARNING: unhandled riscv64-linux syscall: 258\n--1920-- You may be able to write your own handler.\n--1920-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1920-- Nevertheless we consider this a bug.  Please report\n--1920-- it at http://valgrind.org/support/bug_reports.html.\n--1920-- WARNING: unhandled riscv64-linux syscall: 258\n--1920-- You may be able to write your own handler.\n--1920-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1920-- Nevertheless we consider this a bug.  Please report\n--1920-- it at http://valgrind.org/support/bug_reports.html.\n--1920-- WARNING: unhandled riscv64-linux syscall: 258\n--1920-- You may be able to write your own handler.\n--1920-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1920-- Nevertheless we consider this a bug.  Please report\n--1920-- it at http://valgrind.org/support/bug_reports.html.\n--1920-- WARNING: unhandled riscv64-linux syscall: 258\n--1920-- You may be able to write your own handler.\n--1920-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1920-- Nevertheless we consider this a bug.  Please report\n--1920-- it at http://valgrind.org/support/bug_reports.html.\n--1920-- WARNING: unhandled riscv64-linux syscall: 258\n--1920-- You may be able to write your own handler.\n--1920-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1920-- Nevertheless we consider this a bug.  Please report\n--1920-- it at http://valgrind.org/support/bug_reports.html.\n--1920-- WARNING: unhandled riscv64-linux syscall: 258\n--1920-- You may be able to write your own handler.\n--1920-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1920-- Nevertheless we consider this a bug.  Please report\n--1920-- it at http://valgrind.org/support/bug_reports.html.\n--1920-- WARNING: unhandled riscv64-linux syscall: 258\n--1920-- You may be able to write your own handler.\n--1920-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1920-- Nevertheless we consider this a bug.  Please report\n--1920-- it at http://valgrind.org/support/bug_reports.html.\n--1920-- WARNING: unhandled riscv64-linux syscall: 258\n--1920-- You may be able to write your own handler.\n--1920-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1920-- Nevertheless we consider this a bug.  Please report\n--1920-- 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:
'--1928-- WARNING: unhandled riscv64-linux syscall: 258\n--1928-- You may be able to write your own handler.\n--1928-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1928-- Nevertheless we consider this a bug.  Please report\n--1928-- it at http://valgrind.org/support/bug_reports.html.\n--1928-- WARNING: unhandled riscv64-linux syscall: 258\n--1928-- You may be able to write your own handler.\n--1928-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1928-- Nevertheless we consider this a bug.  Please report\n--1928-- it at http://valgrind.org/support/bug_reports.html.\n--1928-- WARNING: unhandled riscv64-linux syscall: 258\n--1928-- You may be able to write your own handler.\n--1928-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1928-- Nevertheless we consider this a bug.  Please report\n--1928-- it at http://valgrind.org/support/bug_reports.html.\n--1928-- WARNING: unhandled riscv64-linux syscall: 258\n--1928-- You may be able to write your own handler.\n--1928-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1928-- Nevertheless we consider this a bug.  Please report\n--1928-- it at http://valgrind.org/support/bug_reports.html.\n--1928-- WARNING: unhandled riscv64-linux syscall: 258\n--1928-- You may be able to write your own handler.\n--1928-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1928-- Nevertheless we consider this a bug.  Please report\n--1928-- it at http://valgrind.org/support/bug_reports.html.\n--1928-- WARNING: unhandled riscv64-linux syscall: 258\n--1928-- You may be able to write your own handler.\n--1928-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1928-- Nevertheless we consider this a bug.  Please report\n--1928-- it at http://valgrind.org/support/bug_reports.html.\n--1928-- WARNING: unhandled riscv64-linux syscall: 258\n--1928-- You may be able to write your own handler.\n--1928-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1928-- Nevertheless we consider this a bug.  Please report\n--1928-- it at http://valgrind.org/support/bug_reports.html.\n--1928-- WARNING: unhandled riscv64-linux syscall: 258\n--1928-- You may be able to write your own handler.\n--1928-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1928-- Nevertheless we consider this a bug.  Please report\n--1928-- it at http://valgrind.org/support/bug_reports.html.\n--1928-- WARNING: unhandled riscv64-linux syscall: 258\n--1928-- You may be able to write your own handler.\n--1928-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1928-- Nevertheless we consider this a bug.  Please report\n--1928-- it at http://valgrind.org/support/bug_reports.html.\n--1928-- WARNING: unhandled riscv64-linux syscall: 258\n--1928-- You may be able to write your own handler.\n--1928-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1928-- Nevertheless we consider this a bug.  Please report\n--1928-- it at http://valgrind.org/support/bug_reports.html.\n--1928-- WARNING: unhandled riscv64-linux syscall: 258\n--1928-- You may be able to write your own handler.\n--1928-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1928-- Nevertheless we consider this a bug.  Please report\n--1928-- it at http://valgrind.org/support/bug_reports.html.\n--1928-- WARNING: unhandled riscv64-linux syscall: 258\n--1928-- You may be able to write your own handler.\n--1928-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1928-- Nevertheless we consider this a bug.  Please report\n--1928-- it at http://valgrind.org/support/bug_reports.html.\n--1928-- WARNING: unhandled riscv64-linux syscall: 258\n--1928-- You may be able to write your own handler.\n--1928-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1928-- Nevertheless we consider this a bug.  Please report\n--1928-- it at http://valgrind.org/support/bug_reports.html.\n--1928-- WARNING: unhandled riscv64-linux syscall: 258\n--1928-- You may be able to write your own handler.\n--1928-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1928-- Nevertheless we consider this a bug.  Please report\n--1928-- it at http://valgrind.org/support/bug_reports.html.\n--1928-- WARNING: unhandled riscv64-linux syscall: 258\n--1928-- You may be able to write your own handler.\n--1928-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1928-- Nevertheless we consider this a bug.  Please report\n--1928-- it at http://valgrind.org/support/bug_reports.html.\n--1928-- WARNING: unhandled riscv64-linux syscall: 258\n--1928-- You may be able to write your own handler.\n--1928-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1928-- Nevertheless we consider this a bug.  Please report\n--1928-- it at http://valgrind.org/support/bug_reports.html.\n--1928-- WARNING: unhandled riscv64-linux syscall: 258\n--1928-- You may be able to write your own handler.\n--1928-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1928-- Nevertheless we consider this a bug.  Please report\n--1928-- it at http://valgrind.org/support/bug_reports.html.\n--1928-- WARNING: unhandled riscv64-linux syscall: 258\n--1928-- You may be able to write your own handler.\n--1928-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1928-- Nevertheless we consider this a bug.  Please report\n--1928-- 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:
'--1936-- WARNING: unhandled riscv64-linux syscall: 258\n--1936-- You may be able to write your own handler.\n--1936-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1936-- Nevertheless we consider this a bug.  Please report\n--1936-- it at http://valgrind.org/support/bug_reports.html.\n--1936-- WARNING: unhandled riscv64-linux syscall: 258\n--1936-- You may be able to write your own handler.\n--1936-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1936-- Nevertheless we consider this a bug.  Please report\n--1936-- it at http://valgrind.org/support/bug_reports.html.\n--1936-- WARNING: unhandled riscv64-linux syscall: 258\n--1936-- You may be able to write your own handler.\n--1936-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1936-- Nevertheless we consider this a bug.  Please report\n--1936-- it at http://valgrind.org/support/bug_reports.html.\n--1936-- WARNING: unhandled riscv64-linux syscall: 258\n--1936-- You may be able to write your own handler.\n--1936-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1936-- Nevertheless we consider this a bug.  Please report\n--1936-- it at http://valgrind.org/support/bug_reports.html.\n--1936-- WARNING: unhandled riscv64-linux syscall: 258\n--1936-- You may be able to write your own handler.\n--1936-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1936-- Nevertheless we consider this a bug.  Please report\n--1936-- it at http://valgrind.org/support/bug_reports.html.\n--1936-- WARNING: unhandled riscv64-linux syscall: 258\n--1936-- You may be able to write your own handler.\n--1936-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1936-- Nevertheless we consider this a bug.  Please report\n--1936-- it at http://valgrind.org/support/bug_reports.html.\n--1936-- WARNING: unhandled riscv64-linux syscall: 258\n--1936-- You may be able to write your own handler.\n--1936-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1936-- Nevertheless we consider this a bug.  Please report\n--1936-- it at http://valgrind.org/support/bug_reports.html.\n--1936-- WARNING: unhandled riscv64-linux syscall: 258\n--1936-- You may be able to write your own handler.\n--1936-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1936-- Nevertheless we consider this a bug.  Please report\n--1936-- it at http://valgrind.org/support/bug_reports.html.\n--1936-- WARNING: unhandled riscv64-linux syscall: 258\n--1936-- You may be able to write your own handler.\n--1936-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1936-- Nevertheless we consider this a bug.  Please report\n--1936-- it at http://valgrind.org/support/bug_reports.html.\n--1936-- WARNING: unhandled riscv64-linux syscall: 258\n--1936-- You may be able to write your own handler.\n--1936-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1936-- Nevertheless we consider this a bug.  Please report\n--1936-- it at http://valgrind.org/support/bug_reports.html.\n--1936-- WARNING: unhandled riscv64-linux syscall: 258\n--1936-- You may be able to write your own handler.\n--1936-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1936-- Nevertheless we consider this a bug.  Please report\n--1936-- it at http://valgrind.org/support/bug_reports.html.\n--1936-- WARNING: unhandled riscv64-linux syscall: 258\n--1936-- You may be able to write your own handler.\n--1936-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1936-- Nevertheless we consider this a bug.  Please report\n--1936-- it at http://valgrind.org/support/bug_reports.html.\n--1936-- WARNING: unhandled riscv64-linux syscall: 258\n--1936-- You may be able to write your own handler.\n--1936-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1936-- Nevertheless we consider this a bug.  Please report\n--1936-- it at http://valgrind.org/support/bug_reports.html.\n--1936-- WARNING: unhandled riscv64-linux syscall: 258\n--1936-- You may be able to write your own handler.\n--1936-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1936-- Nevertheless we consider this a bug.  Please report\n--1936-- it at http://valgrind.org/support/bug_reports.html.\n--1936-- WARNING: unhandled riscv64-linux syscall: 258\n--1936-- You may be able to write your own handler.\n--1936-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1936-- Nevertheless we consider this a bug.  Please report\n--1936-- it at http://valgrind.org/support/bug_reports.html.\n--1936-- WARNING: unhandled riscv64-linux syscall: 258\n--1936-- You may be able to write your own handler.\n--1936-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1936-- Nevertheless we consider this a bug.  Please report\n--1936-- it at http://valgrind.org/support/bug_reports.html.\n--1936-- WARNING: unhandled riscv64-linux syscall: 258\n--1936-- You may be able to write your own handler.\n--1936-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1936-- Nevertheless we consider this a bug.  Please report\n--1936-- it at http://valgrind.org/support/bug_reports.html.\n--1936-- WARNING: unhandled riscv64-linux syscall: 258\n--1936-- You may be able to write your own handler.\n--1936-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1936-- Nevertheless we consider this a bug.  Please report\n--1936-- 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:
'--1944-- WARNING: unhandled riscv64-linux syscall: 258\n--1944-- You may be able to write your own handler.\n--1944-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1944-- Nevertheless we consider this a bug.  Please report\n--1944-- it at http://valgrind.org/support/bug_reports.html.\n--1944-- WARNING: unhandled riscv64-linux syscall: 258\n--1944-- You may be able to write your own handler.\n--1944-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1944-- Nevertheless we consider this a bug.  Please report\n--1944-- it at http://valgrind.org/support/bug_reports.html.\n--1944-- WARNING: unhandled riscv64-linux syscall: 258\n--1944-- You may be able to write your own handler.\n--1944-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1944-- Nevertheless we consider this a bug.  Please report\n--1944-- it at http://valgrind.org/support/bug_reports.html.\n--1944-- WARNING: unhandled riscv64-linux syscall: 258\n--1944-- You may be able to write your own handler.\n--1944-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1944-- Nevertheless we consider this a bug.  Please report\n--1944-- it at http://valgrind.org/support/bug_reports.html.\n--1944-- WARNING: unhandled riscv64-linux syscall: 258\n--1944-- You may be able to write your own handler.\n--1944-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1944-- Nevertheless we consider this a bug.  Please report\n--1944-- it at http://valgrind.org/support/bug_reports.html.\n--1944-- WARNING: unhandled riscv64-linux syscall: 258\n--1944-- You may be able to write your own handler.\n--1944-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1944-- Nevertheless we consider this a bug.  Please report\n--1944-- it at http://valgrind.org/support/bug_reports.html.\n--1944-- WARNING: unhandled riscv64-linux syscall: 258\n--1944-- You may be able to write your own handler.\n--1944-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1944-- Nevertheless we consider this a bug.  Please report\n--1944-- it at http://valgrind.org/support/bug_reports.html.\n--1944-- WARNING: unhandled riscv64-linux syscall: 258\n--1944-- You may be able to write your own handler.\n--1944-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1944-- Nevertheless we consider this a bug.  Please report\n--1944-- it at http://valgrind.org/support/bug_reports.html.\n--1944-- WARNING: unhandled riscv64-linux syscall: 258\n--1944-- You may be able to write your own handler.\n--1944-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1944-- Nevertheless we consider this a bug.  Please report\n--1944-- it at http://valgrind.org/support/bug_reports.html.\n--1944-- WARNING: unhandled riscv64-linux syscall: 258\n--1944-- You may be able to write your own handler.\n--1944-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1944-- Nevertheless we consider this a bug.  Please report\n--1944-- it at http://valgrind.org/support/bug_reports.html.\n--1944-- WARNING: unhandled riscv64-linux syscall: 258\n--1944-- You may be able to write your own handler.\n--1944-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1944-- Nevertheless we consider this a bug.  Please report\n--1944-- it at http://valgrind.org/support/bug_reports.html.\n--1944-- WARNING: unhandled riscv64-linux syscall: 258\n--1944-- You may be able to write your own handler.\n--1944-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1944-- Nevertheless we consider this a bug.  Please report\n--1944-- it at http://valgrind.org/support/bug_reports.html.\n--1944-- WARNING: unhandled riscv64-linux syscall: 258\n--1944-- You may be able to write your own handler.\n--1944-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1944-- Nevertheless we consider this a bug.  Please report\n--1944-- it at http://valgrind.org/support/bug_reports.html.\n--1944-- WARNING: unhandled riscv64-linux syscall: 258\n--1944-- You may be able to write your own handler.\n--1944-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1944-- Nevertheless we consider this a bug.  Please report\n--1944-- it at http://valgrind.org/support/bug_reports.html.\n--1944-- WARNING: unhandled riscv64-linux syscall: 258\n--1944-- You may be able to write your own handler.\n--1944-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1944-- Nevertheless we consider this a bug.  Please report\n--1944-- it at http://valgrind.org/support/bug_reports.html.\n--1944-- WARNING: unhandled riscv64-linux syscall: 258\n--1944-- You may be able to write your own handler.\n--1944-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1944-- Nevertheless we consider this a bug.  Please report\n--1944-- it at http://valgrind.org/support/bug_reports.html.\n--1944-- WARNING: unhandled riscv64-linux syscall: 258\n--1944-- You may be able to write your own handler.\n--1944-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1944-- Nevertheless we consider this a bug.  Please report\n--1944-- it at http://valgrind.org/support/bug_reports.html.\n--1944-- WARNING: unhandled riscv64-linux syscall: 258\n--1944-- You may be able to write your own handler.\n--1944-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1944-- Nevertheless we consider this a bug.  Please report\n--1944-- 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:
'--1952-- WARNING: unhandled riscv64-linux syscall: 258\n--1952-- You may be able to write your own handler.\n--1952-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1952-- Nevertheless we consider this a bug.  Please report\n--1952-- it at http://valgrind.org/support/bug_reports.html.\n--1952-- WARNING: unhandled riscv64-linux syscall: 258\n--1952-- You may be able to write your own handler.\n--1952-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1952-- Nevertheless we consider this a bug.  Please report\n--1952-- it at http://valgrind.org/support/bug_reports.html.\n--1952-- WARNING: unhandled riscv64-linux syscall: 258\n--1952-- You may be able to write your own handler.\n--1952-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1952-- Nevertheless we consider this a bug.  Please report\n--1952-- it at http://valgrind.org/support/bug_reports.html.\n--1952-- WARNING: unhandled riscv64-linux syscall: 258\n--1952-- You may be able to write your own handler.\n--1952-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1952-- Nevertheless we consider this a bug.  Please report\n--1952-- it at http://valgrind.org/support/bug_reports.html.\n--1952-- WARNING: unhandled riscv64-linux syscall: 258\n--1952-- You may be able to write your own handler.\n--1952-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1952-- Nevertheless we consider this a bug.  Please report\n--1952-- it at http://valgrind.org/support/bug_reports.html.\n--1952-- WARNING: unhandled riscv64-linux syscall: 258\n--1952-- You may be able to write your own handler.\n--1952-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1952-- Nevertheless we consider this a bug.  Please report\n--1952-- it at http://valgrind.org/support/bug_reports.html.\n--1952-- WARNING: unhandled riscv64-linux syscall: 258\n--1952-- You may be able to write your own handler.\n--1952-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1952-- Nevertheless we consider this a bug.  Please report\n--1952-- it at http://valgrind.org/support/bug_reports.html.\n--1952-- WARNING: unhandled riscv64-linux syscall: 258\n--1952-- You may be able to write your own handler.\n--1952-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1952-- Nevertheless we consider this a bug.  Please report\n--1952-- it at http://valgrind.org/support/bug_reports.html.\n--1952-- WARNING: unhandled riscv64-linux syscall: 258\n--1952-- You may be able to write your own handler.\n--1952-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1952-- Nevertheless we consider this a bug.  Please report\n--1952-- it at http://valgrind.org/support/bug_reports.html.\n--1952-- WARNING: unhandled riscv64-linux syscall: 258\n--1952-- You may be able to write your own handler.\n--1952-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1952-- Nevertheless we consider this a bug.  Please report\n--1952-- it at http://valgrind.org/support/bug_reports.html.\n--1952-- WARNING: unhandled riscv64-linux syscall: 258\n--1952-- You may be able to write your own handler.\n--1952-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1952-- Nevertheless we consider this a bug.  Please report\n--1952-- it at http://valgrind.org/support/bug_reports.html.\n--1952-- WARNING: unhandled riscv64-linux syscall: 258\n--1952-- You may be able to write your own handler.\n--1952-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1952-- Nevertheless we consider this a bug.  Please report\n--1952-- it at http://valgrind.org/support/bug_reports.html.\n--1952-- WARNING: unhandled riscv64-linux syscall: 258\n--1952-- You may be able to write your own handler.\n--1952-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1952-- Nevertheless we consider this a bug.  Please report\n--1952-- it at http://valgrind.org/support/bug_reports.html.\n--1952-- WARNING: unhandled riscv64-linux syscall: 258\n--1952-- You may be able to write your own handler.\n--1952-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1952-- Nevertheless we consider this a bug.  Please report\n--1952-- it at http://valgrind.org/support/bug_reports.html.\n--1952-- WARNING: unhandled riscv64-linux syscall: 258\n--1952-- You may be able to write your own handler.\n--1952-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1952-- Nevertheless we consider this a bug.  Please report\n--1952-- it at http://valgrind.org/support/bug_reports.html.\n--1952-- WARNING: unhandled riscv64-linux syscall: 258\n--1952-- You may be able to write your own handler.\n--1952-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1952-- Nevertheless we consider this a bug.  Please report\n--1952-- it at http://valgrind.org/support/bug_reports.html.\n--1952-- WARNING: unhandled riscv64-linux syscall: 258\n--1952-- You may be able to write your own handler.\n--1952-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1952-- Nevertheless we consider this a bug.  Please report\n--1952-- it at http://valgrind.org/support/bug_reports.html.\n--1952-- WARNING: unhandled riscv64-linux syscall: 258\n--1952-- You may be able to write your own handler.\n--1952-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1952-- Nevertheless we consider this a bug.  Please report\n--1952-- 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:
'--1960-- WARNING: unhandled riscv64-linux syscall: 258\n--1960-- You may be able to write your own handler.\n--1960-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1960-- Nevertheless we consider this a bug.  Please report\n--1960-- it at http://valgrind.org/support/bug_reports.html.\n--1960-- WARNING: unhandled riscv64-linux syscall: 258\n--1960-- You may be able to write your own handler.\n--1960-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1960-- Nevertheless we consider this a bug.  Please report\n--1960-- it at http://valgrind.org/support/bug_reports.html.\n--1960-- WARNING: unhandled riscv64-linux syscall: 258\n--1960-- You may be able to write your own handler.\n--1960-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1960-- Nevertheless we consider this a bug.  Please report\n--1960-- it at http://valgrind.org/support/bug_reports.html.\n--1960-- WARNING: unhandled riscv64-linux syscall: 258\n--1960-- You may be able to write your own handler.\n--1960-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1960-- Nevertheless we consider this a bug.  Please report\n--1960-- it at http://valgrind.org/support/bug_reports.html.\n--1960-- WARNING: unhandled riscv64-linux syscall: 258\n--1960-- You may be able to write your own handler.\n--1960-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1960-- Nevertheless we consider this a bug.  Please report\n--1960-- it at http://valgrind.org/support/bug_reports.html.\n--1960-- WARNING: unhandled riscv64-linux syscall: 258\n--1960-- You may be able to write your own handler.\n--1960-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1960-- Nevertheless we consider this a bug.  Please report\n--1960-- it at http://valgrind.org/support/bug_reports.html.\n--1960-- WARNING: unhandled riscv64-linux syscall: 258\n--1960-- You may be able to write your own handler.\n--1960-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1960-- Nevertheless we consider this a bug.  Please report\n--1960-- it at http://valgrind.org/support/bug_reports.html.\n--1960-- WARNING: unhandled riscv64-linux syscall: 258\n--1960-- You may be able to write your own handler.\n--1960-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1960-- Nevertheless we consider this a bug.  Please report\n--1960-- it at http://valgrind.org/support/bug_reports.html.\n--1960-- WARNING: unhandled riscv64-linux syscall: 258\n--1960-- You may be able to write your own handler.\n--1960-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1960-- Nevertheless we consider this a bug.  Please report\n--1960-- it at http://valgrind.org/support/bug_reports.html.\n--1960-- WARNING: unhandled riscv64-linux syscall: 258\n--1960-- You may be able to write your own handler.\n--1960-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1960-- Nevertheless we consider this a bug.  Please report\n--1960-- it at http://valgrind.org/support/bug_reports.html.\n--1960-- WARNING: unhandled riscv64-linux syscall: 258\n--1960-- You may be able to write your own handler.\n--1960-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1960-- Nevertheless we consider this a bug.  Please report\n--1960-- it at http://valgrind.org/support/bug_reports.html.\n--1960-- WARNING: unhandled riscv64-linux syscall: 258\n--1960-- You may be able to write your own handler.\n--1960-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1960-- Nevertheless we consider this a bug.  Please report\n--1960-- it at http://valgrind.org/support/bug_reports.html.\n--1960-- WARNING: unhandled riscv64-linux syscall: 258\n--1960-- You may be able to write your own handler.\n--1960-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1960-- Nevertheless we consider this a bug.  Please report\n--1960-- it at http://valgrind.org/support/bug_reports.html.\n--1960-- WARNING: unhandled riscv64-linux syscall: 258\n--1960-- You may be able to write your own handler.\n--1960-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1960-- Nevertheless we consider this a bug.  Please report\n--1960-- it at http://valgrind.org/support/bug_reports.html.\n--1960-- WARNING: unhandled riscv64-linux syscall: 258\n--1960-- You may be able to write your own handler.\n--1960-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1960-- Nevertheless we consider this a bug.  Please report\n--1960-- it at http://valgrind.org/support/bug_reports.html.\n--1960-- WARNING: unhandled riscv64-linux syscall: 258\n--1960-- You may be able to write your own handler.\n--1960-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1960-- Nevertheless we consider this a bug.  Please report\n--1960-- it at http://valgrind.org/support/bug_reports.html.\n--1960-- WARNING: unhandled riscv64-linux syscall: 258\n--1960-- You may be able to write your own handler.\n--1960-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1960-- Nevertheless we consider this a bug.  Please report\n--1960-- it at http://valgrind.org/support/bug_reports.html.\n--1960-- WARNING: unhandled riscv64-linux syscall: 258\n--1960-- You may be able to write your own handler.\n--1960-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1960-- Nevertheless we consider this a bug.  Please report\n--1960-- 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:
'--1968-- WARNING: unhandled riscv64-linux syscall: 258\n--1968-- You may be able to write your own handler.\n--1968-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1968-- Nevertheless we consider this a bug.  Please report\n--1968-- it at http://valgrind.org/support/bug_reports.html.\n--1968-- WARNING: unhandled riscv64-linux syscall: 258\n--1968-- You may be able to write your own handler.\n--1968-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1968-- Nevertheless we consider this a bug.  Please report\n--1968-- it at http://valgrind.org/support/bug_reports.html.\n--1968-- WARNING: unhandled riscv64-linux syscall: 258\n--1968-- You may be able to write your own handler.\n--1968-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1968-- Nevertheless we consider this a bug.  Please report\n--1968-- it at http://valgrind.org/support/bug_reports.html.\n--1968-- WARNING: unhandled riscv64-linux syscall: 258\n--1968-- You may be able to write your own handler.\n--1968-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1968-- Nevertheless we consider this a bug.  Please report\n--1968-- it at http://valgrind.org/support/bug_reports.html.\n--1968-- WARNING: unhandled riscv64-linux syscall: 258\n--1968-- You may be able to write your own handler.\n--1968-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1968-- Nevertheless we consider this a bug.  Please report\n--1968-- it at http://valgrind.org/support/bug_reports.html.\n--1968-- WARNING: unhandled riscv64-linux syscall: 258\n--1968-- You may be able to write your own handler.\n--1968-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1968-- Nevertheless we consider this a bug.  Please report\n--1968-- it at http://valgrind.org/support/bug_reports.html.\n--1968-- WARNING: unhandled riscv64-linux syscall: 258\n--1968-- You may be able to write your own handler.\n--1968-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1968-- Nevertheless we consider this a bug.  Please report\n--1968-- it at http://valgrind.org/support/bug_reports.html.\n--1968-- WARNING: unhandled riscv64-linux syscall: 258\n--1968-- You may be able to write your own handler.\n--1968-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1968-- Nevertheless we consider this a bug.  Please report\n--1968-- it at http://valgrind.org/support/bug_reports.html.\n--1968-- WARNING: unhandled riscv64-linux syscall: 258\n--1968-- You may be able to write your own handler.\n--1968-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1968-- Nevertheless we consider this a bug.  Please report\n--1968-- it at http://valgrind.org/support/bug_reports.html.\n--1968-- WARNING: unhandled riscv64-linux syscall: 258\n--1968-- You may be able to write your own handler.\n--1968-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1968-- Nevertheless we consider this a bug.  Please report\n--1968-- it at http://valgrind.org/support/bug_reports.html.\n--1968-- WARNING: unhandled riscv64-linux syscall: 258\n--1968-- You may be able to write your own handler.\n--1968-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1968-- Nevertheless we consider this a bug.  Please report\n--1968-- it at http://valgrind.org/support/bug_reports.html.\n--1968-- WARNING: unhandled riscv64-linux syscall: 258\n--1968-- You may be able to write your own handler.\n--1968-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1968-- Nevertheless we consider this a bug.  Please report\n--1968-- it at http://valgrind.org/support/bug_reports.html.\n--1968-- WARNING: unhandled riscv64-linux syscall: 258\n--1968-- You may be able to write your own handler.\n--1968-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1968-- Nevertheless we consider this a bug.  Please report\n--1968-- it at http://valgrind.org/support/bug_reports.html.\n--1968-- WARNING: unhandled riscv64-linux syscall: 258\n--1968-- You may be able to write your own handler.\n--1968-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1968-- Nevertheless we consider this a bug.  Please report\n--1968-- it at http://valgrind.org/support/bug_reports.html.\n--1968-- WARNING: unhandled riscv64-linux syscall: 258\n--1968-- You may be able to write your own handler.\n--1968-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1968-- Nevertheless we consider this a bug.  Please report\n--1968-- it at http://valgrind.org/support/bug_reports.html.\n--1968-- WARNING: unhandled riscv64-linux syscall: 258\n--1968-- You may be able to write your own handler.\n--1968-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1968-- Nevertheless we consider this a bug.  Please report\n--1968-- it at http://valgrind.org/support/bug_reports.html.\n--1968-- WARNING: unhandled riscv64-linux syscall: 258\n--1968-- You may be able to write your own handler.\n--1968-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1968-- Nevertheless we consider this a bug.  Please report\n--1968-- it at http://valgrind.org/support/bug_reports.html.\n--1968-- WARNING: unhandled riscv64-linux syscall: 258\n--1968-- You may be able to write your own handler.\n--1968-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1968-- Nevertheless we consider this a bug.  Please report\n--1968-- 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:
'--1976-- WARNING: unhandled riscv64-linux syscall: 258\n--1976-- You may be able to write your own handler.\n--1976-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1976-- Nevertheless we consider this a bug.  Please report\n--1976-- it at http://valgrind.org/support/bug_reports.html.\n--1976-- WARNING: unhandled riscv64-linux syscall: 258\n--1976-- You may be able to write your own handler.\n--1976-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1976-- Nevertheless we consider this a bug.  Please report\n--1976-- it at http://valgrind.org/support/bug_reports.html.\n--1976-- WARNING: unhandled riscv64-linux syscall: 258\n--1976-- You may be able to write your own handler.\n--1976-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1976-- Nevertheless we consider this a bug.  Please report\n--1976-- it at http://valgrind.org/support/bug_reports.html.\n--1976-- WARNING: unhandled riscv64-linux syscall: 258\n--1976-- You may be able to write your own handler.\n--1976-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1976-- Nevertheless we consider this a bug.  Please report\n--1976-- it at http://valgrind.org/support/bug_reports.html.\n--1976-- WARNING: unhandled riscv64-linux syscall: 258\n--1976-- You may be able to write your own handler.\n--1976-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1976-- Nevertheless we consider this a bug.  Please report\n--1976-- it at http://valgrind.org/support/bug_reports.html.\n--1976-- WARNING: unhandled riscv64-linux syscall: 258\n--1976-- You may be able to write your own handler.\n--1976-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1976-- Nevertheless we consider this a bug.  Please report\n--1976-- it at http://valgrind.org/support/bug_reports.html.\n--1976-- WARNING: unhandled riscv64-linux syscall: 258\n--1976-- You may be able to write your own handler.\n--1976-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1976-- Nevertheless we consider this a bug.  Please report\n--1976-- it at http://valgrind.org/support/bug_reports.html.\n--1976-- WARNING: unhandled riscv64-linux syscall: 258\n--1976-- You may be able to write your own handler.\n--1976-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1976-- Nevertheless we consider this a bug.  Please report\n--1976-- it at http://valgrind.org/support/bug_reports.html.\n--1976-- WARNING: unhandled riscv64-linux syscall: 258\n--1976-- You may be able to write your own handler.\n--1976-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1976-- Nevertheless we consider this a bug.  Please report\n--1976-- it at http://valgrind.org/support/bug_reports.html.\n--1976-- WARNING: unhandled riscv64-linux syscall: 258\n--1976-- You may be able to write your own handler.\n--1976-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1976-- Nevertheless we consider this a bug.  Please report\n--1976-- it at http://valgrind.org/support/bug_reports.html.\n--1976-- WARNING: unhandled riscv64-linux syscall: 258\n--1976-- You may be able to write your own handler.\n--1976-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1976-- Nevertheless we consider this a bug.  Please report\n--1976-- it at http://valgrind.org/support/bug_reports.html.\n--1976-- WARNING: unhandled riscv64-linux syscall: 258\n--1976-- You may be able to write your own handler.\n--1976-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1976-- Nevertheless we consider this a bug.  Please report\n--1976-- it at http://valgrind.org/support/bug_reports.html.\n--1976-- WARNING: unhandled riscv64-linux syscall: 258\n--1976-- You may be able to write your own handler.\n--1976-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1976-- Nevertheless we consider this a bug.  Please report\n--1976-- it at http://valgrind.org/support/bug_reports.html.\n--1976-- WARNING: unhandled riscv64-linux syscall: 258\n--1976-- You may be able to write your own handler.\n--1976-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1976-- Nevertheless we consider this a bug.  Please report\n--1976-- it at http://valgrind.org/support/bug_reports.html.\n--1976-- WARNING: unhandled riscv64-linux syscall: 258\n--1976-- You may be able to write your own handler.\n--1976-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1976-- Nevertheless we consider this a bug.  Please report\n--1976-- it at http://valgrind.org/support/bug_reports.html.\n--1976-- WARNING: unhandled riscv64-linux syscall: 258\n--1976-- You may be able to write your own handler.\n--1976-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1976-- Nevertheless we consider this a bug.  Please report\n--1976-- it at http://valgrind.org/support/bug_reports.html.\n--1976-- WARNING: unhandled riscv64-linux syscall: 258\n--1976-- You may be able to write your own handler.\n--1976-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1976-- Nevertheless we consider this a bug.  Please report\n--1976-- it at http://valgrind.org/support/bug_reports.html.\n--1976-- WARNING: unhandled riscv64-linux syscall: 258\n--1976-- You may be able to write your own handler.\n--1976-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1976-- Nevertheless we consider this a bug.  Please report\n--1976-- it at http://valgrind.org/support/bug_reports.html.\n'
--- returncode --- 
expected:
0
got:
0
89: failed	localhost -g '{scheme} {host'
--- stderr --- 
expected:
''
got:
'--1984-- WARNING: unhandled riscv64-linux syscall: 258\n--1984-- You may be able to write your own handler.\n--1984-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1984-- Nevertheless we consider this a bug.  Please report\n--1984-- it at http://valgrind.org/support/bug_reports.html.\n--1984-- WARNING: unhandled riscv64-linux syscall: 258\n--1984-- You may be able to write your own handler.\n--1984-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1984-- Nevertheless we consider this a bug.  Please report\n--1984-- it at http://valgrind.org/support/bug_reports.html.\n--1984-- WARNING: unhandled riscv64-linux syscall: 258\n--1984-- You may be able to write your own handler.\n--1984-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1984-- Nevertheless we consider this a bug.  Please report\n--1984-- it at http://valgrind.org/support/bug_reports.html.\n--1984-- WARNING: unhandled riscv64-linux syscall: 258\n--1984-- You may be able to write your own handler.\n--1984-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1984-- Nevertheless we consider this a bug.  Please report\n--1984-- it at http://valgrind.org/support/bug_reports.html.\n--1984-- WARNING: unhandled riscv64-linux syscall: 258\n--1984-- You may be able to write your own handler.\n--1984-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1984-- Nevertheless we consider this a bug.  Please report\n--1984-- it at http://valgrind.org/support/bug_reports.html.\n--1984-- WARNING: unhandled riscv64-linux syscall: 258\n--1984-- You may be able to write your own handler.\n--1984-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1984-- Nevertheless we consider this a bug.  Please report\n--1984-- it at http://valgrind.org/support/bug_reports.html.\n--1984-- WARNING: unhandled riscv64-linux syscall: 258\n--1984-- You may be able to write your own handler.\n--1984-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1984-- Nevertheless we consider this a bug.  Please report\n--1984-- it at http://valgrind.org/support/bug_reports.html.\n--1984-- WARNING: unhandled riscv64-linux syscall: 258\n--1984-- You may be able to write your own handler.\n--1984-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1984-- Nevertheless we consider this a bug.  Please report\n--1984-- it at http://valgrind.org/support/bug_reports.html.\n--1984-- WARNING: unhandled riscv64-linux syscall: 258\n--1984-- You may be able to write your own handler.\n--1984-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1984-- Nevertheless we consider this a bug.  Please report\n--1984-- it at http://valgrind.org/support/bug_reports.html.\n--1984-- WARNING: unhandled riscv64-linux syscall: 258\n--1984-- You may be able to write your own handler.\n--1984-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1984-- Nevertheless we consider this a bug.  Please report\n--1984-- it at http://valgrind.org/support/bug_reports.html.\n--1984-- WARNING: unhandled riscv64-linux syscall: 258\n--1984-- You may be able to write your own handler.\n--1984-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1984-- Nevertheless we consider this a bug.  Please report\n--1984-- it at http://valgrind.org/support/bug_reports.html.\n--1984-- WARNING: unhandled riscv64-linux syscall: 258\n--1984-- You may be able to write your own handler.\n--1984-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1984-- Nevertheless we consider this a bug.  Please report\n--1984-- it at http://valgrind.org/support/bug_reports.html.\n--1984-- WARNING: unhandled riscv64-linux syscall: 258\n--1984-- You may be able to write your own handler.\n--1984-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1984-- Nevertheless we consider this a bug.  Please report\n--1984-- it at http://valgrind.org/support/bug_reports.html.\n--1984-- WARNING: unhandled riscv64-linux syscall: 258\n--1984-- You may be able to write your own handler.\n--1984-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1984-- Nevertheless we consider this a bug.  Please report\n--1984-- it at http://valgrind.org/support/bug_reports.html.\n--1984-- WARNING: unhandled riscv64-linux syscall: 258\n--1984-- You may be able to write your own handler.\n--1984-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1984-- Nevertheless we consider this a bug.  Please report\n--1984-- it at http://valgrind.org/support/bug_reports.html.\n--1984-- WARNING: unhandled riscv64-linux syscall: 258\n--1984-- You may be able to write your own handler.\n--1984-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1984-- Nevertheless we consider this a bug.  Please report\n--1984-- it at http://valgrind.org/support/bug_reports.html.\n--1984-- WARNING: unhandled riscv64-linux syscall: 258\n--1984-- You may be able to write your own handler.\n--1984-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1984-- Nevertheless we consider this a bug.  Please report\n--1984-- it at http://valgrind.org/support/bug_reports.html.\n--1984-- WARNING: unhandled riscv64-linux syscall: 258\n--1984-- You may be able to write your own handler.\n--1984-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1984-- Nevertheless we consider this a bug.  Please report\n--1984-- 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:
'--1992-- WARNING: unhandled riscv64-linux syscall: 258\n--1992-- You may be able to write your own handler.\n--1992-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1992-- Nevertheless we consider this a bug.  Please report\n--1992-- it at http://valgrind.org/support/bug_reports.html.\n--1992-- WARNING: unhandled riscv64-linux syscall: 258\n--1992-- You may be able to write your own handler.\n--1992-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1992-- Nevertheless we consider this a bug.  Please report\n--1992-- it at http://valgrind.org/support/bug_reports.html.\n--1992-- WARNING: unhandled riscv64-linux syscall: 258\n--1992-- You may be able to write your own handler.\n--1992-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1992-- Nevertheless we consider this a bug.  Please report\n--1992-- it at http://valgrind.org/support/bug_reports.html.\n--1992-- WARNING: unhandled riscv64-linux syscall: 258\n--1992-- You may be able to write your own handler.\n--1992-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1992-- Nevertheless we consider this a bug.  Please report\n--1992-- it at http://valgrind.org/support/bug_reports.html.\n--1992-- WARNING: unhandled riscv64-linux syscall: 258\n--1992-- You may be able to write your own handler.\n--1992-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1992-- Nevertheless we consider this a bug.  Please report\n--1992-- it at http://valgrind.org/support/bug_reports.html.\n--1992-- WARNING: unhandled riscv64-linux syscall: 258\n--1992-- You may be able to write your own handler.\n--1992-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1992-- Nevertheless we consider this a bug.  Please report\n--1992-- it at http://valgrind.org/support/bug_reports.html.\n--1992-- WARNING: unhandled riscv64-linux syscall: 258\n--1992-- You may be able to write your own handler.\n--1992-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1992-- Nevertheless we consider this a bug.  Please report\n--1992-- it at http://valgrind.org/support/bug_reports.html.\n--1992-- WARNING: unhandled riscv64-linux syscall: 258\n--1992-- You may be able to write your own handler.\n--1992-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1992-- Nevertheless we consider this a bug.  Please report\n--1992-- it at http://valgrind.org/support/bug_reports.html.\n--1992-- WARNING: unhandled riscv64-linux syscall: 258\n--1992-- You may be able to write your own handler.\n--1992-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1992-- Nevertheless we consider this a bug.  Please report\n--1992-- it at http://valgrind.org/support/bug_reports.html.\n--1992-- WARNING: unhandled riscv64-linux syscall: 258\n--1992-- You may be able to write your own handler.\n--1992-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1992-- Nevertheless we consider this a bug.  Please report\n--1992-- it at http://valgrind.org/support/bug_reports.html.\n--1992-- WARNING: unhandled riscv64-linux syscall: 258\n--1992-- You may be able to write your own handler.\n--1992-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1992-- Nevertheless we consider this a bug.  Please report\n--1992-- it at http://valgrind.org/support/bug_reports.html.\n--1992-- WARNING: unhandled riscv64-linux syscall: 258\n--1992-- You may be able to write your own handler.\n--1992-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1992-- Nevertheless we consider this a bug.  Please report\n--1992-- it at http://valgrind.org/support/bug_reports.html.\n--1992-- WARNING: unhandled riscv64-linux syscall: 258\n--1992-- You may be able to write your own handler.\n--1992-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1992-- Nevertheless we consider this a bug.  Please report\n--1992-- it at http://valgrind.org/support/bug_reports.html.\n--1992-- WARNING: unhandled riscv64-linux syscall: 258\n--1992-- You may be able to write your own handler.\n--1992-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1992-- Nevertheless we consider this a bug.  Please report\n--1992-- it at http://valgrind.org/support/bug_reports.html.\n--1992-- WARNING: unhandled riscv64-linux syscall: 258\n--1992-- You may be able to write your own handler.\n--1992-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1992-- Nevertheless we consider this a bug.  Please report\n--1992-- it at http://valgrind.org/support/bug_reports.html.\n--1992-- WARNING: unhandled riscv64-linux syscall: 258\n--1992-- You may be able to write your own handler.\n--1992-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1992-- Nevertheless we consider this a bug.  Please report\n--1992-- it at http://valgrind.org/support/bug_reports.html.\n--1992-- WARNING: unhandled riscv64-linux syscall: 258\n--1992-- You may be able to write your own handler.\n--1992-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1992-- Nevertheless we consider this a bug.  Please report\n--1992-- it at http://valgrind.org/support/bug_reports.html.\n--1992-- WARNING: unhandled riscv64-linux syscall: 258\n--1992-- You may be able to write your own handler.\n--1992-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--1992-- Nevertheless we consider this a bug.  Please report\n--1992-- 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:
'--2000-- WARNING: unhandled riscv64-linux syscall: 258\n--2000-- You may be able to write your own handler.\n--2000-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2000-- Nevertheless we consider this a bug.  Please report\n--2000-- it at http://valgrind.org/support/bug_reports.html.\n--2000-- WARNING: unhandled riscv64-linux syscall: 258\n--2000-- You may be able to write your own handler.\n--2000-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2000-- Nevertheless we consider this a bug.  Please report\n--2000-- it at http://valgrind.org/support/bug_reports.html.\n--2000-- WARNING: unhandled riscv64-linux syscall: 258\n--2000-- You may be able to write your own handler.\n--2000-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2000-- Nevertheless we consider this a bug.  Please report\n--2000-- it at http://valgrind.org/support/bug_reports.html.\n--2000-- WARNING: unhandled riscv64-linux syscall: 258\n--2000-- You may be able to write your own handler.\n--2000-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2000-- Nevertheless we consider this a bug.  Please report\n--2000-- it at http://valgrind.org/support/bug_reports.html.\n--2000-- WARNING: unhandled riscv64-linux syscall: 258\n--2000-- You may be able to write your own handler.\n--2000-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2000-- Nevertheless we consider this a bug.  Please report\n--2000-- it at http://valgrind.org/support/bug_reports.html.\n--2000-- WARNING: unhandled riscv64-linux syscall: 258\n--2000-- You may be able to write your own handler.\n--2000-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2000-- Nevertheless we consider this a bug.  Please report\n--2000-- it at http://valgrind.org/support/bug_reports.html.\n--2000-- WARNING: unhandled riscv64-linux syscall: 258\n--2000-- You may be able to write your own handler.\n--2000-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2000-- Nevertheless we consider this a bug.  Please report\n--2000-- it at http://valgrind.org/support/bug_reports.html.\n--2000-- WARNING: unhandled riscv64-linux syscall: 258\n--2000-- You may be able to write your own handler.\n--2000-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2000-- Nevertheless we consider this a bug.  Please report\n--2000-- it at http://valgrind.org/support/bug_reports.html.\n--2000-- WARNING: unhandled riscv64-linux syscall: 258\n--2000-- You may be able to write your own handler.\n--2000-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2000-- Nevertheless we consider this a bug.  Please report\n--2000-- it at http://valgrind.org/support/bug_reports.html.\n--2000-- WARNING: unhandled riscv64-linux syscall: 258\n--2000-- You may be able to write your own handler.\n--2000-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2000-- Nevertheless we consider this a bug.  Please report\n--2000-- it at http://valgrind.org/support/bug_reports.html.\n--2000-- WARNING: unhandled riscv64-linux syscall: 258\n--2000-- You may be able to write your own handler.\n--2000-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2000-- Nevertheless we consider this a bug.  Please report\n--2000-- it at http://valgrind.org/support/bug_reports.html.\n--2000-- WARNING: unhandled riscv64-linux syscall: 258\n--2000-- You may be able to write your own handler.\n--2000-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2000-- Nevertheless we consider this a bug.  Please report\n--2000-- it at http://valgrind.org/support/bug_reports.html.\n--2000-- WARNING: unhandled riscv64-linux syscall: 258\n--2000-- You may be able to write your own handler.\n--2000-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2000-- Nevertheless we consider this a bug.  Please report\n--2000-- it at http://valgrind.org/support/bug_reports.html.\n--2000-- WARNING: unhandled riscv64-linux syscall: 258\n--2000-- You may be able to write your own handler.\n--2000-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2000-- Nevertheless we consider this a bug.  Please report\n--2000-- it at http://valgrind.org/support/bug_reports.html.\n--2000-- WARNING: unhandled riscv64-linux syscall: 258\n--2000-- You may be able to write your own handler.\n--2000-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2000-- Nevertheless we consider this a bug.  Please report\n--2000-- it at http://valgrind.org/support/bug_reports.html.\n--2000-- WARNING: unhandled riscv64-linux syscall: 258\n--2000-- You may be able to write your own handler.\n--2000-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2000-- Nevertheless we consider this a bug.  Please report\n--2000-- it at http://valgrind.org/support/bug_reports.html.\n--2000-- WARNING: unhandled riscv64-linux syscall: 258\n--2000-- You may be able to write your own handler.\n--2000-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2000-- Nevertheless we consider this a bug.  Please report\n--2000-- it at http://valgrind.org/support/bug_reports.html.\n--2000-- WARNING: unhandled riscv64-linux syscall: 258\n--2000-- You may be able to write your own handler.\n--2000-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2000-- Nevertheless we consider this a bug.  Please report\n--2000-- 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:
'--2008-- WARNING: unhandled riscv64-linux syscall: 258\n--2008-- You may be able to write your own handler.\n--2008-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2008-- Nevertheless we consider this a bug.  Please report\n--2008-- it at http://valgrind.org/support/bug_reports.html.\n--2008-- WARNING: unhandled riscv64-linux syscall: 258\n--2008-- You may be able to write your own handler.\n--2008-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2008-- Nevertheless we consider this a bug.  Please report\n--2008-- it at http://valgrind.org/support/bug_reports.html.\n--2008-- WARNING: unhandled riscv64-linux syscall: 258\n--2008-- You may be able to write your own handler.\n--2008-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2008-- Nevertheless we consider this a bug.  Please report\n--2008-- it at http://valgrind.org/support/bug_reports.html.\n--2008-- WARNING: unhandled riscv64-linux syscall: 258\n--2008-- You may be able to write your own handler.\n--2008-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2008-- Nevertheless we consider this a bug.  Please report\n--2008-- it at http://valgrind.org/support/bug_reports.html.\n--2008-- WARNING: unhandled riscv64-linux syscall: 258\n--2008-- You may be able to write your own handler.\n--2008-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2008-- Nevertheless we consider this a bug.  Please report\n--2008-- it at http://valgrind.org/support/bug_reports.html.\n--2008-- WARNING: unhandled riscv64-linux syscall: 258\n--2008-- You may be able to write your own handler.\n--2008-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2008-- Nevertheless we consider this a bug.  Please report\n--2008-- it at http://valgrind.org/support/bug_reports.html.\n--2008-- WARNING: unhandled riscv64-linux syscall: 258\n--2008-- You may be able to write your own handler.\n--2008-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2008-- Nevertheless we consider this a bug.  Please report\n--2008-- it at http://valgrind.org/support/bug_reports.html.\n--2008-- WARNING: unhandled riscv64-linux syscall: 258\n--2008-- You may be able to write your own handler.\n--2008-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2008-- Nevertheless we consider this a bug.  Please report\n--2008-- it at http://valgrind.org/support/bug_reports.html.\n--2008-- WARNING: unhandled riscv64-linux syscall: 258\n--2008-- You may be able to write your own handler.\n--2008-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2008-- Nevertheless we consider this a bug.  Please report\n--2008-- it at http://valgrind.org/support/bug_reports.html.\n--2008-- WARNING: unhandled riscv64-linux syscall: 258\n--2008-- You may be able to write your own handler.\n--2008-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2008-- Nevertheless we consider this a bug.  Please report\n--2008-- it at http://valgrind.org/support/bug_reports.html.\n--2008-- WARNING: unhandled riscv64-linux syscall: 258\n--2008-- You may be able to write your own handler.\n--2008-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2008-- Nevertheless we consider this a bug.  Please report\n--2008-- it at http://valgrind.org/support/bug_reports.html.\n--2008-- WARNING: unhandled riscv64-linux syscall: 258\n--2008-- You may be able to write your own handler.\n--2008-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2008-- Nevertheless we consider this a bug.  Please report\n--2008-- it at http://valgrind.org/support/bug_reports.html.\n--2008-- WARNING: unhandled riscv64-linux syscall: 258\n--2008-- You may be able to write your own handler.\n--2008-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2008-- Nevertheless we consider this a bug.  Please report\n--2008-- it at http://valgrind.org/support/bug_reports.html.\n--2008-- WARNING: unhandled riscv64-linux syscall: 258\n--2008-- You may be able to write your own handler.\n--2008-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2008-- Nevertheless we consider this a bug.  Please report\n--2008-- it at http://valgrind.org/support/bug_reports.html.\n--2008-- WARNING: unhandled riscv64-linux syscall: 258\n--2008-- You may be able to write your own handler.\n--2008-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2008-- Nevertheless we consider this a bug.  Please report\n--2008-- it at http://valgrind.org/support/bug_reports.html.\n--2008-- WARNING: unhandled riscv64-linux syscall: 258\n--2008-- You may be able to write your own handler.\n--2008-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2008-- Nevertheless we consider this a bug.  Please report\n--2008-- it at http://valgrind.org/support/bug_reports.html.\n--2008-- WARNING: unhandled riscv64-linux syscall: 258\n--2008-- You may be able to write your own handler.\n--2008-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2008-- Nevertheless we consider this a bug.  Please report\n--2008-- it at http://valgrind.org/support/bug_reports.html.\n--2008-- WARNING: unhandled riscv64-linux syscall: 258\n--2008-- You may be able to write your own handler.\n--2008-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2008-- Nevertheless we consider this a bug.  Please report\n--2008-- 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:
'--2016-- WARNING: unhandled riscv64-linux syscall: 258\n--2016-- You may be able to write your own handler.\n--2016-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2016-- Nevertheless we consider this a bug.  Please report\n--2016-- it at http://valgrind.org/support/bug_reports.html.\n--2016-- WARNING: unhandled riscv64-linux syscall: 258\n--2016-- You may be able to write your own handler.\n--2016-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2016-- Nevertheless we consider this a bug.  Please report\n--2016-- it at http://valgrind.org/support/bug_reports.html.\n--2016-- WARNING: unhandled riscv64-linux syscall: 258\n--2016-- You may be able to write your own handler.\n--2016-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2016-- Nevertheless we consider this a bug.  Please report\n--2016-- it at http://valgrind.org/support/bug_reports.html.\n--2016-- WARNING: unhandled riscv64-linux syscall: 258\n--2016-- You may be able to write your own handler.\n--2016-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2016-- Nevertheless we consider this a bug.  Please report\n--2016-- it at http://valgrind.org/support/bug_reports.html.\n--2016-- WARNING: unhandled riscv64-linux syscall: 258\n--2016-- You may be able to write your own handler.\n--2016-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2016-- Nevertheless we consider this a bug.  Please report\n--2016-- it at http://valgrind.org/support/bug_reports.html.\n--2016-- WARNING: unhandled riscv64-linux syscall: 258\n--2016-- You may be able to write your own handler.\n--2016-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2016-- Nevertheless we consider this a bug.  Please report\n--2016-- it at http://valgrind.org/support/bug_reports.html.\n--2016-- WARNING: unhandled riscv64-linux syscall: 258\n--2016-- You may be able to write your own handler.\n--2016-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2016-- Nevertheless we consider this a bug.  Please report\n--2016-- it at http://valgrind.org/support/bug_reports.html.\n--2016-- WARNING: unhandled riscv64-linux syscall: 258\n--2016-- You may be able to write your own handler.\n--2016-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2016-- Nevertheless we consider this a bug.  Please report\n--2016-- it at http://valgrind.org/support/bug_reports.html.\n--2016-- WARNING: unhandled riscv64-linux syscall: 258\n--2016-- You may be able to write your own handler.\n--2016-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2016-- Nevertheless we consider this a bug.  Please report\n--2016-- it at http://valgrind.org/support/bug_reports.html.\n--2016-- WARNING: unhandled riscv64-linux syscall: 258\n--2016-- You may be able to write your own handler.\n--2016-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2016-- Nevertheless we consider this a bug.  Please report\n--2016-- it at http://valgrind.org/support/bug_reports.html.\n--2016-- WARNING: unhandled riscv64-linux syscall: 258\n--2016-- You may be able to write your own handler.\n--2016-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2016-- Nevertheless we consider this a bug.  Please report\n--2016-- it at http://valgrind.org/support/bug_reports.html.\n--2016-- WARNING: unhandled riscv64-linux syscall: 258\n--2016-- You may be able to write your own handler.\n--2016-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2016-- Nevertheless we consider this a bug.  Please report\n--2016-- it at http://valgrind.org/support/bug_reports.html.\n--2016-- WARNING: unhandled riscv64-linux syscall: 258\n--2016-- You may be able to write your own handler.\n--2016-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2016-- Nevertheless we consider this a bug.  Please report\n--2016-- it at http://valgrind.org/support/bug_reports.html.\n--2016-- WARNING: unhandled riscv64-linux syscall: 258\n--2016-- You may be able to write your own handler.\n--2016-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2016-- Nevertheless we consider this a bug.  Please report\n--2016-- it at http://valgrind.org/support/bug_reports.html.\n--2016-- WARNING: unhandled riscv64-linux syscall: 258\n--2016-- You may be able to write your own handler.\n--2016-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2016-- Nevertheless we consider this a bug.  Please report\n--2016-- it at http://valgrind.org/support/bug_reports.html.\n--2016-- WARNING: unhandled riscv64-linux syscall: 258\n--2016-- You may be able to write your own handler.\n--2016-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2016-- Nevertheless we consider this a bug.  Please report\n--2016-- it at http://valgrind.org/support/bug_reports.html.\n--2016-- WARNING: unhandled riscv64-linux syscall: 258\n--2016-- You may be able to write your own handler.\n--2016-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2016-- Nevertheless we consider this a bug.  Please report\n--2016-- it at http://valgrind.org/support/bug_reports.html.\n--2016-- WARNING: unhandled riscv64-linux syscall: 258\n--2016-- You may be able to write your own handler.\n--2016-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2016-- Nevertheless we consider this a bug.  Please report\n--2016-- 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:
'--2024-- WARNING: unhandled riscv64-linux syscall: 258\n--2024-- You may be able to write your own handler.\n--2024-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2024-- Nevertheless we consider this a bug.  Please report\n--2024-- it at http://valgrind.org/support/bug_reports.html.\n--2024-- WARNING: unhandled riscv64-linux syscall: 258\n--2024-- You may be able to write your own handler.\n--2024-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2024-- Nevertheless we consider this a bug.  Please report\n--2024-- it at http://valgrind.org/support/bug_reports.html.\n--2024-- WARNING: unhandled riscv64-linux syscall: 258\n--2024-- You may be able to write your own handler.\n--2024-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2024-- Nevertheless we consider this a bug.  Please report\n--2024-- it at http://valgrind.org/support/bug_reports.html.\n--2024-- WARNING: unhandled riscv64-linux syscall: 258\n--2024-- You may be able to write your own handler.\n--2024-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2024-- Nevertheless we consider this a bug.  Please report\n--2024-- it at http://valgrind.org/support/bug_reports.html.\n--2024-- WARNING: unhandled riscv64-linux syscall: 258\n--2024-- You may be able to write your own handler.\n--2024-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2024-- Nevertheless we consider this a bug.  Please report\n--2024-- it at http://valgrind.org/support/bug_reports.html.\n--2024-- WARNING: unhandled riscv64-linux syscall: 258\n--2024-- You may be able to write your own handler.\n--2024-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2024-- Nevertheless we consider this a bug.  Please report\n--2024-- it at http://valgrind.org/support/bug_reports.html.\n--2024-- WARNING: unhandled riscv64-linux syscall: 258\n--2024-- You may be able to write your own handler.\n--2024-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2024-- Nevertheless we consider this a bug.  Please report\n--2024-- it at http://valgrind.org/support/bug_reports.html.\n--2024-- WARNING: unhandled riscv64-linux syscall: 258\n--2024-- You may be able to write your own handler.\n--2024-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2024-- Nevertheless we consider this a bug.  Please report\n--2024-- it at http://valgrind.org/support/bug_reports.html.\n--2024-- WARNING: unhandled riscv64-linux syscall: 258\n--2024-- You may be able to write your own handler.\n--2024-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2024-- Nevertheless we consider this a bug.  Please report\n--2024-- it at http://valgrind.org/support/bug_reports.html.\n--2024-- WARNING: unhandled riscv64-linux syscall: 258\n--2024-- You may be able to write your own handler.\n--2024-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2024-- Nevertheless we consider this a bug.  Please report\n--2024-- it at http://valgrind.org/support/bug_reports.html.\n--2024-- WARNING: unhandled riscv64-linux syscall: 258\n--2024-- You may be able to write your own handler.\n--2024-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2024-- Nevertheless we consider this a bug.  Please report\n--2024-- it at http://valgrind.org/support/bug_reports.html.\n--2024-- WARNING: unhandled riscv64-linux syscall: 258\n--2024-- You may be able to write your own handler.\n--2024-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2024-- Nevertheless we consider this a bug.  Please report\n--2024-- it at http://valgrind.org/support/bug_reports.html.\n--2024-- WARNING: unhandled riscv64-linux syscall: 258\n--2024-- You may be able to write your own handler.\n--2024-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2024-- Nevertheless we consider this a bug.  Please report\n--2024-- it at http://valgrind.org/support/bug_reports.html.\n--2024-- WARNING: unhandled riscv64-linux syscall: 258\n--2024-- You may be able to write your own handler.\n--2024-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2024-- Nevertheless we consider this a bug.  Please report\n--2024-- it at http://valgrind.org/support/bug_reports.html.\n--2024-- WARNING: unhandled riscv64-linux syscall: 258\n--2024-- You may be able to write your own handler.\n--2024-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2024-- Nevertheless we consider this a bug.  Please report\n--2024-- it at http://valgrind.org/support/bug_reports.html.\n--2024-- WARNING: unhandled riscv64-linux syscall: 258\n--2024-- You may be able to write your own handler.\n--2024-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2024-- Nevertheless we consider this a bug.  Please report\n--2024-- it at http://valgrind.org/support/bug_reports.html.\n--2024-- WARNING: unhandled riscv64-linux syscall: 258\n--2024-- You may be able to write your own handler.\n--2024-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2024-- Nevertheless we consider this a bug.  Please report\n--2024-- it at http://valgrind.org/support/bug_reports.html.\n--2024-- WARNING: unhandled riscv64-linux syscall: 258\n--2024-- You may be able to write your own handler.\n--2024-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2024-- Nevertheless we consider this a bug.  Please report\n--2024-- 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:
'--2032-- WARNING: unhandled riscv64-linux syscall: 258\n--2032-- You may be able to write your own handler.\n--2032-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2032-- Nevertheless we consider this a bug.  Please report\n--2032-- it at http://valgrind.org/support/bug_reports.html.\n--2032-- WARNING: unhandled riscv64-linux syscall: 258\n--2032-- You may be able to write your own handler.\n--2032-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2032-- Nevertheless we consider this a bug.  Please report\n--2032-- it at http://valgrind.org/support/bug_reports.html.\n--2032-- WARNING: unhandled riscv64-linux syscall: 258\n--2032-- You may be able to write your own handler.\n--2032-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2032-- Nevertheless we consider this a bug.  Please report\n--2032-- it at http://valgrind.org/support/bug_reports.html.\n--2032-- WARNING: unhandled riscv64-linux syscall: 258\n--2032-- You may be able to write your own handler.\n--2032-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2032-- Nevertheless we consider this a bug.  Please report\n--2032-- it at http://valgrind.org/support/bug_reports.html.\n--2032-- WARNING: unhandled riscv64-linux syscall: 258\n--2032-- You may be able to write your own handler.\n--2032-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2032-- Nevertheless we consider this a bug.  Please report\n--2032-- it at http://valgrind.org/support/bug_reports.html.\n--2032-- WARNING: unhandled riscv64-linux syscall: 258\n--2032-- You may be able to write your own handler.\n--2032-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2032-- Nevertheless we consider this a bug.  Please report\n--2032-- it at http://valgrind.org/support/bug_reports.html.\n--2032-- WARNING: unhandled riscv64-linux syscall: 258\n--2032-- You may be able to write your own handler.\n--2032-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2032-- Nevertheless we consider this a bug.  Please report\n--2032-- it at http://valgrind.org/support/bug_reports.html.\n--2032-- WARNING: unhandled riscv64-linux syscall: 258\n--2032-- You may be able to write your own handler.\n--2032-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2032-- Nevertheless we consider this a bug.  Please report\n--2032-- it at http://valgrind.org/support/bug_reports.html.\n--2032-- WARNING: unhandled riscv64-linux syscall: 258\n--2032-- You may be able to write your own handler.\n--2032-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2032-- Nevertheless we consider this a bug.  Please report\n--2032-- it at http://valgrind.org/support/bug_reports.html.\n--2032-- WARNING: unhandled riscv64-linux syscall: 258\n--2032-- You may be able to write your own handler.\n--2032-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2032-- Nevertheless we consider this a bug.  Please report\n--2032-- it at http://valgrind.org/support/bug_reports.html.\n--2032-- WARNING: unhandled riscv64-linux syscall: 258\n--2032-- You may be able to write your own handler.\n--2032-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2032-- Nevertheless we consider this a bug.  Please report\n--2032-- it at http://valgrind.org/support/bug_reports.html.\n--2032-- WARNING: unhandled riscv64-linux syscall: 258\n--2032-- You may be able to write your own handler.\n--2032-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2032-- Nevertheless we consider this a bug.  Please report\n--2032-- it at http://valgrind.org/support/bug_reports.html.\n--2032-- WARNING: unhandled riscv64-linux syscall: 258\n--2032-- You may be able to write your own handler.\n--2032-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2032-- Nevertheless we consider this a bug.  Please report\n--2032-- it at http://valgrind.org/support/bug_reports.html.\n--2032-- WARNING: unhandled riscv64-linux syscall: 258\n--2032-- You may be able to write your own handler.\n--2032-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2032-- Nevertheless we consider this a bug.  Please report\n--2032-- it at http://valgrind.org/support/bug_reports.html.\n--2032-- WARNING: unhandled riscv64-linux syscall: 258\n--2032-- You may be able to write your own handler.\n--2032-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2032-- Nevertheless we consider this a bug.  Please report\n--2032-- it at http://valgrind.org/support/bug_reports.html.\n--2032-- WARNING: unhandled riscv64-linux syscall: 258\n--2032-- You may be able to write your own handler.\n--2032-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2032-- Nevertheless we consider this a bug.  Please report\n--2032-- it at http://valgrind.org/support/bug_reports.html.\n--2032-- WARNING: unhandled riscv64-linux syscall: 258\n--2032-- You may be able to write your own handler.\n--2032-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2032-- Nevertheless we consider this a bug.  Please report\n--2032-- it at http://valgrind.org/support/bug_reports.html.\n--2032-- WARNING: unhandled riscv64-linux syscall: 258\n--2032-- You may be able to write your own handler.\n--2032-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2032-- Nevertheless we consider this a bug.  Please report\n--2032-- 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:
'--2040-- WARNING: unhandled riscv64-linux syscall: 258\n--2040-- You may be able to write your own handler.\n--2040-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2040-- Nevertheless we consider this a bug.  Please report\n--2040-- it at http://valgrind.org/support/bug_reports.html.\n--2040-- WARNING: unhandled riscv64-linux syscall: 258\n--2040-- You may be able to write your own handler.\n--2040-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2040-- Nevertheless we consider this a bug.  Please report\n--2040-- it at http://valgrind.org/support/bug_reports.html.\n--2040-- WARNING: unhandled riscv64-linux syscall: 258\n--2040-- You may be able to write your own handler.\n--2040-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2040-- Nevertheless we consider this a bug.  Please report\n--2040-- it at http://valgrind.org/support/bug_reports.html.\n--2040-- WARNING: unhandled riscv64-linux syscall: 258\n--2040-- You may be able to write your own handler.\n--2040-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2040-- Nevertheless we consider this a bug.  Please report\n--2040-- it at http://valgrind.org/support/bug_reports.html.\n--2040-- WARNING: unhandled riscv64-linux syscall: 258\n--2040-- You may be able to write your own handler.\n--2040-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2040-- Nevertheless we consider this a bug.  Please report\n--2040-- it at http://valgrind.org/support/bug_reports.html.\n--2040-- WARNING: unhandled riscv64-linux syscall: 258\n--2040-- You may be able to write your own handler.\n--2040-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2040-- Nevertheless we consider this a bug.  Please report\n--2040-- it at http://valgrind.org/support/bug_reports.html.\n--2040-- WARNING: unhandled riscv64-linux syscall: 258\n--2040-- You may be able to write your own handler.\n--2040-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2040-- Nevertheless we consider this a bug.  Please report\n--2040-- it at http://valgrind.org/support/bug_reports.html.\n--2040-- WARNING: unhandled riscv64-linux syscall: 258\n--2040-- You may be able to write your own handler.\n--2040-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2040-- Nevertheless we consider this a bug.  Please report\n--2040-- it at http://valgrind.org/support/bug_reports.html.\n--2040-- WARNING: unhandled riscv64-linux syscall: 258\n--2040-- You may be able to write your own handler.\n--2040-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2040-- Nevertheless we consider this a bug.  Please report\n--2040-- it at http://valgrind.org/support/bug_reports.html.\n--2040-- WARNING: unhandled riscv64-linux syscall: 258\n--2040-- You may be able to write your own handler.\n--2040-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2040-- Nevertheless we consider this a bug.  Please report\n--2040-- it at http://valgrind.org/support/bug_reports.html.\n--2040-- WARNING: unhandled riscv64-linux syscall: 258\n--2040-- You may be able to write your own handler.\n--2040-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2040-- Nevertheless we consider this a bug.  Please report\n--2040-- it at http://valgrind.org/support/bug_reports.html.\n--2040-- WARNING: unhandled riscv64-linux syscall: 258\n--2040-- You may be able to write your own handler.\n--2040-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2040-- Nevertheless we consider this a bug.  Please report\n--2040-- it at http://valgrind.org/support/bug_reports.html.\n--2040-- WARNING: unhandled riscv64-linux syscall: 258\n--2040-- You may be able to write your own handler.\n--2040-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2040-- Nevertheless we consider this a bug.  Please report\n--2040-- it at http://valgrind.org/support/bug_reports.html.\n--2040-- WARNING: unhandled riscv64-linux syscall: 258\n--2040-- You may be able to write your own handler.\n--2040-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2040-- Nevertheless we consider this a bug.  Please report\n--2040-- it at http://valgrind.org/support/bug_reports.html.\n--2040-- WARNING: unhandled riscv64-linux syscall: 258\n--2040-- You may be able to write your own handler.\n--2040-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2040-- Nevertheless we consider this a bug.  Please report\n--2040-- it at http://valgrind.org/support/bug_reports.html.\n--2040-- WARNING: unhandled riscv64-linux syscall: 258\n--2040-- You may be able to write your own handler.\n--2040-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2040-- Nevertheless we consider this a bug.  Please report\n--2040-- it at http://valgrind.org/support/bug_reports.html.\n--2040-- WARNING: unhandled riscv64-linux syscall: 258\n--2040-- You may be able to write your own handler.\n--2040-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2040-- Nevertheless we consider this a bug.  Please report\n--2040-- it at http://valgrind.org/support/bug_reports.html.\n--2040-- WARNING: unhandled riscv64-linux syscall: 258\n--2040-- You may be able to write your own handler.\n--2040-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2040-- Nevertheless we consider this a bug.  Please report\n--2040-- 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:
'--2048-- WARNING: unhandled riscv64-linux syscall: 258\n--2048-- You may be able to write your own handler.\n--2048-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2048-- Nevertheless we consider this a bug.  Please report\n--2048-- it at http://valgrind.org/support/bug_reports.html.\n--2048-- WARNING: unhandled riscv64-linux syscall: 258\n--2048-- You may be able to write your own handler.\n--2048-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2048-- Nevertheless we consider this a bug.  Please report\n--2048-- it at http://valgrind.org/support/bug_reports.html.\n--2048-- WARNING: unhandled riscv64-linux syscall: 258\n--2048-- You may be able to write your own handler.\n--2048-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2048-- Nevertheless we consider this a bug.  Please report\n--2048-- it at http://valgrind.org/support/bug_reports.html.\n--2048-- WARNING: unhandled riscv64-linux syscall: 258\n--2048-- You may be able to write your own handler.\n--2048-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2048-- Nevertheless we consider this a bug.  Please report\n--2048-- it at http://valgrind.org/support/bug_reports.html.\n--2048-- WARNING: unhandled riscv64-linux syscall: 258\n--2048-- You may be able to write your own handler.\n--2048-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2048-- Nevertheless we consider this a bug.  Please report\n--2048-- it at http://valgrind.org/support/bug_reports.html.\n--2048-- WARNING: unhandled riscv64-linux syscall: 258\n--2048-- You may be able to write your own handler.\n--2048-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2048-- Nevertheless we consider this a bug.  Please report\n--2048-- it at http://valgrind.org/support/bug_reports.html.\n--2048-- WARNING: unhandled riscv64-linux syscall: 258\n--2048-- You may be able to write your own handler.\n--2048-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2048-- Nevertheless we consider this a bug.  Please report\n--2048-- it at http://valgrind.org/support/bug_reports.html.\n--2048-- WARNING: unhandled riscv64-linux syscall: 258\n--2048-- You may be able to write your own handler.\n--2048-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2048-- Nevertheless we consider this a bug.  Please report\n--2048-- it at http://valgrind.org/support/bug_reports.html.\n--2048-- WARNING: unhandled riscv64-linux syscall: 258\n--2048-- You may be able to write your own handler.\n--2048-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2048-- Nevertheless we consider this a bug.  Please report\n--2048-- it at http://valgrind.org/support/bug_reports.html.\n--2048-- WARNING: unhandled riscv64-linux syscall: 258\n--2048-- You may be able to write your own handler.\n--2048-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2048-- Nevertheless we consider this a bug.  Please report\n--2048-- it at http://valgrind.org/support/bug_reports.html.\n--2048-- WARNING: unhandled riscv64-linux syscall: 258\n--2048-- You may be able to write your own handler.\n--2048-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2048-- Nevertheless we consider this a bug.  Please report\n--2048-- it at http://valgrind.org/support/bug_reports.html.\n--2048-- WARNING: unhandled riscv64-linux syscall: 258\n--2048-- You may be able to write your own handler.\n--2048-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2048-- Nevertheless we consider this a bug.  Please report\n--2048-- it at http://valgrind.org/support/bug_reports.html.\n--2048-- WARNING: unhandled riscv64-linux syscall: 258\n--2048-- You may be able to write your own handler.\n--2048-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2048-- Nevertheless we consider this a bug.  Please report\n--2048-- it at http://valgrind.org/support/bug_reports.html.\n--2048-- WARNING: unhandled riscv64-linux syscall: 258\n--2048-- You may be able to write your own handler.\n--2048-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2048-- Nevertheless we consider this a bug.  Please report\n--2048-- it at http://valgrind.org/support/bug_reports.html.\n--2048-- WARNING: unhandled riscv64-linux syscall: 258\n--2048-- You may be able to write your own handler.\n--2048-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2048-- Nevertheless we consider this a bug.  Please report\n--2048-- it at http://valgrind.org/support/bug_reports.html.\n--2048-- WARNING: unhandled riscv64-linux syscall: 258\n--2048-- You may be able to write your own handler.\n--2048-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2048-- Nevertheless we consider this a bug.  Please report\n--2048-- it at http://valgrind.org/support/bug_reports.html.\n--2048-- WARNING: unhandled riscv64-linux syscall: 258\n--2048-- You may be able to write your own handler.\n--2048-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2048-- Nevertheless we consider this a bug.  Please report\n--2048-- it at http://valgrind.org/support/bug_reports.html.\n--2048-- WARNING: unhandled riscv64-linux syscall: 258\n--2048-- You may be able to write your own handler.\n--2048-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2048-- Nevertheless we consider this a bug.  Please report\n--2048-- 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:
'--2056-- WARNING: unhandled riscv64-linux syscall: 258\n--2056-- You may be able to write your own handler.\n--2056-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2056-- Nevertheless we consider this a bug.  Please report\n--2056-- it at http://valgrind.org/support/bug_reports.html.\n--2056-- WARNING: unhandled riscv64-linux syscall: 258\n--2056-- You may be able to write your own handler.\n--2056-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2056-- Nevertheless we consider this a bug.  Please report\n--2056-- it at http://valgrind.org/support/bug_reports.html.\n--2056-- WARNING: unhandled riscv64-linux syscall: 258\n--2056-- You may be able to write your own handler.\n--2056-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2056-- Nevertheless we consider this a bug.  Please report\n--2056-- it at http://valgrind.org/support/bug_reports.html.\n--2056-- WARNING: unhandled riscv64-linux syscall: 258\n--2056-- You may be able to write your own handler.\n--2056-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2056-- Nevertheless we consider this a bug.  Please report\n--2056-- it at http://valgrind.org/support/bug_reports.html.\n--2056-- WARNING: unhandled riscv64-linux syscall: 258\n--2056-- You may be able to write your own handler.\n--2056-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2056-- Nevertheless we consider this a bug.  Please report\n--2056-- it at http://valgrind.org/support/bug_reports.html.\n--2056-- WARNING: unhandled riscv64-linux syscall: 258\n--2056-- You may be able to write your own handler.\n--2056-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2056-- Nevertheless we consider this a bug.  Please report\n--2056-- it at http://valgrind.org/support/bug_reports.html.\n--2056-- WARNING: unhandled riscv64-linux syscall: 258\n--2056-- You may be able to write your own handler.\n--2056-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2056-- Nevertheless we consider this a bug.  Please report\n--2056-- it at http://valgrind.org/support/bug_reports.html.\n--2056-- WARNING: unhandled riscv64-linux syscall: 258\n--2056-- You may be able to write your own handler.\n--2056-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2056-- Nevertheless we consider this a bug.  Please report\n--2056-- it at http://valgrind.org/support/bug_reports.html.\n--2056-- WARNING: unhandled riscv64-linux syscall: 258\n--2056-- You may be able to write your own handler.\n--2056-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2056-- Nevertheless we consider this a bug.  Please report\n--2056-- it at http://valgrind.org/support/bug_reports.html.\n--2056-- WARNING: unhandled riscv64-linux syscall: 258\n--2056-- You may be able to write your own handler.\n--2056-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2056-- Nevertheless we consider this a bug.  Please report\n--2056-- it at http://valgrind.org/support/bug_reports.html.\n--2056-- WARNING: unhandled riscv64-linux syscall: 258\n--2056-- You may be able to write your own handler.\n--2056-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2056-- Nevertheless we consider this a bug.  Please report\n--2056-- it at http://valgrind.org/support/bug_reports.html.\n--2056-- WARNING: unhandled riscv64-linux syscall: 258\n--2056-- You may be able to write your own handler.\n--2056-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2056-- Nevertheless we consider this a bug.  Please report\n--2056-- it at http://valgrind.org/support/bug_reports.html.\n--2056-- WARNING: unhandled riscv64-linux syscall: 258\n--2056-- You may be able to write your own handler.\n--2056-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2056-- Nevertheless we consider this a bug.  Please report\n--2056-- it at http://valgrind.org/support/bug_reports.html.\n--2056-- WARNING: unhandled riscv64-linux syscall: 258\n--2056-- You may be able to write your own handler.\n--2056-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2056-- Nevertheless we consider this a bug.  Please report\n--2056-- it at http://valgrind.org/support/bug_reports.html.\n--2056-- WARNING: unhandled riscv64-linux syscall: 258\n--2056-- You may be able to write your own handler.\n--2056-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2056-- Nevertheless we consider this a bug.  Please report\n--2056-- it at http://valgrind.org/support/bug_reports.html.\n--2056-- WARNING: unhandled riscv64-linux syscall: 258\n--2056-- You may be able to write your own handler.\n--2056-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2056-- Nevertheless we consider this a bug.  Please report\n--2056-- it at http://valgrind.org/support/bug_reports.html.\n--2056-- WARNING: unhandled riscv64-linux syscall: 258\n--2056-- You may be able to write your own handler.\n--2056-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2056-- Nevertheless we consider this a bug.  Please report\n--2056-- it at http://valgrind.org/support/bug_reports.html.\n--2056-- WARNING: unhandled riscv64-linux syscall: 258\n--2056-- You may be able to write your own handler.\n--2056-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2056-- Nevertheless we consider this a bug.  Please report\n--2056-- 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:
'--2064-- WARNING: unhandled riscv64-linux syscall: 258\n--2064-- You may be able to write your own handler.\n--2064-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2064-- Nevertheless we consider this a bug.  Please report\n--2064-- it at http://valgrind.org/support/bug_reports.html.\n--2064-- WARNING: unhandled riscv64-linux syscall: 258\n--2064-- You may be able to write your own handler.\n--2064-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2064-- Nevertheless we consider this a bug.  Please report\n--2064-- it at http://valgrind.org/support/bug_reports.html.\n--2064-- WARNING: unhandled riscv64-linux syscall: 258\n--2064-- You may be able to write your own handler.\n--2064-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2064-- Nevertheless we consider this a bug.  Please report\n--2064-- it at http://valgrind.org/support/bug_reports.html.\n--2064-- WARNING: unhandled riscv64-linux syscall: 258\n--2064-- You may be able to write your own handler.\n--2064-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2064-- Nevertheless we consider this a bug.  Please report\n--2064-- it at http://valgrind.org/support/bug_reports.html.\n--2064-- WARNING: unhandled riscv64-linux syscall: 258\n--2064-- You may be able to write your own handler.\n--2064-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2064-- Nevertheless we consider this a bug.  Please report\n--2064-- it at http://valgrind.org/support/bug_reports.html.\n--2064-- WARNING: unhandled riscv64-linux syscall: 258\n--2064-- You may be able to write your own handler.\n--2064-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2064-- Nevertheless we consider this a bug.  Please report\n--2064-- it at http://valgrind.org/support/bug_reports.html.\n--2064-- WARNING: unhandled riscv64-linux syscall: 258\n--2064-- You may be able to write your own handler.\n--2064-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2064-- Nevertheless we consider this a bug.  Please report\n--2064-- it at http://valgrind.org/support/bug_reports.html.\n--2064-- WARNING: unhandled riscv64-linux syscall: 258\n--2064-- You may be able to write your own handler.\n--2064-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2064-- Nevertheless we consider this a bug.  Please report\n--2064-- it at http://valgrind.org/support/bug_reports.html.\n--2064-- WARNING: unhandled riscv64-linux syscall: 258\n--2064-- You may be able to write your own handler.\n--2064-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2064-- Nevertheless we consider this a bug.  Please report\n--2064-- it at http://valgrind.org/support/bug_reports.html.\n--2064-- WARNING: unhandled riscv64-linux syscall: 258\n--2064-- You may be able to write your own handler.\n--2064-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2064-- Nevertheless we consider this a bug.  Please report\n--2064-- it at http://valgrind.org/support/bug_reports.html.\n--2064-- WARNING: unhandled riscv64-linux syscall: 258\n--2064-- You may be able to write your own handler.\n--2064-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2064-- Nevertheless we consider this a bug.  Please report\n--2064-- it at http://valgrind.org/support/bug_reports.html.\n--2064-- WARNING: unhandled riscv64-linux syscall: 258\n--2064-- You may be able to write your own handler.\n--2064-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2064-- Nevertheless we consider this a bug.  Please report\n--2064-- it at http://valgrind.org/support/bug_reports.html.\n--2064-- WARNING: unhandled riscv64-linux syscall: 258\n--2064-- You may be able to write your own handler.\n--2064-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2064-- Nevertheless we consider this a bug.  Please report\n--2064-- it at http://valgrind.org/support/bug_reports.html.\n--2064-- WARNING: unhandled riscv64-linux syscall: 258\n--2064-- You may be able to write your own handler.\n--2064-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2064-- Nevertheless we consider this a bug.  Please report\n--2064-- it at http://valgrind.org/support/bug_reports.html.\n--2064-- WARNING: unhandled riscv64-linux syscall: 258\n--2064-- You may be able to write your own handler.\n--2064-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2064-- Nevertheless we consider this a bug.  Please report\n--2064-- it at http://valgrind.org/support/bug_reports.html.\n--2064-- WARNING: unhandled riscv64-linux syscall: 258\n--2064-- You may be able to write your own handler.\n--2064-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2064-- Nevertheless we consider this a bug.  Please report\n--2064-- it at http://valgrind.org/support/bug_reports.html.\n--2064-- WARNING: unhandled riscv64-linux syscall: 258\n--2064-- You may be able to write your own handler.\n--2064-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2064-- Nevertheless we consider this a bug.  Please report\n--2064-- it at http://valgrind.org/support/bug_reports.html.\n--2064-- WARNING: unhandled riscv64-linux syscall: 258\n--2064-- You may be able to write your own handler.\n--2064-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2064-- Nevertheless we consider this a bug.  Please report\n--2064-- 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:
'--2072-- WARNING: unhandled riscv64-linux syscall: 258\n--2072-- You may be able to write your own handler.\n--2072-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2072-- Nevertheless we consider this a bug.  Please report\n--2072-- it at http://valgrind.org/support/bug_reports.html.\n--2072-- WARNING: unhandled riscv64-linux syscall: 258\n--2072-- You may be able to write your own handler.\n--2072-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2072-- Nevertheless we consider this a bug.  Please report\n--2072-- it at http://valgrind.org/support/bug_reports.html.\n--2072-- WARNING: unhandled riscv64-linux syscall: 258\n--2072-- You may be able to write your own handler.\n--2072-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2072-- Nevertheless we consider this a bug.  Please report\n--2072-- it at http://valgrind.org/support/bug_reports.html.\n--2072-- WARNING: unhandled riscv64-linux syscall: 258\n--2072-- You may be able to write your own handler.\n--2072-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2072-- Nevertheless we consider this a bug.  Please report\n--2072-- it at http://valgrind.org/support/bug_reports.html.\n--2072-- WARNING: unhandled riscv64-linux syscall: 258\n--2072-- You may be able to write your own handler.\n--2072-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2072-- Nevertheless we consider this a bug.  Please report\n--2072-- it at http://valgrind.org/support/bug_reports.html.\n--2072-- WARNING: unhandled riscv64-linux syscall: 258\n--2072-- You may be able to write your own handler.\n--2072-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2072-- Nevertheless we consider this a bug.  Please report\n--2072-- it at http://valgrind.org/support/bug_reports.html.\n--2072-- WARNING: unhandled riscv64-linux syscall: 258\n--2072-- You may be able to write your own handler.\n--2072-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2072-- Nevertheless we consider this a bug.  Please report\n--2072-- it at http://valgrind.org/support/bug_reports.html.\n--2072-- WARNING: unhandled riscv64-linux syscall: 258\n--2072-- You may be able to write your own handler.\n--2072-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2072-- Nevertheless we consider this a bug.  Please report\n--2072-- it at http://valgrind.org/support/bug_reports.html.\n--2072-- WARNING: unhandled riscv64-linux syscall: 258\n--2072-- You may be able to write your own handler.\n--2072-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2072-- Nevertheless we consider this a bug.  Please report\n--2072-- it at http://valgrind.org/support/bug_reports.html.\n--2072-- WARNING: unhandled riscv64-linux syscall: 258\n--2072-- You may be able to write your own handler.\n--2072-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2072-- Nevertheless we consider this a bug.  Please report\n--2072-- it at http://valgrind.org/support/bug_reports.html.\n--2072-- WARNING: unhandled riscv64-linux syscall: 258\n--2072-- You may be able to write your own handler.\n--2072-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2072-- Nevertheless we consider this a bug.  Please report\n--2072-- it at http://valgrind.org/support/bug_reports.html.\n--2072-- WARNING: unhandled riscv64-linux syscall: 258\n--2072-- You may be able to write your own handler.\n--2072-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2072-- Nevertheless we consider this a bug.  Please report\n--2072-- it at http://valgrind.org/support/bug_reports.html.\n--2072-- WARNING: unhandled riscv64-linux syscall: 258\n--2072-- You may be able to write your own handler.\n--2072-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2072-- Nevertheless we consider this a bug.  Please report\n--2072-- it at http://valgrind.org/support/bug_reports.html.\n--2072-- WARNING: unhandled riscv64-linux syscall: 258\n--2072-- You may be able to write your own handler.\n--2072-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2072-- Nevertheless we consider this a bug.  Please report\n--2072-- it at http://valgrind.org/support/bug_reports.html.\n--2072-- WARNING: unhandled riscv64-linux syscall: 258\n--2072-- You may be able to write your own handler.\n--2072-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2072-- Nevertheless we consider this a bug.  Please report\n--2072-- it at http://valgrind.org/support/bug_reports.html.\n--2072-- WARNING: unhandled riscv64-linux syscall: 258\n--2072-- You may be able to write your own handler.\n--2072-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2072-- Nevertheless we consider this a bug.  Please report\n--2072-- it at http://valgrind.org/support/bug_reports.html.\n--2072-- WARNING: unhandled riscv64-linux syscall: 258\n--2072-- You may be able to write your own handler.\n--2072-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2072-- Nevertheless we consider this a bug.  Please report\n--2072-- it at http://valgrind.org/support/bug_reports.html.\n--2072-- WARNING: unhandled riscv64-linux syscall: 258\n--2072-- You may be able to write your own handler.\n--2072-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2072-- Nevertheless we consider this a bug.  Please report\n--2072-- 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:
'--2080-- WARNING: unhandled riscv64-linux syscall: 258\n--2080-- You may be able to write your own handler.\n--2080-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2080-- Nevertheless we consider this a bug.  Please report\n--2080-- it at http://valgrind.org/support/bug_reports.html.\n--2080-- WARNING: unhandled riscv64-linux syscall: 258\n--2080-- You may be able to write your own handler.\n--2080-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2080-- Nevertheless we consider this a bug.  Please report\n--2080-- it at http://valgrind.org/support/bug_reports.html.\n--2080-- WARNING: unhandled riscv64-linux syscall: 258\n--2080-- You may be able to write your own handler.\n--2080-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2080-- Nevertheless we consider this a bug.  Please report\n--2080-- it at http://valgrind.org/support/bug_reports.html.\n--2080-- WARNING: unhandled riscv64-linux syscall: 258\n--2080-- You may be able to write your own handler.\n--2080-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2080-- Nevertheless we consider this a bug.  Please report\n--2080-- it at http://valgrind.org/support/bug_reports.html.\n--2080-- WARNING: unhandled riscv64-linux syscall: 258\n--2080-- You may be able to write your own handler.\n--2080-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2080-- Nevertheless we consider this a bug.  Please report\n--2080-- it at http://valgrind.org/support/bug_reports.html.\n--2080-- WARNING: unhandled riscv64-linux syscall: 258\n--2080-- You may be able to write your own handler.\n--2080-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2080-- Nevertheless we consider this a bug.  Please report\n--2080-- it at http://valgrind.org/support/bug_reports.html.\n--2080-- WARNING: unhandled riscv64-linux syscall: 258\n--2080-- You may be able to write your own handler.\n--2080-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2080-- Nevertheless we consider this a bug.  Please report\n--2080-- it at http://valgrind.org/support/bug_reports.html.\n--2080-- WARNING: unhandled riscv64-linux syscall: 258\n--2080-- You may be able to write your own handler.\n--2080-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2080-- Nevertheless we consider this a bug.  Please report\n--2080-- it at http://valgrind.org/support/bug_reports.html.\n--2080-- WARNING: unhandled riscv64-linux syscall: 258\n--2080-- You may be able to write your own handler.\n--2080-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2080-- Nevertheless we consider this a bug.  Please report\n--2080-- it at http://valgrind.org/support/bug_reports.html.\n--2080-- WARNING: unhandled riscv64-linux syscall: 258\n--2080-- You may be able to write your own handler.\n--2080-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2080-- Nevertheless we consider this a bug.  Please report\n--2080-- it at http://valgrind.org/support/bug_reports.html.\n--2080-- WARNING: unhandled riscv64-linux syscall: 258\n--2080-- You may be able to write your own handler.\n--2080-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2080-- Nevertheless we consider this a bug.  Please report\n--2080-- it at http://valgrind.org/support/bug_reports.html.\n--2080-- WARNING: unhandled riscv64-linux syscall: 258\n--2080-- You may be able to write your own handler.\n--2080-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2080-- Nevertheless we consider this a bug.  Please report\n--2080-- it at http://valgrind.org/support/bug_reports.html.\n--2080-- WARNING: unhandled riscv64-linux syscall: 258\n--2080-- You may be able to write your own handler.\n--2080-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2080-- Nevertheless we consider this a bug.  Please report\n--2080-- it at http://valgrind.org/support/bug_reports.html.\n--2080-- WARNING: unhandled riscv64-linux syscall: 258\n--2080-- You may be able to write your own handler.\n--2080-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2080-- Nevertheless we consider this a bug.  Please report\n--2080-- it at http://valgrind.org/support/bug_reports.html.\n--2080-- WARNING: unhandled riscv64-linux syscall: 258\n--2080-- You may be able to write your own handler.\n--2080-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2080-- Nevertheless we consider this a bug.  Please report\n--2080-- it at http://valgrind.org/support/bug_reports.html.\n--2080-- WARNING: unhandled riscv64-linux syscall: 258\n--2080-- You may be able to write your own handler.\n--2080-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2080-- Nevertheless we consider this a bug.  Please report\n--2080-- it at http://valgrind.org/support/bug_reports.html.\n--2080-- WARNING: unhandled riscv64-linux syscall: 258\n--2080-- You may be able to write your own handler.\n--2080-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2080-- Nevertheless we consider this a bug.  Please report\n--2080-- it at http://valgrind.org/support/bug_reports.html.\n--2080-- WARNING: unhandled riscv64-linux syscall: 258\n--2080-- You may be able to write your own handler.\n--2080-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2080-- Nevertheless we consider this a bug.  Please report\n--2080-- 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:
'--2088-- WARNING: unhandled riscv64-linux syscall: 258\n--2088-- You may be able to write your own handler.\n--2088-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2088-- Nevertheless we consider this a bug.  Please report\n--2088-- it at http://valgrind.org/support/bug_reports.html.\n--2088-- WARNING: unhandled riscv64-linux syscall: 258\n--2088-- You may be able to write your own handler.\n--2088-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2088-- Nevertheless we consider this a bug.  Please report\n--2088-- it at http://valgrind.org/support/bug_reports.html.\n--2088-- WARNING: unhandled riscv64-linux syscall: 258\n--2088-- You may be able to write your own handler.\n--2088-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2088-- Nevertheless we consider this a bug.  Please report\n--2088-- it at http://valgrind.org/support/bug_reports.html.\n--2088-- WARNING: unhandled riscv64-linux syscall: 258\n--2088-- You may be able to write your own handler.\n--2088-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2088-- Nevertheless we consider this a bug.  Please report\n--2088-- it at http://valgrind.org/support/bug_reports.html.\n--2088-- WARNING: unhandled riscv64-linux syscall: 258\n--2088-- You may be able to write your own handler.\n--2088-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2088-- Nevertheless we consider this a bug.  Please report\n--2088-- it at http://valgrind.org/support/bug_reports.html.\n--2088-- WARNING: unhandled riscv64-linux syscall: 258\n--2088-- You may be able to write your own handler.\n--2088-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2088-- Nevertheless we consider this a bug.  Please report\n--2088-- it at http://valgrind.org/support/bug_reports.html.\n--2088-- WARNING: unhandled riscv64-linux syscall: 258\n--2088-- You may be able to write your own handler.\n--2088-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2088-- Nevertheless we consider this a bug.  Please report\n--2088-- it at http://valgrind.org/support/bug_reports.html.\n--2088-- WARNING: unhandled riscv64-linux syscall: 258\n--2088-- You may be able to write your own handler.\n--2088-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2088-- Nevertheless we consider this a bug.  Please report\n--2088-- it at http://valgrind.org/support/bug_reports.html.\n--2088-- WARNING: unhandled riscv64-linux syscall: 258\n--2088-- You may be able to write your own handler.\n--2088-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2088-- Nevertheless we consider this a bug.  Please report\n--2088-- it at http://valgrind.org/support/bug_reports.html.\n--2088-- WARNING: unhandled riscv64-linux syscall: 258\n--2088-- You may be able to write your own handler.\n--2088-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2088-- Nevertheless we consider this a bug.  Please report\n--2088-- it at http://valgrind.org/support/bug_reports.html.\n--2088-- WARNING: unhandled riscv64-linux syscall: 258\n--2088-- You may be able to write your own handler.\n--2088-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2088-- Nevertheless we consider this a bug.  Please report\n--2088-- it at http://valgrind.org/support/bug_reports.html.\n--2088-- WARNING: unhandled riscv64-linux syscall: 258\n--2088-- You may be able to write your own handler.\n--2088-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2088-- Nevertheless we consider this a bug.  Please report\n--2088-- it at http://valgrind.org/support/bug_reports.html.\n--2088-- WARNING: unhandled riscv64-linux syscall: 258\n--2088-- You may be able to write your own handler.\n--2088-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2088-- Nevertheless we consider this a bug.  Please report\n--2088-- it at http://valgrind.org/support/bug_reports.html.\n--2088-- WARNING: unhandled riscv64-linux syscall: 258\n--2088-- You may be able to write your own handler.\n--2088-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2088-- Nevertheless we consider this a bug.  Please report\n--2088-- it at http://valgrind.org/support/bug_reports.html.\n--2088-- WARNING: unhandled riscv64-linux syscall: 258\n--2088-- You may be able to write your own handler.\n--2088-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2088-- Nevertheless we consider this a bug.  Please report\n--2088-- it at http://valgrind.org/support/bug_reports.html.\n--2088-- WARNING: unhandled riscv64-linux syscall: 258\n--2088-- You may be able to write your own handler.\n--2088-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2088-- Nevertheless we consider this a bug.  Please report\n--2088-- it at http://valgrind.org/support/bug_reports.html.\n--2088-- WARNING: unhandled riscv64-linux syscall: 258\n--2088-- You may be able to write your own handler.\n--2088-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2088-- Nevertheless we consider this a bug.  Please report\n--2088-- it at http://valgrind.org/support/bug_reports.html.\n--2088-- WARNING: unhandled riscv64-linux syscall: 258\n--2088-- You may be able to write your own handler.\n--2088-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2088-- Nevertheless we consider this a bug.  Please report\n--2088-- 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:
'--2096-- WARNING: unhandled riscv64-linux syscall: 258\n--2096-- You may be able to write your own handler.\n--2096-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2096-- Nevertheless we consider this a bug.  Please report\n--2096-- it at http://valgrind.org/support/bug_reports.html.\n--2096-- WARNING: unhandled riscv64-linux syscall: 258\n--2096-- You may be able to write your own handler.\n--2096-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2096-- Nevertheless we consider this a bug.  Please report\n--2096-- it at http://valgrind.org/support/bug_reports.html.\n--2096-- WARNING: unhandled riscv64-linux syscall: 258\n--2096-- You may be able to write your own handler.\n--2096-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2096-- Nevertheless we consider this a bug.  Please report\n--2096-- it at http://valgrind.org/support/bug_reports.html.\n--2096-- WARNING: unhandled riscv64-linux syscall: 258\n--2096-- You may be able to write your own handler.\n--2096-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2096-- Nevertheless we consider this a bug.  Please report\n--2096-- it at http://valgrind.org/support/bug_reports.html.\n--2096-- WARNING: unhandled riscv64-linux syscall: 258\n--2096-- You may be able to write your own handler.\n--2096-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2096-- Nevertheless we consider this a bug.  Please report\n--2096-- it at http://valgrind.org/support/bug_reports.html.\n--2096-- WARNING: unhandled riscv64-linux syscall: 258\n--2096-- You may be able to write your own handler.\n--2096-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2096-- Nevertheless we consider this a bug.  Please report\n--2096-- it at http://valgrind.org/support/bug_reports.html.\n--2096-- WARNING: unhandled riscv64-linux syscall: 258\n--2096-- You may be able to write your own handler.\n--2096-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2096-- Nevertheless we consider this a bug.  Please report\n--2096-- it at http://valgrind.org/support/bug_reports.html.\n--2096-- WARNING: unhandled riscv64-linux syscall: 258\n--2096-- You may be able to write your own handler.\n--2096-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2096-- Nevertheless we consider this a bug.  Please report\n--2096-- it at http://valgrind.org/support/bug_reports.html.\n--2096-- WARNING: unhandled riscv64-linux syscall: 258\n--2096-- You may be able to write your own handler.\n--2096-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2096-- Nevertheless we consider this a bug.  Please report\n--2096-- it at http://valgrind.org/support/bug_reports.html.\n--2096-- WARNING: unhandled riscv64-linux syscall: 258\n--2096-- You may be able to write your own handler.\n--2096-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2096-- Nevertheless we consider this a bug.  Please report\n--2096-- it at http://valgrind.org/support/bug_reports.html.\n--2096-- WARNING: unhandled riscv64-linux syscall: 258\n--2096-- You may be able to write your own handler.\n--2096-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2096-- Nevertheless we consider this a bug.  Please report\n--2096-- it at http://valgrind.org/support/bug_reports.html.\n--2096-- WARNING: unhandled riscv64-linux syscall: 258\n--2096-- You may be able to write your own handler.\n--2096-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2096-- Nevertheless we consider this a bug.  Please report\n--2096-- it at http://valgrind.org/support/bug_reports.html.\n--2096-- WARNING: unhandled riscv64-linux syscall: 258\n--2096-- You may be able to write your own handler.\n--2096-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2096-- Nevertheless we consider this a bug.  Please report\n--2096-- it at http://valgrind.org/support/bug_reports.html.\n--2096-- WARNING: unhandled riscv64-linux syscall: 258\n--2096-- You may be able to write your own handler.\n--2096-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2096-- Nevertheless we consider this a bug.  Please report\n--2096-- it at http://valgrind.org/support/bug_reports.html.\n--2096-- WARNING: unhandled riscv64-linux syscall: 258\n--2096-- You may be able to write your own handler.\n--2096-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2096-- Nevertheless we consider this a bug.  Please report\n--2096-- it at http://valgrind.org/support/bug_reports.html.\n--2096-- WARNING: unhandled riscv64-linux syscall: 258\n--2096-- You may be able to write your own handler.\n--2096-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2096-- Nevertheless we consider this a bug.  Please report\n--2096-- it at http://valgrind.org/support/bug_reports.html.\n--2096-- WARNING: unhandled riscv64-linux syscall: 258\n--2096-- You may be able to write your own handler.\n--2096-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2096-- Nevertheless we consider this a bug.  Please report\n--2096-- it at http://valgrind.org/support/bug_reports.html.\n--2096-- WARNING: unhandled riscv64-linux syscall: 258\n--2096-- You may be able to write your own handler.\n--2096-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2096-- Nevertheless we consider this a bug.  Please report\n--2096-- 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:
'--2104-- WARNING: unhandled riscv64-linux syscall: 258\n--2104-- You may be able to write your own handler.\n--2104-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2104-- Nevertheless we consider this a bug.  Please report\n--2104-- it at http://valgrind.org/support/bug_reports.html.\n--2104-- WARNING: unhandled riscv64-linux syscall: 258\n--2104-- You may be able to write your own handler.\n--2104-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2104-- Nevertheless we consider this a bug.  Please report\n--2104-- it at http://valgrind.org/support/bug_reports.html.\n--2104-- WARNING: unhandled riscv64-linux syscall: 258\n--2104-- You may be able to write your own handler.\n--2104-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2104-- Nevertheless we consider this a bug.  Please report\n--2104-- it at http://valgrind.org/support/bug_reports.html.\n--2104-- WARNING: unhandled riscv64-linux syscall: 258\n--2104-- You may be able to write your own handler.\n--2104-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2104-- Nevertheless we consider this a bug.  Please report\n--2104-- it at http://valgrind.org/support/bug_reports.html.\n--2104-- WARNING: unhandled riscv64-linux syscall: 258\n--2104-- You may be able to write your own handler.\n--2104-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2104-- Nevertheless we consider this a bug.  Please report\n--2104-- it at http://valgrind.org/support/bug_reports.html.\n--2104-- WARNING: unhandled riscv64-linux syscall: 258\n--2104-- You may be able to write your own handler.\n--2104-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2104-- Nevertheless we consider this a bug.  Please report\n--2104-- it at http://valgrind.org/support/bug_reports.html.\n--2104-- WARNING: unhandled riscv64-linux syscall: 258\n--2104-- You may be able to write your own handler.\n--2104-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2104-- Nevertheless we consider this a bug.  Please report\n--2104-- it at http://valgrind.org/support/bug_reports.html.\n--2104-- WARNING: unhandled riscv64-linux syscall: 258\n--2104-- You may be able to write your own handler.\n--2104-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2104-- Nevertheless we consider this a bug.  Please report\n--2104-- it at http://valgrind.org/support/bug_reports.html.\n--2104-- WARNING: unhandled riscv64-linux syscall: 258\n--2104-- You may be able to write your own handler.\n--2104-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2104-- Nevertheless we consider this a bug.  Please report\n--2104-- it at http://valgrind.org/support/bug_reports.html.\n--2104-- WARNING: unhandled riscv64-linux syscall: 258\n--2104-- You may be able to write your own handler.\n--2104-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2104-- Nevertheless we consider this a bug.  Please report\n--2104-- it at http://valgrind.org/support/bug_reports.html.\n--2104-- WARNING: unhandled riscv64-linux syscall: 258\n--2104-- You may be able to write your own handler.\n--2104-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2104-- Nevertheless we consider this a bug.  Please report\n--2104-- it at http://valgrind.org/support/bug_reports.html.\n--2104-- WARNING: unhandled riscv64-linux syscall: 258\n--2104-- You may be able to write your own handler.\n--2104-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2104-- Nevertheless we consider this a bug.  Please report\n--2104-- it at http://valgrind.org/support/bug_reports.html.\n--2104-- WARNING: unhandled riscv64-linux syscall: 258\n--2104-- You may be able to write your own handler.\n--2104-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2104-- Nevertheless we consider this a bug.  Please report\n--2104-- it at http://valgrind.org/support/bug_reports.html.\n--2104-- WARNING: unhandled riscv64-linux syscall: 258\n--2104-- You may be able to write your own handler.\n--2104-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2104-- Nevertheless we consider this a bug.  Please report\n--2104-- it at http://valgrind.org/support/bug_reports.html.\n--2104-- WARNING: unhandled riscv64-linux syscall: 258\n--2104-- You may be able to write your own handler.\n--2104-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2104-- Nevertheless we consider this a bug.  Please report\n--2104-- it at http://valgrind.org/support/bug_reports.html.\n--2104-- WARNING: unhandled riscv64-linux syscall: 258\n--2104-- You may be able to write your own handler.\n--2104-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2104-- Nevertheless we consider this a bug.  Please report\n--2104-- it at http://valgrind.org/support/bug_reports.html.\n--2104-- WARNING: unhandled riscv64-linux syscall: 258\n--2104-- You may be able to write your own handler.\n--2104-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2104-- Nevertheless we consider this a bug.  Please report\n--2104-- it at http://valgrind.org/support/bug_reports.html.\n--2104-- WARNING: unhandled riscv64-linux syscall: 258\n--2104-- You may be able to write your own handler.\n--2104-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2104-- Nevertheless we consider this a bug.  Please report\n--2104-- 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:
'--2112-- WARNING: unhandled riscv64-linux syscall: 258\n--2112-- You may be able to write your own handler.\n--2112-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2112-- Nevertheless we consider this a bug.  Please report\n--2112-- it at http://valgrind.org/support/bug_reports.html.\n--2112-- WARNING: unhandled riscv64-linux syscall: 258\n--2112-- You may be able to write your own handler.\n--2112-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2112-- Nevertheless we consider this a bug.  Please report\n--2112-- it at http://valgrind.org/support/bug_reports.html.\n--2112-- WARNING: unhandled riscv64-linux syscall: 258\n--2112-- You may be able to write your own handler.\n--2112-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2112-- Nevertheless we consider this a bug.  Please report\n--2112-- it at http://valgrind.org/support/bug_reports.html.\n--2112-- WARNING: unhandled riscv64-linux syscall: 258\n--2112-- You may be able to write your own handler.\n--2112-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2112-- Nevertheless we consider this a bug.  Please report\n--2112-- it at http://valgrind.org/support/bug_reports.html.\n--2112-- WARNING: unhandled riscv64-linux syscall: 258\n--2112-- You may be able to write your own handler.\n--2112-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2112-- Nevertheless we consider this a bug.  Please report\n--2112-- it at http://valgrind.org/support/bug_reports.html.\n--2112-- WARNING: unhandled riscv64-linux syscall: 258\n--2112-- You may be able to write your own handler.\n--2112-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2112-- Nevertheless we consider this a bug.  Please report\n--2112-- it at http://valgrind.org/support/bug_reports.html.\n--2112-- WARNING: unhandled riscv64-linux syscall: 258\n--2112-- You may be able to write your own handler.\n--2112-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2112-- Nevertheless we consider this a bug.  Please report\n--2112-- it at http://valgrind.org/support/bug_reports.html.\n--2112-- WARNING: unhandled riscv64-linux syscall: 258\n--2112-- You may be able to write your own handler.\n--2112-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2112-- Nevertheless we consider this a bug.  Please report\n--2112-- it at http://valgrind.org/support/bug_reports.html.\n--2112-- WARNING: unhandled riscv64-linux syscall: 258\n--2112-- You may be able to write your own handler.\n--2112-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2112-- Nevertheless we consider this a bug.  Please report\n--2112-- it at http://valgrind.org/support/bug_reports.html.\n--2112-- WARNING: unhandled riscv64-linux syscall: 258\n--2112-- You may be able to write your own handler.\n--2112-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2112-- Nevertheless we consider this a bug.  Please report\n--2112-- it at http://valgrind.org/support/bug_reports.html.\n--2112-- WARNING: unhandled riscv64-linux syscall: 258\n--2112-- You may be able to write your own handler.\n--2112-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2112-- Nevertheless we consider this a bug.  Please report\n--2112-- it at http://valgrind.org/support/bug_reports.html.\n--2112-- WARNING: unhandled riscv64-linux syscall: 258\n--2112-- You may be able to write your own handler.\n--2112-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2112-- Nevertheless we consider this a bug.  Please report\n--2112-- it at http://valgrind.org/support/bug_reports.html.\n--2112-- WARNING: unhandled riscv64-linux syscall: 258\n--2112-- You may be able to write your own handler.\n--2112-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2112-- Nevertheless we consider this a bug.  Please report\n--2112-- it at http://valgrind.org/support/bug_reports.html.\n--2112-- WARNING: unhandled riscv64-linux syscall: 258\n--2112-- You may be able to write your own handler.\n--2112-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2112-- Nevertheless we consider this a bug.  Please report\n--2112-- it at http://valgrind.org/support/bug_reports.html.\n--2112-- WARNING: unhandled riscv64-linux syscall: 258\n--2112-- You may be able to write your own handler.\n--2112-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2112-- Nevertheless we consider this a bug.  Please report\n--2112-- it at http://valgrind.org/support/bug_reports.html.\n--2112-- WARNING: unhandled riscv64-linux syscall: 258\n--2112-- You may be able to write your own handler.\n--2112-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2112-- Nevertheless we consider this a bug.  Please report\n--2112-- it at http://valgrind.org/support/bug_reports.html.\n--2112-- WARNING: unhandled riscv64-linux syscall: 258\n--2112-- You may be able to write your own handler.\n--2112-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2112-- Nevertheless we consider this a bug.  Please report\n--2112-- it at http://valgrind.org/support/bug_reports.html.\n--2112-- WARNING: unhandled riscv64-linux syscall: 258\n--2112-- You may be able to write your own handler.\n--2112-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2112-- Nevertheless we consider this a bug.  Please report\n--2112-- 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:
'--2120-- WARNING: unhandled riscv64-linux syscall: 258\n--2120-- You may be able to write your own handler.\n--2120-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2120-- Nevertheless we consider this a bug.  Please report\n--2120-- it at http://valgrind.org/support/bug_reports.html.\n--2120-- WARNING: unhandled riscv64-linux syscall: 258\n--2120-- You may be able to write your own handler.\n--2120-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2120-- Nevertheless we consider this a bug.  Please report\n--2120-- it at http://valgrind.org/support/bug_reports.html.\n--2120-- WARNING: unhandled riscv64-linux syscall: 258\n--2120-- You may be able to write your own handler.\n--2120-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2120-- Nevertheless we consider this a bug.  Please report\n--2120-- it at http://valgrind.org/support/bug_reports.html.\n--2120-- WARNING: unhandled riscv64-linux syscall: 258\n--2120-- You may be able to write your own handler.\n--2120-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2120-- Nevertheless we consider this a bug.  Please report\n--2120-- it at http://valgrind.org/support/bug_reports.html.\n--2120-- WARNING: unhandled riscv64-linux syscall: 258\n--2120-- You may be able to write your own handler.\n--2120-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2120-- Nevertheless we consider this a bug.  Please report\n--2120-- it at http://valgrind.org/support/bug_reports.html.\n--2120-- WARNING: unhandled riscv64-linux syscall: 258\n--2120-- You may be able to write your own handler.\n--2120-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2120-- Nevertheless we consider this a bug.  Please report\n--2120-- it at http://valgrind.org/support/bug_reports.html.\n--2120-- WARNING: unhandled riscv64-linux syscall: 258\n--2120-- You may be able to write your own handler.\n--2120-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2120-- Nevertheless we consider this a bug.  Please report\n--2120-- it at http://valgrind.org/support/bug_reports.html.\n--2120-- WARNING: unhandled riscv64-linux syscall: 258\n--2120-- You may be able to write your own handler.\n--2120-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2120-- Nevertheless we consider this a bug.  Please report\n--2120-- it at http://valgrind.org/support/bug_reports.html.\n--2120-- WARNING: unhandled riscv64-linux syscall: 258\n--2120-- You may be able to write your own handler.\n--2120-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2120-- Nevertheless we consider this a bug.  Please report\n--2120-- it at http://valgrind.org/support/bug_reports.html.\n--2120-- WARNING: unhandled riscv64-linux syscall: 258\n--2120-- You may be able to write your own handler.\n--2120-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2120-- Nevertheless we consider this a bug.  Please report\n--2120-- it at http://valgrind.org/support/bug_reports.html.\n--2120-- WARNING: unhandled riscv64-linux syscall: 258\n--2120-- You may be able to write your own handler.\n--2120-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2120-- Nevertheless we consider this a bug.  Please report\n--2120-- it at http://valgrind.org/support/bug_reports.html.\n--2120-- WARNING: unhandled riscv64-linux syscall: 258\n--2120-- You may be able to write your own handler.\n--2120-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2120-- Nevertheless we consider this a bug.  Please report\n--2120-- it at http://valgrind.org/support/bug_reports.html.\n--2120-- WARNING: unhandled riscv64-linux syscall: 258\n--2120-- You may be able to write your own handler.\n--2120-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2120-- Nevertheless we consider this a bug.  Please report\n--2120-- it at http://valgrind.org/support/bug_reports.html.\n--2120-- WARNING: unhandled riscv64-linux syscall: 258\n--2120-- You may be able to write your own handler.\n--2120-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2120-- Nevertheless we consider this a bug.  Please report\n--2120-- it at http://valgrind.org/support/bug_reports.html.\n--2120-- WARNING: unhandled riscv64-linux syscall: 258\n--2120-- You may be able to write your own handler.\n--2120-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2120-- Nevertheless we consider this a bug.  Please report\n--2120-- it at http://valgrind.org/support/bug_reports.html.\n--2120-- WARNING: unhandled riscv64-linux syscall: 258\n--2120-- You may be able to write your own handler.\n--2120-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2120-- Nevertheless we consider this a bug.  Please report\n--2120-- it at http://valgrind.org/support/bug_reports.html.\n--2120-- WARNING: unhandled riscv64-linux syscall: 258\n--2120-- You may be able to write your own handler.\n--2120-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2120-- Nevertheless we consider this a bug.  Please report\n--2120-- it at http://valgrind.org/support/bug_reports.html.\n--2120-- WARNING: unhandled riscv64-linux syscall: 258\n--2120-- You may be able to write your own handler.\n--2120-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2120-- Nevertheless we consider this a bug.  Please report\n--2120-- 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:
'--2128-- WARNING: unhandled riscv64-linux syscall: 258\n--2128-- You may be able to write your own handler.\n--2128-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2128-- Nevertheless we consider this a bug.  Please report\n--2128-- it at http://valgrind.org/support/bug_reports.html.\n--2128-- WARNING: unhandled riscv64-linux syscall: 258\n--2128-- You may be able to write your own handler.\n--2128-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2128-- Nevertheless we consider this a bug.  Please report\n--2128-- it at http://valgrind.org/support/bug_reports.html.\n--2128-- WARNING: unhandled riscv64-linux syscall: 258\n--2128-- You may be able to write your own handler.\n--2128-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2128-- Nevertheless we consider this a bug.  Please report\n--2128-- it at http://valgrind.org/support/bug_reports.html.\n--2128-- WARNING: unhandled riscv64-linux syscall: 258\n--2128-- You may be able to write your own handler.\n--2128-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2128-- Nevertheless we consider this a bug.  Please report\n--2128-- it at http://valgrind.org/support/bug_reports.html.\n--2128-- WARNING: unhandled riscv64-linux syscall: 258\n--2128-- You may be able to write your own handler.\n--2128-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2128-- Nevertheless we consider this a bug.  Please report\n--2128-- it at http://valgrind.org/support/bug_reports.html.\n--2128-- WARNING: unhandled riscv64-linux syscall: 258\n--2128-- You may be able to write your own handler.\n--2128-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2128-- Nevertheless we consider this a bug.  Please report\n--2128-- it at http://valgrind.org/support/bug_reports.html.\n--2128-- WARNING: unhandled riscv64-linux syscall: 258\n--2128-- You may be able to write your own handler.\n--2128-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2128-- Nevertheless we consider this a bug.  Please report\n--2128-- it at http://valgrind.org/support/bug_reports.html.\n--2128-- WARNING: unhandled riscv64-linux syscall: 258\n--2128-- You may be able to write your own handler.\n--2128-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2128-- Nevertheless we consider this a bug.  Please report\n--2128-- it at http://valgrind.org/support/bug_reports.html.\n--2128-- WARNING: unhandled riscv64-linux syscall: 258\n--2128-- You may be able to write your own handler.\n--2128-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2128-- Nevertheless we consider this a bug.  Please report\n--2128-- it at http://valgrind.org/support/bug_reports.html.\n--2128-- WARNING: unhandled riscv64-linux syscall: 258\n--2128-- You may be able to write your own handler.\n--2128-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2128-- Nevertheless we consider this a bug.  Please report\n--2128-- it at http://valgrind.org/support/bug_reports.html.\n--2128-- WARNING: unhandled riscv64-linux syscall: 258\n--2128-- You may be able to write your own handler.\n--2128-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2128-- Nevertheless we consider this a bug.  Please report\n--2128-- it at http://valgrind.org/support/bug_reports.html.\n--2128-- WARNING: unhandled riscv64-linux syscall: 258\n--2128-- You may be able to write your own handler.\n--2128-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2128-- Nevertheless we consider this a bug.  Please report\n--2128-- it at http://valgrind.org/support/bug_reports.html.\n--2128-- WARNING: unhandled riscv64-linux syscall: 258\n--2128-- You may be able to write your own handler.\n--2128-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2128-- Nevertheless we consider this a bug.  Please report\n--2128-- it at http://valgrind.org/support/bug_reports.html.\n--2128-- WARNING: unhandled riscv64-linux syscall: 258\n--2128-- You may be able to write your own handler.\n--2128-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2128-- Nevertheless we consider this a bug.  Please report\n--2128-- it at http://valgrind.org/support/bug_reports.html.\n--2128-- WARNING: unhandled riscv64-linux syscall: 258\n--2128-- You may be able to write your own handler.\n--2128-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2128-- Nevertheless we consider this a bug.  Please report\n--2128-- it at http://valgrind.org/support/bug_reports.html.\n--2128-- WARNING: unhandled riscv64-linux syscall: 258\n--2128-- You may be able to write your own handler.\n--2128-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2128-- Nevertheless we consider this a bug.  Please report\n--2128-- it at http://valgrind.org/support/bug_reports.html.\n--2128-- WARNING: unhandled riscv64-linux syscall: 258\n--2128-- You may be able to write your own handler.\n--2128-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2128-- Nevertheless we consider this a bug.  Please report\n--2128-- it at http://valgrind.org/support/bug_reports.html.\n--2128-- WARNING: unhandled riscv64-linux syscall: 258\n--2128-- You may be able to write your own handler.\n--2128-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2128-- Nevertheless we consider this a bug.  Please report\n--2128-- 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:
'--2144-- WARNING: unhandled riscv64-linux syscall: 258\n--2144-- You may be able to write your own handler.\n--2144-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2144-- Nevertheless we consider this a bug.  Please report\n--2144-- it at http://valgrind.org/support/bug_reports.html.\n--2144-- WARNING: unhandled riscv64-linux syscall: 258\n--2144-- You may be able to write your own handler.\n--2144-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2144-- Nevertheless we consider this a bug.  Please report\n--2144-- it at http://valgrind.org/support/bug_reports.html.\n--2144-- WARNING: unhandled riscv64-linux syscall: 258\n--2144-- You may be able to write your own handler.\n--2144-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2144-- Nevertheless we consider this a bug.  Please report\n--2144-- it at http://valgrind.org/support/bug_reports.html.\n--2144-- WARNING: unhandled riscv64-linux syscall: 258\n--2144-- You may be able to write your own handler.\n--2144-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2144-- Nevertheless we consider this a bug.  Please report\n--2144-- it at http://valgrind.org/support/bug_reports.html.\n--2144-- WARNING: unhandled riscv64-linux syscall: 258\n--2144-- You may be able to write your own handler.\n--2144-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2144-- Nevertheless we consider this a bug.  Please report\n--2144-- it at http://valgrind.org/support/bug_reports.html.\n--2144-- WARNING: unhandled riscv64-linux syscall: 258\n--2144-- You may be able to write your own handler.\n--2144-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2144-- Nevertheless we consider this a bug.  Please report\n--2144-- it at http://valgrind.org/support/bug_reports.html.\n--2144-- WARNING: unhandled riscv64-linux syscall: 258\n--2144-- You may be able to write your own handler.\n--2144-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2144-- Nevertheless we consider this a bug.  Please report\n--2144-- it at http://valgrind.org/support/bug_reports.html.\n--2144-- WARNING: unhandled riscv64-linux syscall: 258\n--2144-- You may be able to write your own handler.\n--2144-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2144-- Nevertheless we consider this a bug.  Please report\n--2144-- it at http://valgrind.org/support/bug_reports.html.\n--2144-- WARNING: unhandled riscv64-linux syscall: 258\n--2144-- You may be able to write your own handler.\n--2144-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2144-- Nevertheless we consider this a bug.  Please report\n--2144-- it at http://valgrind.org/support/bug_reports.html.\n--2144-- WARNING: unhandled riscv64-linux syscall: 258\n--2144-- You may be able to write your own handler.\n--2144-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2144-- Nevertheless we consider this a bug.  Please report\n--2144-- it at http://valgrind.org/support/bug_reports.html.\n--2144-- WARNING: unhandled riscv64-linux syscall: 258\n--2144-- You may be able to write your own handler.\n--2144-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2144-- Nevertheless we consider this a bug.  Please report\n--2144-- it at http://valgrind.org/support/bug_reports.html.\n--2144-- WARNING: unhandled riscv64-linux syscall: 258\n--2144-- You may be able to write your own handler.\n--2144-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2144-- Nevertheless we consider this a bug.  Please report\n--2144-- it at http://valgrind.org/support/bug_reports.html.\n--2144-- WARNING: unhandled riscv64-linux syscall: 258\n--2144-- You may be able to write your own handler.\n--2144-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2144-- Nevertheless we consider this a bug.  Please report\n--2144-- it at http://valgrind.org/support/bug_reports.html.\n--2144-- WARNING: unhandled riscv64-linux syscall: 258\n--2144-- You may be able to write your own handler.\n--2144-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2144-- Nevertheless we consider this a bug.  Please report\n--2144-- it at http://valgrind.org/support/bug_reports.html.\n--2144-- WARNING: unhandled riscv64-linux syscall: 258\n--2144-- You may be able to write your own handler.\n--2144-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2144-- Nevertheless we consider this a bug.  Please report\n--2144-- it at http://valgrind.org/support/bug_reports.html.\n--2144-- WARNING: unhandled riscv64-linux syscall: 258\n--2144-- You may be able to write your own handler.\n--2144-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2144-- Nevertheless we consider this a bug.  Please report\n--2144-- it at http://valgrind.org/support/bug_reports.html.\n--2144-- WARNING: unhandled riscv64-linux syscall: 258\n--2144-- You may be able to write your own handler.\n--2144-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2144-- Nevertheless we consider this a bug.  Please report\n--2144-- it at http://valgrind.org/support/bug_reports.html.\n--2144-- WARNING: unhandled riscv64-linux syscall: 258\n--2144-- You may be able to write your own handler.\n--2144-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2144-- Nevertheless we consider this a bug.  Please report\n--2144-- 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:
'--2152-- WARNING: unhandled riscv64-linux syscall: 258\n--2152-- You may be able to write your own handler.\n--2152-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2152-- Nevertheless we consider this a bug.  Please report\n--2152-- it at http://valgrind.org/support/bug_reports.html.\n--2152-- WARNING: unhandled riscv64-linux syscall: 258\n--2152-- You may be able to write your own handler.\n--2152-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2152-- Nevertheless we consider this a bug.  Please report\n--2152-- it at http://valgrind.org/support/bug_reports.html.\n--2152-- WARNING: unhandled riscv64-linux syscall: 258\n--2152-- You may be able to write your own handler.\n--2152-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2152-- Nevertheless we consider this a bug.  Please report\n--2152-- it at http://valgrind.org/support/bug_reports.html.\n--2152-- WARNING: unhandled riscv64-linux syscall: 258\n--2152-- You may be able to write your own handler.\n--2152-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2152-- Nevertheless we consider this a bug.  Please report\n--2152-- it at http://valgrind.org/support/bug_reports.html.\n--2152-- WARNING: unhandled riscv64-linux syscall: 258\n--2152-- You may be able to write your own handler.\n--2152-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2152-- Nevertheless we consider this a bug.  Please report\n--2152-- it at http://valgrind.org/support/bug_reports.html.\n--2152-- WARNING: unhandled riscv64-linux syscall: 258\n--2152-- You may be able to write your own handler.\n--2152-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2152-- Nevertheless we consider this a bug.  Please report\n--2152-- it at http://valgrind.org/support/bug_reports.html.\n--2152-- WARNING: unhandled riscv64-linux syscall: 258\n--2152-- You may be able to write your own handler.\n--2152-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2152-- Nevertheless we consider this a bug.  Please report\n--2152-- it at http://valgrind.org/support/bug_reports.html.\n--2152-- WARNING: unhandled riscv64-linux syscall: 258\n--2152-- You may be able to write your own handler.\n--2152-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2152-- Nevertheless we consider this a bug.  Please report\n--2152-- it at http://valgrind.org/support/bug_reports.html.\n--2152-- WARNING: unhandled riscv64-linux syscall: 258\n--2152-- You may be able to write your own handler.\n--2152-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2152-- Nevertheless we consider this a bug.  Please report\n--2152-- it at http://valgrind.org/support/bug_reports.html.\n--2152-- WARNING: unhandled riscv64-linux syscall: 258\n--2152-- You may be able to write your own handler.\n--2152-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2152-- Nevertheless we consider this a bug.  Please report\n--2152-- it at http://valgrind.org/support/bug_reports.html.\n--2152-- WARNING: unhandled riscv64-linux syscall: 258\n--2152-- You may be able to write your own handler.\n--2152-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2152-- Nevertheless we consider this a bug.  Please report\n--2152-- it at http://valgrind.org/support/bug_reports.html.\n--2152-- WARNING: unhandled riscv64-linux syscall: 258\n--2152-- You may be able to write your own handler.\n--2152-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2152-- Nevertheless we consider this a bug.  Please report\n--2152-- it at http://valgrind.org/support/bug_reports.html.\n--2152-- WARNING: unhandled riscv64-linux syscall: 258\n--2152-- You may be able to write your own handler.\n--2152-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2152-- Nevertheless we consider this a bug.  Please report\n--2152-- it at http://valgrind.org/support/bug_reports.html.\n--2152-- WARNING: unhandled riscv64-linux syscall: 258\n--2152-- You may be able to write your own handler.\n--2152-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2152-- Nevertheless we consider this a bug.  Please report\n--2152-- it at http://valgrind.org/support/bug_reports.html.\n--2152-- WARNING: unhandled riscv64-linux syscall: 258\n--2152-- You may be able to write your own handler.\n--2152-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2152-- Nevertheless we consider this a bug.  Please report\n--2152-- it at http://valgrind.org/support/bug_reports.html.\n--2152-- WARNING: unhandled riscv64-linux syscall: 258\n--2152-- You may be able to write your own handler.\n--2152-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2152-- Nevertheless we consider this a bug.  Please report\n--2152-- it at http://valgrind.org/support/bug_reports.html.\n--2152-- WARNING: unhandled riscv64-linux syscall: 258\n--2152-- You may be able to write your own handler.\n--2152-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2152-- Nevertheless we consider this a bug.  Please report\n--2152-- it at http://valgrind.org/support/bug_reports.html.\n--2152-- WARNING: unhandled riscv64-linux syscall: 258\n--2152-- You may be able to write your own handler.\n--2152-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2152-- Nevertheless we consider this a bug.  Please report\n--2152-- 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:
'--2160-- WARNING: unhandled riscv64-linux syscall: 258\n--2160-- You may be able to write your own handler.\n--2160-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2160-- Nevertheless we consider this a bug.  Please report\n--2160-- it at http://valgrind.org/support/bug_reports.html.\n--2160-- WARNING: unhandled riscv64-linux syscall: 258\n--2160-- You may be able to write your own handler.\n--2160-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2160-- Nevertheless we consider this a bug.  Please report\n--2160-- it at http://valgrind.org/support/bug_reports.html.\n--2160-- WARNING: unhandled riscv64-linux syscall: 258\n--2160-- You may be able to write your own handler.\n--2160-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2160-- Nevertheless we consider this a bug.  Please report\n--2160-- it at http://valgrind.org/support/bug_reports.html.\n--2160-- WARNING: unhandled riscv64-linux syscall: 258\n--2160-- You may be able to write your own handler.\n--2160-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2160-- Nevertheless we consider this a bug.  Please report\n--2160-- it at http://valgrind.org/support/bug_reports.html.\n--2160-- WARNING: unhandled riscv64-linux syscall: 258\n--2160-- You may be able to write your own handler.\n--2160-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2160-- Nevertheless we consider this a bug.  Please report\n--2160-- it at http://valgrind.org/support/bug_reports.html.\n--2160-- WARNING: unhandled riscv64-linux syscall: 258\n--2160-- You may be able to write your own handler.\n--2160-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2160-- Nevertheless we consider this a bug.  Please report\n--2160-- it at http://valgrind.org/support/bug_reports.html.\n--2160-- WARNING: unhandled riscv64-linux syscall: 258\n--2160-- You may be able to write your own handler.\n--2160-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2160-- Nevertheless we consider this a bug.  Please report\n--2160-- it at http://valgrind.org/support/bug_reports.html.\n--2160-- WARNING: unhandled riscv64-linux syscall: 258\n--2160-- You may be able to write your own handler.\n--2160-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2160-- Nevertheless we consider this a bug.  Please report\n--2160-- it at http://valgrind.org/support/bug_reports.html.\n--2160-- WARNING: unhandled riscv64-linux syscall: 258\n--2160-- You may be able to write your own handler.\n--2160-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2160-- Nevertheless we consider this a bug.  Please report\n--2160-- it at http://valgrind.org/support/bug_reports.html.\n--2160-- WARNING: unhandled riscv64-linux syscall: 258\n--2160-- You may be able to write your own handler.\n--2160-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2160-- Nevertheless we consider this a bug.  Please report\n--2160-- it at http://valgrind.org/support/bug_reports.html.\n--2160-- WARNING: unhandled riscv64-linux syscall: 258\n--2160-- You may be able to write your own handler.\n--2160-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2160-- Nevertheless we consider this a bug.  Please report\n--2160-- it at http://valgrind.org/support/bug_reports.html.\n--2160-- WARNING: unhandled riscv64-linux syscall: 258\n--2160-- You may be able to write your own handler.\n--2160-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2160-- Nevertheless we consider this a bug.  Please report\n--2160-- it at http://valgrind.org/support/bug_reports.html.\n--2160-- WARNING: unhandled riscv64-linux syscall: 258\n--2160-- You may be able to write your own handler.\n--2160-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2160-- Nevertheless we consider this a bug.  Please report\n--2160-- it at http://valgrind.org/support/bug_reports.html.\n--2160-- WARNING: unhandled riscv64-linux syscall: 258\n--2160-- You may be able to write your own handler.\n--2160-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2160-- Nevertheless we consider this a bug.  Please report\n--2160-- it at http://valgrind.org/support/bug_reports.html.\n--2160-- WARNING: unhandled riscv64-linux syscall: 258\n--2160-- You may be able to write your own handler.\n--2160-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2160-- Nevertheless we consider this a bug.  Please report\n--2160-- it at http://valgrind.org/support/bug_reports.html.\n--2160-- WARNING: unhandled riscv64-linux syscall: 258\n--2160-- You may be able to write your own handler.\n--2160-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2160-- Nevertheless we consider this a bug.  Please report\n--2160-- it at http://valgrind.org/support/bug_reports.html.\n--2160-- WARNING: unhandled riscv64-linux syscall: 258\n--2160-- You may be able to write your own handler.\n--2160-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2160-- Nevertheless we consider this a bug.  Please report\n--2160-- it at http://valgrind.org/support/bug_reports.html.\n--2160-- WARNING: unhandled riscv64-linux syscall: 258\n--2160-- You may be able to write your own handler.\n--2160-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2160-- Nevertheless we consider this a bug.  Please report\n--2160-- 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:
'--2168-- WARNING: unhandled riscv64-linux syscall: 258\n--2168-- You may be able to write your own handler.\n--2168-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2168-- Nevertheless we consider this a bug.  Please report\n--2168-- it at http://valgrind.org/support/bug_reports.html.\n--2168-- WARNING: unhandled riscv64-linux syscall: 258\n--2168-- You may be able to write your own handler.\n--2168-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2168-- Nevertheless we consider this a bug.  Please report\n--2168-- it at http://valgrind.org/support/bug_reports.html.\n--2168-- WARNING: unhandled riscv64-linux syscall: 258\n--2168-- You may be able to write your own handler.\n--2168-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2168-- Nevertheless we consider this a bug.  Please report\n--2168-- it at http://valgrind.org/support/bug_reports.html.\n--2168-- WARNING: unhandled riscv64-linux syscall: 258\n--2168-- You may be able to write your own handler.\n--2168-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2168-- Nevertheless we consider this a bug.  Please report\n--2168-- it at http://valgrind.org/support/bug_reports.html.\n--2168-- WARNING: unhandled riscv64-linux syscall: 258\n--2168-- You may be able to write your own handler.\n--2168-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2168-- Nevertheless we consider this a bug.  Please report\n--2168-- it at http://valgrind.org/support/bug_reports.html.\n--2168-- WARNING: unhandled riscv64-linux syscall: 258\n--2168-- You may be able to write your own handler.\n--2168-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2168-- Nevertheless we consider this a bug.  Please report\n--2168-- it at http://valgrind.org/support/bug_reports.html.\n--2168-- WARNING: unhandled riscv64-linux syscall: 258\n--2168-- You may be able to write your own handler.\n--2168-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2168-- Nevertheless we consider this a bug.  Please report\n--2168-- it at http://valgrind.org/support/bug_reports.html.\n--2168-- WARNING: unhandled riscv64-linux syscall: 258\n--2168-- You may be able to write your own handler.\n--2168-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2168-- Nevertheless we consider this a bug.  Please report\n--2168-- it at http://valgrind.org/support/bug_reports.html.\n--2168-- WARNING: unhandled riscv64-linux syscall: 258\n--2168-- You may be able to write your own handler.\n--2168-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2168-- Nevertheless we consider this a bug.  Please report\n--2168-- it at http://valgrind.org/support/bug_reports.html.\n--2168-- WARNING: unhandled riscv64-linux syscall: 258\n--2168-- You may be able to write your own handler.\n--2168-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2168-- Nevertheless we consider this a bug.  Please report\n--2168-- it at http://valgrind.org/support/bug_reports.html.\n--2168-- WARNING: unhandled riscv64-linux syscall: 258\n--2168-- You may be able to write your own handler.\n--2168-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2168-- Nevertheless we consider this a bug.  Please report\n--2168-- it at http://valgrind.org/support/bug_reports.html.\n--2168-- WARNING: unhandled riscv64-linux syscall: 258\n--2168-- You may be able to write your own handler.\n--2168-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2168-- Nevertheless we consider this a bug.  Please report\n--2168-- it at http://valgrind.org/support/bug_reports.html.\n--2168-- WARNING: unhandled riscv64-linux syscall: 258\n--2168-- You may be able to write your own handler.\n--2168-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2168-- Nevertheless we consider this a bug.  Please report\n--2168-- it at http://valgrind.org/support/bug_reports.html.\n--2168-- WARNING: unhandled riscv64-linux syscall: 258\n--2168-- You may be able to write your own handler.\n--2168-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2168-- Nevertheless we consider this a bug.  Please report\n--2168-- it at http://valgrind.org/support/bug_reports.html.\n--2168-- WARNING: unhandled riscv64-linux syscall: 258\n--2168-- You may be able to write your own handler.\n--2168-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2168-- Nevertheless we consider this a bug.  Please report\n--2168-- it at http://valgrind.org/support/bug_reports.html.\n--2168-- WARNING: unhandled riscv64-linux syscall: 258\n--2168-- You may be able to write your own handler.\n--2168-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2168-- Nevertheless we consider this a bug.  Please report\n--2168-- it at http://valgrind.org/support/bug_reports.html.\n--2168-- WARNING: unhandled riscv64-linux syscall: 258\n--2168-- You may be able to write your own handler.\n--2168-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2168-- Nevertheless we consider this a bug.  Please report\n--2168-- it at http://valgrind.org/support/bug_reports.html.\n--2168-- WARNING: unhandled riscv64-linux syscall: 258\n--2168-- You may be able to write your own handler.\n--2168-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2168-- Nevertheless we consider this a bug.  Please report\n--2168-- 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:
'--2176-- WARNING: unhandled riscv64-linux syscall: 258\n--2176-- You may be able to write your own handler.\n--2176-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2176-- Nevertheless we consider this a bug.  Please report\n--2176-- it at http://valgrind.org/support/bug_reports.html.\n--2176-- WARNING: unhandled riscv64-linux syscall: 258\n--2176-- You may be able to write your own handler.\n--2176-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2176-- Nevertheless we consider this a bug.  Please report\n--2176-- it at http://valgrind.org/support/bug_reports.html.\n--2176-- WARNING: unhandled riscv64-linux syscall: 258\n--2176-- You may be able to write your own handler.\n--2176-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2176-- Nevertheless we consider this a bug.  Please report\n--2176-- it at http://valgrind.org/support/bug_reports.html.\n--2176-- WARNING: unhandled riscv64-linux syscall: 258\n--2176-- You may be able to write your own handler.\n--2176-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2176-- Nevertheless we consider this a bug.  Please report\n--2176-- it at http://valgrind.org/support/bug_reports.html.\n--2176-- WARNING: unhandled riscv64-linux syscall: 258\n--2176-- You may be able to write your own handler.\n--2176-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2176-- Nevertheless we consider this a bug.  Please report\n--2176-- it at http://valgrind.org/support/bug_reports.html.\n--2176-- WARNING: unhandled riscv64-linux syscall: 258\n--2176-- You may be able to write your own handler.\n--2176-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2176-- Nevertheless we consider this a bug.  Please report\n--2176-- it at http://valgrind.org/support/bug_reports.html.\n--2176-- WARNING: unhandled riscv64-linux syscall: 258\n--2176-- You may be able to write your own handler.\n--2176-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2176-- Nevertheless we consider this a bug.  Please report\n--2176-- it at http://valgrind.org/support/bug_reports.html.\n--2176-- WARNING: unhandled riscv64-linux syscall: 258\n--2176-- You may be able to write your own handler.\n--2176-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2176-- Nevertheless we consider this a bug.  Please report\n--2176-- it at http://valgrind.org/support/bug_reports.html.\n--2176-- WARNING: unhandled riscv64-linux syscall: 258\n--2176-- You may be able to write your own handler.\n--2176-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2176-- Nevertheless we consider this a bug.  Please report\n--2176-- it at http://valgrind.org/support/bug_reports.html.\n--2176-- WARNING: unhandled riscv64-linux syscall: 258\n--2176-- You may be able to write your own handler.\n--2176-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2176-- Nevertheless we consider this a bug.  Please report\n--2176-- it at http://valgrind.org/support/bug_reports.html.\n--2176-- WARNING: unhandled riscv64-linux syscall: 258\n--2176-- You may be able to write your own handler.\n--2176-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2176-- Nevertheless we consider this a bug.  Please report\n--2176-- it at http://valgrind.org/support/bug_reports.html.\n--2176-- WARNING: unhandled riscv64-linux syscall: 258\n--2176-- You may be able to write your own handler.\n--2176-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2176-- Nevertheless we consider this a bug.  Please report\n--2176-- it at http://valgrind.org/support/bug_reports.html.\n--2176-- WARNING: unhandled riscv64-linux syscall: 258\n--2176-- You may be able to write your own handler.\n--2176-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2176-- Nevertheless we consider this a bug.  Please report\n--2176-- it at http://valgrind.org/support/bug_reports.html.\n--2176-- WARNING: unhandled riscv64-linux syscall: 258\n--2176-- You may be able to write your own handler.\n--2176-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2176-- Nevertheless we consider this a bug.  Please report\n--2176-- it at http://valgrind.org/support/bug_reports.html.\n--2176-- WARNING: unhandled riscv64-linux syscall: 258\n--2176-- You may be able to write your own handler.\n--2176-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2176-- Nevertheless we consider this a bug.  Please report\n--2176-- it at http://valgrind.org/support/bug_reports.html.\n--2176-- WARNING: unhandled riscv64-linux syscall: 258\n--2176-- You may be able to write your own handler.\n--2176-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2176-- Nevertheless we consider this a bug.  Please report\n--2176-- it at http://valgrind.org/support/bug_reports.html.\n--2176-- WARNING: unhandled riscv64-linux syscall: 258\n--2176-- You may be able to write your own handler.\n--2176-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2176-- Nevertheless we consider this a bug.  Please report\n--2176-- it at http://valgrind.org/support/bug_reports.html.\n--2176-- WARNING: unhandled riscv64-linux syscall: 258\n--2176-- You may be able to write your own handler.\n--2176-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2176-- Nevertheless we consider this a bug.  Please report\n--2176-- 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:
'--2185-- WARNING: unhandled riscv64-linux syscall: 258\n--2185-- You may be able to write your own handler.\n--2185-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2185-- Nevertheless we consider this a bug.  Please report\n--2185-- it at http://valgrind.org/support/bug_reports.html.\n--2185-- WARNING: unhandled riscv64-linux syscall: 258\n--2185-- You may be able to write your own handler.\n--2185-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2185-- Nevertheless we consider this a bug.  Please report\n--2185-- it at http://valgrind.org/support/bug_reports.html.\n--2185-- WARNING: unhandled riscv64-linux syscall: 258\n--2185-- You may be able to write your own handler.\n--2185-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2185-- Nevertheless we consider this a bug.  Please report\n--2185-- it at http://valgrind.org/support/bug_reports.html.\n--2185-- WARNING: unhandled riscv64-linux syscall: 258\n--2185-- You may be able to write your own handler.\n--2185-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2185-- Nevertheless we consider this a bug.  Please report\n--2185-- it at http://valgrind.org/support/bug_reports.html.\n--2185-- WARNING: unhandled riscv64-linux syscall: 258\n--2185-- You may be able to write your own handler.\n--2185-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2185-- Nevertheless we consider this a bug.  Please report\n--2185-- it at http://valgrind.org/support/bug_reports.html.\n--2185-- WARNING: unhandled riscv64-linux syscall: 258\n--2185-- You may be able to write your own handler.\n--2185-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2185-- Nevertheless we consider this a bug.  Please report\n--2185-- it at http://valgrind.org/support/bug_reports.html.\n--2185-- WARNING: unhandled riscv64-linux syscall: 258\n--2185-- You may be able to write your own handler.\n--2185-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2185-- Nevertheless we consider this a bug.  Please report\n--2185-- it at http://valgrind.org/support/bug_reports.html.\n--2185-- WARNING: unhandled riscv64-linux syscall: 258\n--2185-- You may be able to write your own handler.\n--2185-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2185-- Nevertheless we consider this a bug.  Please report\n--2185-- it at http://valgrind.org/support/bug_reports.html.\n--2185-- WARNING: unhandled riscv64-linux syscall: 258\n--2185-- You may be able to write your own handler.\n--2185-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2185-- Nevertheless we consider this a bug.  Please report\n--2185-- it at http://valgrind.org/support/bug_reports.html.\n--2185-- WARNING: unhandled riscv64-linux syscall: 258\n--2185-- You may be able to write your own handler.\n--2185-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2185-- Nevertheless we consider this a bug.  Please report\n--2185-- it at http://valgrind.org/support/bug_reports.html.\n--2185-- WARNING: unhandled riscv64-linux syscall: 258\n--2185-- You may be able to write your own handler.\n--2185-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2185-- Nevertheless we consider this a bug.  Please report\n--2185-- it at http://valgrind.org/support/bug_reports.html.\n--2185-- WARNING: unhandled riscv64-linux syscall: 258\n--2185-- You may be able to write your own handler.\n--2185-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2185-- Nevertheless we consider this a bug.  Please report\n--2185-- it at http://valgrind.org/support/bug_reports.html.\n--2185-- WARNING: unhandled riscv64-linux syscall: 258\n--2185-- You may be able to write your own handler.\n--2185-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2185-- Nevertheless we consider this a bug.  Please report\n--2185-- it at http://valgrind.org/support/bug_reports.html.\n--2185-- WARNING: unhandled riscv64-linux syscall: 258\n--2185-- You may be able to write your own handler.\n--2185-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2185-- Nevertheless we consider this a bug.  Please report\n--2185-- it at http://valgrind.org/support/bug_reports.html.\n--2185-- WARNING: unhandled riscv64-linux syscall: 258\n--2185-- You may be able to write your own handler.\n--2185-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2185-- Nevertheless we consider this a bug.  Please report\n--2185-- it at http://valgrind.org/support/bug_reports.html.\n--2185-- WARNING: unhandled riscv64-linux syscall: 258\n--2185-- You may be able to write your own handler.\n--2185-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2185-- Nevertheless we consider this a bug.  Please report\n--2185-- it at http://valgrind.org/support/bug_reports.html.\n--2185-- WARNING: unhandled riscv64-linux syscall: 258\n--2185-- You may be able to write your own handler.\n--2185-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2185-- Nevertheless we consider this a bug.  Please report\n--2185-- it at http://valgrind.org/support/bug_reports.html.\n--2185-- WARNING: unhandled riscv64-linux syscall: 258\n--2185-- You may be able to write your own handler.\n--2185-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2185-- Nevertheless we consider this a bug.  Please report\n--2185-- 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:
'--2198-- WARNING: unhandled riscv64-linux syscall: 258\n--2198-- You may be able to write your own handler.\n--2198-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2198-- Nevertheless we consider this a bug.  Please report\n--2198-- it at http://valgrind.org/support/bug_reports.html.\n--2198-- WARNING: unhandled riscv64-linux syscall: 258\n--2198-- You may be able to write your own handler.\n--2198-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2198-- Nevertheless we consider this a bug.  Please report\n--2198-- it at http://valgrind.org/support/bug_reports.html.\n--2198-- WARNING: unhandled riscv64-linux syscall: 258\n--2198-- You may be able to write your own handler.\n--2198-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2198-- Nevertheless we consider this a bug.  Please report\n--2198-- it at http://valgrind.org/support/bug_reports.html.\n--2198-- WARNING: unhandled riscv64-linux syscall: 258\n--2198-- You may be able to write your own handler.\n--2198-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2198-- Nevertheless we consider this a bug.  Please report\n--2198-- it at http://valgrind.org/support/bug_reports.html.\n--2198-- WARNING: unhandled riscv64-linux syscall: 258\n--2198-- You may be able to write your own handler.\n--2198-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2198-- Nevertheless we consider this a bug.  Please report\n--2198-- it at http://valgrind.org/support/bug_reports.html.\n--2198-- WARNING: unhandled riscv64-linux syscall: 258\n--2198-- You may be able to write your own handler.\n--2198-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2198-- Nevertheless we consider this a bug.  Please report\n--2198-- it at http://valgrind.org/support/bug_reports.html.\n--2198-- WARNING: unhandled riscv64-linux syscall: 258\n--2198-- You may be able to write your own handler.\n--2198-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2198-- Nevertheless we consider this a bug.  Please report\n--2198-- it at http://valgrind.org/support/bug_reports.html.\n--2198-- WARNING: unhandled riscv64-linux syscall: 258\n--2198-- You may be able to write your own handler.\n--2198-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2198-- Nevertheless we consider this a bug.  Please report\n--2198-- it at http://valgrind.org/support/bug_reports.html.\n--2198-- WARNING: unhandled riscv64-linux syscall: 258\n--2198-- You may be able to write your own handler.\n--2198-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2198-- Nevertheless we consider this a bug.  Please report\n--2198-- it at http://valgrind.org/support/bug_reports.html.\n--2198-- WARNING: unhandled riscv64-linux syscall: 258\n--2198-- You may be able to write your own handler.\n--2198-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2198-- Nevertheless we consider this a bug.  Please report\n--2198-- it at http://valgrind.org/support/bug_reports.html.\n--2198-- WARNING: unhandled riscv64-linux syscall: 258\n--2198-- You may be able to write your own handler.\n--2198-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2198-- Nevertheless we consider this a bug.  Please report\n--2198-- it at http://valgrind.org/support/bug_reports.html.\n--2198-- WARNING: unhandled riscv64-linux syscall: 258\n--2198-- You may be able to write your own handler.\n--2198-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2198-- Nevertheless we consider this a bug.  Please report\n--2198-- it at http://valgrind.org/support/bug_reports.html.\n--2198-- WARNING: unhandled riscv64-linux syscall: 258\n--2198-- You may be able to write your own handler.\n--2198-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2198-- Nevertheless we consider this a bug.  Please report\n--2198-- it at http://valgrind.org/support/bug_reports.html.\n--2198-- WARNING: unhandled riscv64-linux syscall: 258\n--2198-- You may be able to write your own handler.\n--2198-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2198-- Nevertheless we consider this a bug.  Please report\n--2198-- it at http://valgrind.org/support/bug_reports.html.\n--2198-- WARNING: unhandled riscv64-linux syscall: 258\n--2198-- You may be able to write your own handler.\n--2198-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2198-- Nevertheless we consider this a bug.  Please report\n--2198-- it at http://valgrind.org/support/bug_reports.html.\n--2198-- WARNING: unhandled riscv64-linux syscall: 258\n--2198-- You may be able to write your own handler.\n--2198-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2198-- Nevertheless we consider this a bug.  Please report\n--2198-- it at http://valgrind.org/support/bug_reports.html.\n--2198-- WARNING: unhandled riscv64-linux syscall: 258\n--2198-- You may be able to write your own handler.\n--2198-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2198-- Nevertheless we consider this a bug.  Please report\n--2198-- it at http://valgrind.org/support/bug_reports.html.\n--2198-- WARNING: unhandled riscv64-linux syscall: 258\n--2198-- You may be able to write your own handler.\n--2198-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2198-- Nevertheless we consider this a bug.  Please report\n--2198-- 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:
'--2209-- WARNING: unhandled riscv64-linux syscall: 258\n--2209-- You may be able to write your own handler.\n--2209-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2209-- Nevertheless we consider this a bug.  Please report\n--2209-- it at http://valgrind.org/support/bug_reports.html.\n--2209-- WARNING: unhandled riscv64-linux syscall: 258\n--2209-- You may be able to write your own handler.\n--2209-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2209-- Nevertheless we consider this a bug.  Please report\n--2209-- it at http://valgrind.org/support/bug_reports.html.\n--2209-- WARNING: unhandled riscv64-linux syscall: 258\n--2209-- You may be able to write your own handler.\n--2209-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2209-- Nevertheless we consider this a bug.  Please report\n--2209-- it at http://valgrind.org/support/bug_reports.html.\n--2209-- WARNING: unhandled riscv64-linux syscall: 258\n--2209-- You may be able to write your own handler.\n--2209-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2209-- Nevertheless we consider this a bug.  Please report\n--2209-- it at http://valgrind.org/support/bug_reports.html.\n--2209-- WARNING: unhandled riscv64-linux syscall: 258\n--2209-- You may be able to write your own handler.\n--2209-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2209-- Nevertheless we consider this a bug.  Please report\n--2209-- it at http://valgrind.org/support/bug_reports.html.\n--2209-- WARNING: unhandled riscv64-linux syscall: 258\n--2209-- You may be able to write your own handler.\n--2209-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2209-- Nevertheless we consider this a bug.  Please report\n--2209-- it at http://valgrind.org/support/bug_reports.html.\n--2209-- WARNING: unhandled riscv64-linux syscall: 258\n--2209-- You may be able to write your own handler.\n--2209-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2209-- Nevertheless we consider this a bug.  Please report\n--2209-- it at http://valgrind.org/support/bug_reports.html.\n--2209-- WARNING: unhandled riscv64-linux syscall: 258\n--2209-- You may be able to write your own handler.\n--2209-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2209-- Nevertheless we consider this a bug.  Please report\n--2209-- it at http://valgrind.org/support/bug_reports.html.\n--2209-- WARNING: unhandled riscv64-linux syscall: 258\n--2209-- You may be able to write your own handler.\n--2209-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2209-- Nevertheless we consider this a bug.  Please report\n--2209-- it at http://valgrind.org/support/bug_reports.html.\n--2209-- WARNING: unhandled riscv64-linux syscall: 258\n--2209-- You may be able to write your own handler.\n--2209-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2209-- Nevertheless we consider this a bug.  Please report\n--2209-- it at http://valgrind.org/support/bug_reports.html.\n--2209-- WARNING: unhandled riscv64-linux syscall: 258\n--2209-- You may be able to write your own handler.\n--2209-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2209-- Nevertheless we consider this a bug.  Please report\n--2209-- it at http://valgrind.org/support/bug_reports.html.\n--2209-- WARNING: unhandled riscv64-linux syscall: 258\n--2209-- You may be able to write your own handler.\n--2209-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2209-- Nevertheless we consider this a bug.  Please report\n--2209-- it at http://valgrind.org/support/bug_reports.html.\n--2209-- WARNING: unhandled riscv64-linux syscall: 258\n--2209-- You may be able to write your own handler.\n--2209-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2209-- Nevertheless we consider this a bug.  Please report\n--2209-- it at http://valgrind.org/support/bug_reports.html.\n--2209-- WARNING: unhandled riscv64-linux syscall: 258\n--2209-- You may be able to write your own handler.\n--2209-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2209-- Nevertheless we consider this a bug.  Please report\n--2209-- it at http://valgrind.org/support/bug_reports.html.\n--2209-- WARNING: unhandled riscv64-linux syscall: 258\n--2209-- You may be able to write your own handler.\n--2209-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2209-- Nevertheless we consider this a bug.  Please report\n--2209-- it at http://valgrind.org/support/bug_reports.html.\n--2209-- WARNING: unhandled riscv64-linux syscall: 258\n--2209-- You may be able to write your own handler.\n--2209-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2209-- Nevertheless we consider this a bug.  Please report\n--2209-- it at http://valgrind.org/support/bug_reports.html.\n--2209-- WARNING: unhandled riscv64-linux syscall: 258\n--2209-- You may be able to write your own handler.\n--2209-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2209-- Nevertheless we consider this a bug.  Please report\n--2209-- it at http://valgrind.org/support/bug_reports.html.\n--2209-- WARNING: unhandled riscv64-linux syscall: 258\n--2209-- You may be able to write your own handler.\n--2209-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2209-- Nevertheless we consider this a bug.  Please report\n--2209-- 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:
'--2243-- WARNING: unhandled riscv64-linux syscall: 258\n--2243-- You may be able to write your own handler.\n--2243-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2243-- Nevertheless we consider this a bug.  Please report\n--2243-- it at http://valgrind.org/support/bug_reports.html.\n--2243-- WARNING: unhandled riscv64-linux syscall: 258\n--2243-- You may be able to write your own handler.\n--2243-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2243-- Nevertheless we consider this a bug.  Please report\n--2243-- it at http://valgrind.org/support/bug_reports.html.\n--2243-- WARNING: unhandled riscv64-linux syscall: 258\n--2243-- You may be able to write your own handler.\n--2243-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2243-- Nevertheless we consider this a bug.  Please report\n--2243-- it at http://valgrind.org/support/bug_reports.html.\n--2243-- WARNING: unhandled riscv64-linux syscall: 258\n--2243-- You may be able to write your own handler.\n--2243-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2243-- Nevertheless we consider this a bug.  Please report\n--2243-- it at http://valgrind.org/support/bug_reports.html.\n--2243-- WARNING: unhandled riscv64-linux syscall: 258\n--2243-- You may be able to write your own handler.\n--2243-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2243-- Nevertheless we consider this a bug.  Please report\n--2243-- it at http://valgrind.org/support/bug_reports.html.\n--2243-- WARNING: unhandled riscv64-linux syscall: 258\n--2243-- You may be able to write your own handler.\n--2243-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2243-- Nevertheless we consider this a bug.  Please report\n--2243-- it at http://valgrind.org/support/bug_reports.html.\n--2243-- WARNING: unhandled riscv64-linux syscall: 258\n--2243-- You may be able to write your own handler.\n--2243-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2243-- Nevertheless we consider this a bug.  Please report\n--2243-- it at http://valgrind.org/support/bug_reports.html.\n--2243-- WARNING: unhandled riscv64-linux syscall: 258\n--2243-- You may be able to write your own handler.\n--2243-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2243-- Nevertheless we consider this a bug.  Please report\n--2243-- it at http://valgrind.org/support/bug_reports.html.\n--2243-- WARNING: unhandled riscv64-linux syscall: 258\n--2243-- You may be able to write your own handler.\n--2243-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2243-- Nevertheless we consider this a bug.  Please report\n--2243-- it at http://valgrind.org/support/bug_reports.html.\n--2243-- WARNING: unhandled riscv64-linux syscall: 258\n--2243-- You may be able to write your own handler.\n--2243-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2243-- Nevertheless we consider this a bug.  Please report\n--2243-- it at http://valgrind.org/support/bug_reports.html.\n--2243-- WARNING: unhandled riscv64-linux syscall: 258\n--2243-- You may be able to write your own handler.\n--2243-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2243-- Nevertheless we consider this a bug.  Please report\n--2243-- it at http://valgrind.org/support/bug_reports.html.\n--2243-- WARNING: unhandled riscv64-linux syscall: 258\n--2243-- You may be able to write your own handler.\n--2243-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2243-- Nevertheless we consider this a bug.  Please report\n--2243-- it at http://valgrind.org/support/bug_reports.html.\n--2243-- WARNING: unhandled riscv64-linux syscall: 258\n--2243-- You may be able to write your own handler.\n--2243-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2243-- Nevertheless we consider this a bug.  Please report\n--2243-- it at http://valgrind.org/support/bug_reports.html.\n--2243-- WARNING: unhandled riscv64-linux syscall: 258\n--2243-- You may be able to write your own handler.\n--2243-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2243-- Nevertheless we consider this a bug.  Please report\n--2243-- it at http://valgrind.org/support/bug_reports.html.\n--2243-- WARNING: unhandled riscv64-linux syscall: 258\n--2243-- You may be able to write your own handler.\n--2243-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2243-- Nevertheless we consider this a bug.  Please report\n--2243-- it at http://valgrind.org/support/bug_reports.html.\n--2243-- WARNING: unhandled riscv64-linux syscall: 258\n--2243-- You may be able to write your own handler.\n--2243-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2243-- Nevertheless we consider this a bug.  Please report\n--2243-- it at http://valgrind.org/support/bug_reports.html.\n--2243-- WARNING: unhandled riscv64-linux syscall: 258\n--2243-- You may be able to write your own handler.\n--2243-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2243-- Nevertheless we consider this a bug.  Please report\n--2243-- it at http://valgrind.org/support/bug_reports.html.\n--2243-- WARNING: unhandled riscv64-linux syscall: 258\n--2243-- You may be able to write your own handler.\n--2243-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2243-- Nevertheless we consider this a bug.  Please report\n--2243-- 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:
'--2259-- WARNING: unhandled riscv64-linux syscall: 258\n--2259-- You may be able to write your own handler.\n--2259-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2259-- Nevertheless we consider this a bug.  Please report\n--2259-- it at http://valgrind.org/support/bug_reports.html.\n--2259-- WARNING: unhandled riscv64-linux syscall: 258\n--2259-- You may be able to write your own handler.\n--2259-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2259-- Nevertheless we consider this a bug.  Please report\n--2259-- it at http://valgrind.org/support/bug_reports.html.\n--2259-- WARNING: unhandled riscv64-linux syscall: 258\n--2259-- You may be able to write your own handler.\n--2259-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2259-- Nevertheless we consider this a bug.  Please report\n--2259-- it at http://valgrind.org/support/bug_reports.html.\n--2259-- WARNING: unhandled riscv64-linux syscall: 258\n--2259-- You may be able to write your own handler.\n--2259-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2259-- Nevertheless we consider this a bug.  Please report\n--2259-- it at http://valgrind.org/support/bug_reports.html.\n--2259-- WARNING: unhandled riscv64-linux syscall: 258\n--2259-- You may be able to write your own handler.\n--2259-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2259-- Nevertheless we consider this a bug.  Please report\n--2259-- it at http://valgrind.org/support/bug_reports.html.\n--2259-- WARNING: unhandled riscv64-linux syscall: 258\n--2259-- You may be able to write your own handler.\n--2259-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2259-- Nevertheless we consider this a bug.  Please report\n--2259-- it at http://valgrind.org/support/bug_reports.html.\n--2259-- WARNING: unhandled riscv64-linux syscall: 258\n--2259-- You may be able to write your own handler.\n--2259-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2259-- Nevertheless we consider this a bug.  Please report\n--2259-- it at http://valgrind.org/support/bug_reports.html.\n--2259-- WARNING: unhandled riscv64-linux syscall: 258\n--2259-- You may be able to write your own handler.\n--2259-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2259-- Nevertheless we consider this a bug.  Please report\n--2259-- it at http://valgrind.org/support/bug_reports.html.\n--2259-- WARNING: unhandled riscv64-linux syscall: 258\n--2259-- You may be able to write your own handler.\n--2259-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2259-- Nevertheless we consider this a bug.  Please report\n--2259-- it at http://valgrind.org/support/bug_reports.html.\n--2259-- WARNING: unhandled riscv64-linux syscall: 258\n--2259-- You may be able to write your own handler.\n--2259-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2259-- Nevertheless we consider this a bug.  Please report\n--2259-- it at http://valgrind.org/support/bug_reports.html.\n--2259-- WARNING: unhandled riscv64-linux syscall: 258\n--2259-- You may be able to write your own handler.\n--2259-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2259-- Nevertheless we consider this a bug.  Please report\n--2259-- it at http://valgrind.org/support/bug_reports.html.\n--2259-- WARNING: unhandled riscv64-linux syscall: 258\n--2259-- You may be able to write your own handler.\n--2259-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2259-- Nevertheless we consider this a bug.  Please report\n--2259-- it at http://valgrind.org/support/bug_reports.html.\n--2259-- WARNING: unhandled riscv64-linux syscall: 258\n--2259-- You may be able to write your own handler.\n--2259-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2259-- Nevertheless we consider this a bug.  Please report\n--2259-- it at http://valgrind.org/support/bug_reports.html.\n--2259-- WARNING: unhandled riscv64-linux syscall: 258\n--2259-- You may be able to write your own handler.\n--2259-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2259-- Nevertheless we consider this a bug.  Please report\n--2259-- it at http://valgrind.org/support/bug_reports.html.\n--2259-- WARNING: unhandled riscv64-linux syscall: 258\n--2259-- You may be able to write your own handler.\n--2259-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2259-- Nevertheless we consider this a bug.  Please report\n--2259-- it at http://valgrind.org/support/bug_reports.html.\n--2259-- WARNING: unhandled riscv64-linux syscall: 258\n--2259-- You may be able to write your own handler.\n--2259-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2259-- Nevertheless we consider this a bug.  Please report\n--2259-- it at http://valgrind.org/support/bug_reports.html.\n--2259-- WARNING: unhandled riscv64-linux syscall: 258\n--2259-- You may be able to write your own handler.\n--2259-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2259-- Nevertheless we consider this a bug.  Please report\n--2259-- it at http://valgrind.org/support/bug_reports.html.\n--2259-- WARNING: unhandled riscv64-linux syscall: 258\n--2259-- You may be able to write your own handler.\n--2259-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2259-- Nevertheless we consider this a bug.  Please report\n--2259-- 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:
'--2267-- WARNING: unhandled riscv64-linux syscall: 258\n--2267-- You may be able to write your own handler.\n--2267-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2267-- Nevertheless we consider this a bug.  Please report\n--2267-- it at http://valgrind.org/support/bug_reports.html.\n--2267-- WARNING: unhandled riscv64-linux syscall: 258\n--2267-- You may be able to write your own handler.\n--2267-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2267-- Nevertheless we consider this a bug.  Please report\n--2267-- it at http://valgrind.org/support/bug_reports.html.\n--2267-- WARNING: unhandled riscv64-linux syscall: 258\n--2267-- You may be able to write your own handler.\n--2267-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2267-- Nevertheless we consider this a bug.  Please report\n--2267-- it at http://valgrind.org/support/bug_reports.html.\n--2267-- WARNING: unhandled riscv64-linux syscall: 258\n--2267-- You may be able to write your own handler.\n--2267-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2267-- Nevertheless we consider this a bug.  Please report\n--2267-- it at http://valgrind.org/support/bug_reports.html.\n--2267-- WARNING: unhandled riscv64-linux syscall: 258\n--2267-- You may be able to write your own handler.\n--2267-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2267-- Nevertheless we consider this a bug.  Please report\n--2267-- it at http://valgrind.org/support/bug_reports.html.\n--2267-- WARNING: unhandled riscv64-linux syscall: 258\n--2267-- You may be able to write your own handler.\n--2267-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2267-- Nevertheless we consider this a bug.  Please report\n--2267-- it at http://valgrind.org/support/bug_reports.html.\n--2267-- WARNING: unhandled riscv64-linux syscall: 258\n--2267-- You may be able to write your own handler.\n--2267-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2267-- Nevertheless we consider this a bug.  Please report\n--2267-- it at http://valgrind.org/support/bug_reports.html.\n--2267-- WARNING: unhandled riscv64-linux syscall: 258\n--2267-- You may be able to write your own handler.\n--2267-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2267-- Nevertheless we consider this a bug.  Please report\n--2267-- it at http://valgrind.org/support/bug_reports.html.\n--2267-- WARNING: unhandled riscv64-linux syscall: 258\n--2267-- You may be able to write your own handler.\n--2267-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2267-- Nevertheless we consider this a bug.  Please report\n--2267-- it at http://valgrind.org/support/bug_reports.html.\n--2267-- WARNING: unhandled riscv64-linux syscall: 258\n--2267-- You may be able to write your own handler.\n--2267-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2267-- Nevertheless we consider this a bug.  Please report\n--2267-- it at http://valgrind.org/support/bug_reports.html.\n--2267-- WARNING: unhandled riscv64-linux syscall: 258\n--2267-- You may be able to write your own handler.\n--2267-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2267-- Nevertheless we consider this a bug.  Please report\n--2267-- it at http://valgrind.org/support/bug_reports.html.\n--2267-- WARNING: unhandled riscv64-linux syscall: 258\n--2267-- You may be able to write your own handler.\n--2267-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2267-- Nevertheless we consider this a bug.  Please report\n--2267-- it at http://valgrind.org/support/bug_reports.html.\n--2267-- WARNING: unhandled riscv64-linux syscall: 258\n--2267-- You may be able to write your own handler.\n--2267-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2267-- Nevertheless we consider this a bug.  Please report\n--2267-- it at http://valgrind.org/support/bug_reports.html.\n--2267-- WARNING: unhandled riscv64-linux syscall: 258\n--2267-- You may be able to write your own handler.\n--2267-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2267-- Nevertheless we consider this a bug.  Please report\n--2267-- it at http://valgrind.org/support/bug_reports.html.\n--2267-- WARNING: unhandled riscv64-linux syscall: 258\n--2267-- You may be able to write your own handler.\n--2267-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2267-- Nevertheless we consider this a bug.  Please report\n--2267-- it at http://valgrind.org/support/bug_reports.html.\n--2267-- WARNING: unhandled riscv64-linux syscall: 258\n--2267-- You may be able to write your own handler.\n--2267-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2267-- Nevertheless we consider this a bug.  Please report\n--2267-- it at http://valgrind.org/support/bug_reports.html.\n--2267-- WARNING: unhandled riscv64-linux syscall: 258\n--2267-- You may be able to write your own handler.\n--2267-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2267-- Nevertheless we consider this a bug.  Please report\n--2267-- it at http://valgrind.org/support/bug_reports.html.\n--2267-- WARNING: unhandled riscv64-linux syscall: 258\n--2267-- You may be able to write your own handler.\n--2267-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2267-- Nevertheless we consider this a bug.  Please report\n--2267-- 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:
'--2275-- WARNING: unhandled riscv64-linux syscall: 258\n--2275-- You may be able to write your own handler.\n--2275-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2275-- Nevertheless we consider this a bug.  Please report\n--2275-- it at http://valgrind.org/support/bug_reports.html.\n--2275-- WARNING: unhandled riscv64-linux syscall: 258\n--2275-- You may be able to write your own handler.\n--2275-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2275-- Nevertheless we consider this a bug.  Please report\n--2275-- it at http://valgrind.org/support/bug_reports.html.\n--2275-- WARNING: unhandled riscv64-linux syscall: 258\n--2275-- You may be able to write your own handler.\n--2275-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2275-- Nevertheless we consider this a bug.  Please report\n--2275-- it at http://valgrind.org/support/bug_reports.html.\n--2275-- WARNING: unhandled riscv64-linux syscall: 258\n--2275-- You may be able to write your own handler.\n--2275-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2275-- Nevertheless we consider this a bug.  Please report\n--2275-- it at http://valgrind.org/support/bug_reports.html.\n--2275-- WARNING: unhandled riscv64-linux syscall: 258\n--2275-- You may be able to write your own handler.\n--2275-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2275-- Nevertheless we consider this a bug.  Please report\n--2275-- it at http://valgrind.org/support/bug_reports.html.\n--2275-- WARNING: unhandled riscv64-linux syscall: 258\n--2275-- You may be able to write your own handler.\n--2275-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2275-- Nevertheless we consider this a bug.  Please report\n--2275-- it at http://valgrind.org/support/bug_reports.html.\n--2275-- WARNING: unhandled riscv64-linux syscall: 258\n--2275-- You may be able to write your own handler.\n--2275-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2275-- Nevertheless we consider this a bug.  Please report\n--2275-- it at http://valgrind.org/support/bug_reports.html.\n--2275-- WARNING: unhandled riscv64-linux syscall: 258\n--2275-- You may be able to write your own handler.\n--2275-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2275-- Nevertheless we consider this a bug.  Please report\n--2275-- it at http://valgrind.org/support/bug_reports.html.\n--2275-- WARNING: unhandled riscv64-linux syscall: 258\n--2275-- You may be able to write your own handler.\n--2275-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2275-- Nevertheless we consider this a bug.  Please report\n--2275-- it at http://valgrind.org/support/bug_reports.html.\n--2275-- WARNING: unhandled riscv64-linux syscall: 258\n--2275-- You may be able to write your own handler.\n--2275-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2275-- Nevertheless we consider this a bug.  Please report\n--2275-- it at http://valgrind.org/support/bug_reports.html.\n--2275-- WARNING: unhandled riscv64-linux syscall: 258\n--2275-- You may be able to write your own handler.\n--2275-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2275-- Nevertheless we consider this a bug.  Please report\n--2275-- it at http://valgrind.org/support/bug_reports.html.\n--2275-- WARNING: unhandled riscv64-linux syscall: 258\n--2275-- You may be able to write your own handler.\n--2275-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2275-- Nevertheless we consider this a bug.  Please report\n--2275-- it at http://valgrind.org/support/bug_reports.html.\n--2275-- WARNING: unhandled riscv64-linux syscall: 258\n--2275-- You may be able to write your own handler.\n--2275-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2275-- Nevertheless we consider this a bug.  Please report\n--2275-- it at http://valgrind.org/support/bug_reports.html.\n--2275-- WARNING: unhandled riscv64-linux syscall: 258\n--2275-- You may be able to write your own handler.\n--2275-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2275-- Nevertheless we consider this a bug.  Please report\n--2275-- it at http://valgrind.org/support/bug_reports.html.\n--2275-- WARNING: unhandled riscv64-linux syscall: 258\n--2275-- You may be able to write your own handler.\n--2275-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2275-- Nevertheless we consider this a bug.  Please report\n--2275-- it at http://valgrind.org/support/bug_reports.html.\n--2275-- WARNING: unhandled riscv64-linux syscall: 258\n--2275-- You may be able to write your own handler.\n--2275-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2275-- Nevertheless we consider this a bug.  Please report\n--2275-- it at http://valgrind.org/support/bug_reports.html.\n--2275-- WARNING: unhandled riscv64-linux syscall: 258\n--2275-- You may be able to write your own handler.\n--2275-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2275-- Nevertheless we consider this a bug.  Please report\n--2275-- it at http://valgrind.org/support/bug_reports.html.\n--2275-- WARNING: unhandled riscv64-linux syscall: 258\n--2275-- You may be able to write your own handler.\n--2275-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2275-- Nevertheless we consider this a bug.  Please report\n--2275-- 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:
'--2283-- WARNING: unhandled riscv64-linux syscall: 258\n--2283-- You may be able to write your own handler.\n--2283-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2283-- Nevertheless we consider this a bug.  Please report\n--2283-- it at http://valgrind.org/support/bug_reports.html.\n--2283-- WARNING: unhandled riscv64-linux syscall: 258\n--2283-- You may be able to write your own handler.\n--2283-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2283-- Nevertheless we consider this a bug.  Please report\n--2283-- it at http://valgrind.org/support/bug_reports.html.\n--2283-- WARNING: unhandled riscv64-linux syscall: 258\n--2283-- You may be able to write your own handler.\n--2283-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2283-- Nevertheless we consider this a bug.  Please report\n--2283-- it at http://valgrind.org/support/bug_reports.html.\n--2283-- WARNING: unhandled riscv64-linux syscall: 258\n--2283-- You may be able to write your own handler.\n--2283-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2283-- Nevertheless we consider this a bug.  Please report\n--2283-- it at http://valgrind.org/support/bug_reports.html.\n--2283-- WARNING: unhandled riscv64-linux syscall: 258\n--2283-- You may be able to write your own handler.\n--2283-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2283-- Nevertheless we consider this a bug.  Please report\n--2283-- it at http://valgrind.org/support/bug_reports.html.\n--2283-- WARNING: unhandled riscv64-linux syscall: 258\n--2283-- You may be able to write your own handler.\n--2283-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2283-- Nevertheless we consider this a bug.  Please report\n--2283-- it at http://valgrind.org/support/bug_reports.html.\n--2283-- WARNING: unhandled riscv64-linux syscall: 258\n--2283-- You may be able to write your own handler.\n--2283-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2283-- Nevertheless we consider this a bug.  Please report\n--2283-- it at http://valgrind.org/support/bug_reports.html.\n--2283-- WARNING: unhandled riscv64-linux syscall: 258\n--2283-- You may be able to write your own handler.\n--2283-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2283-- Nevertheless we consider this a bug.  Please report\n--2283-- it at http://valgrind.org/support/bug_reports.html.\n--2283-- WARNING: unhandled riscv64-linux syscall: 258\n--2283-- You may be able to write your own handler.\n--2283-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2283-- Nevertheless we consider this a bug.  Please report\n--2283-- it at http://valgrind.org/support/bug_reports.html.\n--2283-- WARNING: unhandled riscv64-linux syscall: 258\n--2283-- You may be able to write your own handler.\n--2283-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2283-- Nevertheless we consider this a bug.  Please report\n--2283-- it at http://valgrind.org/support/bug_reports.html.\n--2283-- WARNING: unhandled riscv64-linux syscall: 258\n--2283-- You may be able to write your own handler.\n--2283-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2283-- Nevertheless we consider this a bug.  Please report\n--2283-- it at http://valgrind.org/support/bug_reports.html.\n--2283-- WARNING: unhandled riscv64-linux syscall: 258\n--2283-- You may be able to write your own handler.\n--2283-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2283-- Nevertheless we consider this a bug.  Please report\n--2283-- it at http://valgrind.org/support/bug_reports.html.\n--2283-- WARNING: unhandled riscv64-linux syscall: 258\n--2283-- You may be able to write your own handler.\n--2283-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2283-- Nevertheless we consider this a bug.  Please report\n--2283-- it at http://valgrind.org/support/bug_reports.html.\n--2283-- WARNING: unhandled riscv64-linux syscall: 258\n--2283-- You may be able to write your own handler.\n--2283-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2283-- Nevertheless we consider this a bug.  Please report\n--2283-- it at http://valgrind.org/support/bug_reports.html.\n--2283-- WARNING: unhandled riscv64-linux syscall: 258\n--2283-- You may be able to write your own handler.\n--2283-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2283-- Nevertheless we consider this a bug.  Please report\n--2283-- it at http://valgrind.org/support/bug_reports.html.\n--2283-- WARNING: unhandled riscv64-linux syscall: 258\n--2283-- You may be able to write your own handler.\n--2283-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2283-- Nevertheless we consider this a bug.  Please report\n--2283-- it at http://valgrind.org/support/bug_reports.html.\n--2283-- WARNING: unhandled riscv64-linux syscall: 258\n--2283-- You may be able to write your own handler.\n--2283-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2283-- Nevertheless we consider this a bug.  Please report\n--2283-- it at http://valgrind.org/support/bug_reports.html.\n--2283-- WARNING: unhandled riscv64-linux syscall: 258\n--2283-- You may be able to write your own handler.\n--2283-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2283-- Nevertheless we consider this a bug.  Please report\n--2283-- 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:
'--2291-- WARNING: unhandled riscv64-linux syscall: 258\n--2291-- You may be able to write your own handler.\n--2291-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2291-- Nevertheless we consider this a bug.  Please report\n--2291-- it at http://valgrind.org/support/bug_reports.html.\n--2291-- WARNING: unhandled riscv64-linux syscall: 258\n--2291-- You may be able to write your own handler.\n--2291-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2291-- Nevertheless we consider this a bug.  Please report\n--2291-- it at http://valgrind.org/support/bug_reports.html.\n--2291-- WARNING: unhandled riscv64-linux syscall: 258\n--2291-- You may be able to write your own handler.\n--2291-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2291-- Nevertheless we consider this a bug.  Please report\n--2291-- it at http://valgrind.org/support/bug_reports.html.\n--2291-- WARNING: unhandled riscv64-linux syscall: 258\n--2291-- You may be able to write your own handler.\n--2291-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2291-- Nevertheless we consider this a bug.  Please report\n--2291-- it at http://valgrind.org/support/bug_reports.html.\n--2291-- WARNING: unhandled riscv64-linux syscall: 258\n--2291-- You may be able to write your own handler.\n--2291-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2291-- Nevertheless we consider this a bug.  Please report\n--2291-- it at http://valgrind.org/support/bug_reports.html.\n--2291-- WARNING: unhandled riscv64-linux syscall: 258\n--2291-- You may be able to write your own handler.\n--2291-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2291-- Nevertheless we consider this a bug.  Please report\n--2291-- it at http://valgrind.org/support/bug_reports.html.\n--2291-- WARNING: unhandled riscv64-linux syscall: 258\n--2291-- You may be able to write your own handler.\n--2291-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2291-- Nevertheless we consider this a bug.  Please report\n--2291-- it at http://valgrind.org/support/bug_reports.html.\n--2291-- WARNING: unhandled riscv64-linux syscall: 258\n--2291-- You may be able to write your own handler.\n--2291-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2291-- Nevertheless we consider this a bug.  Please report\n--2291-- it at http://valgrind.org/support/bug_reports.html.\n--2291-- WARNING: unhandled riscv64-linux syscall: 258\n--2291-- You may be able to write your own handler.\n--2291-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2291-- Nevertheless we consider this a bug.  Please report\n--2291-- it at http://valgrind.org/support/bug_reports.html.\n--2291-- WARNING: unhandled riscv64-linux syscall: 258\n--2291-- You may be able to write your own handler.\n--2291-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2291-- Nevertheless we consider this a bug.  Please report\n--2291-- it at http://valgrind.org/support/bug_reports.html.\n--2291-- WARNING: unhandled riscv64-linux syscall: 258\n--2291-- You may be able to write your own handler.\n--2291-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2291-- Nevertheless we consider this a bug.  Please report\n--2291-- it at http://valgrind.org/support/bug_reports.html.\n--2291-- WARNING: unhandled riscv64-linux syscall: 258\n--2291-- You may be able to write your own handler.\n--2291-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2291-- Nevertheless we consider this a bug.  Please report\n--2291-- it at http://valgrind.org/support/bug_reports.html.\n--2291-- WARNING: unhandled riscv64-linux syscall: 258\n--2291-- You may be able to write your own handler.\n--2291-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2291-- Nevertheless we consider this a bug.  Please report\n--2291-- it at http://valgrind.org/support/bug_reports.html.\n--2291-- WARNING: unhandled riscv64-linux syscall: 258\n--2291-- You may be able to write your own handler.\n--2291-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2291-- Nevertheless we consider this a bug.  Please report\n--2291-- it at http://valgrind.org/support/bug_reports.html.\n--2291-- WARNING: unhandled riscv64-linux syscall: 258\n--2291-- You may be able to write your own handler.\n--2291-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2291-- Nevertheless we consider this a bug.  Please report\n--2291-- it at http://valgrind.org/support/bug_reports.html.\n--2291-- WARNING: unhandled riscv64-linux syscall: 258\n--2291-- You may be able to write your own handler.\n--2291-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2291-- Nevertheless we consider this a bug.  Please report\n--2291-- it at http://valgrind.org/support/bug_reports.html.\n--2291-- WARNING: unhandled riscv64-linux syscall: 258\n--2291-- You may be able to write your own handler.\n--2291-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2291-- Nevertheless we consider this a bug.  Please report\n--2291-- it at http://valgrind.org/support/bug_reports.html.\n--2291-- WARNING: unhandled riscv64-linux syscall: 258\n--2291-- You may be able to write your own handler.\n--2291-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2291-- Nevertheless we consider this a bug.  Please report\n--2291-- 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:
'--2299-- WARNING: unhandled riscv64-linux syscall: 258\n--2299-- You may be able to write your own handler.\n--2299-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2299-- Nevertheless we consider this a bug.  Please report\n--2299-- it at http://valgrind.org/support/bug_reports.html.\n--2299-- WARNING: unhandled riscv64-linux syscall: 258\n--2299-- You may be able to write your own handler.\n--2299-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2299-- Nevertheless we consider this a bug.  Please report\n--2299-- it at http://valgrind.org/support/bug_reports.html.\n--2299-- WARNING: unhandled riscv64-linux syscall: 258\n--2299-- You may be able to write your own handler.\n--2299-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2299-- Nevertheless we consider this a bug.  Please report\n--2299-- it at http://valgrind.org/support/bug_reports.html.\n--2299-- WARNING: unhandled riscv64-linux syscall: 258\n--2299-- You may be able to write your own handler.\n--2299-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2299-- Nevertheless we consider this a bug.  Please report\n--2299-- it at http://valgrind.org/support/bug_reports.html.\n--2299-- WARNING: unhandled riscv64-linux syscall: 258\n--2299-- You may be able to write your own handler.\n--2299-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2299-- Nevertheless we consider this a bug.  Please report\n--2299-- it at http://valgrind.org/support/bug_reports.html.\n--2299-- WARNING: unhandled riscv64-linux syscall: 258\n--2299-- You may be able to write your own handler.\n--2299-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2299-- Nevertheless we consider this a bug.  Please report\n--2299-- it at http://valgrind.org/support/bug_reports.html.\n--2299-- WARNING: unhandled riscv64-linux syscall: 258\n--2299-- You may be able to write your own handler.\n--2299-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2299-- Nevertheless we consider this a bug.  Please report\n--2299-- it at http://valgrind.org/support/bug_reports.html.\n--2299-- WARNING: unhandled riscv64-linux syscall: 258\n--2299-- You may be able to write your own handler.\n--2299-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2299-- Nevertheless we consider this a bug.  Please report\n--2299-- it at http://valgrind.org/support/bug_reports.html.\n--2299-- WARNING: unhandled riscv64-linux syscall: 258\n--2299-- You may be able to write your own handler.\n--2299-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2299-- Nevertheless we consider this a bug.  Please report\n--2299-- it at http://valgrind.org/support/bug_reports.html.\n--2299-- WARNING: unhandled riscv64-linux syscall: 258\n--2299-- You may be able to write your own handler.\n--2299-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2299-- Nevertheless we consider this a bug.  Please report\n--2299-- it at http://valgrind.org/support/bug_reports.html.\n--2299-- WARNING: unhandled riscv64-linux syscall: 258\n--2299-- You may be able to write your own handler.\n--2299-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2299-- Nevertheless we consider this a bug.  Please report\n--2299-- it at http://valgrind.org/support/bug_reports.html.\n--2299-- WARNING: unhandled riscv64-linux syscall: 258\n--2299-- You may be able to write your own handler.\n--2299-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2299-- Nevertheless we consider this a bug.  Please report\n--2299-- it at http://valgrind.org/support/bug_reports.html.\n--2299-- WARNING: unhandled riscv64-linux syscall: 258\n--2299-- You may be able to write your own handler.\n--2299-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2299-- Nevertheless we consider this a bug.  Please report\n--2299-- it at http://valgrind.org/support/bug_reports.html.\n--2299-- WARNING: unhandled riscv64-linux syscall: 258\n--2299-- You may be able to write your own handler.\n--2299-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2299-- Nevertheless we consider this a bug.  Please report\n--2299-- it at http://valgrind.org/support/bug_reports.html.\n--2299-- WARNING: unhandled riscv64-linux syscall: 258\n--2299-- You may be able to write your own handler.\n--2299-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2299-- Nevertheless we consider this a bug.  Please report\n--2299-- it at http://valgrind.org/support/bug_reports.html.\n--2299-- WARNING: unhandled riscv64-linux syscall: 258\n--2299-- You may be able to write your own handler.\n--2299-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2299-- Nevertheless we consider this a bug.  Please report\n--2299-- it at http://valgrind.org/support/bug_reports.html.\n--2299-- WARNING: unhandled riscv64-linux syscall: 258\n--2299-- You may be able to write your own handler.\n--2299-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2299-- Nevertheless we consider this a bug.  Please report\n--2299-- it at http://valgrind.org/support/bug_reports.html.\n--2299-- WARNING: unhandled riscv64-linux syscall: 258\n--2299-- You may be able to write your own handler.\n--2299-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2299-- Nevertheless we consider this a bug.  Please report\n--2299-- 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:
'--2307-- WARNING: unhandled riscv64-linux syscall: 258\n--2307-- You may be able to write your own handler.\n--2307-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2307-- Nevertheless we consider this a bug.  Please report\n--2307-- it at http://valgrind.org/support/bug_reports.html.\n--2307-- WARNING: unhandled riscv64-linux syscall: 258\n--2307-- You may be able to write your own handler.\n--2307-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2307-- Nevertheless we consider this a bug.  Please report\n--2307-- it at http://valgrind.org/support/bug_reports.html.\n--2307-- WARNING: unhandled riscv64-linux syscall: 258\n--2307-- You may be able to write your own handler.\n--2307-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2307-- Nevertheless we consider this a bug.  Please report\n--2307-- it at http://valgrind.org/support/bug_reports.html.\n--2307-- WARNING: unhandled riscv64-linux syscall: 258\n--2307-- You may be able to write your own handler.\n--2307-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2307-- Nevertheless we consider this a bug.  Please report\n--2307-- it at http://valgrind.org/support/bug_reports.html.\n--2307-- WARNING: unhandled riscv64-linux syscall: 258\n--2307-- You may be able to write your own handler.\n--2307-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2307-- Nevertheless we consider this a bug.  Please report\n--2307-- it at http://valgrind.org/support/bug_reports.html.\n--2307-- WARNING: unhandled riscv64-linux syscall: 258\n--2307-- You may be able to write your own handler.\n--2307-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2307-- Nevertheless we consider this a bug.  Please report\n--2307-- it at http://valgrind.org/support/bug_reports.html.\n--2307-- WARNING: unhandled riscv64-linux syscall: 258\n--2307-- You may be able to write your own handler.\n--2307-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2307-- Nevertheless we consider this a bug.  Please report\n--2307-- it at http://valgrind.org/support/bug_reports.html.\n--2307-- WARNING: unhandled riscv64-linux syscall: 258\n--2307-- You may be able to write your own handler.\n--2307-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2307-- Nevertheless we consider this a bug.  Please report\n--2307-- it at http://valgrind.org/support/bug_reports.html.\n--2307-- WARNING: unhandled riscv64-linux syscall: 258\n--2307-- You may be able to write your own handler.\n--2307-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2307-- Nevertheless we consider this a bug.  Please report\n--2307-- it at http://valgrind.org/support/bug_reports.html.\n--2307-- WARNING: unhandled riscv64-linux syscall: 258\n--2307-- You may be able to write your own handler.\n--2307-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2307-- Nevertheless we consider this a bug.  Please report\n--2307-- it at http://valgrind.org/support/bug_reports.html.\n--2307-- WARNING: unhandled riscv64-linux syscall: 258\n--2307-- You may be able to write your own handler.\n--2307-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2307-- Nevertheless we consider this a bug.  Please report\n--2307-- it at http://valgrind.org/support/bug_reports.html.\n--2307-- WARNING: unhandled riscv64-linux syscall: 258\n--2307-- You may be able to write your own handler.\n--2307-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2307-- Nevertheless we consider this a bug.  Please report\n--2307-- it at http://valgrind.org/support/bug_reports.html.\n--2307-- WARNING: unhandled riscv64-linux syscall: 258\n--2307-- You may be able to write your own handler.\n--2307-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2307-- Nevertheless we consider this a bug.  Please report\n--2307-- it at http://valgrind.org/support/bug_reports.html.\n--2307-- WARNING: unhandled riscv64-linux syscall: 258\n--2307-- You may be able to write your own handler.\n--2307-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2307-- Nevertheless we consider this a bug.  Please report\n--2307-- it at http://valgrind.org/support/bug_reports.html.\n--2307-- WARNING: unhandled riscv64-linux syscall: 258\n--2307-- You may be able to write your own handler.\n--2307-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2307-- Nevertheless we consider this a bug.  Please report\n--2307-- it at http://valgrind.org/support/bug_reports.html.\n--2307-- WARNING: unhandled riscv64-linux syscall: 258\n--2307-- You may be able to write your own handler.\n--2307-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2307-- Nevertheless we consider this a bug.  Please report\n--2307-- it at http://valgrind.org/support/bug_reports.html.\n--2307-- WARNING: unhandled riscv64-linux syscall: 258\n--2307-- You may be able to write your own handler.\n--2307-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2307-- Nevertheless we consider this a bug.  Please report\n--2307-- it at http://valgrind.org/support/bug_reports.html.\n--2307-- WARNING: unhandled riscv64-linux syscall: 258\n--2307-- You may be able to write your own handler.\n--2307-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2307-- Nevertheless we consider this a bug.  Please report\n--2307-- 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:
'--2315-- WARNING: unhandled riscv64-linux syscall: 258\n--2315-- You may be able to write your own handler.\n--2315-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2315-- Nevertheless we consider this a bug.  Please report\n--2315-- it at http://valgrind.org/support/bug_reports.html.\n--2315-- WARNING: unhandled riscv64-linux syscall: 258\n--2315-- You may be able to write your own handler.\n--2315-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2315-- Nevertheless we consider this a bug.  Please report\n--2315-- it at http://valgrind.org/support/bug_reports.html.\n--2315-- WARNING: unhandled riscv64-linux syscall: 258\n--2315-- You may be able to write your own handler.\n--2315-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2315-- Nevertheless we consider this a bug.  Please report\n--2315-- it at http://valgrind.org/support/bug_reports.html.\n--2315-- WARNING: unhandled riscv64-linux syscall: 258\n--2315-- You may be able to write your own handler.\n--2315-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2315-- Nevertheless we consider this a bug.  Please report\n--2315-- it at http://valgrind.org/support/bug_reports.html.\n--2315-- WARNING: unhandled riscv64-linux syscall: 258\n--2315-- You may be able to write your own handler.\n--2315-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2315-- Nevertheless we consider this a bug.  Please report\n--2315-- it at http://valgrind.org/support/bug_reports.html.\n--2315-- WARNING: unhandled riscv64-linux syscall: 258\n--2315-- You may be able to write your own handler.\n--2315-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2315-- Nevertheless we consider this a bug.  Please report\n--2315-- it at http://valgrind.org/support/bug_reports.html.\n--2315-- WARNING: unhandled riscv64-linux syscall: 258\n--2315-- You may be able to write your own handler.\n--2315-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2315-- Nevertheless we consider this a bug.  Please report\n--2315-- it at http://valgrind.org/support/bug_reports.html.\n--2315-- WARNING: unhandled riscv64-linux syscall: 258\n--2315-- You may be able to write your own handler.\n--2315-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2315-- Nevertheless we consider this a bug.  Please report\n--2315-- it at http://valgrind.org/support/bug_reports.html.\n--2315-- WARNING: unhandled riscv64-linux syscall: 258\n--2315-- You may be able to write your own handler.\n--2315-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2315-- Nevertheless we consider this a bug.  Please report\n--2315-- it at http://valgrind.org/support/bug_reports.html.\n--2315-- WARNING: unhandled riscv64-linux syscall: 258\n--2315-- You may be able to write your own handler.\n--2315-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2315-- Nevertheless we consider this a bug.  Please report\n--2315-- it at http://valgrind.org/support/bug_reports.html.\n--2315-- WARNING: unhandled riscv64-linux syscall: 258\n--2315-- You may be able to write your own handler.\n--2315-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2315-- Nevertheless we consider this a bug.  Please report\n--2315-- it at http://valgrind.org/support/bug_reports.html.\n--2315-- WARNING: unhandled riscv64-linux syscall: 258\n--2315-- You may be able to write your own handler.\n--2315-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2315-- Nevertheless we consider this a bug.  Please report\n--2315-- it at http://valgrind.org/support/bug_reports.html.\n--2315-- WARNING: unhandled riscv64-linux syscall: 258\n--2315-- You may be able to write your own handler.\n--2315-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2315-- Nevertheless we consider this a bug.  Please report\n--2315-- it at http://valgrind.org/support/bug_reports.html.\n--2315-- WARNING: unhandled riscv64-linux syscall: 258\n--2315-- You may be able to write your own handler.\n--2315-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2315-- Nevertheless we consider this a bug.  Please report\n--2315-- it at http://valgrind.org/support/bug_reports.html.\n--2315-- WARNING: unhandled riscv64-linux syscall: 258\n--2315-- You may be able to write your own handler.\n--2315-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2315-- Nevertheless we consider this a bug.  Please report\n--2315-- it at http://valgrind.org/support/bug_reports.html.\n--2315-- WARNING: unhandled riscv64-linux syscall: 258\n--2315-- You may be able to write your own handler.\n--2315-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2315-- Nevertheless we consider this a bug.  Please report\n--2315-- it at http://valgrind.org/support/bug_reports.html.\n--2315-- WARNING: unhandled riscv64-linux syscall: 258\n--2315-- You may be able to write your own handler.\n--2315-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2315-- Nevertheless we consider this a bug.  Please report\n--2315-- it at http://valgrind.org/support/bug_reports.html.\n--2315-- WARNING: unhandled riscv64-linux syscall: 258\n--2315-- You may be able to write your own handler.\n--2315-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2315-- Nevertheless we consider this a bug.  Please report\n--2315-- 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:
'--2323-- WARNING: unhandled riscv64-linux syscall: 258\n--2323-- You may be able to write your own handler.\n--2323-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2323-- Nevertheless we consider this a bug.  Please report\n--2323-- it at http://valgrind.org/support/bug_reports.html.\n--2323-- WARNING: unhandled riscv64-linux syscall: 258\n--2323-- You may be able to write your own handler.\n--2323-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2323-- Nevertheless we consider this a bug.  Please report\n--2323-- it at http://valgrind.org/support/bug_reports.html.\n--2323-- WARNING: unhandled riscv64-linux syscall: 258\n--2323-- You may be able to write your own handler.\n--2323-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2323-- Nevertheless we consider this a bug.  Please report\n--2323-- it at http://valgrind.org/support/bug_reports.html.\n--2323-- WARNING: unhandled riscv64-linux syscall: 258\n--2323-- You may be able to write your own handler.\n--2323-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2323-- Nevertheless we consider this a bug.  Please report\n--2323-- it at http://valgrind.org/support/bug_reports.html.\n--2323-- WARNING: unhandled riscv64-linux syscall: 258\n--2323-- You may be able to write your own handler.\n--2323-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2323-- Nevertheless we consider this a bug.  Please report\n--2323-- it at http://valgrind.org/support/bug_reports.html.\n--2323-- WARNING: unhandled riscv64-linux syscall: 258\n--2323-- You may be able to write your own handler.\n--2323-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2323-- Nevertheless we consider this a bug.  Please report\n--2323-- it at http://valgrind.org/support/bug_reports.html.\n--2323-- WARNING: unhandled riscv64-linux syscall: 258\n--2323-- You may be able to write your own handler.\n--2323-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2323-- Nevertheless we consider this a bug.  Please report\n--2323-- it at http://valgrind.org/support/bug_reports.html.\n--2323-- WARNING: unhandled riscv64-linux syscall: 258\n--2323-- You may be able to write your own handler.\n--2323-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2323-- Nevertheless we consider this a bug.  Please report\n--2323-- it at http://valgrind.org/support/bug_reports.html.\n--2323-- WARNING: unhandled riscv64-linux syscall: 258\n--2323-- You may be able to write your own handler.\n--2323-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2323-- Nevertheless we consider this a bug.  Please report\n--2323-- it at http://valgrind.org/support/bug_reports.html.\n--2323-- WARNING: unhandled riscv64-linux syscall: 258\n--2323-- You may be able to write your own handler.\n--2323-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2323-- Nevertheless we consider this a bug.  Please report\n--2323-- it at http://valgrind.org/support/bug_reports.html.\n--2323-- WARNING: unhandled riscv64-linux syscall: 258\n--2323-- You may be able to write your own handler.\n--2323-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2323-- Nevertheless we consider this a bug.  Please report\n--2323-- it at http://valgrind.org/support/bug_reports.html.\n--2323-- WARNING: unhandled riscv64-linux syscall: 258\n--2323-- You may be able to write your own handler.\n--2323-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2323-- Nevertheless we consider this a bug.  Please report\n--2323-- it at http://valgrind.org/support/bug_reports.html.\n--2323-- WARNING: unhandled riscv64-linux syscall: 258\n--2323-- You may be able to write your own handler.\n--2323-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2323-- Nevertheless we consider this a bug.  Please report\n--2323-- it at http://valgrind.org/support/bug_reports.html.\n--2323-- WARNING: unhandled riscv64-linux syscall: 258\n--2323-- You may be able to write your own handler.\n--2323-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2323-- Nevertheless we consider this a bug.  Please report\n--2323-- it at http://valgrind.org/support/bug_reports.html.\n--2323-- WARNING: unhandled riscv64-linux syscall: 258\n--2323-- You may be able to write your own handler.\n--2323-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2323-- Nevertheless we consider this a bug.  Please report\n--2323-- it at http://valgrind.org/support/bug_reports.html.\n--2323-- WARNING: unhandled riscv64-linux syscall: 258\n--2323-- You may be able to write your own handler.\n--2323-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2323-- Nevertheless we consider this a bug.  Please report\n--2323-- it at http://valgrind.org/support/bug_reports.html.\n--2323-- WARNING: unhandled riscv64-linux syscall: 258\n--2323-- You may be able to write your own handler.\n--2323-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2323-- Nevertheless we consider this a bug.  Please report\n--2323-- it at http://valgrind.org/support/bug_reports.html.\n--2323-- WARNING: unhandled riscv64-linux syscall: 258\n--2323-- You may be able to write your own handler.\n--2323-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2323-- Nevertheless we consider this a bug.  Please report\n--2323-- 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:
'--2331-- WARNING: unhandled riscv64-linux syscall: 258\n--2331-- You may be able to write your own handler.\n--2331-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2331-- Nevertheless we consider this a bug.  Please report\n--2331-- it at http://valgrind.org/support/bug_reports.html.\n--2331-- WARNING: unhandled riscv64-linux syscall: 258\n--2331-- You may be able to write your own handler.\n--2331-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2331-- Nevertheless we consider this a bug.  Please report\n--2331-- it at http://valgrind.org/support/bug_reports.html.\n--2331-- WARNING: unhandled riscv64-linux syscall: 258\n--2331-- You may be able to write your own handler.\n--2331-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2331-- Nevertheless we consider this a bug.  Please report\n--2331-- it at http://valgrind.org/support/bug_reports.html.\n--2331-- WARNING: unhandled riscv64-linux syscall: 258\n--2331-- You may be able to write your own handler.\n--2331-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2331-- Nevertheless we consider this a bug.  Please report\n--2331-- it at http://valgrind.org/support/bug_reports.html.\n--2331-- WARNING: unhandled riscv64-linux syscall: 258\n--2331-- You may be able to write your own handler.\n--2331-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2331-- Nevertheless we consider this a bug.  Please report\n--2331-- it at http://valgrind.org/support/bug_reports.html.\n--2331-- WARNING: unhandled riscv64-linux syscall: 258\n--2331-- You may be able to write your own handler.\n--2331-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2331-- Nevertheless we consider this a bug.  Please report\n--2331-- it at http://valgrind.org/support/bug_reports.html.\n--2331-- WARNING: unhandled riscv64-linux syscall: 258\n--2331-- You may be able to write your own handler.\n--2331-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2331-- Nevertheless we consider this a bug.  Please report\n--2331-- it at http://valgrind.org/support/bug_reports.html.\n--2331-- WARNING: unhandled riscv64-linux syscall: 258\n--2331-- You may be able to write your own handler.\n--2331-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2331-- Nevertheless we consider this a bug.  Please report\n--2331-- it at http://valgrind.org/support/bug_reports.html.\n--2331-- WARNING: unhandled riscv64-linux syscall: 258\n--2331-- You may be able to write your own handler.\n--2331-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2331-- Nevertheless we consider this a bug.  Please report\n--2331-- it at http://valgrind.org/support/bug_reports.html.\n--2331-- WARNING: unhandled riscv64-linux syscall: 258\n--2331-- You may be able to write your own handler.\n--2331-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2331-- Nevertheless we consider this a bug.  Please report\n--2331-- it at http://valgrind.org/support/bug_reports.html.\n--2331-- WARNING: unhandled riscv64-linux syscall: 258\n--2331-- You may be able to write your own handler.\n--2331-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2331-- Nevertheless we consider this a bug.  Please report\n--2331-- it at http://valgrind.org/support/bug_reports.html.\n--2331-- WARNING: unhandled riscv64-linux syscall: 258\n--2331-- You may be able to write your own handler.\n--2331-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2331-- Nevertheless we consider this a bug.  Please report\n--2331-- it at http://valgrind.org/support/bug_reports.html.\n--2331-- WARNING: unhandled riscv64-linux syscall: 258\n--2331-- You may be able to write your own handler.\n--2331-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2331-- Nevertheless we consider this a bug.  Please report\n--2331-- it at http://valgrind.org/support/bug_reports.html.\n--2331-- WARNING: unhandled riscv64-linux syscall: 258\n--2331-- You may be able to write your own handler.\n--2331-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2331-- Nevertheless we consider this a bug.  Please report\n--2331-- it at http://valgrind.org/support/bug_reports.html.\n--2331-- WARNING: unhandled riscv64-linux syscall: 258\n--2331-- You may be able to write your own handler.\n--2331-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2331-- Nevertheless we consider this a bug.  Please report\n--2331-- it at http://valgrind.org/support/bug_reports.html.\n--2331-- WARNING: unhandled riscv64-linux syscall: 258\n--2331-- You may be able to write your own handler.\n--2331-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2331-- Nevertheless we consider this a bug.  Please report\n--2331-- it at http://valgrind.org/support/bug_reports.html.\n--2331-- WARNING: unhandled riscv64-linux syscall: 258\n--2331-- You may be able to write your own handler.\n--2331-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2331-- Nevertheless we consider this a bug.  Please report\n--2331-- it at http://valgrind.org/support/bug_reports.html.\n--2331-- WARNING: unhandled riscv64-linux syscall: 258\n--2331-- You may be able to write your own handler.\n--2331-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2331-- Nevertheless we consider this a bug.  Please report\n--2331-- 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:
'--2339-- WARNING: unhandled riscv64-linux syscall: 258\n--2339-- You may be able to write your own handler.\n--2339-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2339-- Nevertheless we consider this a bug.  Please report\n--2339-- it at http://valgrind.org/support/bug_reports.html.\n--2339-- WARNING: unhandled riscv64-linux syscall: 258\n--2339-- You may be able to write your own handler.\n--2339-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2339-- Nevertheless we consider this a bug.  Please report\n--2339-- it at http://valgrind.org/support/bug_reports.html.\n--2339-- WARNING: unhandled riscv64-linux syscall: 258\n--2339-- You may be able to write your own handler.\n--2339-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2339-- Nevertheless we consider this a bug.  Please report\n--2339-- it at http://valgrind.org/support/bug_reports.html.\n--2339-- WARNING: unhandled riscv64-linux syscall: 258\n--2339-- You may be able to write your own handler.\n--2339-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2339-- Nevertheless we consider this a bug.  Please report\n--2339-- it at http://valgrind.org/support/bug_reports.html.\n--2339-- WARNING: unhandled riscv64-linux syscall: 258\n--2339-- You may be able to write your own handler.\n--2339-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2339-- Nevertheless we consider this a bug.  Please report\n--2339-- it at http://valgrind.org/support/bug_reports.html.\n--2339-- WARNING: unhandled riscv64-linux syscall: 258\n--2339-- You may be able to write your own handler.\n--2339-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2339-- Nevertheless we consider this a bug.  Please report\n--2339-- it at http://valgrind.org/support/bug_reports.html.\n--2339-- WARNING: unhandled riscv64-linux syscall: 258\n--2339-- You may be able to write your own handler.\n--2339-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2339-- Nevertheless we consider this a bug.  Please report\n--2339-- it at http://valgrind.org/support/bug_reports.html.\n--2339-- WARNING: unhandled riscv64-linux syscall: 258\n--2339-- You may be able to write your own handler.\n--2339-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2339-- Nevertheless we consider this a bug.  Please report\n--2339-- it at http://valgrind.org/support/bug_reports.html.\n--2339-- WARNING: unhandled riscv64-linux syscall: 258\n--2339-- You may be able to write your own handler.\n--2339-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2339-- Nevertheless we consider this a bug.  Please report\n--2339-- it at http://valgrind.org/support/bug_reports.html.\n--2339-- WARNING: unhandled riscv64-linux syscall: 258\n--2339-- You may be able to write your own handler.\n--2339-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2339-- Nevertheless we consider this a bug.  Please report\n--2339-- it at http://valgrind.org/support/bug_reports.html.\n--2339-- WARNING: unhandled riscv64-linux syscall: 258\n--2339-- You may be able to write your own handler.\n--2339-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2339-- Nevertheless we consider this a bug.  Please report\n--2339-- it at http://valgrind.org/support/bug_reports.html.\n--2339-- WARNING: unhandled riscv64-linux syscall: 258\n--2339-- You may be able to write your own handler.\n--2339-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2339-- Nevertheless we consider this a bug.  Please report\n--2339-- it at http://valgrind.org/support/bug_reports.html.\n--2339-- WARNING: unhandled riscv64-linux syscall: 258\n--2339-- You may be able to write your own handler.\n--2339-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2339-- Nevertheless we consider this a bug.  Please report\n--2339-- it at http://valgrind.org/support/bug_reports.html.\n--2339-- WARNING: unhandled riscv64-linux syscall: 258\n--2339-- You may be able to write your own handler.\n--2339-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2339-- Nevertheless we consider this a bug.  Please report\n--2339-- it at http://valgrind.org/support/bug_reports.html.\n--2339-- WARNING: unhandled riscv64-linux syscall: 258\n--2339-- You may be able to write your own handler.\n--2339-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2339-- Nevertheless we consider this a bug.  Please report\n--2339-- it at http://valgrind.org/support/bug_reports.html.\n--2339-- WARNING: unhandled riscv64-linux syscall: 258\n--2339-- You may be able to write your own handler.\n--2339-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2339-- Nevertheless we consider this a bug.  Please report\n--2339-- it at http://valgrind.org/support/bug_reports.html.\n--2339-- WARNING: unhandled riscv64-linux syscall: 258\n--2339-- You may be able to write your own handler.\n--2339-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2339-- Nevertheless we consider this a bug.  Please report\n--2339-- it at http://valgrind.org/support/bug_reports.html.\n--2339-- WARNING: unhandled riscv64-linux syscall: 258\n--2339-- You may be able to write your own handler.\n--2339-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2339-- Nevertheless we consider this a bug.  Please report\n--2339-- 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:
'--2347-- WARNING: unhandled riscv64-linux syscall: 258\n--2347-- You may be able to write your own handler.\n--2347-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2347-- Nevertheless we consider this a bug.  Please report\n--2347-- it at http://valgrind.org/support/bug_reports.html.\n--2347-- WARNING: unhandled riscv64-linux syscall: 258\n--2347-- You may be able to write your own handler.\n--2347-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2347-- Nevertheless we consider this a bug.  Please report\n--2347-- it at http://valgrind.org/support/bug_reports.html.\n--2347-- WARNING: unhandled riscv64-linux syscall: 258\n--2347-- You may be able to write your own handler.\n--2347-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2347-- Nevertheless we consider this a bug.  Please report\n--2347-- it at http://valgrind.org/support/bug_reports.html.\n--2347-- WARNING: unhandled riscv64-linux syscall: 258\n--2347-- You may be able to write your own handler.\n--2347-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2347-- Nevertheless we consider this a bug.  Please report\n--2347-- it at http://valgrind.org/support/bug_reports.html.\n--2347-- WARNING: unhandled riscv64-linux syscall: 258\n--2347-- You may be able to write your own handler.\n--2347-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2347-- Nevertheless we consider this a bug.  Please report\n--2347-- it at http://valgrind.org/support/bug_reports.html.\n--2347-- WARNING: unhandled riscv64-linux syscall: 258\n--2347-- You may be able to write your own handler.\n--2347-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2347-- Nevertheless we consider this a bug.  Please report\n--2347-- it at http://valgrind.org/support/bug_reports.html.\n--2347-- WARNING: unhandled riscv64-linux syscall: 258\n--2347-- You may be able to write your own handler.\n--2347-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2347-- Nevertheless we consider this a bug.  Please report\n--2347-- it at http://valgrind.org/support/bug_reports.html.\n--2347-- WARNING: unhandled riscv64-linux syscall: 258\n--2347-- You may be able to write your own handler.\n--2347-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2347-- Nevertheless we consider this a bug.  Please report\n--2347-- it at http://valgrind.org/support/bug_reports.html.\n--2347-- WARNING: unhandled riscv64-linux syscall: 258\n--2347-- You may be able to write your own handler.\n--2347-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2347-- Nevertheless we consider this a bug.  Please report\n--2347-- it at http://valgrind.org/support/bug_reports.html.\n--2347-- WARNING: unhandled riscv64-linux syscall: 258\n--2347-- You may be able to write your own handler.\n--2347-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2347-- Nevertheless we consider this a bug.  Please report\n--2347-- it at http://valgrind.org/support/bug_reports.html.\n--2347-- WARNING: unhandled riscv64-linux syscall: 258\n--2347-- You may be able to write your own handler.\n--2347-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2347-- Nevertheless we consider this a bug.  Please report\n--2347-- it at http://valgrind.org/support/bug_reports.html.\n--2347-- WARNING: unhandled riscv64-linux syscall: 258\n--2347-- You may be able to write your own handler.\n--2347-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2347-- Nevertheless we consider this a bug.  Please report\n--2347-- it at http://valgrind.org/support/bug_reports.html.\n--2347-- WARNING: unhandled riscv64-linux syscall: 258\n--2347-- You may be able to write your own handler.\n--2347-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2347-- Nevertheless we consider this a bug.  Please report\n--2347-- it at http://valgrind.org/support/bug_reports.html.\n--2347-- WARNING: unhandled riscv64-linux syscall: 258\n--2347-- You may be able to write your own handler.\n--2347-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2347-- Nevertheless we consider this a bug.  Please report\n--2347-- it at http://valgrind.org/support/bug_reports.html.\n--2347-- WARNING: unhandled riscv64-linux syscall: 258\n--2347-- You may be able to write your own handler.\n--2347-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2347-- Nevertheless we consider this a bug.  Please report\n--2347-- it at http://valgrind.org/support/bug_reports.html.\n--2347-- WARNING: unhandled riscv64-linux syscall: 258\n--2347-- You may be able to write your own handler.\n--2347-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2347-- Nevertheless we consider this a bug.  Please report\n--2347-- it at http://valgrind.org/support/bug_reports.html.\n--2347-- WARNING: unhandled riscv64-linux syscall: 258\n--2347-- You may be able to write your own handler.\n--2347-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2347-- Nevertheless we consider this a bug.  Please report\n--2347-- it at http://valgrind.org/support/bug_reports.html.\n--2347-- WARNING: unhandled riscv64-linux syscall: 258\n--2347-- You may be able to write your own handler.\n--2347-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2347-- Nevertheless we consider this a bug.  Please report\n--2347-- 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:
'--2355-- WARNING: unhandled riscv64-linux syscall: 258\n--2355-- You may be able to write your own handler.\n--2355-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2355-- Nevertheless we consider this a bug.  Please report\n--2355-- it at http://valgrind.org/support/bug_reports.html.\n--2355-- WARNING: unhandled riscv64-linux syscall: 258\n--2355-- You may be able to write your own handler.\n--2355-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2355-- Nevertheless we consider this a bug.  Please report\n--2355-- it at http://valgrind.org/support/bug_reports.html.\n--2355-- WARNING: unhandled riscv64-linux syscall: 258\n--2355-- You may be able to write your own handler.\n--2355-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2355-- Nevertheless we consider this a bug.  Please report\n--2355-- it at http://valgrind.org/support/bug_reports.html.\n--2355-- WARNING: unhandled riscv64-linux syscall: 258\n--2355-- You may be able to write your own handler.\n--2355-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2355-- Nevertheless we consider this a bug.  Please report\n--2355-- it at http://valgrind.org/support/bug_reports.html.\n--2355-- WARNING: unhandled riscv64-linux syscall: 258\n--2355-- You may be able to write your own handler.\n--2355-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2355-- Nevertheless we consider this a bug.  Please report\n--2355-- it at http://valgrind.org/support/bug_reports.html.\n--2355-- WARNING: unhandled riscv64-linux syscall: 258\n--2355-- You may be able to write your own handler.\n--2355-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2355-- Nevertheless we consider this a bug.  Please report\n--2355-- it at http://valgrind.org/support/bug_reports.html.\n--2355-- WARNING: unhandled riscv64-linux syscall: 258\n--2355-- You may be able to write your own handler.\n--2355-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2355-- Nevertheless we consider this a bug.  Please report\n--2355-- it at http://valgrind.org/support/bug_reports.html.\n--2355-- WARNING: unhandled riscv64-linux syscall: 258\n--2355-- You may be able to write your own handler.\n--2355-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2355-- Nevertheless we consider this a bug.  Please report\n--2355-- it at http://valgrind.org/support/bug_reports.html.\n--2355-- WARNING: unhandled riscv64-linux syscall: 258\n--2355-- You may be able to write your own handler.\n--2355-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2355-- Nevertheless we consider this a bug.  Please report\n--2355-- it at http://valgrind.org/support/bug_reports.html.\n--2355-- WARNING: unhandled riscv64-linux syscall: 258\n--2355-- You may be able to write your own handler.\n--2355-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2355-- Nevertheless we consider this a bug.  Please report\n--2355-- it at http://valgrind.org/support/bug_reports.html.\n--2355-- WARNING: unhandled riscv64-linux syscall: 258\n--2355-- You may be able to write your own handler.\n--2355-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2355-- Nevertheless we consider this a bug.  Please report\n--2355-- it at http://valgrind.org/support/bug_reports.html.\n--2355-- WARNING: unhandled riscv64-linux syscall: 258\n--2355-- You may be able to write your own handler.\n--2355-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2355-- Nevertheless we consider this a bug.  Please report\n--2355-- it at http://valgrind.org/support/bug_reports.html.\n--2355-- WARNING: unhandled riscv64-linux syscall: 258\n--2355-- You may be able to write your own handler.\n--2355-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2355-- Nevertheless we consider this a bug.  Please report\n--2355-- it at http://valgrind.org/support/bug_reports.html.\n--2355-- WARNING: unhandled riscv64-linux syscall: 258\n--2355-- You may be able to write your own handler.\n--2355-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2355-- Nevertheless we consider this a bug.  Please report\n--2355-- it at http://valgrind.org/support/bug_reports.html.\n--2355-- WARNING: unhandled riscv64-linux syscall: 258\n--2355-- You may be able to write your own handler.\n--2355-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2355-- Nevertheless we consider this a bug.  Please report\n--2355-- it at http://valgrind.org/support/bug_reports.html.\n--2355-- WARNING: unhandled riscv64-linux syscall: 258\n--2355-- You may be able to write your own handler.\n--2355-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2355-- Nevertheless we consider this a bug.  Please report\n--2355-- it at http://valgrind.org/support/bug_reports.html.\n--2355-- WARNING: unhandled riscv64-linux syscall: 258\n--2355-- You may be able to write your own handler.\n--2355-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2355-- Nevertheless we consider this a bug.  Please report\n--2355-- it at http://valgrind.org/support/bug_reports.html.\n--2355-- WARNING: unhandled riscv64-linux syscall: 258\n--2355-- You may be able to write your own handler.\n--2355-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2355-- Nevertheless we consider this a bug.  Please report\n--2355-- 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:
'--2363-- WARNING: unhandled riscv64-linux syscall: 258\n--2363-- You may be able to write your own handler.\n--2363-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2363-- Nevertheless we consider this a bug.  Please report\n--2363-- it at http://valgrind.org/support/bug_reports.html.\n--2363-- WARNING: unhandled riscv64-linux syscall: 258\n--2363-- You may be able to write your own handler.\n--2363-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2363-- Nevertheless we consider this a bug.  Please report\n--2363-- it at http://valgrind.org/support/bug_reports.html.\n--2363-- WARNING: unhandled riscv64-linux syscall: 258\n--2363-- You may be able to write your own handler.\n--2363-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2363-- Nevertheless we consider this a bug.  Please report\n--2363-- it at http://valgrind.org/support/bug_reports.html.\n--2363-- WARNING: unhandled riscv64-linux syscall: 258\n--2363-- You may be able to write your own handler.\n--2363-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2363-- Nevertheless we consider this a bug.  Please report\n--2363-- it at http://valgrind.org/support/bug_reports.html.\n--2363-- WARNING: unhandled riscv64-linux syscall: 258\n--2363-- You may be able to write your own handler.\n--2363-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2363-- Nevertheless we consider this a bug.  Please report\n--2363-- it at http://valgrind.org/support/bug_reports.html.\n--2363-- WARNING: unhandled riscv64-linux syscall: 258\n--2363-- You may be able to write your own handler.\n--2363-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2363-- Nevertheless we consider this a bug.  Please report\n--2363-- it at http://valgrind.org/support/bug_reports.html.\n--2363-- WARNING: unhandled riscv64-linux syscall: 258\n--2363-- You may be able to write your own handler.\n--2363-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2363-- Nevertheless we consider this a bug.  Please report\n--2363-- it at http://valgrind.org/support/bug_reports.html.\n--2363-- WARNING: unhandled riscv64-linux syscall: 258\n--2363-- You may be able to write your own handler.\n--2363-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2363-- Nevertheless we consider this a bug.  Please report\n--2363-- it at http://valgrind.org/support/bug_reports.html.\n--2363-- WARNING: unhandled riscv64-linux syscall: 258\n--2363-- You may be able to write your own handler.\n--2363-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2363-- Nevertheless we consider this a bug.  Please report\n--2363-- it at http://valgrind.org/support/bug_reports.html.\n--2363-- WARNING: unhandled riscv64-linux syscall: 258\n--2363-- You may be able to write your own handler.\n--2363-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2363-- Nevertheless we consider this a bug.  Please report\n--2363-- it at http://valgrind.org/support/bug_reports.html.\n--2363-- WARNING: unhandled riscv64-linux syscall: 258\n--2363-- You may be able to write your own handler.\n--2363-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2363-- Nevertheless we consider this a bug.  Please report\n--2363-- it at http://valgrind.org/support/bug_reports.html.\n--2363-- WARNING: unhandled riscv64-linux syscall: 258\n--2363-- You may be able to write your own handler.\n--2363-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2363-- Nevertheless we consider this a bug.  Please report\n--2363-- it at http://valgrind.org/support/bug_reports.html.\n--2363-- WARNING: unhandled riscv64-linux syscall: 258\n--2363-- You may be able to write your own handler.\n--2363-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2363-- Nevertheless we consider this a bug.  Please report\n--2363-- it at http://valgrind.org/support/bug_reports.html.\n--2363-- WARNING: unhandled riscv64-linux syscall: 258\n--2363-- You may be able to write your own handler.\n--2363-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2363-- Nevertheless we consider this a bug.  Please report\n--2363-- it at http://valgrind.org/support/bug_reports.html.\n--2363-- WARNING: unhandled riscv64-linux syscall: 258\n--2363-- You may be able to write your own handler.\n--2363-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2363-- Nevertheless we consider this a bug.  Please report\n--2363-- it at http://valgrind.org/support/bug_reports.html.\n--2363-- WARNING: unhandled riscv64-linux syscall: 258\n--2363-- You may be able to write your own handler.\n--2363-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2363-- Nevertheless we consider this a bug.  Please report\n--2363-- it at http://valgrind.org/support/bug_reports.html.\n--2363-- WARNING: unhandled riscv64-linux syscall: 258\n--2363-- You may be able to write your own handler.\n--2363-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2363-- Nevertheless we consider this a bug.  Please report\n--2363-- it at http://valgrind.org/support/bug_reports.html.\n--2363-- WARNING: unhandled riscv64-linux syscall: 258\n--2363-- You may be able to write your own handler.\n--2363-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2363-- Nevertheless we consider this a bug.  Please report\n--2363-- 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:
'--2371-- WARNING: unhandled riscv64-linux syscall: 258\n--2371-- You may be able to write your own handler.\n--2371-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2371-- Nevertheless we consider this a bug.  Please report\n--2371-- it at http://valgrind.org/support/bug_reports.html.\n--2371-- WARNING: unhandled riscv64-linux syscall: 258\n--2371-- You may be able to write your own handler.\n--2371-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2371-- Nevertheless we consider this a bug.  Please report\n--2371-- it at http://valgrind.org/support/bug_reports.html.\n--2371-- WARNING: unhandled riscv64-linux syscall: 258\n--2371-- You may be able to write your own handler.\n--2371-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2371-- Nevertheless we consider this a bug.  Please report\n--2371-- it at http://valgrind.org/support/bug_reports.html.\n--2371-- WARNING: unhandled riscv64-linux syscall: 258\n--2371-- You may be able to write your own handler.\n--2371-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2371-- Nevertheless we consider this a bug.  Please report\n--2371-- it at http://valgrind.org/support/bug_reports.html.\n--2371-- WARNING: unhandled riscv64-linux syscall: 258\n--2371-- You may be able to write your own handler.\n--2371-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2371-- Nevertheless we consider this a bug.  Please report\n--2371-- it at http://valgrind.org/support/bug_reports.html.\n--2371-- WARNING: unhandled riscv64-linux syscall: 258\n--2371-- You may be able to write your own handler.\n--2371-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2371-- Nevertheless we consider this a bug.  Please report\n--2371-- it at http://valgrind.org/support/bug_reports.html.\n--2371-- WARNING: unhandled riscv64-linux syscall: 258\n--2371-- You may be able to write your own handler.\n--2371-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2371-- Nevertheless we consider this a bug.  Please report\n--2371-- it at http://valgrind.org/support/bug_reports.html.\n--2371-- WARNING: unhandled riscv64-linux syscall: 258\n--2371-- You may be able to write your own handler.\n--2371-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2371-- Nevertheless we consider this a bug.  Please report\n--2371-- it at http://valgrind.org/support/bug_reports.html.\n--2371-- WARNING: unhandled riscv64-linux syscall: 258\n--2371-- You may be able to write your own handler.\n--2371-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2371-- Nevertheless we consider this a bug.  Please report\n--2371-- it at http://valgrind.org/support/bug_reports.html.\n--2371-- WARNING: unhandled riscv64-linux syscall: 258\n--2371-- You may be able to write your own handler.\n--2371-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2371-- Nevertheless we consider this a bug.  Please report\n--2371-- it at http://valgrind.org/support/bug_reports.html.\n--2371-- WARNING: unhandled riscv64-linux syscall: 258\n--2371-- You may be able to write your own handler.\n--2371-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2371-- Nevertheless we consider this a bug.  Please report\n--2371-- it at http://valgrind.org/support/bug_reports.html.\n--2371-- WARNING: unhandled riscv64-linux syscall: 258\n--2371-- You may be able to write your own handler.\n--2371-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2371-- Nevertheless we consider this a bug.  Please report\n--2371-- it at http://valgrind.org/support/bug_reports.html.\n--2371-- WARNING: unhandled riscv64-linux syscall: 258\n--2371-- You may be able to write your own handler.\n--2371-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2371-- Nevertheless we consider this a bug.  Please report\n--2371-- it at http://valgrind.org/support/bug_reports.html.\n--2371-- WARNING: unhandled riscv64-linux syscall: 258\n--2371-- You may be able to write your own handler.\n--2371-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2371-- Nevertheless we consider this a bug.  Please report\n--2371-- it at http://valgrind.org/support/bug_reports.html.\n--2371-- WARNING: unhandled riscv64-linux syscall: 258\n--2371-- You may be able to write your own handler.\n--2371-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2371-- Nevertheless we consider this a bug.  Please report\n--2371-- it at http://valgrind.org/support/bug_reports.html.\n--2371-- WARNING: unhandled riscv64-linux syscall: 258\n--2371-- You may be able to write your own handler.\n--2371-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2371-- Nevertheless we consider this a bug.  Please report\n--2371-- it at http://valgrind.org/support/bug_reports.html.\n--2371-- WARNING: unhandled riscv64-linux syscall: 258\n--2371-- You may be able to write your own handler.\n--2371-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2371-- Nevertheless we consider this a bug.  Please report\n--2371-- it at http://valgrind.org/support/bug_reports.html.\n--2371-- WARNING: unhandled riscv64-linux syscall: 258\n--2371-- You may be able to write your own handler.\n--2371-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2371-- Nevertheless we consider this a bug.  Please report\n--2371-- it at http://valgrind.org/support/bug_reports.html.\n'
137: failed	'http://example.com/?q=mr%00smith' --json --urlencode
--- stderr --- 
expected:
''
got:
'--2379-- WARNING: unhandled riscv64-linux syscall: 258\n--2379-- You may be able to write your own handler.\n--2379-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2379-- Nevertheless we consider this a bug.  Please report\n--2379-- it at http://valgrind.org/support/bug_reports.html.\n--2379-- WARNING: unhandled riscv64-linux syscall: 258\n--2379-- You may be able to write your own handler.\n--2379-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2379-- Nevertheless we consider this a bug.  Please report\n--2379-- it at http://valgrind.org/support/bug_reports.html.\n--2379-- WARNING: unhandled riscv64-linux syscall: 258\n--2379-- You may be able to write your own handler.\n--2379-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2379-- Nevertheless we consider this a bug.  Please report\n--2379-- it at http://valgrind.org/support/bug_reports.html.\n--2379-- WARNING: unhandled riscv64-linux syscall: 258\n--2379-- You may be able to write your own handler.\n--2379-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2379-- Nevertheless we consider this a bug.  Please report\n--2379-- it at http://valgrind.org/support/bug_reports.html.\n--2379-- WARNING: unhandled riscv64-linux syscall: 258\n--2379-- You may be able to write your own handler.\n--2379-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2379-- Nevertheless we consider this a bug.  Please report\n--2379-- it at http://valgrind.org/support/bug_reports.html.\n--2379-- WARNING: unhandled riscv64-linux syscall: 258\n--2379-- You may be able to write your own handler.\n--2379-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2379-- Nevertheless we consider this a bug.  Please report\n--2379-- it at http://valgrind.org/support/bug_reports.html.\n--2379-- WARNING: unhandled riscv64-linux syscall: 258\n--2379-- You may be able to write your own handler.\n--2379-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2379-- Nevertheless we consider this a bug.  Please report\n--2379-- it at http://valgrind.org/support/bug_reports.html.\n--2379-- WARNING: unhandled riscv64-linux syscall: 258\n--2379-- You may be able to write your own handler.\n--2379-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2379-- Nevertheless we consider this a bug.  Please report\n--2379-- it at http://valgrind.org/support/bug_reports.html.\n--2379-- WARNING: unhandled riscv64-linux syscall: 258\n--2379-- You may be able to write your own handler.\n--2379-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2379-- Nevertheless we consider this a bug.  Please report\n--2379-- it at http://valgrind.org/support/bug_reports.html.\n--2379-- WARNING: unhandled riscv64-linux syscall: 258\n--2379-- You may be able to write your own handler.\n--2379-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2379-- Nevertheless we consider this a bug.  Please report\n--2379-- it at http://valgrind.org/support/bug_reports.html.\n--2379-- WARNING: unhandled riscv64-linux syscall: 258\n--2379-- You may be able to write your own handler.\n--2379-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2379-- Nevertheless we consider this a bug.  Please report\n--2379-- it at http://valgrind.org/support/bug_reports.html.\n--2379-- WARNING: unhandled riscv64-linux syscall: 258\n--2379-- You may be able to write your own handler.\n--2379-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2379-- Nevertheless we consider this a bug.  Please report\n--2379-- it at http://valgrind.org/support/bug_reports.html.\n--2379-- WARNING: unhandled riscv64-linux syscall: 258\n--2379-- You may be able to write your own handler.\n--2379-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2379-- Nevertheless we consider this a bug.  Please report\n--2379-- it at http://valgrind.org/support/bug_reports.html.\n--2379-- WARNING: unhandled riscv64-linux syscall: 258\n--2379-- You may be able to write your own handler.\n--2379-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2379-- Nevertheless we consider this a bug.  Please report\n--2379-- it at http://valgrind.org/support/bug_reports.html.\n--2379-- WARNING: unhandled riscv64-linux syscall: 258\n--2379-- You may be able to write your own handler.\n--2379-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2379-- Nevertheless we consider this a bug.  Please report\n--2379-- it at http://valgrind.org/support/bug_reports.html.\n--2379-- WARNING: unhandled riscv64-linux syscall: 258\n--2379-- You may be able to write your own handler.\n--2379-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2379-- Nevertheless we consider this a bug.  Please report\n--2379-- it at http://valgrind.org/support/bug_reports.html.\n--2379-- WARNING: unhandled riscv64-linux syscall: 258\n--2379-- You may be able to write your own handler.\n--2379-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2379-- Nevertheless we consider this a bug.  Please report\n--2379-- it at http://valgrind.org/support/bug_reports.html.\n--2379-- WARNING: unhandled riscv64-linux syscall: 258\n--2379-- You may be able to write your own handler.\n--2379-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2379-- Nevertheless we consider this a bug.  Please report\n--2379-- 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:
'--2387-- WARNING: unhandled riscv64-linux syscall: 258\n--2387-- You may be able to write your own handler.\n--2387-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2387-- Nevertheless we consider this a bug.  Please report\n--2387-- it at http://valgrind.org/support/bug_reports.html.\n--2387-- WARNING: unhandled riscv64-linux syscall: 258\n--2387-- You may be able to write your own handler.\n--2387-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2387-- Nevertheless we consider this a bug.  Please report\n--2387-- it at http://valgrind.org/support/bug_reports.html.\n--2387-- WARNING: unhandled riscv64-linux syscall: 258\n--2387-- You may be able to write your own handler.\n--2387-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2387-- Nevertheless we consider this a bug.  Please report\n--2387-- it at http://valgrind.org/support/bug_reports.html.\n--2387-- WARNING: unhandled riscv64-linux syscall: 258\n--2387-- You may be able to write your own handler.\n--2387-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2387-- Nevertheless we consider this a bug.  Please report\n--2387-- it at http://valgrind.org/support/bug_reports.html.\n--2387-- WARNING: unhandled riscv64-linux syscall: 258\n--2387-- You may be able to write your own handler.\n--2387-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2387-- Nevertheless we consider this a bug.  Please report\n--2387-- it at http://valgrind.org/support/bug_reports.html.\n--2387-- WARNING: unhandled riscv64-linux syscall: 258\n--2387-- You may be able to write your own handler.\n--2387-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2387-- Nevertheless we consider this a bug.  Please report\n--2387-- it at http://valgrind.org/support/bug_reports.html.\n--2387-- WARNING: unhandled riscv64-linux syscall: 258\n--2387-- You may be able to write your own handler.\n--2387-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2387-- Nevertheless we consider this a bug.  Please report\n--2387-- it at http://valgrind.org/support/bug_reports.html.\n--2387-- WARNING: unhandled riscv64-linux syscall: 258\n--2387-- You may be able to write your own handler.\n--2387-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2387-- Nevertheless we consider this a bug.  Please report\n--2387-- it at http://valgrind.org/support/bug_reports.html.\n--2387-- WARNING: unhandled riscv64-linux syscall: 258\n--2387-- You may be able to write your own handler.\n--2387-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2387-- Nevertheless we consider this a bug.  Please report\n--2387-- it at http://valgrind.org/support/bug_reports.html.\n--2387-- WARNING: unhandled riscv64-linux syscall: 258\n--2387-- You may be able to write your own handler.\n--2387-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2387-- Nevertheless we consider this a bug.  Please report\n--2387-- it at http://valgrind.org/support/bug_reports.html.\n--2387-- WARNING: unhandled riscv64-linux syscall: 258\n--2387-- You may be able to write your own handler.\n--2387-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2387-- Nevertheless we consider this a bug.  Please report\n--2387-- it at http://valgrind.org/support/bug_reports.html.\n--2387-- WARNING: unhandled riscv64-linux syscall: 258\n--2387-- You may be able to write your own handler.\n--2387-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2387-- Nevertheless we consider this a bug.  Please report\n--2387-- it at http://valgrind.org/support/bug_reports.html.\n--2387-- WARNING: unhandled riscv64-linux syscall: 258\n--2387-- You may be able to write your own handler.\n--2387-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2387-- Nevertheless we consider this a bug.  Please report\n--2387-- it at http://valgrind.org/support/bug_reports.html.\n--2387-- WARNING: unhandled riscv64-linux syscall: 258\n--2387-- You may be able to write your own handler.\n--2387-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2387-- Nevertheless we consider this a bug.  Please report\n--2387-- it at http://valgrind.org/support/bug_reports.html.\n--2387-- WARNING: unhandled riscv64-linux syscall: 258\n--2387-- You may be able to write your own handler.\n--2387-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2387-- Nevertheless we consider this a bug.  Please report\n--2387-- it at http://valgrind.org/support/bug_reports.html.\n--2387-- WARNING: unhandled riscv64-linux syscall: 258\n--2387-- You may be able to write your own handler.\n--2387-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2387-- Nevertheless we consider this a bug.  Please report\n--2387-- it at http://valgrind.org/support/bug_reports.html.\n--2387-- WARNING: unhandled riscv64-linux syscall: 258\n--2387-- You may be able to write your own handler.\n--2387-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2387-- Nevertheless we consider this a bug.  Please report\n--2387-- it at http://valgrind.org/support/bug_reports.html.\n--2387-- WARNING: unhandled riscv64-linux syscall: 258\n--2387-- You may be able to write your own handler.\n--2387-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2387-- Nevertheless we consider this a bug.  Please report\n--2387-- 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:
'--2395-- WARNING: unhandled riscv64-linux syscall: 258\n--2395-- You may be able to write your own handler.\n--2395-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2395-- Nevertheless we consider this a bug.  Please report\n--2395-- it at http://valgrind.org/support/bug_reports.html.\n--2395-- WARNING: unhandled riscv64-linux syscall: 258\n--2395-- You may be able to write your own handler.\n--2395-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2395-- Nevertheless we consider this a bug.  Please report\n--2395-- it at http://valgrind.org/support/bug_reports.html.\n--2395-- WARNING: unhandled riscv64-linux syscall: 258\n--2395-- You may be able to write your own handler.\n--2395-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2395-- Nevertheless we consider this a bug.  Please report\n--2395-- it at http://valgrind.org/support/bug_reports.html.\n--2395-- WARNING: unhandled riscv64-linux syscall: 258\n--2395-- You may be able to write your own handler.\n--2395-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2395-- Nevertheless we consider this a bug.  Please report\n--2395-- it at http://valgrind.org/support/bug_reports.html.\n--2395-- WARNING: unhandled riscv64-linux syscall: 258\n--2395-- You may be able to write your own handler.\n--2395-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2395-- Nevertheless we consider this a bug.  Please report\n--2395-- it at http://valgrind.org/support/bug_reports.html.\n--2395-- WARNING: unhandled riscv64-linux syscall: 258\n--2395-- You may be able to write your own handler.\n--2395-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2395-- Nevertheless we consider this a bug.  Please report\n--2395-- it at http://valgrind.org/support/bug_reports.html.\n--2395-- WARNING: unhandled riscv64-linux syscall: 258\n--2395-- You may be able to write your own handler.\n--2395-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2395-- Nevertheless we consider this a bug.  Please report\n--2395-- it at http://valgrind.org/support/bug_reports.html.\n--2395-- WARNING: unhandled riscv64-linux syscall: 258\n--2395-- You may be able to write your own handler.\n--2395-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2395-- Nevertheless we consider this a bug.  Please report\n--2395-- it at http://valgrind.org/support/bug_reports.html.\n--2395-- WARNING: unhandled riscv64-linux syscall: 258\n--2395-- You may be able to write your own handler.\n--2395-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2395-- Nevertheless we consider this a bug.  Please report\n--2395-- it at http://valgrind.org/support/bug_reports.html.\n--2395-- WARNING: unhandled riscv64-linux syscall: 258\n--2395-- You may be able to write your own handler.\n--2395-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2395-- Nevertheless we consider this a bug.  Please report\n--2395-- it at http://valgrind.org/support/bug_reports.html.\n--2395-- WARNING: unhandled riscv64-linux syscall: 258\n--2395-- You may be able to write your own handler.\n--2395-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2395-- Nevertheless we consider this a bug.  Please report\n--2395-- it at http://valgrind.org/support/bug_reports.html.\n--2395-- WARNING: unhandled riscv64-linux syscall: 258\n--2395-- You may be able to write your own handler.\n--2395-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2395-- Nevertheless we consider this a bug.  Please report\n--2395-- it at http://valgrind.org/support/bug_reports.html.\n--2395-- WARNING: unhandled riscv64-linux syscall: 258\n--2395-- You may be able to write your own handler.\n--2395-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2395-- Nevertheless we consider this a bug.  Please report\n--2395-- it at http://valgrind.org/support/bug_reports.html.\n--2395-- WARNING: unhandled riscv64-linux syscall: 258\n--2395-- You may be able to write your own handler.\n--2395-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2395-- Nevertheless we consider this a bug.  Please report\n--2395-- it at http://valgrind.org/support/bug_reports.html.\n--2395-- WARNING: unhandled riscv64-linux syscall: 258\n--2395-- You may be able to write your own handler.\n--2395-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2395-- Nevertheless we consider this a bug.  Please report\n--2395-- it at http://valgrind.org/support/bug_reports.html.\n--2395-- WARNING: unhandled riscv64-linux syscall: 258\n--2395-- You may be able to write your own handler.\n--2395-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2395-- Nevertheless we consider this a bug.  Please report\n--2395-- it at http://valgrind.org/support/bug_reports.html.\n--2395-- WARNING: unhandled riscv64-linux syscall: 258\n--2395-- You may be able to write your own handler.\n--2395-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2395-- Nevertheless we consider this a bug.  Please report\n--2395-- it at http://valgrind.org/support/bug_reports.html.\n--2395-- WARNING: unhandled riscv64-linux syscall: 258\n--2395-- You may be able to write your own handler.\n--2395-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2395-- Nevertheless we consider this a bug.  Please report\n--2395-- 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:
'--2403-- WARNING: unhandled riscv64-linux syscall: 258\n--2403-- You may be able to write your own handler.\n--2403-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2403-- Nevertheless we consider this a bug.  Please report\n--2403-- it at http://valgrind.org/support/bug_reports.html.\n--2403-- WARNING: unhandled riscv64-linux syscall: 258\n--2403-- You may be able to write your own handler.\n--2403-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2403-- Nevertheless we consider this a bug.  Please report\n--2403-- it at http://valgrind.org/support/bug_reports.html.\n--2403-- WARNING: unhandled riscv64-linux syscall: 258\n--2403-- You may be able to write your own handler.\n--2403-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2403-- Nevertheless we consider this a bug.  Please report\n--2403-- it at http://valgrind.org/support/bug_reports.html.\n--2403-- WARNING: unhandled riscv64-linux syscall: 258\n--2403-- You may be able to write your own handler.\n--2403-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2403-- Nevertheless we consider this a bug.  Please report\n--2403-- it at http://valgrind.org/support/bug_reports.html.\n--2403-- WARNING: unhandled riscv64-linux syscall: 258\n--2403-- You may be able to write your own handler.\n--2403-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2403-- Nevertheless we consider this a bug.  Please report\n--2403-- it at http://valgrind.org/support/bug_reports.html.\n--2403-- WARNING: unhandled riscv64-linux syscall: 258\n--2403-- You may be able to write your own handler.\n--2403-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2403-- Nevertheless we consider this a bug.  Please report\n--2403-- it at http://valgrind.org/support/bug_reports.html.\n--2403-- WARNING: unhandled riscv64-linux syscall: 258\n--2403-- You may be able to write your own handler.\n--2403-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2403-- Nevertheless we consider this a bug.  Please report\n--2403-- it at http://valgrind.org/support/bug_reports.html.\n--2403-- WARNING: unhandled riscv64-linux syscall: 258\n--2403-- You may be able to write your own handler.\n--2403-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2403-- Nevertheless we consider this a bug.  Please report\n--2403-- it at http://valgrind.org/support/bug_reports.html.\n--2403-- WARNING: unhandled riscv64-linux syscall: 258\n--2403-- You may be able to write your own handler.\n--2403-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2403-- Nevertheless we consider this a bug.  Please report\n--2403-- it at http://valgrind.org/support/bug_reports.html.\n--2403-- WARNING: unhandled riscv64-linux syscall: 258\n--2403-- You may be able to write your own handler.\n--2403-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2403-- Nevertheless we consider this a bug.  Please report\n--2403-- it at http://valgrind.org/support/bug_reports.html.\n--2403-- WARNING: unhandled riscv64-linux syscall: 258\n--2403-- You may be able to write your own handler.\n--2403-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2403-- Nevertheless we consider this a bug.  Please report\n--2403-- it at http://valgrind.org/support/bug_reports.html.\n--2403-- WARNING: unhandled riscv64-linux syscall: 258\n--2403-- You may be able to write your own handler.\n--2403-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2403-- Nevertheless we consider this a bug.  Please report\n--2403-- it at http://valgrind.org/support/bug_reports.html.\n--2403-- WARNING: unhandled riscv64-linux syscall: 258\n--2403-- You may be able to write your own handler.\n--2403-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2403-- Nevertheless we consider this a bug.  Please report\n--2403-- it at http://valgrind.org/support/bug_reports.html.\n--2403-- WARNING: unhandled riscv64-linux syscall: 258\n--2403-- You may be able to write your own handler.\n--2403-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2403-- Nevertheless we consider this a bug.  Please report\n--2403-- it at http://valgrind.org/support/bug_reports.html.\n--2403-- WARNING: unhandled riscv64-linux syscall: 258\n--2403-- You may be able to write your own handler.\n--2403-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2403-- Nevertheless we consider this a bug.  Please report\n--2403-- it at http://valgrind.org/support/bug_reports.html.\n--2403-- WARNING: unhandled riscv64-linux syscall: 258\n--2403-- You may be able to write your own handler.\n--2403-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2403-- Nevertheless we consider this a bug.  Please report\n--2403-- it at http://valgrind.org/support/bug_reports.html.\n--2403-- WARNING: unhandled riscv64-linux syscall: 258\n--2403-- You may be able to write your own handler.\n--2403-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2403-- Nevertheless we consider this a bug.  Please report\n--2403-- it at http://valgrind.org/support/bug_reports.html.\n--2403-- WARNING: unhandled riscv64-linux syscall: 258\n--2403-- You may be able to write your own handler.\n--2403-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2403-- Nevertheless we consider this a bug.  Please report\n--2403-- 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:
'--2412-- WARNING: unhandled riscv64-linux syscall: 258\n--2412-- You may be able to write your own handler.\n--2412-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2412-- Nevertheless we consider this a bug.  Please report\n--2412-- it at http://valgrind.org/support/bug_reports.html.\n--2412-- WARNING: unhandled riscv64-linux syscall: 258\n--2412-- You may be able to write your own handler.\n--2412-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2412-- Nevertheless we consider this a bug.  Please report\n--2412-- it at http://valgrind.org/support/bug_reports.html.\n--2412-- WARNING: unhandled riscv64-linux syscall: 258\n--2412-- You may be able to write your own handler.\n--2412-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2412-- Nevertheless we consider this a bug.  Please report\n--2412-- it at http://valgrind.org/support/bug_reports.html.\n--2412-- WARNING: unhandled riscv64-linux syscall: 258\n--2412-- You may be able to write your own handler.\n--2412-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2412-- Nevertheless we consider this a bug.  Please report\n--2412-- it at http://valgrind.org/support/bug_reports.html.\n--2412-- WARNING: unhandled riscv64-linux syscall: 258\n--2412-- You may be able to write your own handler.\n--2412-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2412-- Nevertheless we consider this a bug.  Please report\n--2412-- it at http://valgrind.org/support/bug_reports.html.\n--2412-- WARNING: unhandled riscv64-linux syscall: 258\n--2412-- You may be able to write your own handler.\n--2412-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2412-- Nevertheless we consider this a bug.  Please report\n--2412-- it at http://valgrind.org/support/bug_reports.html.\n--2412-- WARNING: unhandled riscv64-linux syscall: 258\n--2412-- You may be able to write your own handler.\n--2412-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2412-- Nevertheless we consider this a bug.  Please report\n--2412-- it at http://valgrind.org/support/bug_reports.html.\n--2412-- WARNING: unhandled riscv64-linux syscall: 258\n--2412-- You may be able to write your own handler.\n--2412-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2412-- Nevertheless we consider this a bug.  Please report\n--2412-- it at http://valgrind.org/support/bug_reports.html.\n--2412-- WARNING: unhandled riscv64-linux syscall: 258\n--2412-- You may be able to write your own handler.\n--2412-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2412-- Nevertheless we consider this a bug.  Please report\n--2412-- it at http://valgrind.org/support/bug_reports.html.\n--2412-- WARNING: unhandled riscv64-linux syscall: 258\n--2412-- You may be able to write your own handler.\n--2412-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2412-- Nevertheless we consider this a bug.  Please report\n--2412-- it at http://valgrind.org/support/bug_reports.html.\n--2412-- WARNING: unhandled riscv64-linux syscall: 258\n--2412-- You may be able to write your own handler.\n--2412-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2412-- Nevertheless we consider this a bug.  Please report\n--2412-- it at http://valgrind.org/support/bug_reports.html.\n--2412-- WARNING: unhandled riscv64-linux syscall: 258\n--2412-- You may be able to write your own handler.\n--2412-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2412-- Nevertheless we consider this a bug.  Please report\n--2412-- it at http://valgrind.org/support/bug_reports.html.\n--2412-- WARNING: unhandled riscv64-linux syscall: 258\n--2412-- You may be able to write your own handler.\n--2412-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2412-- Nevertheless we consider this a bug.  Please report\n--2412-- it at http://valgrind.org/support/bug_reports.html.\n--2412-- WARNING: unhandled riscv64-linux syscall: 258\n--2412-- You may be able to write your own handler.\n--2412-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2412-- Nevertheless we consider this a bug.  Please report\n--2412-- it at http://valgrind.org/support/bug_reports.html.\n--2412-- WARNING: unhandled riscv64-linux syscall: 258\n--2412-- You may be able to write your own handler.\n--2412-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2412-- Nevertheless we consider this a bug.  Please report\n--2412-- it at http://valgrind.org/support/bug_reports.html.\n--2412-- WARNING: unhandled riscv64-linux syscall: 258\n--2412-- You may be able to write your own handler.\n--2412-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2412-- Nevertheless we consider this a bug.  Please report\n--2412-- it at http://valgrind.org/support/bug_reports.html.\n--2412-- WARNING: unhandled riscv64-linux syscall: 258\n--2412-- You may be able to write your own handler.\n--2412-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2412-- Nevertheless we consider this a bug.  Please report\n--2412-- it at http://valgrind.org/support/bug_reports.html.\n--2412-- WARNING: unhandled riscv64-linux syscall: 258\n--2412-- You may be able to write your own handler.\n--2412-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2412-- Nevertheless we consider this a bug.  Please report\n--2412-- 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:
'--2423-- WARNING: unhandled riscv64-linux syscall: 258\n--2423-- You may be able to write your own handler.\n--2423-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2423-- Nevertheless we consider this a bug.  Please report\n--2423-- it at http://valgrind.org/support/bug_reports.html.\n--2423-- WARNING: unhandled riscv64-linux syscall: 258\n--2423-- You may be able to write your own handler.\n--2423-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2423-- Nevertheless we consider this a bug.  Please report\n--2423-- it at http://valgrind.org/support/bug_reports.html.\n--2423-- WARNING: unhandled riscv64-linux syscall: 258\n--2423-- You may be able to write your own handler.\n--2423-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2423-- Nevertheless we consider this a bug.  Please report\n--2423-- it at http://valgrind.org/support/bug_reports.html.\n--2423-- WARNING: unhandled riscv64-linux syscall: 258\n--2423-- You may be able to write your own handler.\n--2423-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2423-- Nevertheless we consider this a bug.  Please report\n--2423-- it at http://valgrind.org/support/bug_reports.html.\n--2423-- WARNING: unhandled riscv64-linux syscall: 258\n--2423-- You may be able to write your own handler.\n--2423-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2423-- Nevertheless we consider this a bug.  Please report\n--2423-- it at http://valgrind.org/support/bug_reports.html.\n--2423-- WARNING: unhandled riscv64-linux syscall: 258\n--2423-- You may be able to write your own handler.\n--2423-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2423-- Nevertheless we consider this a bug.  Please report\n--2423-- it at http://valgrind.org/support/bug_reports.html.\n--2423-- WARNING: unhandled riscv64-linux syscall: 258\n--2423-- You may be able to write your own handler.\n--2423-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2423-- Nevertheless we consider this a bug.  Please report\n--2423-- it at http://valgrind.org/support/bug_reports.html.\n--2423-- WARNING: unhandled riscv64-linux syscall: 258\n--2423-- You may be able to write your own handler.\n--2423-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2423-- Nevertheless we consider this a bug.  Please report\n--2423-- it at http://valgrind.org/support/bug_reports.html.\n--2423-- WARNING: unhandled riscv64-linux syscall: 258\n--2423-- You may be able to write your own handler.\n--2423-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2423-- Nevertheless we consider this a bug.  Please report\n--2423-- it at http://valgrind.org/support/bug_reports.html.\n--2423-- WARNING: unhandled riscv64-linux syscall: 258\n--2423-- You may be able to write your own handler.\n--2423-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2423-- Nevertheless we consider this a bug.  Please report\n--2423-- it at http://valgrind.org/support/bug_reports.html.\n--2423-- WARNING: unhandled riscv64-linux syscall: 258\n--2423-- You may be able to write your own handler.\n--2423-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2423-- Nevertheless we consider this a bug.  Please report\n--2423-- it at http://valgrind.org/support/bug_reports.html.\n--2423-- WARNING: unhandled riscv64-linux syscall: 258\n--2423-- You may be able to write your own handler.\n--2423-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2423-- Nevertheless we consider this a bug.  Please report\n--2423-- it at http://valgrind.org/support/bug_reports.html.\n--2423-- WARNING: unhandled riscv64-linux syscall: 258\n--2423-- You may be able to write your own handler.\n--2423-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2423-- Nevertheless we consider this a bug.  Please report\n--2423-- it at http://valgrind.org/support/bug_reports.html.\n--2423-- WARNING: unhandled riscv64-linux syscall: 258\n--2423-- You may be able to write your own handler.\n--2423-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2423-- Nevertheless we consider this a bug.  Please report\n--2423-- it at http://valgrind.org/support/bug_reports.html.\n--2423-- WARNING: unhandled riscv64-linux syscall: 258\n--2423-- You may be able to write your own handler.\n--2423-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2423-- Nevertheless we consider this a bug.  Please report\n--2423-- it at http://valgrind.org/support/bug_reports.html.\n--2423-- WARNING: unhandled riscv64-linux syscall: 258\n--2423-- You may be able to write your own handler.\n--2423-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2423-- Nevertheless we consider this a bug.  Please report\n--2423-- it at http://valgrind.org/support/bug_reports.html.\n--2423-- WARNING: unhandled riscv64-linux syscall: 258\n--2423-- You may be able to write your own handler.\n--2423-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2423-- Nevertheless we consider this a bug.  Please report\n--2423-- it at http://valgrind.org/support/bug_reports.html.\n--2423-- WARNING: unhandled riscv64-linux syscall: 258\n--2423-- You may be able to write your own handler.\n--2423-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2423-- Nevertheless we consider this a bug.  Please report\n--2423-- 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:
'--2434-- WARNING: unhandled riscv64-linux syscall: 258\n--2434-- You may be able to write your own handler.\n--2434-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2434-- Nevertheless we consider this a bug.  Please report\n--2434-- it at http://valgrind.org/support/bug_reports.html.\n--2434-- WARNING: unhandled riscv64-linux syscall: 258\n--2434-- You may be able to write your own handler.\n--2434-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2434-- Nevertheless we consider this a bug.  Please report\n--2434-- it at http://valgrind.org/support/bug_reports.html.\n--2434-- WARNING: unhandled riscv64-linux syscall: 258\n--2434-- You may be able to write your own handler.\n--2434-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2434-- Nevertheless we consider this a bug.  Please report\n--2434-- it at http://valgrind.org/support/bug_reports.html.\n--2434-- WARNING: unhandled riscv64-linux syscall: 258\n--2434-- You may be able to write your own handler.\n--2434-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2434-- Nevertheless we consider this a bug.  Please report\n--2434-- it at http://valgrind.org/support/bug_reports.html.\n--2434-- WARNING: unhandled riscv64-linux syscall: 258\n--2434-- You may be able to write your own handler.\n--2434-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2434-- Nevertheless we consider this a bug.  Please report\n--2434-- it at http://valgrind.org/support/bug_reports.html.\n--2434-- WARNING: unhandled riscv64-linux syscall: 258\n--2434-- You may be able to write your own handler.\n--2434-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2434-- Nevertheless we consider this a bug.  Please report\n--2434-- it at http://valgrind.org/support/bug_reports.html.\n--2434-- WARNING: unhandled riscv64-linux syscall: 258\n--2434-- You may be able to write your own handler.\n--2434-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2434-- Nevertheless we consider this a bug.  Please report\n--2434-- it at http://valgrind.org/support/bug_reports.html.\n--2434-- WARNING: unhandled riscv64-linux syscall: 258\n--2434-- You may be able to write your own handler.\n--2434-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2434-- Nevertheless we consider this a bug.  Please report\n--2434-- it at http://valgrind.org/support/bug_reports.html.\n--2434-- WARNING: unhandled riscv64-linux syscall: 258\n--2434-- You may be able to write your own handler.\n--2434-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2434-- Nevertheless we consider this a bug.  Please report\n--2434-- it at http://valgrind.org/support/bug_reports.html.\n--2434-- WARNING: unhandled riscv64-linux syscall: 258\n--2434-- You may be able to write your own handler.\n--2434-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2434-- Nevertheless we consider this a bug.  Please report\n--2434-- it at http://valgrind.org/support/bug_reports.html.\n--2434-- WARNING: unhandled riscv64-linux syscall: 258\n--2434-- You may be able to write your own handler.\n--2434-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2434-- Nevertheless we consider this a bug.  Please report\n--2434-- it at http://valgrind.org/support/bug_reports.html.\n--2434-- WARNING: unhandled riscv64-linux syscall: 258\n--2434-- You may be able to write your own handler.\n--2434-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2434-- Nevertheless we consider this a bug.  Please report\n--2434-- it at http://valgrind.org/support/bug_reports.html.\n--2434-- WARNING: unhandled riscv64-linux syscall: 258\n--2434-- You may be able to write your own handler.\n--2434-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2434-- Nevertheless we consider this a bug.  Please report\n--2434-- it at http://valgrind.org/support/bug_reports.html.\n--2434-- WARNING: unhandled riscv64-linux syscall: 258\n--2434-- You may be able to write your own handler.\n--2434-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2434-- Nevertheless we consider this a bug.  Please report\n--2434-- it at http://valgrind.org/support/bug_reports.html.\n--2434-- WARNING: unhandled riscv64-linux syscall: 258\n--2434-- You may be able to write your own handler.\n--2434-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2434-- Nevertheless we consider this a bug.  Please report\n--2434-- it at http://valgrind.org/support/bug_reports.html.\n--2434-- WARNING: unhandled riscv64-linux syscall: 258\n--2434-- You may be able to write your own handler.\n--2434-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2434-- Nevertheless we consider this a bug.  Please report\n--2434-- it at http://valgrind.org/support/bug_reports.html.\n--2434-- WARNING: unhandled riscv64-linux syscall: 258\n--2434-- You may be able to write your own handler.\n--2434-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2434-- Nevertheless we consider this a bug.  Please report\n--2434-- it at http://valgrind.org/support/bug_reports.html.\n--2434-- WARNING: unhandled riscv64-linux syscall: 258\n--2434-- You may be able to write your own handler.\n--2434-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2434-- Nevertheless we consider this a bug.  Please report\n--2434-- 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:
'--2443-- WARNING: unhandled riscv64-linux syscall: 258\n--2443-- You may be able to write your own handler.\n--2443-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2443-- Nevertheless we consider this a bug.  Please report\n--2443-- it at http://valgrind.org/support/bug_reports.html.\n--2443-- WARNING: unhandled riscv64-linux syscall: 258\n--2443-- You may be able to write your own handler.\n--2443-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2443-- Nevertheless we consider this a bug.  Please report\n--2443-- it at http://valgrind.org/support/bug_reports.html.\n--2443-- WARNING: unhandled riscv64-linux syscall: 258\n--2443-- You may be able to write your own handler.\n--2443-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2443-- Nevertheless we consider this a bug.  Please report\n--2443-- it at http://valgrind.org/support/bug_reports.html.\n--2443-- WARNING: unhandled riscv64-linux syscall: 258\n--2443-- You may be able to write your own handler.\n--2443-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2443-- Nevertheless we consider this a bug.  Please report\n--2443-- it at http://valgrind.org/support/bug_reports.html.\n--2443-- WARNING: unhandled riscv64-linux syscall: 258\n--2443-- You may be able to write your own handler.\n--2443-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2443-- Nevertheless we consider this a bug.  Please report\n--2443-- it at http://valgrind.org/support/bug_reports.html.\n--2443-- WARNING: unhandled riscv64-linux syscall: 258\n--2443-- You may be able to write your own handler.\n--2443-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2443-- Nevertheless we consider this a bug.  Please report\n--2443-- it at http://valgrind.org/support/bug_reports.html.\n--2443-- WARNING: unhandled riscv64-linux syscall: 258\n--2443-- You may be able to write your own handler.\n--2443-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2443-- Nevertheless we consider this a bug.  Please report\n--2443-- it at http://valgrind.org/support/bug_reports.html.\n--2443-- WARNING: unhandled riscv64-linux syscall: 258\n--2443-- You may be able to write your own handler.\n--2443-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2443-- Nevertheless we consider this a bug.  Please report\n--2443-- it at http://valgrind.org/support/bug_reports.html.\n--2443-- WARNING: unhandled riscv64-linux syscall: 258\n--2443-- You may be able to write your own handler.\n--2443-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2443-- Nevertheless we consider this a bug.  Please report\n--2443-- it at http://valgrind.org/support/bug_reports.html.\n--2443-- WARNING: unhandled riscv64-linux syscall: 258\n--2443-- You may be able to write your own handler.\n--2443-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2443-- Nevertheless we consider this a bug.  Please report\n--2443-- it at http://valgrind.org/support/bug_reports.html.\n--2443-- WARNING: unhandled riscv64-linux syscall: 258\n--2443-- You may be able to write your own handler.\n--2443-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2443-- Nevertheless we consider this a bug.  Please report\n--2443-- it at http://valgrind.org/support/bug_reports.html.\n--2443-- WARNING: unhandled riscv64-linux syscall: 258\n--2443-- You may be able to write your own handler.\n--2443-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2443-- Nevertheless we consider this a bug.  Please report\n--2443-- it at http://valgrind.org/support/bug_reports.html.\n--2443-- WARNING: unhandled riscv64-linux syscall: 258\n--2443-- You may be able to write your own handler.\n--2443-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2443-- Nevertheless we consider this a bug.  Please report\n--2443-- it at http://valgrind.org/support/bug_reports.html.\n--2443-- WARNING: unhandled riscv64-linux syscall: 258\n--2443-- You may be able to write your own handler.\n--2443-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2443-- Nevertheless we consider this a bug.  Please report\n--2443-- it at http://valgrind.org/support/bug_reports.html.\n--2443-- WARNING: unhandled riscv64-linux syscall: 258\n--2443-- You may be able to write your own handler.\n--2443-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2443-- Nevertheless we consider this a bug.  Please report\n--2443-- it at http://valgrind.org/support/bug_reports.html.\n--2443-- WARNING: unhandled riscv64-linux syscall: 258\n--2443-- You may be able to write your own handler.\n--2443-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2443-- Nevertheless we consider this a bug.  Please report\n--2443-- it at http://valgrind.org/support/bug_reports.html.\n--2443-- WARNING: unhandled riscv64-linux syscall: 258\n--2443-- You may be able to write your own handler.\n--2443-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2443-- Nevertheless we consider this a bug.  Please report\n--2443-- it at http://valgrind.org/support/bug_reports.html.\n--2443-- WARNING: unhandled riscv64-linux syscall: 258\n--2443-- You may be able to write your own handler.\n--2443-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2443-- Nevertheless we consider this a bug.  Please report\n--2443-- 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:
'--2451-- WARNING: unhandled riscv64-linux syscall: 258\n--2451-- You may be able to write your own handler.\n--2451-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2451-- Nevertheless we consider this a bug.  Please report\n--2451-- it at http://valgrind.org/support/bug_reports.html.\n--2451-- WARNING: unhandled riscv64-linux syscall: 258\n--2451-- You may be able to write your own handler.\n--2451-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2451-- Nevertheless we consider this a bug.  Please report\n--2451-- it at http://valgrind.org/support/bug_reports.html.\n--2451-- WARNING: unhandled riscv64-linux syscall: 258\n--2451-- You may be able to write your own handler.\n--2451-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2451-- Nevertheless we consider this a bug.  Please report\n--2451-- it at http://valgrind.org/support/bug_reports.html.\n--2451-- WARNING: unhandled riscv64-linux syscall: 258\n--2451-- You may be able to write your own handler.\n--2451-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2451-- Nevertheless we consider this a bug.  Please report\n--2451-- it at http://valgrind.org/support/bug_reports.html.\n--2451-- WARNING: unhandled riscv64-linux syscall: 258\n--2451-- You may be able to write your own handler.\n--2451-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2451-- Nevertheless we consider this a bug.  Please report\n--2451-- it at http://valgrind.org/support/bug_reports.html.\n--2451-- WARNING: unhandled riscv64-linux syscall: 258\n--2451-- You may be able to write your own handler.\n--2451-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2451-- Nevertheless we consider this a bug.  Please report\n--2451-- it at http://valgrind.org/support/bug_reports.html.\n--2451-- WARNING: unhandled riscv64-linux syscall: 258\n--2451-- You may be able to write your own handler.\n--2451-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2451-- Nevertheless we consider this a bug.  Please report\n--2451-- it at http://valgrind.org/support/bug_reports.html.\n--2451-- WARNING: unhandled riscv64-linux syscall: 258\n--2451-- You may be able to write your own handler.\n--2451-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2451-- Nevertheless we consider this a bug.  Please report\n--2451-- it at http://valgrind.org/support/bug_reports.html.\n--2451-- WARNING: unhandled riscv64-linux syscall: 258\n--2451-- You may be able to write your own handler.\n--2451-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2451-- Nevertheless we consider this a bug.  Please report\n--2451-- it at http://valgrind.org/support/bug_reports.html.\n--2451-- WARNING: unhandled riscv64-linux syscall: 258\n--2451-- You may be able to write your own handler.\n--2451-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2451-- Nevertheless we consider this a bug.  Please report\n--2451-- it at http://valgrind.org/support/bug_reports.html.\n--2451-- WARNING: unhandled riscv64-linux syscall: 258\n--2451-- You may be able to write your own handler.\n--2451-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2451-- Nevertheless we consider this a bug.  Please report\n--2451-- it at http://valgrind.org/support/bug_reports.html.\n--2451-- WARNING: unhandled riscv64-linux syscall: 258\n--2451-- You may be able to write your own handler.\n--2451-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2451-- Nevertheless we consider this a bug.  Please report\n--2451-- it at http://valgrind.org/support/bug_reports.html.\n--2451-- WARNING: unhandled riscv64-linux syscall: 258\n--2451-- You may be able to write your own handler.\n--2451-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2451-- Nevertheless we consider this a bug.  Please report\n--2451-- it at http://valgrind.org/support/bug_reports.html.\n--2451-- WARNING: unhandled riscv64-linux syscall: 258\n--2451-- You may be able to write your own handler.\n--2451-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2451-- Nevertheless we consider this a bug.  Please report\n--2451-- it at http://valgrind.org/support/bug_reports.html.\n--2451-- WARNING: unhandled riscv64-linux syscall: 258\n--2451-- You may be able to write your own handler.\n--2451-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2451-- Nevertheless we consider this a bug.  Please report\n--2451-- it at http://valgrind.org/support/bug_reports.html.\n--2451-- WARNING: unhandled riscv64-linux syscall: 258\n--2451-- You may be able to write your own handler.\n--2451-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2451-- Nevertheless we consider this a bug.  Please report\n--2451-- it at http://valgrind.org/support/bug_reports.html.\n--2451-- WARNING: unhandled riscv64-linux syscall: 258\n--2451-- You may be able to write your own handler.\n--2451-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2451-- Nevertheless we consider this a bug.  Please report\n--2451-- it at http://valgrind.org/support/bug_reports.html.\n--2451-- WARNING: unhandled riscv64-linux syscall: 258\n--2451-- You may be able to write your own handler.\n--2451-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2451-- Nevertheless we consider this a bug.  Please report\n--2451-- 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:
'--2467-- WARNING: unhandled riscv64-linux syscall: 258\n--2467-- You may be able to write your own handler.\n--2467-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2467-- Nevertheless we consider this a bug.  Please report\n--2467-- it at http://valgrind.org/support/bug_reports.html.\n--2467-- WARNING: unhandled riscv64-linux syscall: 258\n--2467-- You may be able to write your own handler.\n--2467-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2467-- Nevertheless we consider this a bug.  Please report\n--2467-- it at http://valgrind.org/support/bug_reports.html.\n--2467-- WARNING: unhandled riscv64-linux syscall: 258\n--2467-- You may be able to write your own handler.\n--2467-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2467-- Nevertheless we consider this a bug.  Please report\n--2467-- it at http://valgrind.org/support/bug_reports.html.\n--2467-- WARNING: unhandled riscv64-linux syscall: 258\n--2467-- You may be able to write your own handler.\n--2467-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2467-- Nevertheless we consider this a bug.  Please report\n--2467-- it at http://valgrind.org/support/bug_reports.html.\n--2467-- WARNING: unhandled riscv64-linux syscall: 258\n--2467-- You may be able to write your own handler.\n--2467-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2467-- Nevertheless we consider this a bug.  Please report\n--2467-- it at http://valgrind.org/support/bug_reports.html.\n--2467-- WARNING: unhandled riscv64-linux syscall: 258\n--2467-- You may be able to write your own handler.\n--2467-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2467-- Nevertheless we consider this a bug.  Please report\n--2467-- it at http://valgrind.org/support/bug_reports.html.\n--2467-- WARNING: unhandled riscv64-linux syscall: 258\n--2467-- You may be able to write your own handler.\n--2467-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2467-- Nevertheless we consider this a bug.  Please report\n--2467-- it at http://valgrind.org/support/bug_reports.html.\n--2467-- WARNING: unhandled riscv64-linux syscall: 258\n--2467-- You may be able to write your own handler.\n--2467-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2467-- Nevertheless we consider this a bug.  Please report\n--2467-- it at http://valgrind.org/support/bug_reports.html.\n--2467-- WARNING: unhandled riscv64-linux syscall: 258\n--2467-- You may be able to write your own handler.\n--2467-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2467-- Nevertheless we consider this a bug.  Please report\n--2467-- it at http://valgrind.org/support/bug_reports.html.\n--2467-- WARNING: unhandled riscv64-linux syscall: 258\n--2467-- You may be able to write your own handler.\n--2467-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2467-- Nevertheless we consider this a bug.  Please report\n--2467-- it at http://valgrind.org/support/bug_reports.html.\n--2467-- WARNING: unhandled riscv64-linux syscall: 258\n--2467-- You may be able to write your own handler.\n--2467-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2467-- Nevertheless we consider this a bug.  Please report\n--2467-- it at http://valgrind.org/support/bug_reports.html.\n--2467-- WARNING: unhandled riscv64-linux syscall: 258\n--2467-- You may be able to write your own handler.\n--2467-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2467-- Nevertheless we consider this a bug.  Please report\n--2467-- it at http://valgrind.org/support/bug_reports.html.\n--2467-- WARNING: unhandled riscv64-linux syscall: 258\n--2467-- You may be able to write your own handler.\n--2467-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2467-- Nevertheless we consider this a bug.  Please report\n--2467-- it at http://valgrind.org/support/bug_reports.html.\n--2467-- WARNING: unhandled riscv64-linux syscall: 258\n--2467-- You may be able to write your own handler.\n--2467-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2467-- Nevertheless we consider this a bug.  Please report\n--2467-- it at http://valgrind.org/support/bug_reports.html.\n--2467-- WARNING: unhandled riscv64-linux syscall: 258\n--2467-- You may be able to write your own handler.\n--2467-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2467-- Nevertheless we consider this a bug.  Please report\n--2467-- it at http://valgrind.org/support/bug_reports.html.\n--2467-- WARNING: unhandled riscv64-linux syscall: 258\n--2467-- You may be able to write your own handler.\n--2467-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2467-- Nevertheless we consider this a bug.  Please report\n--2467-- it at http://valgrind.org/support/bug_reports.html.\n--2467-- WARNING: unhandled riscv64-linux syscall: 258\n--2467-- You may be able to write your own handler.\n--2467-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2467-- Nevertheless we consider this a bug.  Please report\n--2467-- it at http://valgrind.org/support/bug_reports.html.\n--2467-- WARNING: unhandled riscv64-linux syscall: 258\n--2467-- You may be able to write your own handler.\n--2467-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2467-- Nevertheless we consider this a bug.  Please report\n--2467-- 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:
'--2475-- WARNING: unhandled riscv64-linux syscall: 258\n--2475-- You may be able to write your own handler.\n--2475-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2475-- Nevertheless we consider this a bug.  Please report\n--2475-- it at http://valgrind.org/support/bug_reports.html.\n--2475-- WARNING: unhandled riscv64-linux syscall: 258\n--2475-- You may be able to write your own handler.\n--2475-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2475-- Nevertheless we consider this a bug.  Please report\n--2475-- it at http://valgrind.org/support/bug_reports.html.\n--2475-- WARNING: unhandled riscv64-linux syscall: 258\n--2475-- You may be able to write your own handler.\n--2475-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2475-- Nevertheless we consider this a bug.  Please report\n--2475-- it at http://valgrind.org/support/bug_reports.html.\n--2475-- WARNING: unhandled riscv64-linux syscall: 258\n--2475-- You may be able to write your own handler.\n--2475-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2475-- Nevertheless we consider this a bug.  Please report\n--2475-- it at http://valgrind.org/support/bug_reports.html.\n--2475-- WARNING: unhandled riscv64-linux syscall: 258\n--2475-- You may be able to write your own handler.\n--2475-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2475-- Nevertheless we consider this a bug.  Please report\n--2475-- it at http://valgrind.org/support/bug_reports.html.\n--2475-- WARNING: unhandled riscv64-linux syscall: 258\n--2475-- You may be able to write your own handler.\n--2475-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2475-- Nevertheless we consider this a bug.  Please report\n--2475-- it at http://valgrind.org/support/bug_reports.html.\n--2475-- WARNING: unhandled riscv64-linux syscall: 258\n--2475-- You may be able to write your own handler.\n--2475-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2475-- Nevertheless we consider this a bug.  Please report\n--2475-- it at http://valgrind.org/support/bug_reports.html.\n--2475-- WARNING: unhandled riscv64-linux syscall: 258\n--2475-- You may be able to write your own handler.\n--2475-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2475-- Nevertheless we consider this a bug.  Please report\n--2475-- it at http://valgrind.org/support/bug_reports.html.\n--2475-- WARNING: unhandled riscv64-linux syscall: 258\n--2475-- You may be able to write your own handler.\n--2475-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2475-- Nevertheless we consider this a bug.  Please report\n--2475-- it at http://valgrind.org/support/bug_reports.html.\n--2475-- WARNING: unhandled riscv64-linux syscall: 258\n--2475-- You may be able to write your own handler.\n--2475-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2475-- Nevertheless we consider this a bug.  Please report\n--2475-- it at http://valgrind.org/support/bug_reports.html.\n--2475-- WARNING: unhandled riscv64-linux syscall: 258\n--2475-- You may be able to write your own handler.\n--2475-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2475-- Nevertheless we consider this a bug.  Please report\n--2475-- it at http://valgrind.org/support/bug_reports.html.\n--2475-- WARNING: unhandled riscv64-linux syscall: 258\n--2475-- You may be able to write your own handler.\n--2475-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2475-- Nevertheless we consider this a bug.  Please report\n--2475-- it at http://valgrind.org/support/bug_reports.html.\n--2475-- WARNING: unhandled riscv64-linux syscall: 258\n--2475-- You may be able to write your own handler.\n--2475-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2475-- Nevertheless we consider this a bug.  Please report\n--2475-- it at http://valgrind.org/support/bug_reports.html.\n--2475-- WARNING: unhandled riscv64-linux syscall: 258\n--2475-- You may be able to write your own handler.\n--2475-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2475-- Nevertheless we consider this a bug.  Please report\n--2475-- it at http://valgrind.org/support/bug_reports.html.\n--2475-- WARNING: unhandled riscv64-linux syscall: 258\n--2475-- You may be able to write your own handler.\n--2475-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2475-- Nevertheless we consider this a bug.  Please report\n--2475-- it at http://valgrind.org/support/bug_reports.html.\n--2475-- WARNING: unhandled riscv64-linux syscall: 258\n--2475-- You may be able to write your own handler.\n--2475-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2475-- Nevertheless we consider this a bug.  Please report\n--2475-- it at http://valgrind.org/support/bug_reports.html.\n--2475-- WARNING: unhandled riscv64-linux syscall: 258\n--2475-- You may be able to write your own handler.\n--2475-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2475-- Nevertheless we consider this a bug.  Please report\n--2475-- it at http://valgrind.org/support/bug_reports.html.\n--2475-- WARNING: unhandled riscv64-linux syscall: 258\n--2475-- You may be able to write your own handler.\n--2475-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2475-- Nevertheless we consider this a bug.  Please report\n--2475-- 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:
'--2483-- WARNING: unhandled riscv64-linux syscall: 258\n--2483-- You may be able to write your own handler.\n--2483-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2483-- Nevertheless we consider this a bug.  Please report\n--2483-- it at http://valgrind.org/support/bug_reports.html.\n--2483-- WARNING: unhandled riscv64-linux syscall: 258\n--2483-- You may be able to write your own handler.\n--2483-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2483-- Nevertheless we consider this a bug.  Please report\n--2483-- it at http://valgrind.org/support/bug_reports.html.\n--2483-- WARNING: unhandled riscv64-linux syscall: 258\n--2483-- You may be able to write your own handler.\n--2483-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2483-- Nevertheless we consider this a bug.  Please report\n--2483-- it at http://valgrind.org/support/bug_reports.html.\n--2483-- WARNING: unhandled riscv64-linux syscall: 258\n--2483-- You may be able to write your own handler.\n--2483-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2483-- Nevertheless we consider this a bug.  Please report\n--2483-- it at http://valgrind.org/support/bug_reports.html.\n--2483-- WARNING: unhandled riscv64-linux syscall: 258\n--2483-- You may be able to write your own handler.\n--2483-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2483-- Nevertheless we consider this a bug.  Please report\n--2483-- it at http://valgrind.org/support/bug_reports.html.\n--2483-- WARNING: unhandled riscv64-linux syscall: 258\n--2483-- You may be able to write your own handler.\n--2483-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2483-- Nevertheless we consider this a bug.  Please report\n--2483-- it at http://valgrind.org/support/bug_reports.html.\n--2483-- WARNING: unhandled riscv64-linux syscall: 258\n--2483-- You may be able to write your own handler.\n--2483-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2483-- Nevertheless we consider this a bug.  Please report\n--2483-- it at http://valgrind.org/support/bug_reports.html.\n--2483-- WARNING: unhandled riscv64-linux syscall: 258\n--2483-- You may be able to write your own handler.\n--2483-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2483-- Nevertheless we consider this a bug.  Please report\n--2483-- it at http://valgrind.org/support/bug_reports.html.\n--2483-- WARNING: unhandled riscv64-linux syscall: 258\n--2483-- You may be able to write your own handler.\n--2483-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2483-- Nevertheless we consider this a bug.  Please report\n--2483-- it at http://valgrind.org/support/bug_reports.html.\n--2483-- WARNING: unhandled riscv64-linux syscall: 258\n--2483-- You may be able to write your own handler.\n--2483-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2483-- Nevertheless we consider this a bug.  Please report\n--2483-- it at http://valgrind.org/support/bug_reports.html.\n--2483-- WARNING: unhandled riscv64-linux syscall: 258\n--2483-- You may be able to write your own handler.\n--2483-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2483-- Nevertheless we consider this a bug.  Please report\n--2483-- it at http://valgrind.org/support/bug_reports.html.\n--2483-- WARNING: unhandled riscv64-linux syscall: 258\n--2483-- You may be able to write your own handler.\n--2483-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2483-- Nevertheless we consider this a bug.  Please report\n--2483-- it at http://valgrind.org/support/bug_reports.html.\n--2483-- WARNING: unhandled riscv64-linux syscall: 258\n--2483-- You may be able to write your own handler.\n--2483-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2483-- Nevertheless we consider this a bug.  Please report\n--2483-- it at http://valgrind.org/support/bug_reports.html.\n--2483-- WARNING: unhandled riscv64-linux syscall: 258\n--2483-- You may be able to write your own handler.\n--2483-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2483-- Nevertheless we consider this a bug.  Please report\n--2483-- it at http://valgrind.org/support/bug_reports.html.\n--2483-- WARNING: unhandled riscv64-linux syscall: 258\n--2483-- You may be able to write your own handler.\n--2483-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2483-- Nevertheless we consider this a bug.  Please report\n--2483-- it at http://valgrind.org/support/bug_reports.html.\n--2483-- WARNING: unhandled riscv64-linux syscall: 258\n--2483-- You may be able to write your own handler.\n--2483-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2483-- Nevertheless we consider this a bug.  Please report\n--2483-- it at http://valgrind.org/support/bug_reports.html.\n--2483-- WARNING: unhandled riscv64-linux syscall: 258\n--2483-- You may be able to write your own handler.\n--2483-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2483-- Nevertheless we consider this a bug.  Please report\n--2483-- it at http://valgrind.org/support/bug_reports.html.\n--2483-- WARNING: unhandled riscv64-linux syscall: 258\n--2483-- You may be able to write your own handler.\n--2483-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2483-- Nevertheless we consider this a bug.  Please report\n--2483-- 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:
'--2491-- WARNING: unhandled riscv64-linux syscall: 258\n--2491-- You may be able to write your own handler.\n--2491-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2491-- Nevertheless we consider this a bug.  Please report\n--2491-- it at http://valgrind.org/support/bug_reports.html.\n--2491-- WARNING: unhandled riscv64-linux syscall: 258\n--2491-- You may be able to write your own handler.\n--2491-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2491-- Nevertheless we consider this a bug.  Please report\n--2491-- it at http://valgrind.org/support/bug_reports.html.\n--2491-- WARNING: unhandled riscv64-linux syscall: 258\n--2491-- You may be able to write your own handler.\n--2491-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2491-- Nevertheless we consider this a bug.  Please report\n--2491-- it at http://valgrind.org/support/bug_reports.html.\n--2491-- WARNING: unhandled riscv64-linux syscall: 258\n--2491-- You may be able to write your own handler.\n--2491-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2491-- Nevertheless we consider this a bug.  Please report\n--2491-- it at http://valgrind.org/support/bug_reports.html.\n--2491-- WARNING: unhandled riscv64-linux syscall: 258\n--2491-- You may be able to write your own handler.\n--2491-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2491-- Nevertheless we consider this a bug.  Please report\n--2491-- it at http://valgrind.org/support/bug_reports.html.\n--2491-- WARNING: unhandled riscv64-linux syscall: 258\n--2491-- You may be able to write your own handler.\n--2491-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2491-- Nevertheless we consider this a bug.  Please report\n--2491-- it at http://valgrind.org/support/bug_reports.html.\n--2491-- WARNING: unhandled riscv64-linux syscall: 258\n--2491-- You may be able to write your own handler.\n--2491-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2491-- Nevertheless we consider this a bug.  Please report\n--2491-- it at http://valgrind.org/support/bug_reports.html.\n--2491-- WARNING: unhandled riscv64-linux syscall: 258\n--2491-- You may be able to write your own handler.\n--2491-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2491-- Nevertheless we consider this a bug.  Please report\n--2491-- it at http://valgrind.org/support/bug_reports.html.\n--2491-- WARNING: unhandled riscv64-linux syscall: 258\n--2491-- You may be able to write your own handler.\n--2491-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2491-- Nevertheless we consider this a bug.  Please report\n--2491-- it at http://valgrind.org/support/bug_reports.html.\n--2491-- WARNING: unhandled riscv64-linux syscall: 258\n--2491-- You may be able to write your own handler.\n--2491-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2491-- Nevertheless we consider this a bug.  Please report\n--2491-- it at http://valgrind.org/support/bug_reports.html.\n--2491-- WARNING: unhandled riscv64-linux syscall: 258\n--2491-- You may be able to write your own handler.\n--2491-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2491-- Nevertheless we consider this a bug.  Please report\n--2491-- it at http://valgrind.org/support/bug_reports.html.\n--2491-- WARNING: unhandled riscv64-linux syscall: 258\n--2491-- You may be able to write your own handler.\n--2491-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2491-- Nevertheless we consider this a bug.  Please report\n--2491-- it at http://valgrind.org/support/bug_reports.html.\n--2491-- WARNING: unhandled riscv64-linux syscall: 258\n--2491-- You may be able to write your own handler.\n--2491-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2491-- Nevertheless we consider this a bug.  Please report\n--2491-- it at http://valgrind.org/support/bug_reports.html.\n--2491-- WARNING: unhandled riscv64-linux syscall: 258\n--2491-- You may be able to write your own handler.\n--2491-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2491-- Nevertheless we consider this a bug.  Please report\n--2491-- it at http://valgrind.org/support/bug_reports.html.\n--2491-- WARNING: unhandled riscv64-linux syscall: 258\n--2491-- You may be able to write your own handler.\n--2491-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2491-- Nevertheless we consider this a bug.  Please report\n--2491-- it at http://valgrind.org/support/bug_reports.html.\n--2491-- WARNING: unhandled riscv64-linux syscall: 258\n--2491-- You may be able to write your own handler.\n--2491-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2491-- Nevertheless we consider this a bug.  Please report\n--2491-- it at http://valgrind.org/support/bug_reports.html.\n--2491-- WARNING: unhandled riscv64-linux syscall: 258\n--2491-- You may be able to write your own handler.\n--2491-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2491-- Nevertheless we consider this a bug.  Please report\n--2491-- it at http://valgrind.org/support/bug_reports.html.\n--2491-- WARNING: unhandled riscv64-linux syscall: 258\n--2491-- You may be able to write your own handler.\n--2491-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2491-- Nevertheless we consider this a bug.  Please report\n--2491-- 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:
'--2499-- WARNING: unhandled riscv64-linux syscall: 258\n--2499-- You may be able to write your own handler.\n--2499-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2499-- Nevertheless we consider this a bug.  Please report\n--2499-- it at http://valgrind.org/support/bug_reports.html.\n--2499-- WARNING: unhandled riscv64-linux syscall: 258\n--2499-- You may be able to write your own handler.\n--2499-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2499-- Nevertheless we consider this a bug.  Please report\n--2499-- it at http://valgrind.org/support/bug_reports.html.\n--2499-- WARNING: unhandled riscv64-linux syscall: 258\n--2499-- You may be able to write your own handler.\n--2499-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2499-- Nevertheless we consider this a bug.  Please report\n--2499-- it at http://valgrind.org/support/bug_reports.html.\n--2499-- WARNING: unhandled riscv64-linux syscall: 258\n--2499-- You may be able to write your own handler.\n--2499-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2499-- Nevertheless we consider this a bug.  Please report\n--2499-- it at http://valgrind.org/support/bug_reports.html.\n--2499-- WARNING: unhandled riscv64-linux syscall: 258\n--2499-- You may be able to write your own handler.\n--2499-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2499-- Nevertheless we consider this a bug.  Please report\n--2499-- it at http://valgrind.org/support/bug_reports.html.\n--2499-- WARNING: unhandled riscv64-linux syscall: 258\n--2499-- You may be able to write your own handler.\n--2499-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2499-- Nevertheless we consider this a bug.  Please report\n--2499-- it at http://valgrind.org/support/bug_reports.html.\n--2499-- WARNING: unhandled riscv64-linux syscall: 258\n--2499-- You may be able to write your own handler.\n--2499-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2499-- Nevertheless we consider this a bug.  Please report\n--2499-- it at http://valgrind.org/support/bug_reports.html.\n--2499-- WARNING: unhandled riscv64-linux syscall: 258\n--2499-- You may be able to write your own handler.\n--2499-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2499-- Nevertheless we consider this a bug.  Please report\n--2499-- it at http://valgrind.org/support/bug_reports.html.\n--2499-- WARNING: unhandled riscv64-linux syscall: 258\n--2499-- You may be able to write your own handler.\n--2499-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2499-- Nevertheless we consider this a bug.  Please report\n--2499-- it at http://valgrind.org/support/bug_reports.html.\n--2499-- WARNING: unhandled riscv64-linux syscall: 258\n--2499-- You may be able to write your own handler.\n--2499-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2499-- Nevertheless we consider this a bug.  Please report\n--2499-- it at http://valgrind.org/support/bug_reports.html.\n--2499-- WARNING: unhandled riscv64-linux syscall: 258\n--2499-- You may be able to write your own handler.\n--2499-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2499-- Nevertheless we consider this a bug.  Please report\n--2499-- it at http://valgrind.org/support/bug_reports.html.\n--2499-- WARNING: unhandled riscv64-linux syscall: 258\n--2499-- You may be able to write your own handler.\n--2499-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2499-- Nevertheless we consider this a bug.  Please report\n--2499-- it at http://valgrind.org/support/bug_reports.html.\n--2499-- WARNING: unhandled riscv64-linux syscall: 258\n--2499-- You may be able to write your own handler.\n--2499-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2499-- Nevertheless we consider this a bug.  Please report\n--2499-- it at http://valgrind.org/support/bug_reports.html.\n--2499-- WARNING: unhandled riscv64-linux syscall: 258\n--2499-- You may be able to write your own handler.\n--2499-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2499-- Nevertheless we consider this a bug.  Please report\n--2499-- it at http://valgrind.org/support/bug_reports.html.\n--2499-- WARNING: unhandled riscv64-linux syscall: 258\n--2499-- You may be able to write your own handler.\n--2499-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2499-- Nevertheless we consider this a bug.  Please report\n--2499-- it at http://valgrind.org/support/bug_reports.html.\n--2499-- WARNING: unhandled riscv64-linux syscall: 258\n--2499-- You may be able to write your own handler.\n--2499-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2499-- Nevertheless we consider this a bug.  Please report\n--2499-- it at http://valgrind.org/support/bug_reports.html.\n--2499-- WARNING: unhandled riscv64-linux syscall: 258\n--2499-- You may be able to write your own handler.\n--2499-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2499-- Nevertheless we consider this a bug.  Please report\n--2499-- it at http://valgrind.org/support/bug_reports.html.\n--2499-- WARNING: unhandled riscv64-linux syscall: 258\n--2499-- You may be able to write your own handler.\n--2499-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2499-- Nevertheless we consider this a bug.  Please report\n--2499-- 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:
'--2507-- WARNING: unhandled riscv64-linux syscall: 258\n--2507-- You may be able to write your own handler.\n--2507-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2507-- Nevertheless we consider this a bug.  Please report\n--2507-- it at http://valgrind.org/support/bug_reports.html.\n--2507-- WARNING: unhandled riscv64-linux syscall: 258\n--2507-- You may be able to write your own handler.\n--2507-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2507-- Nevertheless we consider this a bug.  Please report\n--2507-- it at http://valgrind.org/support/bug_reports.html.\n--2507-- WARNING: unhandled riscv64-linux syscall: 258\n--2507-- You may be able to write your own handler.\n--2507-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2507-- Nevertheless we consider this a bug.  Please report\n--2507-- it at http://valgrind.org/support/bug_reports.html.\n--2507-- WARNING: unhandled riscv64-linux syscall: 258\n--2507-- You may be able to write your own handler.\n--2507-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2507-- Nevertheless we consider this a bug.  Please report\n--2507-- it at http://valgrind.org/support/bug_reports.html.\n--2507-- WARNING: unhandled riscv64-linux syscall: 258\n--2507-- You may be able to write your own handler.\n--2507-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2507-- Nevertheless we consider this a bug.  Please report\n--2507-- it at http://valgrind.org/support/bug_reports.html.\n--2507-- WARNING: unhandled riscv64-linux syscall: 258\n--2507-- You may be able to write your own handler.\n--2507-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2507-- Nevertheless we consider this a bug.  Please report\n--2507-- it at http://valgrind.org/support/bug_reports.html.\n--2507-- WARNING: unhandled riscv64-linux syscall: 258\n--2507-- You may be able to write your own handler.\n--2507-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2507-- Nevertheless we consider this a bug.  Please report\n--2507-- it at http://valgrind.org/support/bug_reports.html.\n--2507-- WARNING: unhandled riscv64-linux syscall: 258\n--2507-- You may be able to write your own handler.\n--2507-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2507-- Nevertheless we consider this a bug.  Please report\n--2507-- it at http://valgrind.org/support/bug_reports.html.\n--2507-- WARNING: unhandled riscv64-linux syscall: 258\n--2507-- You may be able to write your own handler.\n--2507-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2507-- Nevertheless we consider this a bug.  Please report\n--2507-- it at http://valgrind.org/support/bug_reports.html.\n--2507-- WARNING: unhandled riscv64-linux syscall: 258\n--2507-- You may be able to write your own handler.\n--2507-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2507-- Nevertheless we consider this a bug.  Please report\n--2507-- it at http://valgrind.org/support/bug_reports.html.\n--2507-- WARNING: unhandled riscv64-linux syscall: 258\n--2507-- You may be able to write your own handler.\n--2507-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2507-- Nevertheless we consider this a bug.  Please report\n--2507-- it at http://valgrind.org/support/bug_reports.html.\n--2507-- WARNING: unhandled riscv64-linux syscall: 258\n--2507-- You may be able to write your own handler.\n--2507-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2507-- Nevertheless we consider this a bug.  Please report\n--2507-- it at http://valgrind.org/support/bug_reports.html.\n--2507-- WARNING: unhandled riscv64-linux syscall: 258\n--2507-- You may be able to write your own handler.\n--2507-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2507-- Nevertheless we consider this a bug.  Please report\n--2507-- it at http://valgrind.org/support/bug_reports.html.\n--2507-- WARNING: unhandled riscv64-linux syscall: 258\n--2507-- You may be able to write your own handler.\n--2507-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2507-- Nevertheless we consider this a bug.  Please report\n--2507-- it at http://valgrind.org/support/bug_reports.html.\n--2507-- WARNING: unhandled riscv64-linux syscall: 258\n--2507-- You may be able to write your own handler.\n--2507-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2507-- Nevertheless we consider this a bug.  Please report\n--2507-- it at http://valgrind.org/support/bug_reports.html.\n--2507-- WARNING: unhandled riscv64-linux syscall: 258\n--2507-- You may be able to write your own handler.\n--2507-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2507-- Nevertheless we consider this a bug.  Please report\n--2507-- it at http://valgrind.org/support/bug_reports.html.\n--2507-- WARNING: unhandled riscv64-linux syscall: 258\n--2507-- You may be able to write your own handler.\n--2507-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2507-- Nevertheless we consider this a bug.  Please report\n--2507-- it at http://valgrind.org/support/bug_reports.html.\n--2507-- WARNING: unhandled riscv64-linux syscall: 258\n--2507-- You may be able to write your own handler.\n--2507-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2507-- Nevertheless we consider this a bug.  Please report\n--2507-- 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:
'--2515-- WARNING: unhandled riscv64-linux syscall: 258\n--2515-- You may be able to write your own handler.\n--2515-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2515-- Nevertheless we consider this a bug.  Please report\n--2515-- it at http://valgrind.org/support/bug_reports.html.\n--2515-- WARNING: unhandled riscv64-linux syscall: 258\n--2515-- You may be able to write your own handler.\n--2515-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2515-- Nevertheless we consider this a bug.  Please report\n--2515-- it at http://valgrind.org/support/bug_reports.html.\n--2515-- WARNING: unhandled riscv64-linux syscall: 258\n--2515-- You may be able to write your own handler.\n--2515-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2515-- Nevertheless we consider this a bug.  Please report\n--2515-- it at http://valgrind.org/support/bug_reports.html.\n--2515-- WARNING: unhandled riscv64-linux syscall: 258\n--2515-- You may be able to write your own handler.\n--2515-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2515-- Nevertheless we consider this a bug.  Please report\n--2515-- it at http://valgrind.org/support/bug_reports.html.\n--2515-- WARNING: unhandled riscv64-linux syscall: 258\n--2515-- You may be able to write your own handler.\n--2515-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2515-- Nevertheless we consider this a bug.  Please report\n--2515-- it at http://valgrind.org/support/bug_reports.html.\n--2515-- WARNING: unhandled riscv64-linux syscall: 258\n--2515-- You may be able to write your own handler.\n--2515-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2515-- Nevertheless we consider this a bug.  Please report\n--2515-- it at http://valgrind.org/support/bug_reports.html.\n--2515-- WARNING: unhandled riscv64-linux syscall: 258\n--2515-- You may be able to write your own handler.\n--2515-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2515-- Nevertheless we consider this a bug.  Please report\n--2515-- it at http://valgrind.org/support/bug_reports.html.\n--2515-- WARNING: unhandled riscv64-linux syscall: 258\n--2515-- You may be able to write your own handler.\n--2515-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2515-- Nevertheless we consider this a bug.  Please report\n--2515-- it at http://valgrind.org/support/bug_reports.html.\n--2515-- WARNING: unhandled riscv64-linux syscall: 258\n--2515-- You may be able to write your own handler.\n--2515-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2515-- Nevertheless we consider this a bug.  Please report\n--2515-- it at http://valgrind.org/support/bug_reports.html.\n--2515-- WARNING: unhandled riscv64-linux syscall: 258\n--2515-- You may be able to write your own handler.\n--2515-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2515-- Nevertheless we consider this a bug.  Please report\n--2515-- it at http://valgrind.org/support/bug_reports.html.\n--2515-- WARNING: unhandled riscv64-linux syscall: 258\n--2515-- You may be able to write your own handler.\n--2515-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2515-- Nevertheless we consider this a bug.  Please report\n--2515-- it at http://valgrind.org/support/bug_reports.html.\n--2515-- WARNING: unhandled riscv64-linux syscall: 258\n--2515-- You may be able to write your own handler.\n--2515-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2515-- Nevertheless we consider this a bug.  Please report\n--2515-- it at http://valgrind.org/support/bug_reports.html.\n--2515-- WARNING: unhandled riscv64-linux syscall: 258\n--2515-- You may be able to write your own handler.\n--2515-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2515-- Nevertheless we consider this a bug.  Please report\n--2515-- it at http://valgrind.org/support/bug_reports.html.\n--2515-- WARNING: unhandled riscv64-linux syscall: 258\n--2515-- You may be able to write your own handler.\n--2515-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2515-- Nevertheless we consider this a bug.  Please report\n--2515-- it at http://valgrind.org/support/bug_reports.html.\n--2515-- WARNING: unhandled riscv64-linux syscall: 258\n--2515-- You may be able to write your own handler.\n--2515-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2515-- Nevertheless we consider this a bug.  Please report\n--2515-- it at http://valgrind.org/support/bug_reports.html.\n--2515-- WARNING: unhandled riscv64-linux syscall: 258\n--2515-- You may be able to write your own handler.\n--2515-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2515-- Nevertheless we consider this a bug.  Please report\n--2515-- it at http://valgrind.org/support/bug_reports.html.\n--2515-- WARNING: unhandled riscv64-linux syscall: 258\n--2515-- You may be able to write your own handler.\n--2515-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2515-- Nevertheless we consider this a bug.  Please report\n--2515-- it at http://valgrind.org/support/bug_reports.html.\n--2515-- WARNING: unhandled riscv64-linux syscall: 258\n--2515-- You may be able to write your own handler.\n--2515-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2515-- Nevertheless we consider this a bug.  Please report\n--2515-- 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:
'--2523-- WARNING: unhandled riscv64-linux syscall: 258\n--2523-- You may be able to write your own handler.\n--2523-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2523-- Nevertheless we consider this a bug.  Please report\n--2523-- it at http://valgrind.org/support/bug_reports.html.\n--2523-- WARNING: unhandled riscv64-linux syscall: 258\n--2523-- You may be able to write your own handler.\n--2523-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2523-- Nevertheless we consider this a bug.  Please report\n--2523-- it at http://valgrind.org/support/bug_reports.html.\n--2523-- WARNING: unhandled riscv64-linux syscall: 258\n--2523-- You may be able to write your own handler.\n--2523-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2523-- Nevertheless we consider this a bug.  Please report\n--2523-- it at http://valgrind.org/support/bug_reports.html.\n--2523-- WARNING: unhandled riscv64-linux syscall: 258\n--2523-- You may be able to write your own handler.\n--2523-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2523-- Nevertheless we consider this a bug.  Please report\n--2523-- it at http://valgrind.org/support/bug_reports.html.\n--2523-- WARNING: unhandled riscv64-linux syscall: 258\n--2523-- You may be able to write your own handler.\n--2523-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2523-- Nevertheless we consider this a bug.  Please report\n--2523-- it at http://valgrind.org/support/bug_reports.html.\n--2523-- WARNING: unhandled riscv64-linux syscall: 258\n--2523-- You may be able to write your own handler.\n--2523-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2523-- Nevertheless we consider this a bug.  Please report\n--2523-- it at http://valgrind.org/support/bug_reports.html.\n--2523-- WARNING: unhandled riscv64-linux syscall: 258\n--2523-- You may be able to write your own handler.\n--2523-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2523-- Nevertheless we consider this a bug.  Please report\n--2523-- it at http://valgrind.org/support/bug_reports.html.\n--2523-- WARNING: unhandled riscv64-linux syscall: 258\n--2523-- You may be able to write your own handler.\n--2523-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2523-- Nevertheless we consider this a bug.  Please report\n--2523-- it at http://valgrind.org/support/bug_reports.html.\n--2523-- WARNING: unhandled riscv64-linux syscall: 258\n--2523-- You may be able to write your own handler.\n--2523-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2523-- Nevertheless we consider this a bug.  Please report\n--2523-- it at http://valgrind.org/support/bug_reports.html.\n--2523-- WARNING: unhandled riscv64-linux syscall: 258\n--2523-- You may be able to write your own handler.\n--2523-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2523-- Nevertheless we consider this a bug.  Please report\n--2523-- it at http://valgrind.org/support/bug_reports.html.\n--2523-- WARNING: unhandled riscv64-linux syscall: 258\n--2523-- You may be able to write your own handler.\n--2523-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2523-- Nevertheless we consider this a bug.  Please report\n--2523-- it at http://valgrind.org/support/bug_reports.html.\n--2523-- WARNING: unhandled riscv64-linux syscall: 258\n--2523-- You may be able to write your own handler.\n--2523-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2523-- Nevertheless we consider this a bug.  Please report\n--2523-- it at http://valgrind.org/support/bug_reports.html.\n--2523-- WARNING: unhandled riscv64-linux syscall: 258\n--2523-- You may be able to write your own handler.\n--2523-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2523-- Nevertheless we consider this a bug.  Please report\n--2523-- it at http://valgrind.org/support/bug_reports.html.\n--2523-- WARNING: unhandled riscv64-linux syscall: 258\n--2523-- You may be able to write your own handler.\n--2523-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2523-- Nevertheless we consider this a bug.  Please report\n--2523-- it at http://valgrind.org/support/bug_reports.html.\n--2523-- WARNING: unhandled riscv64-linux syscall: 258\n--2523-- You may be able to write your own handler.\n--2523-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2523-- Nevertheless we consider this a bug.  Please report\n--2523-- it at http://valgrind.org/support/bug_reports.html.\n--2523-- WARNING: unhandled riscv64-linux syscall: 258\n--2523-- You may be able to write your own handler.\n--2523-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2523-- Nevertheless we consider this a bug.  Please report\n--2523-- it at http://valgrind.org/support/bug_reports.html.\n--2523-- WARNING: unhandled riscv64-linux syscall: 258\n--2523-- You may be able to write your own handler.\n--2523-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2523-- Nevertheless we consider this a bug.  Please report\n--2523-- it at http://valgrind.org/support/bug_reports.html.\n--2523-- WARNING: unhandled riscv64-linux syscall: 258\n--2523-- You may be able to write your own handler.\n--2523-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2523-- Nevertheless we consider this a bug.  Please report\n--2523-- 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:
'--2531-- WARNING: unhandled riscv64-linux syscall: 258\n--2531-- You may be able to write your own handler.\n--2531-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2531-- Nevertheless we consider this a bug.  Please report\n--2531-- it at http://valgrind.org/support/bug_reports.html.\n--2531-- WARNING: unhandled riscv64-linux syscall: 258\n--2531-- You may be able to write your own handler.\n--2531-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2531-- Nevertheless we consider this a bug.  Please report\n--2531-- it at http://valgrind.org/support/bug_reports.html.\n--2531-- WARNING: unhandled riscv64-linux syscall: 258\n--2531-- You may be able to write your own handler.\n--2531-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2531-- Nevertheless we consider this a bug.  Please report\n--2531-- it at http://valgrind.org/support/bug_reports.html.\n--2531-- WARNING: unhandled riscv64-linux syscall: 258\n--2531-- You may be able to write your own handler.\n--2531-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2531-- Nevertheless we consider this a bug.  Please report\n--2531-- it at http://valgrind.org/support/bug_reports.html.\n--2531-- WARNING: unhandled riscv64-linux syscall: 258\n--2531-- You may be able to write your own handler.\n--2531-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2531-- Nevertheless we consider this a bug.  Please report\n--2531-- it at http://valgrind.org/support/bug_reports.html.\n--2531-- WARNING: unhandled riscv64-linux syscall: 258\n--2531-- You may be able to write your own handler.\n--2531-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2531-- Nevertheless we consider this a bug.  Please report\n--2531-- it at http://valgrind.org/support/bug_reports.html.\n--2531-- WARNING: unhandled riscv64-linux syscall: 258\n--2531-- You may be able to write your own handler.\n--2531-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2531-- Nevertheless we consider this a bug.  Please report\n--2531-- it at http://valgrind.org/support/bug_reports.html.\n--2531-- WARNING: unhandled riscv64-linux syscall: 258\n--2531-- You may be able to write your own handler.\n--2531-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2531-- Nevertheless we consider this a bug.  Please report\n--2531-- it at http://valgrind.org/support/bug_reports.html.\n--2531-- WARNING: unhandled riscv64-linux syscall: 258\n--2531-- You may be able to write your own handler.\n--2531-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2531-- Nevertheless we consider this a bug.  Please report\n--2531-- it at http://valgrind.org/support/bug_reports.html.\n--2531-- WARNING: unhandled riscv64-linux syscall: 258\n--2531-- You may be able to write your own handler.\n--2531-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2531-- Nevertheless we consider this a bug.  Please report\n--2531-- it at http://valgrind.org/support/bug_reports.html.\n--2531-- WARNING: unhandled riscv64-linux syscall: 258\n--2531-- You may be able to write your own handler.\n--2531-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2531-- Nevertheless we consider this a bug.  Please report\n--2531-- it at http://valgrind.org/support/bug_reports.html.\n--2531-- WARNING: unhandled riscv64-linux syscall: 258\n--2531-- You may be able to write your own handler.\n--2531-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2531-- Nevertheless we consider this a bug.  Please report\n--2531-- it at http://valgrind.org/support/bug_reports.html.\n--2531-- WARNING: unhandled riscv64-linux syscall: 258\n--2531-- You may be able to write your own handler.\n--2531-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2531-- Nevertheless we consider this a bug.  Please report\n--2531-- it at http://valgrind.org/support/bug_reports.html.\n--2531-- WARNING: unhandled riscv64-linux syscall: 258\n--2531-- You may be able to write your own handler.\n--2531-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2531-- Nevertheless we consider this a bug.  Please report\n--2531-- it at http://valgrind.org/support/bug_reports.html.\n--2531-- WARNING: unhandled riscv64-linux syscall: 258\n--2531-- You may be able to write your own handler.\n--2531-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2531-- Nevertheless we consider this a bug.  Please report\n--2531-- it at http://valgrind.org/support/bug_reports.html.\n--2531-- WARNING: unhandled riscv64-linux syscall: 258\n--2531-- You may be able to write your own handler.\n--2531-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2531-- Nevertheless we consider this a bug.  Please report\n--2531-- it at http://valgrind.org/support/bug_reports.html.\n--2531-- WARNING: unhandled riscv64-linux syscall: 258\n--2531-- You may be able to write your own handler.\n--2531-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2531-- Nevertheless we consider this a bug.  Please report\n--2531-- it at http://valgrind.org/support/bug_reports.html.\n--2531-- WARNING: unhandled riscv64-linux syscall: 258\n--2531-- You may be able to write your own handler.\n--2531-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2531-- Nevertheless we consider this a bug.  Please report\n--2531-- 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:
'--2539-- WARNING: unhandled riscv64-linux syscall: 258\n--2539-- You may be able to write your own handler.\n--2539-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2539-- Nevertheless we consider this a bug.  Please report\n--2539-- it at http://valgrind.org/support/bug_reports.html.\n--2539-- WARNING: unhandled riscv64-linux syscall: 258\n--2539-- You may be able to write your own handler.\n--2539-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2539-- Nevertheless we consider this a bug.  Please report\n--2539-- it at http://valgrind.org/support/bug_reports.html.\n--2539-- WARNING: unhandled riscv64-linux syscall: 258\n--2539-- You may be able to write your own handler.\n--2539-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2539-- Nevertheless we consider this a bug.  Please report\n--2539-- it at http://valgrind.org/support/bug_reports.html.\n--2539-- WARNING: unhandled riscv64-linux syscall: 258\n--2539-- You may be able to write your own handler.\n--2539-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2539-- Nevertheless we consider this a bug.  Please report\n--2539-- it at http://valgrind.org/support/bug_reports.html.\n--2539-- WARNING: unhandled riscv64-linux syscall: 258\n--2539-- You may be able to write your own handler.\n--2539-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2539-- Nevertheless we consider this a bug.  Please report\n--2539-- it at http://valgrind.org/support/bug_reports.html.\n--2539-- WARNING: unhandled riscv64-linux syscall: 258\n--2539-- You may be able to write your own handler.\n--2539-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2539-- Nevertheless we consider this a bug.  Please report\n--2539-- it at http://valgrind.org/support/bug_reports.html.\n--2539-- WARNING: unhandled riscv64-linux syscall: 258\n--2539-- You may be able to write your own handler.\n--2539-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2539-- Nevertheless we consider this a bug.  Please report\n--2539-- it at http://valgrind.org/support/bug_reports.html.\n--2539-- WARNING: unhandled riscv64-linux syscall: 258\n--2539-- You may be able to write your own handler.\n--2539-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2539-- Nevertheless we consider this a bug.  Please report\n--2539-- it at http://valgrind.org/support/bug_reports.html.\n--2539-- WARNING: unhandled riscv64-linux syscall: 258\n--2539-- You may be able to write your own handler.\n--2539-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2539-- Nevertheless we consider this a bug.  Please report\n--2539-- it at http://valgrind.org/support/bug_reports.html.\n--2539-- WARNING: unhandled riscv64-linux syscall: 258\n--2539-- You may be able to write your own handler.\n--2539-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2539-- Nevertheless we consider this a bug.  Please report\n--2539-- it at http://valgrind.org/support/bug_reports.html.\n--2539-- WARNING: unhandled riscv64-linux syscall: 258\n--2539-- You may be able to write your own handler.\n--2539-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2539-- Nevertheless we consider this a bug.  Please report\n--2539-- it at http://valgrind.org/support/bug_reports.html.\n--2539-- WARNING: unhandled riscv64-linux syscall: 258\n--2539-- You may be able to write your own handler.\n--2539-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2539-- Nevertheless we consider this a bug.  Please report\n--2539-- it at http://valgrind.org/support/bug_reports.html.\n--2539-- WARNING: unhandled riscv64-linux syscall: 258\n--2539-- You may be able to write your own handler.\n--2539-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2539-- Nevertheless we consider this a bug.  Please report\n--2539-- it at http://valgrind.org/support/bug_reports.html.\n--2539-- WARNING: unhandled riscv64-linux syscall: 258\n--2539-- You may be able to write your own handler.\n--2539-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2539-- Nevertheless we consider this a bug.  Please report\n--2539-- it at http://valgrind.org/support/bug_reports.html.\n--2539-- WARNING: unhandled riscv64-linux syscall: 258\n--2539-- You may be able to write your own handler.\n--2539-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2539-- Nevertheless we consider this a bug.  Please report\n--2539-- it at http://valgrind.org/support/bug_reports.html.\n--2539-- WARNING: unhandled riscv64-linux syscall: 258\n--2539-- You may be able to write your own handler.\n--2539-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2539-- Nevertheless we consider this a bug.  Please report\n--2539-- it at http://valgrind.org/support/bug_reports.html.\n--2539-- WARNING: unhandled riscv64-linux syscall: 258\n--2539-- You may be able to write your own handler.\n--2539-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2539-- Nevertheless we consider this a bug.  Please report\n--2539-- it at http://valgrind.org/support/bug_reports.html.\n--2539-- WARNING: unhandled riscv64-linux syscall: 258\n--2539-- You may be able to write your own handler.\n--2539-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2539-- Nevertheless we consider this a bug.  Please report\n--2539-- 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:
'--2547-- WARNING: unhandled riscv64-linux syscall: 258\n--2547-- You may be able to write your own handler.\n--2547-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2547-- Nevertheless we consider this a bug.  Please report\n--2547-- it at http://valgrind.org/support/bug_reports.html.\n--2547-- WARNING: unhandled riscv64-linux syscall: 258\n--2547-- You may be able to write your own handler.\n--2547-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2547-- Nevertheless we consider this a bug.  Please report\n--2547-- it at http://valgrind.org/support/bug_reports.html.\n--2547-- WARNING: unhandled riscv64-linux syscall: 258\n--2547-- You may be able to write your own handler.\n--2547-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2547-- Nevertheless we consider this a bug.  Please report\n--2547-- it at http://valgrind.org/support/bug_reports.html.\n--2547-- WARNING: unhandled riscv64-linux syscall: 258\n--2547-- You may be able to write your own handler.\n--2547-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2547-- Nevertheless we consider this a bug.  Please report\n--2547-- it at http://valgrind.org/support/bug_reports.html.\n--2547-- WARNING: unhandled riscv64-linux syscall: 258\n--2547-- You may be able to write your own handler.\n--2547-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2547-- Nevertheless we consider this a bug.  Please report\n--2547-- it at http://valgrind.org/support/bug_reports.html.\n--2547-- WARNING: unhandled riscv64-linux syscall: 258\n--2547-- You may be able to write your own handler.\n--2547-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2547-- Nevertheless we consider this a bug.  Please report\n--2547-- it at http://valgrind.org/support/bug_reports.html.\n--2547-- WARNING: unhandled riscv64-linux syscall: 258\n--2547-- You may be able to write your own handler.\n--2547-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2547-- Nevertheless we consider this a bug.  Please report\n--2547-- it at http://valgrind.org/support/bug_reports.html.\n--2547-- WARNING: unhandled riscv64-linux syscall: 258\n--2547-- You may be able to write your own handler.\n--2547-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2547-- Nevertheless we consider this a bug.  Please report\n--2547-- it at http://valgrind.org/support/bug_reports.html.\n--2547-- WARNING: unhandled riscv64-linux syscall: 258\n--2547-- You may be able to write your own handler.\n--2547-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2547-- Nevertheless we consider this a bug.  Please report\n--2547-- it at http://valgrind.org/support/bug_reports.html.\n--2547-- WARNING: unhandled riscv64-linux syscall: 258\n--2547-- You may be able to write your own handler.\n--2547-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2547-- Nevertheless we consider this a bug.  Please report\n--2547-- it at http://valgrind.org/support/bug_reports.html.\n--2547-- WARNING: unhandled riscv64-linux syscall: 258\n--2547-- You may be able to write your own handler.\n--2547-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2547-- Nevertheless we consider this a bug.  Please report\n--2547-- it at http://valgrind.org/support/bug_reports.html.\n--2547-- WARNING: unhandled riscv64-linux syscall: 258\n--2547-- You may be able to write your own handler.\n--2547-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2547-- Nevertheless we consider this a bug.  Please report\n--2547-- it at http://valgrind.org/support/bug_reports.html.\n--2547-- WARNING: unhandled riscv64-linux syscall: 258\n--2547-- You may be able to write your own handler.\n--2547-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2547-- Nevertheless we consider this a bug.  Please report\n--2547-- it at http://valgrind.org/support/bug_reports.html.\n--2547-- WARNING: unhandled riscv64-linux syscall: 258\n--2547-- You may be able to write your own handler.\n--2547-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2547-- Nevertheless we consider this a bug.  Please report\n--2547-- it at http://valgrind.org/support/bug_reports.html.\n--2547-- WARNING: unhandled riscv64-linux syscall: 258\n--2547-- You may be able to write your own handler.\n--2547-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2547-- Nevertheless we consider this a bug.  Please report\n--2547-- it at http://valgrind.org/support/bug_reports.html.\n--2547-- WARNING: unhandled riscv64-linux syscall: 258\n--2547-- You may be able to write your own handler.\n--2547-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2547-- Nevertheless we consider this a bug.  Please report\n--2547-- it at http://valgrind.org/support/bug_reports.html.\n--2547-- WARNING: unhandled riscv64-linux syscall: 258\n--2547-- You may be able to write your own handler.\n--2547-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2547-- Nevertheless we consider this a bug.  Please report\n--2547-- it at http://valgrind.org/support/bug_reports.html.\n--2547-- WARNING: unhandled riscv64-linux syscall: 258\n--2547-- You may be able to write your own handler.\n--2547-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2547-- Nevertheless we consider this a bug.  Please report\n--2547-- 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:
'--2555-- WARNING: unhandled riscv64-linux syscall: 258\n--2555-- You may be able to write your own handler.\n--2555-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2555-- Nevertheless we consider this a bug.  Please report\n--2555-- it at http://valgrind.org/support/bug_reports.html.\n--2555-- WARNING: unhandled riscv64-linux syscall: 258\n--2555-- You may be able to write your own handler.\n--2555-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2555-- Nevertheless we consider this a bug.  Please report\n--2555-- it at http://valgrind.org/support/bug_reports.html.\n--2555-- WARNING: unhandled riscv64-linux syscall: 258\n--2555-- You may be able to write your own handler.\n--2555-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2555-- Nevertheless we consider this a bug.  Please report\n--2555-- it at http://valgrind.org/support/bug_reports.html.\n--2555-- WARNING: unhandled riscv64-linux syscall: 258\n--2555-- You may be able to write your own handler.\n--2555-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2555-- Nevertheless we consider this a bug.  Please report\n--2555-- it at http://valgrind.org/support/bug_reports.html.\n--2555-- WARNING: unhandled riscv64-linux syscall: 258\n--2555-- You may be able to write your own handler.\n--2555-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2555-- Nevertheless we consider this a bug.  Please report\n--2555-- it at http://valgrind.org/support/bug_reports.html.\n--2555-- WARNING: unhandled riscv64-linux syscall: 258\n--2555-- You may be able to write your own handler.\n--2555-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2555-- Nevertheless we consider this a bug.  Please report\n--2555-- it at http://valgrind.org/support/bug_reports.html.\n--2555-- WARNING: unhandled riscv64-linux syscall: 258\n--2555-- You may be able to write your own handler.\n--2555-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2555-- Nevertheless we consider this a bug.  Please report\n--2555-- it at http://valgrind.org/support/bug_reports.html.\n--2555-- WARNING: unhandled riscv64-linux syscall: 258\n--2555-- You may be able to write your own handler.\n--2555-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2555-- Nevertheless we consider this a bug.  Please report\n--2555-- it at http://valgrind.org/support/bug_reports.html.\n--2555-- WARNING: unhandled riscv64-linux syscall: 258\n--2555-- You may be able to write your own handler.\n--2555-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2555-- Nevertheless we consider this a bug.  Please report\n--2555-- it at http://valgrind.org/support/bug_reports.html.\n--2555-- WARNING: unhandled riscv64-linux syscall: 258\n--2555-- You may be able to write your own handler.\n--2555-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2555-- Nevertheless we consider this a bug.  Please report\n--2555-- it at http://valgrind.org/support/bug_reports.html.\n--2555-- WARNING: unhandled riscv64-linux syscall: 258\n--2555-- You may be able to write your own handler.\n--2555-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2555-- Nevertheless we consider this a bug.  Please report\n--2555-- it at http://valgrind.org/support/bug_reports.html.\n--2555-- WARNING: unhandled riscv64-linux syscall: 258\n--2555-- You may be able to write your own handler.\n--2555-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2555-- Nevertheless we consider this a bug.  Please report\n--2555-- it at http://valgrind.org/support/bug_reports.html.\n--2555-- WARNING: unhandled riscv64-linux syscall: 258\n--2555-- You may be able to write your own handler.\n--2555-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2555-- Nevertheless we consider this a bug.  Please report\n--2555-- it at http://valgrind.org/support/bug_reports.html.\n--2555-- WARNING: unhandled riscv64-linux syscall: 258\n--2555-- You may be able to write your own handler.\n--2555-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2555-- Nevertheless we consider this a bug.  Please report\n--2555-- it at http://valgrind.org/support/bug_reports.html.\n--2555-- WARNING: unhandled riscv64-linux syscall: 258\n--2555-- You may be able to write your own handler.\n--2555-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2555-- Nevertheless we consider this a bug.  Please report\n--2555-- it at http://valgrind.org/support/bug_reports.html.\n--2555-- WARNING: unhandled riscv64-linux syscall: 258\n--2555-- You may be able to write your own handler.\n--2555-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2555-- Nevertheless we consider this a bug.  Please report\n--2555-- it at http://valgrind.org/support/bug_reports.html.\n--2555-- WARNING: unhandled riscv64-linux syscall: 258\n--2555-- You may be able to write your own handler.\n--2555-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2555-- Nevertheless we consider this a bug.  Please report\n--2555-- it at http://valgrind.org/support/bug_reports.html.\n--2555-- WARNING: unhandled riscv64-linux syscall: 258\n--2555-- You may be able to write your own handler.\n--2555-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2555-- Nevertheless we consider this a bug.  Please report\n--2555-- 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:
'--2563-- WARNING: unhandled riscv64-linux syscall: 258\n--2563-- You may be able to write your own handler.\n--2563-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2563-- Nevertheless we consider this a bug.  Please report\n--2563-- it at http://valgrind.org/support/bug_reports.html.\n--2563-- WARNING: unhandled riscv64-linux syscall: 258\n--2563-- You may be able to write your own handler.\n--2563-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2563-- Nevertheless we consider this a bug.  Please report\n--2563-- it at http://valgrind.org/support/bug_reports.html.\n--2563-- WARNING: unhandled riscv64-linux syscall: 258\n--2563-- You may be able to write your own handler.\n--2563-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2563-- Nevertheless we consider this a bug.  Please report\n--2563-- it at http://valgrind.org/support/bug_reports.html.\n--2563-- WARNING: unhandled riscv64-linux syscall: 258\n--2563-- You may be able to write your own handler.\n--2563-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2563-- Nevertheless we consider this a bug.  Please report\n--2563-- it at http://valgrind.org/support/bug_reports.html.\n--2563-- WARNING: unhandled riscv64-linux syscall: 258\n--2563-- You may be able to write your own handler.\n--2563-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2563-- Nevertheless we consider this a bug.  Please report\n--2563-- it at http://valgrind.org/support/bug_reports.html.\n--2563-- WARNING: unhandled riscv64-linux syscall: 258\n--2563-- You may be able to write your own handler.\n--2563-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2563-- Nevertheless we consider this a bug.  Please report\n--2563-- it at http://valgrind.org/support/bug_reports.html.\n--2563-- WARNING: unhandled riscv64-linux syscall: 258\n--2563-- You may be able to write your own handler.\n--2563-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2563-- Nevertheless we consider this a bug.  Please report\n--2563-- it at http://valgrind.org/support/bug_reports.html.\n--2563-- WARNING: unhandled riscv64-linux syscall: 258\n--2563-- You may be able to write your own handler.\n--2563-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2563-- Nevertheless we consider this a bug.  Please report\n--2563-- it at http://valgrind.org/support/bug_reports.html.\n--2563-- WARNING: unhandled riscv64-linux syscall: 258\n--2563-- You may be able to write your own handler.\n--2563-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2563-- Nevertheless we consider this a bug.  Please report\n--2563-- it at http://valgrind.org/support/bug_reports.html.\n--2563-- WARNING: unhandled riscv64-linux syscall: 258\n--2563-- You may be able to write your own handler.\n--2563-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2563-- Nevertheless we consider this a bug.  Please report\n--2563-- it at http://valgrind.org/support/bug_reports.html.\n--2563-- WARNING: unhandled riscv64-linux syscall: 258\n--2563-- You may be able to write your own handler.\n--2563-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2563-- Nevertheless we consider this a bug.  Please report\n--2563-- it at http://valgrind.org/support/bug_reports.html.\n--2563-- WARNING: unhandled riscv64-linux syscall: 258\n--2563-- You may be able to write your own handler.\n--2563-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2563-- Nevertheless we consider this a bug.  Please report\n--2563-- it at http://valgrind.org/support/bug_reports.html.\n--2563-- WARNING: unhandled riscv64-linux syscall: 258\n--2563-- You may be able to write your own handler.\n--2563-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2563-- Nevertheless we consider this a bug.  Please report\n--2563-- it at http://valgrind.org/support/bug_reports.html.\n--2563-- WARNING: unhandled riscv64-linux syscall: 258\n--2563-- You may be able to write your own handler.\n--2563-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2563-- Nevertheless we consider this a bug.  Please report\n--2563-- it at http://valgrind.org/support/bug_reports.html.\n--2563-- WARNING: unhandled riscv64-linux syscall: 258\n--2563-- You may be able to write your own handler.\n--2563-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2563-- Nevertheless we consider this a bug.  Please report\n--2563-- it at http://valgrind.org/support/bug_reports.html.\n--2563-- WARNING: unhandled riscv64-linux syscall: 258\n--2563-- You may be able to write your own handler.\n--2563-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2563-- Nevertheless we consider this a bug.  Please report\n--2563-- it at http://valgrind.org/support/bug_reports.html.\n--2563-- WARNING: unhandled riscv64-linux syscall: 258\n--2563-- You may be able to write your own handler.\n--2563-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2563-- Nevertheless we consider this a bug.  Please report\n--2563-- it at http://valgrind.org/support/bug_reports.html.\n--2563-- WARNING: unhandled riscv64-linux syscall: 258\n--2563-- You may be able to write your own handler.\n--2563-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2563-- Nevertheless we consider this a bug.  Please report\n--2563-- 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:
'--2571-- WARNING: unhandled riscv64-linux syscall: 258\n--2571-- You may be able to write your own handler.\n--2571-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2571-- Nevertheless we consider this a bug.  Please report\n--2571-- it at http://valgrind.org/support/bug_reports.html.\n--2571-- WARNING: unhandled riscv64-linux syscall: 258\n--2571-- You may be able to write your own handler.\n--2571-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2571-- Nevertheless we consider this a bug.  Please report\n--2571-- it at http://valgrind.org/support/bug_reports.html.\n--2571-- WARNING: unhandled riscv64-linux syscall: 258\n--2571-- You may be able to write your own handler.\n--2571-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2571-- Nevertheless we consider this a bug.  Please report\n--2571-- it at http://valgrind.org/support/bug_reports.html.\n--2571-- WARNING: unhandled riscv64-linux syscall: 258\n--2571-- You may be able to write your own handler.\n--2571-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2571-- Nevertheless we consider this a bug.  Please report\n--2571-- it at http://valgrind.org/support/bug_reports.html.\n--2571-- WARNING: unhandled riscv64-linux syscall: 258\n--2571-- You may be able to write your own handler.\n--2571-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2571-- Nevertheless we consider this a bug.  Please report\n--2571-- it at http://valgrind.org/support/bug_reports.html.\n--2571-- WARNING: unhandled riscv64-linux syscall: 258\n--2571-- You may be able to write your own handler.\n--2571-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2571-- Nevertheless we consider this a bug.  Please report\n--2571-- it at http://valgrind.org/support/bug_reports.html.\n--2571-- WARNING: unhandled riscv64-linux syscall: 258\n--2571-- You may be able to write your own handler.\n--2571-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2571-- Nevertheless we consider this a bug.  Please report\n--2571-- it at http://valgrind.org/support/bug_reports.html.\n--2571-- WARNING: unhandled riscv64-linux syscall: 258\n--2571-- You may be able to write your own handler.\n--2571-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2571-- Nevertheless we consider this a bug.  Please report\n--2571-- it at http://valgrind.org/support/bug_reports.html.\n--2571-- WARNING: unhandled riscv64-linux syscall: 258\n--2571-- You may be able to write your own handler.\n--2571-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2571-- Nevertheless we consider this a bug.  Please report\n--2571-- it at http://valgrind.org/support/bug_reports.html.\n--2571-- WARNING: unhandled riscv64-linux syscall: 258\n--2571-- You may be able to write your own handler.\n--2571-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2571-- Nevertheless we consider this a bug.  Please report\n--2571-- it at http://valgrind.org/support/bug_reports.html.\n--2571-- WARNING: unhandled riscv64-linux syscall: 258\n--2571-- You may be able to write your own handler.\n--2571-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2571-- Nevertheless we consider this a bug.  Please report\n--2571-- it at http://valgrind.org/support/bug_reports.html.\n--2571-- WARNING: unhandled riscv64-linux syscall: 258\n--2571-- You may be able to write your own handler.\n--2571-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2571-- Nevertheless we consider this a bug.  Please report\n--2571-- it at http://valgrind.org/support/bug_reports.html.\n--2571-- WARNING: unhandled riscv64-linux syscall: 258\n--2571-- You may be able to write your own handler.\n--2571-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2571-- Nevertheless we consider this a bug.  Please report\n--2571-- it at http://valgrind.org/support/bug_reports.html.\n--2571-- WARNING: unhandled riscv64-linux syscall: 258\n--2571-- You may be able to write your own handler.\n--2571-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2571-- Nevertheless we consider this a bug.  Please report\n--2571-- it at http://valgrind.org/support/bug_reports.html.\n--2571-- WARNING: unhandled riscv64-linux syscall: 258\n--2571-- You may be able to write your own handler.\n--2571-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2571-- Nevertheless we consider this a bug.  Please report\n--2571-- it at http://valgrind.org/support/bug_reports.html.\n--2571-- WARNING: unhandled riscv64-linux syscall: 258\n--2571-- You may be able to write your own handler.\n--2571-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2571-- Nevertheless we consider this a bug.  Please report\n--2571-- it at http://valgrind.org/support/bug_reports.html.\n--2571-- WARNING: unhandled riscv64-linux syscall: 258\n--2571-- You may be able to write your own handler.\n--2571-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2571-- Nevertheless we consider this a bug.  Please report\n--2571-- it at http://valgrind.org/support/bug_reports.html.\n--2571-- WARNING: unhandled riscv64-linux syscall: 258\n--2571-- You may be able to write your own handler.\n--2571-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2571-- Nevertheless we consider this a bug.  Please report\n--2571-- 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:
'--2579-- WARNING: unhandled riscv64-linux syscall: 258\n--2579-- You may be able to write your own handler.\n--2579-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2579-- Nevertheless we consider this a bug.  Please report\n--2579-- it at http://valgrind.org/support/bug_reports.html.\n--2579-- WARNING: unhandled riscv64-linux syscall: 258\n--2579-- You may be able to write your own handler.\n--2579-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2579-- Nevertheless we consider this a bug.  Please report\n--2579-- it at http://valgrind.org/support/bug_reports.html.\n--2579-- WARNING: unhandled riscv64-linux syscall: 258\n--2579-- You may be able to write your own handler.\n--2579-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2579-- Nevertheless we consider this a bug.  Please report\n--2579-- it at http://valgrind.org/support/bug_reports.html.\n--2579-- WARNING: unhandled riscv64-linux syscall: 258\n--2579-- You may be able to write your own handler.\n--2579-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2579-- Nevertheless we consider this a bug.  Please report\n--2579-- it at http://valgrind.org/support/bug_reports.html.\n--2579-- WARNING: unhandled riscv64-linux syscall: 258\n--2579-- You may be able to write your own handler.\n--2579-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2579-- Nevertheless we consider this a bug.  Please report\n--2579-- it at http://valgrind.org/support/bug_reports.html.\n--2579-- WARNING: unhandled riscv64-linux syscall: 258\n--2579-- You may be able to write your own handler.\n--2579-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2579-- Nevertheless we consider this a bug.  Please report\n--2579-- it at http://valgrind.org/support/bug_reports.html.\n--2579-- WARNING: unhandled riscv64-linux syscall: 258\n--2579-- You may be able to write your own handler.\n--2579-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2579-- Nevertheless we consider this a bug.  Please report\n--2579-- it at http://valgrind.org/support/bug_reports.html.\n--2579-- WARNING: unhandled riscv64-linux syscall: 258\n--2579-- You may be able to write your own handler.\n--2579-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2579-- Nevertheless we consider this a bug.  Please report\n--2579-- it at http://valgrind.org/support/bug_reports.html.\n--2579-- WARNING: unhandled riscv64-linux syscall: 258\n--2579-- You may be able to write your own handler.\n--2579-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2579-- Nevertheless we consider this a bug.  Please report\n--2579-- it at http://valgrind.org/support/bug_reports.html.\n--2579-- WARNING: unhandled riscv64-linux syscall: 258\n--2579-- You may be able to write your own handler.\n--2579-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2579-- Nevertheless we consider this a bug.  Please report\n--2579-- it at http://valgrind.org/support/bug_reports.html.\n--2579-- WARNING: unhandled riscv64-linux syscall: 258\n--2579-- You may be able to write your own handler.\n--2579-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2579-- Nevertheless we consider this a bug.  Please report\n--2579-- it at http://valgrind.org/support/bug_reports.html.\n--2579-- WARNING: unhandled riscv64-linux syscall: 258\n--2579-- You may be able to write your own handler.\n--2579-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2579-- Nevertheless we consider this a bug.  Please report\n--2579-- it at http://valgrind.org/support/bug_reports.html.\n--2579-- WARNING: unhandled riscv64-linux syscall: 258\n--2579-- You may be able to write your own handler.\n--2579-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2579-- Nevertheless we consider this a bug.  Please report\n--2579-- it at http://valgrind.org/support/bug_reports.html.\n--2579-- WARNING: unhandled riscv64-linux syscall: 258\n--2579-- You may be able to write your own handler.\n--2579-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2579-- Nevertheless we consider this a bug.  Please report\n--2579-- it at http://valgrind.org/support/bug_reports.html.\n--2579-- WARNING: unhandled riscv64-linux syscall: 258\n--2579-- You may be able to write your own handler.\n--2579-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2579-- Nevertheless we consider this a bug.  Please report\n--2579-- it at http://valgrind.org/support/bug_reports.html.\n--2579-- WARNING: unhandled riscv64-linux syscall: 258\n--2579-- You may be able to write your own handler.\n--2579-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2579-- Nevertheless we consider this a bug.  Please report\n--2579-- it at http://valgrind.org/support/bug_reports.html.\n--2579-- WARNING: unhandled riscv64-linux syscall: 258\n--2579-- You may be able to write your own handler.\n--2579-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2579-- Nevertheless we consider this a bug.  Please report\n--2579-- it at http://valgrind.org/support/bug_reports.html.\n--2579-- WARNING: unhandled riscv64-linux syscall: 258\n--2579-- You may be able to write your own handler.\n--2579-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2579-- Nevertheless we consider this a bug.  Please report\n--2579-- 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:
'--2587-- WARNING: unhandled riscv64-linux syscall: 258\n--2587-- You may be able to write your own handler.\n--2587-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2587-- Nevertheless we consider this a bug.  Please report\n--2587-- it at http://valgrind.org/support/bug_reports.html.\n--2587-- WARNING: unhandled riscv64-linux syscall: 258\n--2587-- You may be able to write your own handler.\n--2587-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2587-- Nevertheless we consider this a bug.  Please report\n--2587-- it at http://valgrind.org/support/bug_reports.html.\n--2587-- WARNING: unhandled riscv64-linux syscall: 258\n--2587-- You may be able to write your own handler.\n--2587-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2587-- Nevertheless we consider this a bug.  Please report\n--2587-- it at http://valgrind.org/support/bug_reports.html.\n--2587-- WARNING: unhandled riscv64-linux syscall: 258\n--2587-- You may be able to write your own handler.\n--2587-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2587-- Nevertheless we consider this a bug.  Please report\n--2587-- it at http://valgrind.org/support/bug_reports.html.\n--2587-- WARNING: unhandled riscv64-linux syscall: 258\n--2587-- You may be able to write your own handler.\n--2587-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2587-- Nevertheless we consider this a bug.  Please report\n--2587-- it at http://valgrind.org/support/bug_reports.html.\n--2587-- WARNING: unhandled riscv64-linux syscall: 258\n--2587-- You may be able to write your own handler.\n--2587-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2587-- Nevertheless we consider this a bug.  Please report\n--2587-- it at http://valgrind.org/support/bug_reports.html.\n--2587-- WARNING: unhandled riscv64-linux syscall: 258\n--2587-- You may be able to write your own handler.\n--2587-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2587-- Nevertheless we consider this a bug.  Please report\n--2587-- it at http://valgrind.org/support/bug_reports.html.\n--2587-- WARNING: unhandled riscv64-linux syscall: 258\n--2587-- You may be able to write your own handler.\n--2587-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2587-- Nevertheless we consider this a bug.  Please report\n--2587-- it at http://valgrind.org/support/bug_reports.html.\n--2587-- WARNING: unhandled riscv64-linux syscall: 258\n--2587-- You may be able to write your own handler.\n--2587-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2587-- Nevertheless we consider this a bug.  Please report\n--2587-- it at http://valgrind.org/support/bug_reports.html.\n--2587-- WARNING: unhandled riscv64-linux syscall: 258\n--2587-- You may be able to write your own handler.\n--2587-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2587-- Nevertheless we consider this a bug.  Please report\n--2587-- it at http://valgrind.org/support/bug_reports.html.\n--2587-- WARNING: unhandled riscv64-linux syscall: 258\n--2587-- You may be able to write your own handler.\n--2587-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2587-- Nevertheless we consider this a bug.  Please report\n--2587-- it at http://valgrind.org/support/bug_reports.html.\n--2587-- WARNING: unhandled riscv64-linux syscall: 258\n--2587-- You may be able to write your own handler.\n--2587-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2587-- Nevertheless we consider this a bug.  Please report\n--2587-- it at http://valgrind.org/support/bug_reports.html.\n--2587-- WARNING: unhandled riscv64-linux syscall: 258\n--2587-- You may be able to write your own handler.\n--2587-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2587-- Nevertheless we consider this a bug.  Please report\n--2587-- it at http://valgrind.org/support/bug_reports.html.\n--2587-- WARNING: unhandled riscv64-linux syscall: 258\n--2587-- You may be able to write your own handler.\n--2587-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2587-- Nevertheless we consider this a bug.  Please report\n--2587-- it at http://valgrind.org/support/bug_reports.html.\n--2587-- WARNING: unhandled riscv64-linux syscall: 258\n--2587-- You may be able to write your own handler.\n--2587-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2587-- Nevertheless we consider this a bug.  Please report\n--2587-- it at http://valgrind.org/support/bug_reports.html.\n--2587-- WARNING: unhandled riscv64-linux syscall: 258\n--2587-- You may be able to write your own handler.\n--2587-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2587-- Nevertheless we consider this a bug.  Please report\n--2587-- it at http://valgrind.org/support/bug_reports.html.\n--2587-- WARNING: unhandled riscv64-linux syscall: 258\n--2587-- You may be able to write your own handler.\n--2587-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2587-- Nevertheless we consider this a bug.  Please report\n--2587-- it at http://valgrind.org/support/bug_reports.html.\n--2587-- WARNING: unhandled riscv64-linux syscall: 258\n--2587-- You may be able to write your own handler.\n--2587-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2587-- Nevertheless we consider this a bug.  Please report\n--2587-- 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:
'--2595-- WARNING: unhandled riscv64-linux syscall: 258\n--2595-- You may be able to write your own handler.\n--2595-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2595-- Nevertheless we consider this a bug.  Please report\n--2595-- it at http://valgrind.org/support/bug_reports.html.\n--2595-- WARNING: unhandled riscv64-linux syscall: 258\n--2595-- You may be able to write your own handler.\n--2595-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2595-- Nevertheless we consider this a bug.  Please report\n--2595-- it at http://valgrind.org/support/bug_reports.html.\n--2595-- WARNING: unhandled riscv64-linux syscall: 258\n--2595-- You may be able to write your own handler.\n--2595-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2595-- Nevertheless we consider this a bug.  Please report\n--2595-- it at http://valgrind.org/support/bug_reports.html.\n--2595-- WARNING: unhandled riscv64-linux syscall: 258\n--2595-- You may be able to write your own handler.\n--2595-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2595-- Nevertheless we consider this a bug.  Please report\n--2595-- it at http://valgrind.org/support/bug_reports.html.\n--2595-- WARNING: unhandled riscv64-linux syscall: 258\n--2595-- You may be able to write your own handler.\n--2595-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2595-- Nevertheless we consider this a bug.  Please report\n--2595-- it at http://valgrind.org/support/bug_reports.html.\n--2595-- WARNING: unhandled riscv64-linux syscall: 258\n--2595-- You may be able to write your own handler.\n--2595-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2595-- Nevertheless we consider this a bug.  Please report\n--2595-- it at http://valgrind.org/support/bug_reports.html.\n--2595-- WARNING: unhandled riscv64-linux syscall: 258\n--2595-- You may be able to write your own handler.\n--2595-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2595-- Nevertheless we consider this a bug.  Please report\n--2595-- it at http://valgrind.org/support/bug_reports.html.\n--2595-- WARNING: unhandled riscv64-linux syscall: 258\n--2595-- You may be able to write your own handler.\n--2595-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2595-- Nevertheless we consider this a bug.  Please report\n--2595-- it at http://valgrind.org/support/bug_reports.html.\n--2595-- WARNING: unhandled riscv64-linux syscall: 258\n--2595-- You may be able to write your own handler.\n--2595-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2595-- Nevertheless we consider this a bug.  Please report\n--2595-- it at http://valgrind.org/support/bug_reports.html.\n--2595-- WARNING: unhandled riscv64-linux syscall: 258\n--2595-- You may be able to write your own handler.\n--2595-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2595-- Nevertheless we consider this a bug.  Please report\n--2595-- it at http://valgrind.org/support/bug_reports.html.\n--2595-- WARNING: unhandled riscv64-linux syscall: 258\n--2595-- You may be able to write your own handler.\n--2595-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2595-- Nevertheless we consider this a bug.  Please report\n--2595-- it at http://valgrind.org/support/bug_reports.html.\n--2595-- WARNING: unhandled riscv64-linux syscall: 258\n--2595-- You may be able to write your own handler.\n--2595-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2595-- Nevertheless we consider this a bug.  Please report\n--2595-- it at http://valgrind.org/support/bug_reports.html.\n--2595-- WARNING: unhandled riscv64-linux syscall: 258\n--2595-- You may be able to write your own handler.\n--2595-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2595-- Nevertheless we consider this a bug.  Please report\n--2595-- it at http://valgrind.org/support/bug_reports.html.\n--2595-- WARNING: unhandled riscv64-linux syscall: 258\n--2595-- You may be able to write your own handler.\n--2595-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2595-- Nevertheless we consider this a bug.  Please report\n--2595-- it at http://valgrind.org/support/bug_reports.html.\n--2595-- WARNING: unhandled riscv64-linux syscall: 258\n--2595-- You may be able to write your own handler.\n--2595-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2595-- Nevertheless we consider this a bug.  Please report\n--2595-- it at http://valgrind.org/support/bug_reports.html.\n--2595-- WARNING: unhandled riscv64-linux syscall: 258\n--2595-- You may be able to write your own handler.\n--2595-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2595-- Nevertheless we consider this a bug.  Please report\n--2595-- it at http://valgrind.org/support/bug_reports.html.\n--2595-- WARNING: unhandled riscv64-linux syscall: 258\n--2595-- You may be able to write your own handler.\n--2595-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2595-- Nevertheless we consider this a bug.  Please report\n--2595-- it at http://valgrind.org/support/bug_reports.html.\n--2595-- WARNING: unhandled riscv64-linux syscall: 258\n--2595-- You may be able to write your own handler.\n--2595-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2595-- Nevertheless we consider this a bug.  Please report\n--2595-- 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:
'--2603-- WARNING: unhandled riscv64-linux syscall: 258\n--2603-- You may be able to write your own handler.\n--2603-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2603-- Nevertheless we consider this a bug.  Please report\n--2603-- it at http://valgrind.org/support/bug_reports.html.\n--2603-- WARNING: unhandled riscv64-linux syscall: 258\n--2603-- You may be able to write your own handler.\n--2603-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2603-- Nevertheless we consider this a bug.  Please report\n--2603-- it at http://valgrind.org/support/bug_reports.html.\n--2603-- WARNING: unhandled riscv64-linux syscall: 258\n--2603-- You may be able to write your own handler.\n--2603-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2603-- Nevertheless we consider this a bug.  Please report\n--2603-- it at http://valgrind.org/support/bug_reports.html.\n--2603-- WARNING: unhandled riscv64-linux syscall: 258\n--2603-- You may be able to write your own handler.\n--2603-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2603-- Nevertheless we consider this a bug.  Please report\n--2603-- it at http://valgrind.org/support/bug_reports.html.\n--2603-- WARNING: unhandled riscv64-linux syscall: 258\n--2603-- You may be able to write your own handler.\n--2603-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2603-- Nevertheless we consider this a bug.  Please report\n--2603-- it at http://valgrind.org/support/bug_reports.html.\n--2603-- WARNING: unhandled riscv64-linux syscall: 258\n--2603-- You may be able to write your own handler.\n--2603-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2603-- Nevertheless we consider this a bug.  Please report\n--2603-- it at http://valgrind.org/support/bug_reports.html.\n--2603-- WARNING: unhandled riscv64-linux syscall: 258\n--2603-- You may be able to write your own handler.\n--2603-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2603-- Nevertheless we consider this a bug.  Please report\n--2603-- it at http://valgrind.org/support/bug_reports.html.\n--2603-- WARNING: unhandled riscv64-linux syscall: 258\n--2603-- You may be able to write your own handler.\n--2603-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2603-- Nevertheless we consider this a bug.  Please report\n--2603-- it at http://valgrind.org/support/bug_reports.html.\n--2603-- WARNING: unhandled riscv64-linux syscall: 258\n--2603-- You may be able to write your own handler.\n--2603-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2603-- Nevertheless we consider this a bug.  Please report\n--2603-- it at http://valgrind.org/support/bug_reports.html.\n--2603-- WARNING: unhandled riscv64-linux syscall: 258\n--2603-- You may be able to write your own handler.\n--2603-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2603-- Nevertheless we consider this a bug.  Please report\n--2603-- it at http://valgrind.org/support/bug_reports.html.\n--2603-- WARNING: unhandled riscv64-linux syscall: 258\n--2603-- You may be able to write your own handler.\n--2603-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2603-- Nevertheless we consider this a bug.  Please report\n--2603-- it at http://valgrind.org/support/bug_reports.html.\n--2603-- WARNING: unhandled riscv64-linux syscall: 258\n--2603-- You may be able to write your own handler.\n--2603-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2603-- Nevertheless we consider this a bug.  Please report\n--2603-- it at http://valgrind.org/support/bug_reports.html.\n--2603-- WARNING: unhandled riscv64-linux syscall: 258\n--2603-- You may be able to write your own handler.\n--2603-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2603-- Nevertheless we consider this a bug.  Please report\n--2603-- it at http://valgrind.org/support/bug_reports.html.\n--2603-- WARNING: unhandled riscv64-linux syscall: 258\n--2603-- You may be able to write your own handler.\n--2603-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2603-- Nevertheless we consider this a bug.  Please report\n--2603-- it at http://valgrind.org/support/bug_reports.html.\n--2603-- WARNING: unhandled riscv64-linux syscall: 258\n--2603-- You may be able to write your own handler.\n--2603-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2603-- Nevertheless we consider this a bug.  Please report\n--2603-- it at http://valgrind.org/support/bug_reports.html.\n--2603-- WARNING: unhandled riscv64-linux syscall: 258\n--2603-- You may be able to write your own handler.\n--2603-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2603-- Nevertheless we consider this a bug.  Please report\n--2603-- it at http://valgrind.org/support/bug_reports.html.\n--2603-- WARNING: unhandled riscv64-linux syscall: 258\n--2603-- You may be able to write your own handler.\n--2603-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2603-- Nevertheless we consider this a bug.  Please report\n--2603-- it at http://valgrind.org/support/bug_reports.html.\n--2603-- WARNING: unhandled riscv64-linux syscall: 258\n--2603-- You may be able to write your own handler.\n--2603-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2603-- Nevertheless we consider this a bug.  Please report\n--2603-- 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:
'--2611-- WARNING: unhandled riscv64-linux syscall: 258\n--2611-- You may be able to write your own handler.\n--2611-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2611-- Nevertheless we consider this a bug.  Please report\n--2611-- it at http://valgrind.org/support/bug_reports.html.\n--2611-- WARNING: unhandled riscv64-linux syscall: 258\n--2611-- You may be able to write your own handler.\n--2611-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2611-- Nevertheless we consider this a bug.  Please report\n--2611-- it at http://valgrind.org/support/bug_reports.html.\n--2611-- WARNING: unhandled riscv64-linux syscall: 258\n--2611-- You may be able to write your own handler.\n--2611-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2611-- Nevertheless we consider this a bug.  Please report\n--2611-- it at http://valgrind.org/support/bug_reports.html.\n--2611-- WARNING: unhandled riscv64-linux syscall: 258\n--2611-- You may be able to write your own handler.\n--2611-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2611-- Nevertheless we consider this a bug.  Please report\n--2611-- it at http://valgrind.org/support/bug_reports.html.\n--2611-- WARNING: unhandled riscv64-linux syscall: 258\n--2611-- You may be able to write your own handler.\n--2611-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2611-- Nevertheless we consider this a bug.  Please report\n--2611-- it at http://valgrind.org/support/bug_reports.html.\n--2611-- WARNING: unhandled riscv64-linux syscall: 258\n--2611-- You may be able to write your own handler.\n--2611-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2611-- Nevertheless we consider this a bug.  Please report\n--2611-- it at http://valgrind.org/support/bug_reports.html.\n--2611-- WARNING: unhandled riscv64-linux syscall: 258\n--2611-- You may be able to write your own handler.\n--2611-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2611-- Nevertheless we consider this a bug.  Please report\n--2611-- it at http://valgrind.org/support/bug_reports.html.\n--2611-- WARNING: unhandled riscv64-linux syscall: 258\n--2611-- You may be able to write your own handler.\n--2611-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2611-- Nevertheless we consider this a bug.  Please report\n--2611-- it at http://valgrind.org/support/bug_reports.html.\n--2611-- WARNING: unhandled riscv64-linux syscall: 258\n--2611-- You may be able to write your own handler.\n--2611-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2611-- Nevertheless we consider this a bug.  Please report\n--2611-- it at http://valgrind.org/support/bug_reports.html.\n--2611-- WARNING: unhandled riscv64-linux syscall: 258\n--2611-- You may be able to write your own handler.\n--2611-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2611-- Nevertheless we consider this a bug.  Please report\n--2611-- it at http://valgrind.org/support/bug_reports.html.\n--2611-- WARNING: unhandled riscv64-linux syscall: 258\n--2611-- You may be able to write your own handler.\n--2611-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2611-- Nevertheless we consider this a bug.  Please report\n--2611-- it at http://valgrind.org/support/bug_reports.html.\n--2611-- WARNING: unhandled riscv64-linux syscall: 258\n--2611-- You may be able to write your own handler.\n--2611-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2611-- Nevertheless we consider this a bug.  Please report\n--2611-- it at http://valgrind.org/support/bug_reports.html.\n--2611-- WARNING: unhandled riscv64-linux syscall: 258\n--2611-- You may be able to write your own handler.\n--2611-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2611-- Nevertheless we consider this a bug.  Please report\n--2611-- it at http://valgrind.org/support/bug_reports.html.\n--2611-- WARNING: unhandled riscv64-linux syscall: 258\n--2611-- You may be able to write your own handler.\n--2611-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2611-- Nevertheless we consider this a bug.  Please report\n--2611-- it at http://valgrind.org/support/bug_reports.html.\n--2611-- WARNING: unhandled riscv64-linux syscall: 258\n--2611-- You may be able to write your own handler.\n--2611-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2611-- Nevertheless we consider this a bug.  Please report\n--2611-- it at http://valgrind.org/support/bug_reports.html.\n--2611-- WARNING: unhandled riscv64-linux syscall: 258\n--2611-- You may be able to write your own handler.\n--2611-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2611-- Nevertheless we consider this a bug.  Please report\n--2611-- it at http://valgrind.org/support/bug_reports.html.\n--2611-- WARNING: unhandled riscv64-linux syscall: 258\n--2611-- You may be able to write your own handler.\n--2611-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2611-- Nevertheless we consider this a bug.  Please report\n--2611-- it at http://valgrind.org/support/bug_reports.html.\n--2611-- WARNING: unhandled riscv64-linux syscall: 258\n--2611-- You may be able to write your own handler.\n--2611-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2611-- Nevertheless we consider this a bug.  Please report\n--2611-- 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:
'--2619-- WARNING: unhandled riscv64-linux syscall: 258\n--2619-- You may be able to write your own handler.\n--2619-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2619-- Nevertheless we consider this a bug.  Please report\n--2619-- it at http://valgrind.org/support/bug_reports.html.\n--2619-- WARNING: unhandled riscv64-linux syscall: 258\n--2619-- You may be able to write your own handler.\n--2619-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2619-- Nevertheless we consider this a bug.  Please report\n--2619-- it at http://valgrind.org/support/bug_reports.html.\n--2619-- WARNING: unhandled riscv64-linux syscall: 258\n--2619-- You may be able to write your own handler.\n--2619-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2619-- Nevertheless we consider this a bug.  Please report\n--2619-- it at http://valgrind.org/support/bug_reports.html.\n--2619-- WARNING: unhandled riscv64-linux syscall: 258\n--2619-- You may be able to write your own handler.\n--2619-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2619-- Nevertheless we consider this a bug.  Please report\n--2619-- it at http://valgrind.org/support/bug_reports.html.\n--2619-- WARNING: unhandled riscv64-linux syscall: 258\n--2619-- You may be able to write your own handler.\n--2619-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2619-- Nevertheless we consider this a bug.  Please report\n--2619-- it at http://valgrind.org/support/bug_reports.html.\n--2619-- WARNING: unhandled riscv64-linux syscall: 258\n--2619-- You may be able to write your own handler.\n--2619-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2619-- Nevertheless we consider this a bug.  Please report\n--2619-- it at http://valgrind.org/support/bug_reports.html.\n--2619-- WARNING: unhandled riscv64-linux syscall: 258\n--2619-- You may be able to write your own handler.\n--2619-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2619-- Nevertheless we consider this a bug.  Please report\n--2619-- it at http://valgrind.org/support/bug_reports.html.\n--2619-- WARNING: unhandled riscv64-linux syscall: 258\n--2619-- You may be able to write your own handler.\n--2619-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2619-- Nevertheless we consider this a bug.  Please report\n--2619-- it at http://valgrind.org/support/bug_reports.html.\n--2619-- WARNING: unhandled riscv64-linux syscall: 258\n--2619-- You may be able to write your own handler.\n--2619-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2619-- Nevertheless we consider this a bug.  Please report\n--2619-- it at http://valgrind.org/support/bug_reports.html.\n--2619-- WARNING: unhandled riscv64-linux syscall: 258\n--2619-- You may be able to write your own handler.\n--2619-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2619-- Nevertheless we consider this a bug.  Please report\n--2619-- it at http://valgrind.org/support/bug_reports.html.\n--2619-- WARNING: unhandled riscv64-linux syscall: 258\n--2619-- You may be able to write your own handler.\n--2619-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2619-- Nevertheless we consider this a bug.  Please report\n--2619-- it at http://valgrind.org/support/bug_reports.html.\n--2619-- WARNING: unhandled riscv64-linux syscall: 258\n--2619-- You may be able to write your own handler.\n--2619-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2619-- Nevertheless we consider this a bug.  Please report\n--2619-- it at http://valgrind.org/support/bug_reports.html.\n--2619-- WARNING: unhandled riscv64-linux syscall: 258\n--2619-- You may be able to write your own handler.\n--2619-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2619-- Nevertheless we consider this a bug.  Please report\n--2619-- it at http://valgrind.org/support/bug_reports.html.\n--2619-- WARNING: unhandled riscv64-linux syscall: 258\n--2619-- You may be able to write your own handler.\n--2619-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2619-- Nevertheless we consider this a bug.  Please report\n--2619-- it at http://valgrind.org/support/bug_reports.html.\n--2619-- WARNING: unhandled riscv64-linux syscall: 258\n--2619-- You may be able to write your own handler.\n--2619-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2619-- Nevertheless we consider this a bug.  Please report\n--2619-- it at http://valgrind.org/support/bug_reports.html.\n--2619-- WARNING: unhandled riscv64-linux syscall: 258\n--2619-- You may be able to write your own handler.\n--2619-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2619-- Nevertheless we consider this a bug.  Please report\n--2619-- it at http://valgrind.org/support/bug_reports.html.\n--2619-- WARNING: unhandled riscv64-linux syscall: 258\n--2619-- You may be able to write your own handler.\n--2619-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2619-- Nevertheless we consider this a bug.  Please report\n--2619-- it at http://valgrind.org/support/bug_reports.html.\n--2619-- WARNING: unhandled riscv64-linux syscall: 258\n--2619-- You may be able to write your own handler.\n--2619-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2619-- Nevertheless we consider this a bug.  Please report\n--2619-- 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:
'--2627-- WARNING: unhandled riscv64-linux syscall: 258\n--2627-- You may be able to write your own handler.\n--2627-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2627-- Nevertheless we consider this a bug.  Please report\n--2627-- it at http://valgrind.org/support/bug_reports.html.\n--2627-- WARNING: unhandled riscv64-linux syscall: 258\n--2627-- You may be able to write your own handler.\n--2627-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2627-- Nevertheless we consider this a bug.  Please report\n--2627-- it at http://valgrind.org/support/bug_reports.html.\n--2627-- WARNING: unhandled riscv64-linux syscall: 258\n--2627-- You may be able to write your own handler.\n--2627-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2627-- Nevertheless we consider this a bug.  Please report\n--2627-- it at http://valgrind.org/support/bug_reports.html.\n--2627-- WARNING: unhandled riscv64-linux syscall: 258\n--2627-- You may be able to write your own handler.\n--2627-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2627-- Nevertheless we consider this a bug.  Please report\n--2627-- it at http://valgrind.org/support/bug_reports.html.\n--2627-- WARNING: unhandled riscv64-linux syscall: 258\n--2627-- You may be able to write your own handler.\n--2627-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2627-- Nevertheless we consider this a bug.  Please report\n--2627-- it at http://valgrind.org/support/bug_reports.html.\n--2627-- WARNING: unhandled riscv64-linux syscall: 258\n--2627-- You may be able to write your own handler.\n--2627-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2627-- Nevertheless we consider this a bug.  Please report\n--2627-- it at http://valgrind.org/support/bug_reports.html.\n--2627-- WARNING: unhandled riscv64-linux syscall: 258\n--2627-- You may be able to write your own handler.\n--2627-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2627-- Nevertheless we consider this a bug.  Please report\n--2627-- it at http://valgrind.org/support/bug_reports.html.\n--2627-- WARNING: unhandled riscv64-linux syscall: 258\n--2627-- You may be able to write your own handler.\n--2627-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2627-- Nevertheless we consider this a bug.  Please report\n--2627-- it at http://valgrind.org/support/bug_reports.html.\n--2627-- WARNING: unhandled riscv64-linux syscall: 258\n--2627-- You may be able to write your own handler.\n--2627-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2627-- Nevertheless we consider this a bug.  Please report\n--2627-- it at http://valgrind.org/support/bug_reports.html.\n--2627-- WARNING: unhandled riscv64-linux syscall: 258\n--2627-- You may be able to write your own handler.\n--2627-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2627-- Nevertheless we consider this a bug.  Please report\n--2627-- it at http://valgrind.org/support/bug_reports.html.\n--2627-- WARNING: unhandled riscv64-linux syscall: 258\n--2627-- You may be able to write your own handler.\n--2627-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2627-- Nevertheless we consider this a bug.  Please report\n--2627-- it at http://valgrind.org/support/bug_reports.html.\n--2627-- WARNING: unhandled riscv64-linux syscall: 258\n--2627-- You may be able to write your own handler.\n--2627-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2627-- Nevertheless we consider this a bug.  Please report\n--2627-- it at http://valgrind.org/support/bug_reports.html.\n--2627-- WARNING: unhandled riscv64-linux syscall: 258\n--2627-- You may be able to write your own handler.\n--2627-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2627-- Nevertheless we consider this a bug.  Please report\n--2627-- it at http://valgrind.org/support/bug_reports.html.\n--2627-- WARNING: unhandled riscv64-linux syscall: 258\n--2627-- You may be able to write your own handler.\n--2627-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2627-- Nevertheless we consider this a bug.  Please report\n--2627-- it at http://valgrind.org/support/bug_reports.html.\n--2627-- WARNING: unhandled riscv64-linux syscall: 258\n--2627-- You may be able to write your own handler.\n--2627-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2627-- Nevertheless we consider this a bug.  Please report\n--2627-- it at http://valgrind.org/support/bug_reports.html.\n--2627-- WARNING: unhandled riscv64-linux syscall: 258\n--2627-- You may be able to write your own handler.\n--2627-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2627-- Nevertheless we consider this a bug.  Please report\n--2627-- it at http://valgrind.org/support/bug_reports.html.\n--2627-- WARNING: unhandled riscv64-linux syscall: 258\n--2627-- You may be able to write your own handler.\n--2627-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2627-- Nevertheless we consider this a bug.  Please report\n--2627-- it at http://valgrind.org/support/bug_reports.html.\n--2627-- WARNING: unhandled riscv64-linux syscall: 258\n--2627-- You may be able to write your own handler.\n--2627-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2627-- Nevertheless we consider this a bug.  Please report\n--2627-- 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:
'--2635-- WARNING: unhandled riscv64-linux syscall: 258\n--2635-- You may be able to write your own handler.\n--2635-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2635-- Nevertheless we consider this a bug.  Please report\n--2635-- it at http://valgrind.org/support/bug_reports.html.\n--2635-- WARNING: unhandled riscv64-linux syscall: 258\n--2635-- You may be able to write your own handler.\n--2635-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2635-- Nevertheless we consider this a bug.  Please report\n--2635-- it at http://valgrind.org/support/bug_reports.html.\n--2635-- WARNING: unhandled riscv64-linux syscall: 258\n--2635-- You may be able to write your own handler.\n--2635-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2635-- Nevertheless we consider this a bug.  Please report\n--2635-- it at http://valgrind.org/support/bug_reports.html.\n--2635-- WARNING: unhandled riscv64-linux syscall: 258\n--2635-- You may be able to write your own handler.\n--2635-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2635-- Nevertheless we consider this a bug.  Please report\n--2635-- it at http://valgrind.org/support/bug_reports.html.\n--2635-- WARNING: unhandled riscv64-linux syscall: 258\n--2635-- You may be able to write your own handler.\n--2635-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2635-- Nevertheless we consider this a bug.  Please report\n--2635-- it at http://valgrind.org/support/bug_reports.html.\n--2635-- WARNING: unhandled riscv64-linux syscall: 258\n--2635-- You may be able to write your own handler.\n--2635-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2635-- Nevertheless we consider this a bug.  Please report\n--2635-- it at http://valgrind.org/support/bug_reports.html.\n--2635-- WARNING: unhandled riscv64-linux syscall: 258\n--2635-- You may be able to write your own handler.\n--2635-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2635-- Nevertheless we consider this a bug.  Please report\n--2635-- it at http://valgrind.org/support/bug_reports.html.\n--2635-- WARNING: unhandled riscv64-linux syscall: 258\n--2635-- You may be able to write your own handler.\n--2635-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2635-- Nevertheless we consider this a bug.  Please report\n--2635-- it at http://valgrind.org/support/bug_reports.html.\n--2635-- WARNING: unhandled riscv64-linux syscall: 258\n--2635-- You may be able to write your own handler.\n--2635-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2635-- Nevertheless we consider this a bug.  Please report\n--2635-- it at http://valgrind.org/support/bug_reports.html.\n--2635-- WARNING: unhandled riscv64-linux syscall: 258\n--2635-- You may be able to write your own handler.\n--2635-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2635-- Nevertheless we consider this a bug.  Please report\n--2635-- it at http://valgrind.org/support/bug_reports.html.\n--2635-- WARNING: unhandled riscv64-linux syscall: 258\n--2635-- You may be able to write your own handler.\n--2635-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2635-- Nevertheless we consider this a bug.  Please report\n--2635-- it at http://valgrind.org/support/bug_reports.html.\n--2635-- WARNING: unhandled riscv64-linux syscall: 258\n--2635-- You may be able to write your own handler.\n--2635-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2635-- Nevertheless we consider this a bug.  Please report\n--2635-- it at http://valgrind.org/support/bug_reports.html.\n--2635-- WARNING: unhandled riscv64-linux syscall: 258\n--2635-- You may be able to write your own handler.\n--2635-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2635-- Nevertheless we consider this a bug.  Please report\n--2635-- it at http://valgrind.org/support/bug_reports.html.\n--2635-- WARNING: unhandled riscv64-linux syscall: 258\n--2635-- You may be able to write your own handler.\n--2635-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2635-- Nevertheless we consider this a bug.  Please report\n--2635-- it at http://valgrind.org/support/bug_reports.html.\n--2635-- WARNING: unhandled riscv64-linux syscall: 258\n--2635-- You may be able to write your own handler.\n--2635-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2635-- Nevertheless we consider this a bug.  Please report\n--2635-- it at http://valgrind.org/support/bug_reports.html.\n--2635-- WARNING: unhandled riscv64-linux syscall: 258\n--2635-- You may be able to write your own handler.\n--2635-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2635-- Nevertheless we consider this a bug.  Please report\n--2635-- it at http://valgrind.org/support/bug_reports.html.\n--2635-- WARNING: unhandled riscv64-linux syscall: 258\n--2635-- You may be able to write your own handler.\n--2635-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2635-- Nevertheless we consider this a bug.  Please report\n--2635-- it at http://valgrind.org/support/bug_reports.html.\n--2635-- WARNING: unhandled riscv64-linux syscall: 258\n--2635-- You may be able to write your own handler.\n--2635-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2635-- Nevertheless we consider this a bug.  Please report\n--2635-- 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:
'--2643-- WARNING: unhandled riscv64-linux syscall: 258\n--2643-- You may be able to write your own handler.\n--2643-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2643-- Nevertheless we consider this a bug.  Please report\n--2643-- it at http://valgrind.org/support/bug_reports.html.\n--2643-- WARNING: unhandled riscv64-linux syscall: 258\n--2643-- You may be able to write your own handler.\n--2643-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2643-- Nevertheless we consider this a bug.  Please report\n--2643-- it at http://valgrind.org/support/bug_reports.html.\n--2643-- WARNING: unhandled riscv64-linux syscall: 258\n--2643-- You may be able to write your own handler.\n--2643-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2643-- Nevertheless we consider this a bug.  Please report\n--2643-- it at http://valgrind.org/support/bug_reports.html.\n--2643-- WARNING: unhandled riscv64-linux syscall: 258\n--2643-- You may be able to write your own handler.\n--2643-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2643-- Nevertheless we consider this a bug.  Please report\n--2643-- it at http://valgrind.org/support/bug_reports.html.\n--2643-- WARNING: unhandled riscv64-linux syscall: 258\n--2643-- You may be able to write your own handler.\n--2643-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2643-- Nevertheless we consider this a bug.  Please report\n--2643-- it at http://valgrind.org/support/bug_reports.html.\n--2643-- WARNING: unhandled riscv64-linux syscall: 258\n--2643-- You may be able to write your own handler.\n--2643-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2643-- Nevertheless we consider this a bug.  Please report\n--2643-- it at http://valgrind.org/support/bug_reports.html.\n--2643-- WARNING: unhandled riscv64-linux syscall: 258\n--2643-- You may be able to write your own handler.\n--2643-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2643-- Nevertheless we consider this a bug.  Please report\n--2643-- it at http://valgrind.org/support/bug_reports.html.\n--2643-- WARNING: unhandled riscv64-linux syscall: 258\n--2643-- You may be able to write your own handler.\n--2643-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2643-- Nevertheless we consider this a bug.  Please report\n--2643-- it at http://valgrind.org/support/bug_reports.html.\n--2643-- WARNING: unhandled riscv64-linux syscall: 258\n--2643-- You may be able to write your own handler.\n--2643-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2643-- Nevertheless we consider this a bug.  Please report\n--2643-- it at http://valgrind.org/support/bug_reports.html.\n--2643-- WARNING: unhandled riscv64-linux syscall: 258\n--2643-- You may be able to write your own handler.\n--2643-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2643-- Nevertheless we consider this a bug.  Please report\n--2643-- it at http://valgrind.org/support/bug_reports.html.\n--2643-- WARNING: unhandled riscv64-linux syscall: 258\n--2643-- You may be able to write your own handler.\n--2643-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2643-- Nevertheless we consider this a bug.  Please report\n--2643-- it at http://valgrind.org/support/bug_reports.html.\n--2643-- WARNING: unhandled riscv64-linux syscall: 258\n--2643-- You may be able to write your own handler.\n--2643-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2643-- Nevertheless we consider this a bug.  Please report\n--2643-- it at http://valgrind.org/support/bug_reports.html.\n--2643-- WARNING: unhandled riscv64-linux syscall: 258\n--2643-- You may be able to write your own handler.\n--2643-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2643-- Nevertheless we consider this a bug.  Please report\n--2643-- it at http://valgrind.org/support/bug_reports.html.\n--2643-- WARNING: unhandled riscv64-linux syscall: 258\n--2643-- You may be able to write your own handler.\n--2643-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2643-- Nevertheless we consider this a bug.  Please report\n--2643-- it at http://valgrind.org/support/bug_reports.html.\n--2643-- WARNING: unhandled riscv64-linux syscall: 258\n--2643-- You may be able to write your own handler.\n--2643-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2643-- Nevertheless we consider this a bug.  Please report\n--2643-- it at http://valgrind.org/support/bug_reports.html.\n--2643-- WARNING: unhandled riscv64-linux syscall: 258\n--2643-- You may be able to write your own handler.\n--2643-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2643-- Nevertheless we consider this a bug.  Please report\n--2643-- it at http://valgrind.org/support/bug_reports.html.\n--2643-- WARNING: unhandled riscv64-linux syscall: 258\n--2643-- You may be able to write your own handler.\n--2643-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2643-- Nevertheless we consider this a bug.  Please report\n--2643-- it at http://valgrind.org/support/bug_reports.html.\n--2643-- WARNING: unhandled riscv64-linux syscall: 258\n--2643-- You may be able to write your own handler.\n--2643-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2643-- Nevertheless we consider this a bug.  Please report\n--2643-- 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:
'--2651-- WARNING: unhandled riscv64-linux syscall: 258\n--2651-- You may be able to write your own handler.\n--2651-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2651-- Nevertheless we consider this a bug.  Please report\n--2651-- it at http://valgrind.org/support/bug_reports.html.\n--2651-- WARNING: unhandled riscv64-linux syscall: 258\n--2651-- You may be able to write your own handler.\n--2651-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2651-- Nevertheless we consider this a bug.  Please report\n--2651-- it at http://valgrind.org/support/bug_reports.html.\n--2651-- WARNING: unhandled riscv64-linux syscall: 258\n--2651-- You may be able to write your own handler.\n--2651-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2651-- Nevertheless we consider this a bug.  Please report\n--2651-- it at http://valgrind.org/support/bug_reports.html.\n--2651-- WARNING: unhandled riscv64-linux syscall: 258\n--2651-- You may be able to write your own handler.\n--2651-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2651-- Nevertheless we consider this a bug.  Please report\n--2651-- it at http://valgrind.org/support/bug_reports.html.\n--2651-- WARNING: unhandled riscv64-linux syscall: 258\n--2651-- You may be able to write your own handler.\n--2651-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2651-- Nevertheless we consider this a bug.  Please report\n--2651-- it at http://valgrind.org/support/bug_reports.html.\n--2651-- WARNING: unhandled riscv64-linux syscall: 258\n--2651-- You may be able to write your own handler.\n--2651-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2651-- Nevertheless we consider this a bug.  Please report\n--2651-- it at http://valgrind.org/support/bug_reports.html.\n--2651-- WARNING: unhandled riscv64-linux syscall: 258\n--2651-- You may be able to write your own handler.\n--2651-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2651-- Nevertheless we consider this a bug.  Please report\n--2651-- it at http://valgrind.org/support/bug_reports.html.\n--2651-- WARNING: unhandled riscv64-linux syscall: 258\n--2651-- You may be able to write your own handler.\n--2651-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2651-- Nevertheless we consider this a bug.  Please report\n--2651-- it at http://valgrind.org/support/bug_reports.html.\n--2651-- WARNING: unhandled riscv64-linux syscall: 258\n--2651-- You may be able to write your own handler.\n--2651-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2651-- Nevertheless we consider this a bug.  Please report\n--2651-- it at http://valgrind.org/support/bug_reports.html.\n--2651-- WARNING: unhandled riscv64-linux syscall: 258\n--2651-- You may be able to write your own handler.\n--2651-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2651-- Nevertheless we consider this a bug.  Please report\n--2651-- it at http://valgrind.org/support/bug_reports.html.\n--2651-- WARNING: unhandled riscv64-linux syscall: 258\n--2651-- You may be able to write your own handler.\n--2651-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2651-- Nevertheless we consider this a bug.  Please report\n--2651-- it at http://valgrind.org/support/bug_reports.html.\n--2651-- WARNING: unhandled riscv64-linux syscall: 258\n--2651-- You may be able to write your own handler.\n--2651-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2651-- Nevertheless we consider this a bug.  Please report\n--2651-- it at http://valgrind.org/support/bug_reports.html.\n--2651-- WARNING: unhandled riscv64-linux syscall: 258\n--2651-- You may be able to write your own handler.\n--2651-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2651-- Nevertheless we consider this a bug.  Please report\n--2651-- it at http://valgrind.org/support/bug_reports.html.\n--2651-- WARNING: unhandled riscv64-linux syscall: 258\n--2651-- You may be able to write your own handler.\n--2651-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2651-- Nevertheless we consider this a bug.  Please report\n--2651-- it at http://valgrind.org/support/bug_reports.html.\n--2651-- WARNING: unhandled riscv64-linux syscall: 258\n--2651-- You may be able to write your own handler.\n--2651-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2651-- Nevertheless we consider this a bug.  Please report\n--2651-- it at http://valgrind.org/support/bug_reports.html.\n--2651-- WARNING: unhandled riscv64-linux syscall: 258\n--2651-- You may be able to write your own handler.\n--2651-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2651-- Nevertheless we consider this a bug.  Please report\n--2651-- it at http://valgrind.org/support/bug_reports.html.\n--2651-- WARNING: unhandled riscv64-linux syscall: 258\n--2651-- You may be able to write your own handler.\n--2651-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2651-- Nevertheless we consider this a bug.  Please report\n--2651-- it at http://valgrind.org/support/bug_reports.html.\n--2651-- WARNING: unhandled riscv64-linux syscall: 258\n--2651-- You may be able to write your own handler.\n--2651-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2651-- Nevertheless we consider this a bug.  Please report\n--2651-- 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:
'--2659-- WARNING: unhandled riscv64-linux syscall: 258\n--2659-- You may be able to write your own handler.\n--2659-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2659-- Nevertheless we consider this a bug.  Please report\n--2659-- it at http://valgrind.org/support/bug_reports.html.\n--2659-- WARNING: unhandled riscv64-linux syscall: 258\n--2659-- You may be able to write your own handler.\n--2659-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2659-- Nevertheless we consider this a bug.  Please report\n--2659-- it at http://valgrind.org/support/bug_reports.html.\n--2659-- WARNING: unhandled riscv64-linux syscall: 258\n--2659-- You may be able to write your own handler.\n--2659-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2659-- Nevertheless we consider this a bug.  Please report\n--2659-- it at http://valgrind.org/support/bug_reports.html.\n--2659-- WARNING: unhandled riscv64-linux syscall: 258\n--2659-- You may be able to write your own handler.\n--2659-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2659-- Nevertheless we consider this a bug.  Please report\n--2659-- it at http://valgrind.org/support/bug_reports.html.\n--2659-- WARNING: unhandled riscv64-linux syscall: 258\n--2659-- You may be able to write your own handler.\n--2659-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2659-- Nevertheless we consider this a bug.  Please report\n--2659-- it at http://valgrind.org/support/bug_reports.html.\n--2659-- WARNING: unhandled riscv64-linux syscall: 258\n--2659-- You may be able to write your own handler.\n--2659-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2659-- Nevertheless we consider this a bug.  Please report\n--2659-- it at http://valgrind.org/support/bug_reports.html.\n--2659-- WARNING: unhandled riscv64-linux syscall: 258\n--2659-- You may be able to write your own handler.\n--2659-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2659-- Nevertheless we consider this a bug.  Please report\n--2659-- it at http://valgrind.org/support/bug_reports.html.\n--2659-- WARNING: unhandled riscv64-linux syscall: 258\n--2659-- You may be able to write your own handler.\n--2659-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2659-- Nevertheless we consider this a bug.  Please report\n--2659-- it at http://valgrind.org/support/bug_reports.html.\n--2659-- WARNING: unhandled riscv64-linux syscall: 258\n--2659-- You may be able to write your own handler.\n--2659-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2659-- Nevertheless we consider this a bug.  Please report\n--2659-- it at http://valgrind.org/support/bug_reports.html.\n--2659-- WARNING: unhandled riscv64-linux syscall: 258\n--2659-- You may be able to write your own handler.\n--2659-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2659-- Nevertheless we consider this a bug.  Please report\n--2659-- it at http://valgrind.org/support/bug_reports.html.\n--2659-- WARNING: unhandled riscv64-linux syscall: 258\n--2659-- You may be able to write your own handler.\n--2659-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2659-- Nevertheless we consider this a bug.  Please report\n--2659-- it at http://valgrind.org/support/bug_reports.html.\n--2659-- WARNING: unhandled riscv64-linux syscall: 258\n--2659-- You may be able to write your own handler.\n--2659-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2659-- Nevertheless we consider this a bug.  Please report\n--2659-- it at http://valgrind.org/support/bug_reports.html.\n--2659-- WARNING: unhandled riscv64-linux syscall: 258\n--2659-- You may be able to write your own handler.\n--2659-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2659-- Nevertheless we consider this a bug.  Please report\n--2659-- it at http://valgrind.org/support/bug_reports.html.\n--2659-- WARNING: unhandled riscv64-linux syscall: 258\n--2659-- You may be able to write your own handler.\n--2659-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2659-- Nevertheless we consider this a bug.  Please report\n--2659-- it at http://valgrind.org/support/bug_reports.html.\n--2659-- WARNING: unhandled riscv64-linux syscall: 258\n--2659-- You may be able to write your own handler.\n--2659-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2659-- Nevertheless we consider this a bug.  Please report\n--2659-- it at http://valgrind.org/support/bug_reports.html.\n--2659-- WARNING: unhandled riscv64-linux syscall: 258\n--2659-- You may be able to write your own handler.\n--2659-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2659-- Nevertheless we consider this a bug.  Please report\n--2659-- it at http://valgrind.org/support/bug_reports.html.\n--2659-- WARNING: unhandled riscv64-linux syscall: 258\n--2659-- You may be able to write your own handler.\n--2659-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2659-- Nevertheless we consider this a bug.  Please report\n--2659-- it at http://valgrind.org/support/bug_reports.html.\n--2659-- WARNING: unhandled riscv64-linux syscall: 258\n--2659-- You may be able to write your own handler.\n--2659-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2659-- Nevertheless we consider this a bug.  Please report\n--2659-- 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:
'--2667-- WARNING: unhandled riscv64-linux syscall: 258\n--2667-- You may be able to write your own handler.\n--2667-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2667-- Nevertheless we consider this a bug.  Please report\n--2667-- it at http://valgrind.org/support/bug_reports.html.\n--2667-- WARNING: unhandled riscv64-linux syscall: 258\n--2667-- You may be able to write your own handler.\n--2667-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2667-- Nevertheless we consider this a bug.  Please report\n--2667-- it at http://valgrind.org/support/bug_reports.html.\n--2667-- WARNING: unhandled riscv64-linux syscall: 258\n--2667-- You may be able to write your own handler.\n--2667-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2667-- Nevertheless we consider this a bug.  Please report\n--2667-- it at http://valgrind.org/support/bug_reports.html.\n--2667-- WARNING: unhandled riscv64-linux syscall: 258\n--2667-- You may be able to write your own handler.\n--2667-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2667-- Nevertheless we consider this a bug.  Please report\n--2667-- it at http://valgrind.org/support/bug_reports.html.\n--2667-- WARNING: unhandled riscv64-linux syscall: 258\n--2667-- You may be able to write your own handler.\n--2667-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2667-- Nevertheless we consider this a bug.  Please report\n--2667-- it at http://valgrind.org/support/bug_reports.html.\n--2667-- WARNING: unhandled riscv64-linux syscall: 258\n--2667-- You may be able to write your own handler.\n--2667-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2667-- Nevertheless we consider this a bug.  Please report\n--2667-- it at http://valgrind.org/support/bug_reports.html.\n--2667-- WARNING: unhandled riscv64-linux syscall: 258\n--2667-- You may be able to write your own handler.\n--2667-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2667-- Nevertheless we consider this a bug.  Please report\n--2667-- it at http://valgrind.org/support/bug_reports.html.\n--2667-- WARNING: unhandled riscv64-linux syscall: 258\n--2667-- You may be able to write your own handler.\n--2667-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2667-- Nevertheless we consider this a bug.  Please report\n--2667-- it at http://valgrind.org/support/bug_reports.html.\n--2667-- WARNING: unhandled riscv64-linux syscall: 258\n--2667-- You may be able to write your own handler.\n--2667-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2667-- Nevertheless we consider this a bug.  Please report\n--2667-- it at http://valgrind.org/support/bug_reports.html.\n--2667-- WARNING: unhandled riscv64-linux syscall: 258\n--2667-- You may be able to write your own handler.\n--2667-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2667-- Nevertheless we consider this a bug.  Please report\n--2667-- it at http://valgrind.org/support/bug_reports.html.\n--2667-- WARNING: unhandled riscv64-linux syscall: 258\n--2667-- You may be able to write your own handler.\n--2667-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2667-- Nevertheless we consider this a bug.  Please report\n--2667-- it at http://valgrind.org/support/bug_reports.html.\n--2667-- WARNING: unhandled riscv64-linux syscall: 258\n--2667-- You may be able to write your own handler.\n--2667-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2667-- Nevertheless we consider this a bug.  Please report\n--2667-- it at http://valgrind.org/support/bug_reports.html.\n--2667-- WARNING: unhandled riscv64-linux syscall: 258\n--2667-- You may be able to write your own handler.\n--2667-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2667-- Nevertheless we consider this a bug.  Please report\n--2667-- it at http://valgrind.org/support/bug_reports.html.\n--2667-- WARNING: unhandled riscv64-linux syscall: 258\n--2667-- You may be able to write your own handler.\n--2667-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2667-- Nevertheless we consider this a bug.  Please report\n--2667-- it at http://valgrind.org/support/bug_reports.html.\n--2667-- WARNING: unhandled riscv64-linux syscall: 258\n--2667-- You may be able to write your own handler.\n--2667-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2667-- Nevertheless we consider this a bug.  Please report\n--2667-- it at http://valgrind.org/support/bug_reports.html.\n--2667-- WARNING: unhandled riscv64-linux syscall: 258\n--2667-- You may be able to write your own handler.\n--2667-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2667-- Nevertheless we consider this a bug.  Please report\n--2667-- it at http://valgrind.org/support/bug_reports.html.\n--2667-- WARNING: unhandled riscv64-linux syscall: 258\n--2667-- You may be able to write your own handler.\n--2667-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2667-- Nevertheless we consider this a bug.  Please report\n--2667-- it at http://valgrind.org/support/bug_reports.html.\n--2667-- WARNING: unhandled riscv64-linux syscall: 258\n--2667-- You may be able to write your own handler.\n--2667-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2667-- Nevertheless we consider this a bug.  Please report\n--2667-- 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:
'--2675-- WARNING: unhandled riscv64-linux syscall: 258\n--2675-- You may be able to write your own handler.\n--2675-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2675-- Nevertheless we consider this a bug.  Please report\n--2675-- it at http://valgrind.org/support/bug_reports.html.\n--2675-- WARNING: unhandled riscv64-linux syscall: 258\n--2675-- You may be able to write your own handler.\n--2675-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2675-- Nevertheless we consider this a bug.  Please report\n--2675-- it at http://valgrind.org/support/bug_reports.html.\n--2675-- WARNING: unhandled riscv64-linux syscall: 258\n--2675-- You may be able to write your own handler.\n--2675-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2675-- Nevertheless we consider this a bug.  Please report\n--2675-- it at http://valgrind.org/support/bug_reports.html.\n--2675-- WARNING: unhandled riscv64-linux syscall: 258\n--2675-- You may be able to write your own handler.\n--2675-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2675-- Nevertheless we consider this a bug.  Please report\n--2675-- it at http://valgrind.org/support/bug_reports.html.\n--2675-- WARNING: unhandled riscv64-linux syscall: 258\n--2675-- You may be able to write your own handler.\n--2675-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2675-- Nevertheless we consider this a bug.  Please report\n--2675-- it at http://valgrind.org/support/bug_reports.html.\n--2675-- WARNING: unhandled riscv64-linux syscall: 258\n--2675-- You may be able to write your own handler.\n--2675-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2675-- Nevertheless we consider this a bug.  Please report\n--2675-- it at http://valgrind.org/support/bug_reports.html.\n--2675-- WARNING: unhandled riscv64-linux syscall: 258\n--2675-- You may be able to write your own handler.\n--2675-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2675-- Nevertheless we consider this a bug.  Please report\n--2675-- it at http://valgrind.org/support/bug_reports.html.\n--2675-- WARNING: unhandled riscv64-linux syscall: 258\n--2675-- You may be able to write your own handler.\n--2675-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2675-- Nevertheless we consider this a bug.  Please report\n--2675-- it at http://valgrind.org/support/bug_reports.html.\n--2675-- WARNING: unhandled riscv64-linux syscall: 258\n--2675-- You may be able to write your own handler.\n--2675-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2675-- Nevertheless we consider this a bug.  Please report\n--2675-- it at http://valgrind.org/support/bug_reports.html.\n--2675-- WARNING: unhandled riscv64-linux syscall: 258\n--2675-- You may be able to write your own handler.\n--2675-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2675-- Nevertheless we consider this a bug.  Please report\n--2675-- it at http://valgrind.org/support/bug_reports.html.\n--2675-- WARNING: unhandled riscv64-linux syscall: 258\n--2675-- You may be able to write your own handler.\n--2675-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2675-- Nevertheless we consider this a bug.  Please report\n--2675-- it at http://valgrind.org/support/bug_reports.html.\n--2675-- WARNING: unhandled riscv64-linux syscall: 258\n--2675-- You may be able to write your own handler.\n--2675-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2675-- Nevertheless we consider this a bug.  Please report\n--2675-- it at http://valgrind.org/support/bug_reports.html.\n--2675-- WARNING: unhandled riscv64-linux syscall: 258\n--2675-- You may be able to write your own handler.\n--2675-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2675-- Nevertheless we consider this a bug.  Please report\n--2675-- it at http://valgrind.org/support/bug_reports.html.\n--2675-- WARNING: unhandled riscv64-linux syscall: 258\n--2675-- You may be able to write your own handler.\n--2675-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2675-- Nevertheless we consider this a bug.  Please report\n--2675-- it at http://valgrind.org/support/bug_reports.html.\n--2675-- WARNING: unhandled riscv64-linux syscall: 258\n--2675-- You may be able to write your own handler.\n--2675-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2675-- Nevertheless we consider this a bug.  Please report\n--2675-- it at http://valgrind.org/support/bug_reports.html.\n--2675-- WARNING: unhandled riscv64-linux syscall: 258\n--2675-- You may be able to write your own handler.\n--2675-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2675-- Nevertheless we consider this a bug.  Please report\n--2675-- it at http://valgrind.org/support/bug_reports.html.\n--2675-- WARNING: unhandled riscv64-linux syscall: 258\n--2675-- You may be able to write your own handler.\n--2675-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2675-- Nevertheless we consider this a bug.  Please report\n--2675-- it at http://valgrind.org/support/bug_reports.html.\n--2675-- WARNING: unhandled riscv64-linux syscall: 258\n--2675-- You may be able to write your own handler.\n--2675-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2675-- Nevertheless we consider this a bug.  Please report\n--2675-- 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:
'--2683-- WARNING: unhandled riscv64-linux syscall: 258\n--2683-- You may be able to write your own handler.\n--2683-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2683-- Nevertheless we consider this a bug.  Please report\n--2683-- it at http://valgrind.org/support/bug_reports.html.\n--2683-- WARNING: unhandled riscv64-linux syscall: 258\n--2683-- You may be able to write your own handler.\n--2683-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2683-- Nevertheless we consider this a bug.  Please report\n--2683-- it at http://valgrind.org/support/bug_reports.html.\n--2683-- WARNING: unhandled riscv64-linux syscall: 258\n--2683-- You may be able to write your own handler.\n--2683-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2683-- Nevertheless we consider this a bug.  Please report\n--2683-- it at http://valgrind.org/support/bug_reports.html.\n--2683-- WARNING: unhandled riscv64-linux syscall: 258\n--2683-- You may be able to write your own handler.\n--2683-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2683-- Nevertheless we consider this a bug.  Please report\n--2683-- it at http://valgrind.org/support/bug_reports.html.\n--2683-- WARNING: unhandled riscv64-linux syscall: 258\n--2683-- You may be able to write your own handler.\n--2683-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2683-- Nevertheless we consider this a bug.  Please report\n--2683-- it at http://valgrind.org/support/bug_reports.html.\n--2683-- WARNING: unhandled riscv64-linux syscall: 258\n--2683-- You may be able to write your own handler.\n--2683-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2683-- Nevertheless we consider this a bug.  Please report\n--2683-- it at http://valgrind.org/support/bug_reports.html.\n--2683-- WARNING: unhandled riscv64-linux syscall: 258\n--2683-- You may be able to write your own handler.\n--2683-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2683-- Nevertheless we consider this a bug.  Please report\n--2683-- it at http://valgrind.org/support/bug_reports.html.\n--2683-- WARNING: unhandled riscv64-linux syscall: 258\n--2683-- You may be able to write your own handler.\n--2683-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2683-- Nevertheless we consider this a bug.  Please report\n--2683-- it at http://valgrind.org/support/bug_reports.html.\n--2683-- WARNING: unhandled riscv64-linux syscall: 258\n--2683-- You may be able to write your own handler.\n--2683-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2683-- Nevertheless we consider this a bug.  Please report\n--2683-- it at http://valgrind.org/support/bug_reports.html.\n--2683-- WARNING: unhandled riscv64-linux syscall: 258\n--2683-- You may be able to write your own handler.\n--2683-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2683-- Nevertheless we consider this a bug.  Please report\n--2683-- it at http://valgrind.org/support/bug_reports.html.\n--2683-- WARNING: unhandled riscv64-linux syscall: 258\n--2683-- You may be able to write your own handler.\n--2683-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2683-- Nevertheless we consider this a bug.  Please report\n--2683-- it at http://valgrind.org/support/bug_reports.html.\n--2683-- WARNING: unhandled riscv64-linux syscall: 258\n--2683-- You may be able to write your own handler.\n--2683-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2683-- Nevertheless we consider this a bug.  Please report\n--2683-- it at http://valgrind.org/support/bug_reports.html.\n--2683-- WARNING: unhandled riscv64-linux syscall: 258\n--2683-- You may be able to write your own handler.\n--2683-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2683-- Nevertheless we consider this a bug.  Please report\n--2683-- it at http://valgrind.org/support/bug_reports.html.\n--2683-- WARNING: unhandled riscv64-linux syscall: 258\n--2683-- You may be able to write your own handler.\n--2683-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2683-- Nevertheless we consider this a bug.  Please report\n--2683-- it at http://valgrind.org/support/bug_reports.html.\n--2683-- WARNING: unhandled riscv64-linux syscall: 258\n--2683-- You may be able to write your own handler.\n--2683-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2683-- Nevertheless we consider this a bug.  Please report\n--2683-- it at http://valgrind.org/support/bug_reports.html.\n--2683-- WARNING: unhandled riscv64-linux syscall: 258\n--2683-- You may be able to write your own handler.\n--2683-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2683-- Nevertheless we consider this a bug.  Please report\n--2683-- it at http://valgrind.org/support/bug_reports.html.\n--2683-- WARNING: unhandled riscv64-linux syscall: 258\n--2683-- You may be able to write your own handler.\n--2683-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2683-- Nevertheless we consider this a bug.  Please report\n--2683-- it at http://valgrind.org/support/bug_reports.html.\n--2683-- WARNING: unhandled riscv64-linux syscall: 258\n--2683-- You may be able to write your own handler.\n--2683-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2683-- Nevertheless we consider this a bug.  Please report\n--2683-- 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:
'--2691-- WARNING: unhandled riscv64-linux syscall: 258\n--2691-- You may be able to write your own handler.\n--2691-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2691-- Nevertheless we consider this a bug.  Please report\n--2691-- it at http://valgrind.org/support/bug_reports.html.\n--2691-- WARNING: unhandled riscv64-linux syscall: 258\n--2691-- You may be able to write your own handler.\n--2691-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2691-- Nevertheless we consider this a bug.  Please report\n--2691-- it at http://valgrind.org/support/bug_reports.html.\n--2691-- WARNING: unhandled riscv64-linux syscall: 258\n--2691-- You may be able to write your own handler.\n--2691-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2691-- Nevertheless we consider this a bug.  Please report\n--2691-- it at http://valgrind.org/support/bug_reports.html.\n--2691-- WARNING: unhandled riscv64-linux syscall: 258\n--2691-- You may be able to write your own handler.\n--2691-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2691-- Nevertheless we consider this a bug.  Please report\n--2691-- it at http://valgrind.org/support/bug_reports.html.\n--2691-- WARNING: unhandled riscv64-linux syscall: 258\n--2691-- You may be able to write your own handler.\n--2691-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2691-- Nevertheless we consider this a bug.  Please report\n--2691-- it at http://valgrind.org/support/bug_reports.html.\n--2691-- WARNING: unhandled riscv64-linux syscall: 258\n--2691-- You may be able to write your own handler.\n--2691-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2691-- Nevertheless we consider this a bug.  Please report\n--2691-- it at http://valgrind.org/support/bug_reports.html.\n--2691-- WARNING: unhandled riscv64-linux syscall: 258\n--2691-- You may be able to write your own handler.\n--2691-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2691-- Nevertheless we consider this a bug.  Please report\n--2691-- it at http://valgrind.org/support/bug_reports.html.\n--2691-- WARNING: unhandled riscv64-linux syscall: 258\n--2691-- You may be able to write your own handler.\n--2691-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2691-- Nevertheless we consider this a bug.  Please report\n--2691-- it at http://valgrind.org/support/bug_reports.html.\n--2691-- WARNING: unhandled riscv64-linux syscall: 258\n--2691-- You may be able to write your own handler.\n--2691-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2691-- Nevertheless we consider this a bug.  Please report\n--2691-- it at http://valgrind.org/support/bug_reports.html.\n--2691-- WARNING: unhandled riscv64-linux syscall: 258\n--2691-- You may be able to write your own handler.\n--2691-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2691-- Nevertheless we consider this a bug.  Please report\n--2691-- it at http://valgrind.org/support/bug_reports.html.\n--2691-- WARNING: unhandled riscv64-linux syscall: 258\n--2691-- You may be able to write your own handler.\n--2691-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2691-- Nevertheless we consider this a bug.  Please report\n--2691-- it at http://valgrind.org/support/bug_reports.html.\n--2691-- WARNING: unhandled riscv64-linux syscall: 258\n--2691-- You may be able to write your own handler.\n--2691-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2691-- Nevertheless we consider this a bug.  Please report\n--2691-- it at http://valgrind.org/support/bug_reports.html.\n--2691-- WARNING: unhandled riscv64-linux syscall: 258\n--2691-- You may be able to write your own handler.\n--2691-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2691-- Nevertheless we consider this a bug.  Please report\n--2691-- it at http://valgrind.org/support/bug_reports.html.\n--2691-- WARNING: unhandled riscv64-linux syscall: 258\n--2691-- You may be able to write your own handler.\n--2691-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2691-- Nevertheless we consider this a bug.  Please report\n--2691-- it at http://valgrind.org/support/bug_reports.html.\n--2691-- WARNING: unhandled riscv64-linux syscall: 258\n--2691-- You may be able to write your own handler.\n--2691-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2691-- Nevertheless we consider this a bug.  Please report\n--2691-- it at http://valgrind.org/support/bug_reports.html.\n--2691-- WARNING: unhandled riscv64-linux syscall: 258\n--2691-- You may be able to write your own handler.\n--2691-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2691-- Nevertheless we consider this a bug.  Please report\n--2691-- it at http://valgrind.org/support/bug_reports.html.\n--2691-- WARNING: unhandled riscv64-linux syscall: 258\n--2691-- You may be able to write your own handler.\n--2691-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2691-- Nevertheless we consider this a bug.  Please report\n--2691-- it at http://valgrind.org/support/bug_reports.html.\n--2691-- WARNING: unhandled riscv64-linux syscall: 258\n--2691-- You may be able to write your own handler.\n--2691-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2691-- Nevertheless we consider this a bug.  Please report\n--2691-- 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:
'--2699-- WARNING: unhandled riscv64-linux syscall: 258\n--2699-- You may be able to write your own handler.\n--2699-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2699-- Nevertheless we consider this a bug.  Please report\n--2699-- it at http://valgrind.org/support/bug_reports.html.\n--2699-- WARNING: unhandled riscv64-linux syscall: 258\n--2699-- You may be able to write your own handler.\n--2699-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2699-- Nevertheless we consider this a bug.  Please report\n--2699-- it at http://valgrind.org/support/bug_reports.html.\n--2699-- WARNING: unhandled riscv64-linux syscall: 258\n--2699-- You may be able to write your own handler.\n--2699-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2699-- Nevertheless we consider this a bug.  Please report\n--2699-- it at http://valgrind.org/support/bug_reports.html.\n--2699-- WARNING: unhandled riscv64-linux syscall: 258\n--2699-- You may be able to write your own handler.\n--2699-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2699-- Nevertheless we consider this a bug.  Please report\n--2699-- it at http://valgrind.org/support/bug_reports.html.\n--2699-- WARNING: unhandled riscv64-linux syscall: 258\n--2699-- You may be able to write your own handler.\n--2699-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2699-- Nevertheless we consider this a bug.  Please report\n--2699-- it at http://valgrind.org/support/bug_reports.html.\n--2699-- WARNING: unhandled riscv64-linux syscall: 258\n--2699-- You may be able to write your own handler.\n--2699-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2699-- Nevertheless we consider this a bug.  Please report\n--2699-- it at http://valgrind.org/support/bug_reports.html.\n--2699-- WARNING: unhandled riscv64-linux syscall: 258\n--2699-- You may be able to write your own handler.\n--2699-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2699-- Nevertheless we consider this a bug.  Please report\n--2699-- it at http://valgrind.org/support/bug_reports.html.\n--2699-- WARNING: unhandled riscv64-linux syscall: 258\n--2699-- You may be able to write your own handler.\n--2699-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2699-- Nevertheless we consider this a bug.  Please report\n--2699-- it at http://valgrind.org/support/bug_reports.html.\n--2699-- WARNING: unhandled riscv64-linux syscall: 258\n--2699-- You may be able to write your own handler.\n--2699-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2699-- Nevertheless we consider this a bug.  Please report\n--2699-- it at http://valgrind.org/support/bug_reports.html.\n--2699-- WARNING: unhandled riscv64-linux syscall: 258\n--2699-- You may be able to write your own handler.\n--2699-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2699-- Nevertheless we consider this a bug.  Please report\n--2699-- it at http://valgrind.org/support/bug_reports.html.\n--2699-- WARNING: unhandled riscv64-linux syscall: 258\n--2699-- You may be able to write your own handler.\n--2699-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2699-- Nevertheless we consider this a bug.  Please report\n--2699-- it at http://valgrind.org/support/bug_reports.html.\n--2699-- WARNING: unhandled riscv64-linux syscall: 258\n--2699-- You may be able to write your own handler.\n--2699-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2699-- Nevertheless we consider this a bug.  Please report\n--2699-- it at http://valgrind.org/support/bug_reports.html.\n--2699-- WARNING: unhandled riscv64-linux syscall: 258\n--2699-- You may be able to write your own handler.\n--2699-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2699-- Nevertheless we consider this a bug.  Please report\n--2699-- it at http://valgrind.org/support/bug_reports.html.\n--2699-- WARNING: unhandled riscv64-linux syscall: 258\n--2699-- You may be able to write your own handler.\n--2699-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2699-- Nevertheless we consider this a bug.  Please report\n--2699-- it at http://valgrind.org/support/bug_reports.html.\n--2699-- WARNING: unhandled riscv64-linux syscall: 258\n--2699-- You may be able to write your own handler.\n--2699-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2699-- Nevertheless we consider this a bug.  Please report\n--2699-- it at http://valgrind.org/support/bug_reports.html.\n--2699-- WARNING: unhandled riscv64-linux syscall: 258\n--2699-- You may be able to write your own handler.\n--2699-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2699-- Nevertheless we consider this a bug.  Please report\n--2699-- it at http://valgrind.org/support/bug_reports.html.\n--2699-- WARNING: unhandled riscv64-linux syscall: 258\n--2699-- You may be able to write your own handler.\n--2699-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2699-- Nevertheless we consider this a bug.  Please report\n--2699-- it at http://valgrind.org/support/bug_reports.html.\n--2699-- WARNING: unhandled riscv64-linux syscall: 258\n--2699-- You may be able to write your own handler.\n--2699-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2699-- Nevertheless we consider this a bug.  Please report\n--2699-- 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:
'--2707-- WARNING: unhandled riscv64-linux syscall: 258\n--2707-- You may be able to write your own handler.\n--2707-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2707-- Nevertheless we consider this a bug.  Please report\n--2707-- it at http://valgrind.org/support/bug_reports.html.\n--2707-- WARNING: unhandled riscv64-linux syscall: 258\n--2707-- You may be able to write your own handler.\n--2707-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2707-- Nevertheless we consider this a bug.  Please report\n--2707-- it at http://valgrind.org/support/bug_reports.html.\n--2707-- WARNING: unhandled riscv64-linux syscall: 258\n--2707-- You may be able to write your own handler.\n--2707-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2707-- Nevertheless we consider this a bug.  Please report\n--2707-- it at http://valgrind.org/support/bug_reports.html.\n--2707-- WARNING: unhandled riscv64-linux syscall: 258\n--2707-- You may be able to write your own handler.\n--2707-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2707-- Nevertheless we consider this a bug.  Please report\n--2707-- it at http://valgrind.org/support/bug_reports.html.\n--2707-- WARNING: unhandled riscv64-linux syscall: 258\n--2707-- You may be able to write your own handler.\n--2707-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2707-- Nevertheless we consider this a bug.  Please report\n--2707-- it at http://valgrind.org/support/bug_reports.html.\n--2707-- WARNING: unhandled riscv64-linux syscall: 258\n--2707-- You may be able to write your own handler.\n--2707-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2707-- Nevertheless we consider this a bug.  Please report\n--2707-- it at http://valgrind.org/support/bug_reports.html.\n--2707-- WARNING: unhandled riscv64-linux syscall: 258\n--2707-- You may be able to write your own handler.\n--2707-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2707-- Nevertheless we consider this a bug.  Please report\n--2707-- it at http://valgrind.org/support/bug_reports.html.\n--2707-- WARNING: unhandled riscv64-linux syscall: 258\n--2707-- You may be able to write your own handler.\n--2707-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2707-- Nevertheless we consider this a bug.  Please report\n--2707-- it at http://valgrind.org/support/bug_reports.html.\n--2707-- WARNING: unhandled riscv64-linux syscall: 258\n--2707-- You may be able to write your own handler.\n--2707-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2707-- Nevertheless we consider this a bug.  Please report\n--2707-- it at http://valgrind.org/support/bug_reports.html.\n--2707-- WARNING: unhandled riscv64-linux syscall: 258\n--2707-- You may be able to write your own handler.\n--2707-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2707-- Nevertheless we consider this a bug.  Please report\n--2707-- it at http://valgrind.org/support/bug_reports.html.\n--2707-- WARNING: unhandled riscv64-linux syscall: 258\n--2707-- You may be able to write your own handler.\n--2707-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2707-- Nevertheless we consider this a bug.  Please report\n--2707-- it at http://valgrind.org/support/bug_reports.html.\n--2707-- WARNING: unhandled riscv64-linux syscall: 258\n--2707-- You may be able to write your own handler.\n--2707-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2707-- Nevertheless we consider this a bug.  Please report\n--2707-- it at http://valgrind.org/support/bug_reports.html.\n--2707-- WARNING: unhandled riscv64-linux syscall: 258\n--2707-- You may be able to write your own handler.\n--2707-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2707-- Nevertheless we consider this a bug.  Please report\n--2707-- it at http://valgrind.org/support/bug_reports.html.\n--2707-- WARNING: unhandled riscv64-linux syscall: 258\n--2707-- You may be able to write your own handler.\n--2707-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2707-- Nevertheless we consider this a bug.  Please report\n--2707-- it at http://valgrind.org/support/bug_reports.html.\n--2707-- WARNING: unhandled riscv64-linux syscall: 258\n--2707-- You may be able to write your own handler.\n--2707-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2707-- Nevertheless we consider this a bug.  Please report\n--2707-- it at http://valgrind.org/support/bug_reports.html.\n--2707-- WARNING: unhandled riscv64-linux syscall: 258\n--2707-- You may be able to write your own handler.\n--2707-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2707-- Nevertheless we consider this a bug.  Please report\n--2707-- it at http://valgrind.org/support/bug_reports.html.\n--2707-- WARNING: unhandled riscv64-linux syscall: 258\n--2707-- You may be able to write your own handler.\n--2707-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2707-- Nevertheless we consider this a bug.  Please report\n--2707-- it at http://valgrind.org/support/bug_reports.html.\n--2707-- WARNING: unhandled riscv64-linux syscall: 258\n--2707-- You may be able to write your own handler.\n--2707-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2707-- Nevertheless we consider this a bug.  Please report\n--2707-- 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:
'--2715-- WARNING: unhandled riscv64-linux syscall: 258\n--2715-- You may be able to write your own handler.\n--2715-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2715-- Nevertheless we consider this a bug.  Please report\n--2715-- it at http://valgrind.org/support/bug_reports.html.\n--2715-- WARNING: unhandled riscv64-linux syscall: 258\n--2715-- You may be able to write your own handler.\n--2715-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2715-- Nevertheless we consider this a bug.  Please report\n--2715-- it at http://valgrind.org/support/bug_reports.html.\n--2715-- WARNING: unhandled riscv64-linux syscall: 258\n--2715-- You may be able to write your own handler.\n--2715-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2715-- Nevertheless we consider this a bug.  Please report\n--2715-- it at http://valgrind.org/support/bug_reports.html.\n--2715-- WARNING: unhandled riscv64-linux syscall: 258\n--2715-- You may be able to write your own handler.\n--2715-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2715-- Nevertheless we consider this a bug.  Please report\n--2715-- it at http://valgrind.org/support/bug_reports.html.\n--2715-- WARNING: unhandled riscv64-linux syscall: 258\n--2715-- You may be able to write your own handler.\n--2715-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2715-- Nevertheless we consider this a bug.  Please report\n--2715-- it at http://valgrind.org/support/bug_reports.html.\n--2715-- WARNING: unhandled riscv64-linux syscall: 258\n--2715-- You may be able to write your own handler.\n--2715-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2715-- Nevertheless we consider this a bug.  Please report\n--2715-- it at http://valgrind.org/support/bug_reports.html.\n--2715-- WARNING: unhandled riscv64-linux syscall: 258\n--2715-- You may be able to write your own handler.\n--2715-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2715-- Nevertheless we consider this a bug.  Please report\n--2715-- it at http://valgrind.org/support/bug_reports.html.\n--2715-- WARNING: unhandled riscv64-linux syscall: 258\n--2715-- You may be able to write your own handler.\n--2715-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2715-- Nevertheless we consider this a bug.  Please report\n--2715-- it at http://valgrind.org/support/bug_reports.html.\n--2715-- WARNING: unhandled riscv64-linux syscall: 258\n--2715-- You may be able to write your own handler.\n--2715-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2715-- Nevertheless we consider this a bug.  Please report\n--2715-- it at http://valgrind.org/support/bug_reports.html.\n--2715-- WARNING: unhandled riscv64-linux syscall: 258\n--2715-- You may be able to write your own handler.\n--2715-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2715-- Nevertheless we consider this a bug.  Please report\n--2715-- it at http://valgrind.org/support/bug_reports.html.\n--2715-- WARNING: unhandled riscv64-linux syscall: 258\n--2715-- You may be able to write your own handler.\n--2715-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2715-- Nevertheless we consider this a bug.  Please report\n--2715-- it at http://valgrind.org/support/bug_reports.html.\n--2715-- WARNING: unhandled riscv64-linux syscall: 258\n--2715-- You may be able to write your own handler.\n--2715-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2715-- Nevertheless we consider this a bug.  Please report\n--2715-- it at http://valgrind.org/support/bug_reports.html.\n--2715-- WARNING: unhandled riscv64-linux syscall: 258\n--2715-- You may be able to write your own handler.\n--2715-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2715-- Nevertheless we consider this a bug.  Please report\n--2715-- it at http://valgrind.org/support/bug_reports.html.\n--2715-- WARNING: unhandled riscv64-linux syscall: 258\n--2715-- You may be able to write your own handler.\n--2715-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2715-- Nevertheless we consider this a bug.  Please report\n--2715-- it at http://valgrind.org/support/bug_reports.html.\n--2715-- WARNING: unhandled riscv64-linux syscall: 258\n--2715-- You may be able to write your own handler.\n--2715-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2715-- Nevertheless we consider this a bug.  Please report\n--2715-- it at http://valgrind.org/support/bug_reports.html.\n--2715-- WARNING: unhandled riscv64-linux syscall: 258\n--2715-- You may be able to write your own handler.\n--2715-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2715-- Nevertheless we consider this a bug.  Please report\n--2715-- it at http://valgrind.org/support/bug_reports.html.\n--2715-- WARNING: unhandled riscv64-linux syscall: 258\n--2715-- You may be able to write your own handler.\n--2715-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2715-- Nevertheless we consider this a bug.  Please report\n--2715-- it at http://valgrind.org/support/bug_reports.html.\n--2715-- WARNING: unhandled riscv64-linux syscall: 258\n--2715-- You may be able to write your own handler.\n--2715-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2715-- Nevertheless we consider this a bug.  Please report\n--2715-- 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:
'--2723-- WARNING: unhandled riscv64-linux syscall: 258\n--2723-- You may be able to write your own handler.\n--2723-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2723-- Nevertheless we consider this a bug.  Please report\n--2723-- it at http://valgrind.org/support/bug_reports.html.\n--2723-- WARNING: unhandled riscv64-linux syscall: 258\n--2723-- You may be able to write your own handler.\n--2723-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2723-- Nevertheless we consider this a bug.  Please report\n--2723-- it at http://valgrind.org/support/bug_reports.html.\n--2723-- WARNING: unhandled riscv64-linux syscall: 258\n--2723-- You may be able to write your own handler.\n--2723-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2723-- Nevertheless we consider this a bug.  Please report\n--2723-- it at http://valgrind.org/support/bug_reports.html.\n--2723-- WARNING: unhandled riscv64-linux syscall: 258\n--2723-- You may be able to write your own handler.\n--2723-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2723-- Nevertheless we consider this a bug.  Please report\n--2723-- it at http://valgrind.org/support/bug_reports.html.\n--2723-- WARNING: unhandled riscv64-linux syscall: 258\n--2723-- You may be able to write your own handler.\n--2723-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2723-- Nevertheless we consider this a bug.  Please report\n--2723-- it at http://valgrind.org/support/bug_reports.html.\n--2723-- WARNING: unhandled riscv64-linux syscall: 258\n--2723-- You may be able to write your own handler.\n--2723-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2723-- Nevertheless we consider this a bug.  Please report\n--2723-- it at http://valgrind.org/support/bug_reports.html.\n--2723-- WARNING: unhandled riscv64-linux syscall: 258\n--2723-- You may be able to write your own handler.\n--2723-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2723-- Nevertheless we consider this a bug.  Please report\n--2723-- it at http://valgrind.org/support/bug_reports.html.\n--2723-- WARNING: unhandled riscv64-linux syscall: 258\n--2723-- You may be able to write your own handler.\n--2723-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2723-- Nevertheless we consider this a bug.  Please report\n--2723-- it at http://valgrind.org/support/bug_reports.html.\n--2723-- WARNING: unhandled riscv64-linux syscall: 258\n--2723-- You may be able to write your own handler.\n--2723-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2723-- Nevertheless we consider this a bug.  Please report\n--2723-- it at http://valgrind.org/support/bug_reports.html.\n--2723-- WARNING: unhandled riscv64-linux syscall: 258\n--2723-- You may be able to write your own handler.\n--2723-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2723-- Nevertheless we consider this a bug.  Please report\n--2723-- it at http://valgrind.org/support/bug_reports.html.\n--2723-- WARNING: unhandled riscv64-linux syscall: 258\n--2723-- You may be able to write your own handler.\n--2723-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2723-- Nevertheless we consider this a bug.  Please report\n--2723-- it at http://valgrind.org/support/bug_reports.html.\n--2723-- WARNING: unhandled riscv64-linux syscall: 258\n--2723-- You may be able to write your own handler.\n--2723-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2723-- Nevertheless we consider this a bug.  Please report\n--2723-- it at http://valgrind.org/support/bug_reports.html.\n--2723-- WARNING: unhandled riscv64-linux syscall: 258\n--2723-- You may be able to write your own handler.\n--2723-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2723-- Nevertheless we consider this a bug.  Please report\n--2723-- it at http://valgrind.org/support/bug_reports.html.\n--2723-- WARNING: unhandled riscv64-linux syscall: 258\n--2723-- You may be able to write your own handler.\n--2723-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2723-- Nevertheless we consider this a bug.  Please report\n--2723-- it at http://valgrind.org/support/bug_reports.html.\n--2723-- WARNING: unhandled riscv64-linux syscall: 258\n--2723-- You may be able to write your own handler.\n--2723-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2723-- Nevertheless we consider this a bug.  Please report\n--2723-- it at http://valgrind.org/support/bug_reports.html.\n--2723-- WARNING: unhandled riscv64-linux syscall: 258\n--2723-- You may be able to write your own handler.\n--2723-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2723-- Nevertheless we consider this a bug.  Please report\n--2723-- it at http://valgrind.org/support/bug_reports.html.\n--2723-- WARNING: unhandled riscv64-linux syscall: 258\n--2723-- You may be able to write your own handler.\n--2723-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2723-- Nevertheless we consider this a bug.  Please report\n--2723-- it at http://valgrind.org/support/bug_reports.html.\n--2723-- WARNING: unhandled riscv64-linux syscall: 258\n--2723-- You may be able to write your own handler.\n--2723-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2723-- Nevertheless we consider this a bug.  Please report\n--2723-- 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:
'--2731-- WARNING: unhandled riscv64-linux syscall: 258\n--2731-- You may be able to write your own handler.\n--2731-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2731-- Nevertheless we consider this a bug.  Please report\n--2731-- it at http://valgrind.org/support/bug_reports.html.\n--2731-- WARNING: unhandled riscv64-linux syscall: 258\n--2731-- You may be able to write your own handler.\n--2731-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2731-- Nevertheless we consider this a bug.  Please report\n--2731-- it at http://valgrind.org/support/bug_reports.html.\n--2731-- WARNING: unhandled riscv64-linux syscall: 258\n--2731-- You may be able to write your own handler.\n--2731-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2731-- Nevertheless we consider this a bug.  Please report\n--2731-- it at http://valgrind.org/support/bug_reports.html.\n--2731-- WARNING: unhandled riscv64-linux syscall: 258\n--2731-- You may be able to write your own handler.\n--2731-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2731-- Nevertheless we consider this a bug.  Please report\n--2731-- it at http://valgrind.org/support/bug_reports.html.\n--2731-- WARNING: unhandled riscv64-linux syscall: 258\n--2731-- You may be able to write your own handler.\n--2731-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2731-- Nevertheless we consider this a bug.  Please report\n--2731-- it at http://valgrind.org/support/bug_reports.html.\n--2731-- WARNING: unhandled riscv64-linux syscall: 258\n--2731-- You may be able to write your own handler.\n--2731-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2731-- Nevertheless we consider this a bug.  Please report\n--2731-- it at http://valgrind.org/support/bug_reports.html.\n--2731-- WARNING: unhandled riscv64-linux syscall: 258\n--2731-- You may be able to write your own handler.\n--2731-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2731-- Nevertheless we consider this a bug.  Please report\n--2731-- it at http://valgrind.org/support/bug_reports.html.\n--2731-- WARNING: unhandled riscv64-linux syscall: 258\n--2731-- You may be able to write your own handler.\n--2731-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2731-- Nevertheless we consider this a bug.  Please report\n--2731-- it at http://valgrind.org/support/bug_reports.html.\n--2731-- WARNING: unhandled riscv64-linux syscall: 258\n--2731-- You may be able to write your own handler.\n--2731-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2731-- Nevertheless we consider this a bug.  Please report\n--2731-- it at http://valgrind.org/support/bug_reports.html.\n--2731-- WARNING: unhandled riscv64-linux syscall: 258\n--2731-- You may be able to write your own handler.\n--2731-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2731-- Nevertheless we consider this a bug.  Please report\n--2731-- it at http://valgrind.org/support/bug_reports.html.\n--2731-- WARNING: unhandled riscv64-linux syscall: 258\n--2731-- You may be able to write your own handler.\n--2731-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2731-- Nevertheless we consider this a bug.  Please report\n--2731-- it at http://valgrind.org/support/bug_reports.html.\n--2731-- WARNING: unhandled riscv64-linux syscall: 258\n--2731-- You may be able to write your own handler.\n--2731-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2731-- Nevertheless we consider this a bug.  Please report\n--2731-- it at http://valgrind.org/support/bug_reports.html.\n--2731-- WARNING: unhandled riscv64-linux syscall: 258\n--2731-- You may be able to write your own handler.\n--2731-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2731-- Nevertheless we consider this a bug.  Please report\n--2731-- it at http://valgrind.org/support/bug_reports.html.\n--2731-- WARNING: unhandled riscv64-linux syscall: 258\n--2731-- You may be able to write your own handler.\n--2731-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2731-- Nevertheless we consider this a bug.  Please report\n--2731-- it at http://valgrind.org/support/bug_reports.html.\n--2731-- WARNING: unhandled riscv64-linux syscall: 258\n--2731-- You may be able to write your own handler.\n--2731-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2731-- Nevertheless we consider this a bug.  Please report\n--2731-- it at http://valgrind.org/support/bug_reports.html.\n--2731-- WARNING: unhandled riscv64-linux syscall: 258\n--2731-- You may be able to write your own handler.\n--2731-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2731-- Nevertheless we consider this a bug.  Please report\n--2731-- it at http://valgrind.org/support/bug_reports.html.\n--2731-- WARNING: unhandled riscv64-linux syscall: 258\n--2731-- You may be able to write your own handler.\n--2731-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2731-- Nevertheless we consider this a bug.  Please report\n--2731-- it at http://valgrind.org/support/bug_reports.html.\n--2731-- WARNING: unhandled riscv64-linux syscall: 258\n--2731-- You may be able to write your own handler.\n--2731-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2731-- Nevertheless we consider this a bug.  Please report\n--2731-- 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:
'--2739-- WARNING: unhandled riscv64-linux syscall: 258\n--2739-- You may be able to write your own handler.\n--2739-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2739-- Nevertheless we consider this a bug.  Please report\n--2739-- it at http://valgrind.org/support/bug_reports.html.\n--2739-- WARNING: unhandled riscv64-linux syscall: 258\n--2739-- You may be able to write your own handler.\n--2739-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2739-- Nevertheless we consider this a bug.  Please report\n--2739-- it at http://valgrind.org/support/bug_reports.html.\n--2739-- WARNING: unhandled riscv64-linux syscall: 258\n--2739-- You may be able to write your own handler.\n--2739-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2739-- Nevertheless we consider this a bug.  Please report\n--2739-- it at http://valgrind.org/support/bug_reports.html.\n--2739-- WARNING: unhandled riscv64-linux syscall: 258\n--2739-- You may be able to write your own handler.\n--2739-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2739-- Nevertheless we consider this a bug.  Please report\n--2739-- it at http://valgrind.org/support/bug_reports.html.\n--2739-- WARNING: unhandled riscv64-linux syscall: 258\n--2739-- You may be able to write your own handler.\n--2739-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2739-- Nevertheless we consider this a bug.  Please report\n--2739-- it at http://valgrind.org/support/bug_reports.html.\n--2739-- WARNING: unhandled riscv64-linux syscall: 258\n--2739-- You may be able to write your own handler.\n--2739-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2739-- Nevertheless we consider this a bug.  Please report\n--2739-- it at http://valgrind.org/support/bug_reports.html.\n--2739-- WARNING: unhandled riscv64-linux syscall: 258\n--2739-- You may be able to write your own handler.\n--2739-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2739-- Nevertheless we consider this a bug.  Please report\n--2739-- it at http://valgrind.org/support/bug_reports.html.\n--2739-- WARNING: unhandled riscv64-linux syscall: 258\n--2739-- You may be able to write your own handler.\n--2739-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2739-- Nevertheless we consider this a bug.  Please report\n--2739-- it at http://valgrind.org/support/bug_reports.html.\n--2739-- WARNING: unhandled riscv64-linux syscall: 258\n--2739-- You may be able to write your own handler.\n--2739-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2739-- Nevertheless we consider this a bug.  Please report\n--2739-- it at http://valgrind.org/support/bug_reports.html.\n--2739-- WARNING: unhandled riscv64-linux syscall: 258\n--2739-- You may be able to write your own handler.\n--2739-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2739-- Nevertheless we consider this a bug.  Please report\n--2739-- it at http://valgrind.org/support/bug_reports.html.\n--2739-- WARNING: unhandled riscv64-linux syscall: 258\n--2739-- You may be able to write your own handler.\n--2739-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2739-- Nevertheless we consider this a bug.  Please report\n--2739-- it at http://valgrind.org/support/bug_reports.html.\n--2739-- WARNING: unhandled riscv64-linux syscall: 258\n--2739-- You may be able to write your own handler.\n--2739-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2739-- Nevertheless we consider this a bug.  Please report\n--2739-- it at http://valgrind.org/support/bug_reports.html.\n--2739-- WARNING: unhandled riscv64-linux syscall: 258\n--2739-- You may be able to write your own handler.\n--2739-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2739-- Nevertheless we consider this a bug.  Please report\n--2739-- it at http://valgrind.org/support/bug_reports.html.\n--2739-- WARNING: unhandled riscv64-linux syscall: 258\n--2739-- You may be able to write your own handler.\n--2739-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2739-- Nevertheless we consider this a bug.  Please report\n--2739-- it at http://valgrind.org/support/bug_reports.html.\n--2739-- WARNING: unhandled riscv64-linux syscall: 258\n--2739-- You may be able to write your own handler.\n--2739-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2739-- Nevertheless we consider this a bug.  Please report\n--2739-- it at http://valgrind.org/support/bug_reports.html.\n--2739-- WARNING: unhandled riscv64-linux syscall: 258\n--2739-- You may be able to write your own handler.\n--2739-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2739-- Nevertheless we consider this a bug.  Please report\n--2739-- it at http://valgrind.org/support/bug_reports.html.\n--2739-- WARNING: unhandled riscv64-linux syscall: 258\n--2739-- You may be able to write your own handler.\n--2739-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2739-- Nevertheless we consider this a bug.  Please report\n--2739-- it at http://valgrind.org/support/bug_reports.html.\n--2739-- WARNING: unhandled riscv64-linux syscall: 258\n--2739-- You may be able to write your own handler.\n--2739-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2739-- Nevertheless we consider this a bug.  Please report\n--2739-- 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:
'--2747-- WARNING: unhandled riscv64-linux syscall: 258\n--2747-- You may be able to write your own handler.\n--2747-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2747-- Nevertheless we consider this a bug.  Please report\n--2747-- it at http://valgrind.org/support/bug_reports.html.\n--2747-- WARNING: unhandled riscv64-linux syscall: 258\n--2747-- You may be able to write your own handler.\n--2747-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2747-- Nevertheless we consider this a bug.  Please report\n--2747-- it at http://valgrind.org/support/bug_reports.html.\n--2747-- WARNING: unhandled riscv64-linux syscall: 258\n--2747-- You may be able to write your own handler.\n--2747-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2747-- Nevertheless we consider this a bug.  Please report\n--2747-- it at http://valgrind.org/support/bug_reports.html.\n--2747-- WARNING: unhandled riscv64-linux syscall: 258\n--2747-- You may be able to write your own handler.\n--2747-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2747-- Nevertheless we consider this a bug.  Please report\n--2747-- it at http://valgrind.org/support/bug_reports.html.\n--2747-- WARNING: unhandled riscv64-linux syscall: 258\n--2747-- You may be able to write your own handler.\n--2747-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2747-- Nevertheless we consider this a bug.  Please report\n--2747-- it at http://valgrind.org/support/bug_reports.html.\n--2747-- WARNING: unhandled riscv64-linux syscall: 258\n--2747-- You may be able to write your own handler.\n--2747-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2747-- Nevertheless we consider this a bug.  Please report\n--2747-- it at http://valgrind.org/support/bug_reports.html.\n--2747-- WARNING: unhandled riscv64-linux syscall: 258\n--2747-- You may be able to write your own handler.\n--2747-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2747-- Nevertheless we consider this a bug.  Please report\n--2747-- it at http://valgrind.org/support/bug_reports.html.\n--2747-- WARNING: unhandled riscv64-linux syscall: 258\n--2747-- You may be able to write your own handler.\n--2747-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2747-- Nevertheless we consider this a bug.  Please report\n--2747-- it at http://valgrind.org/support/bug_reports.html.\n--2747-- WARNING: unhandled riscv64-linux syscall: 258\n--2747-- You may be able to write your own handler.\n--2747-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2747-- Nevertheless we consider this a bug.  Please report\n--2747-- it at http://valgrind.org/support/bug_reports.html.\n--2747-- WARNING: unhandled riscv64-linux syscall: 258\n--2747-- You may be able to write your own handler.\n--2747-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2747-- Nevertheless we consider this a bug.  Please report\n--2747-- it at http://valgrind.org/support/bug_reports.html.\n--2747-- WARNING: unhandled riscv64-linux syscall: 258\n--2747-- You may be able to write your own handler.\n--2747-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2747-- Nevertheless we consider this a bug.  Please report\n--2747-- it at http://valgrind.org/support/bug_reports.html.\n--2747-- WARNING: unhandled riscv64-linux syscall: 258\n--2747-- You may be able to write your own handler.\n--2747-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2747-- Nevertheless we consider this a bug.  Please report\n--2747-- it at http://valgrind.org/support/bug_reports.html.\n--2747-- WARNING: unhandled riscv64-linux syscall: 258\n--2747-- You may be able to write your own handler.\n--2747-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2747-- Nevertheless we consider this a bug.  Please report\n--2747-- it at http://valgrind.org/support/bug_reports.html.\n--2747-- WARNING: unhandled riscv64-linux syscall: 258\n--2747-- You may be able to write your own handler.\n--2747-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2747-- Nevertheless we consider this a bug.  Please report\n--2747-- it at http://valgrind.org/support/bug_reports.html.\n--2747-- WARNING: unhandled riscv64-linux syscall: 258\n--2747-- You may be able to write your own handler.\n--2747-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2747-- Nevertheless we consider this a bug.  Please report\n--2747-- it at http://valgrind.org/support/bug_reports.html.\n--2747-- WARNING: unhandled riscv64-linux syscall: 258\n--2747-- You may be able to write your own handler.\n--2747-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2747-- Nevertheless we consider this a bug.  Please report\n--2747-- it at http://valgrind.org/support/bug_reports.html.\n--2747-- WARNING: unhandled riscv64-linux syscall: 258\n--2747-- You may be able to write your own handler.\n--2747-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2747-- Nevertheless we consider this a bug.  Please report\n--2747-- it at http://valgrind.org/support/bug_reports.html.\n--2747-- WARNING: unhandled riscv64-linux syscall: 258\n--2747-- You may be able to write your own handler.\n--2747-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2747-- Nevertheless we consider this a bug.  Please report\n--2747-- 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:
'--2755-- WARNING: unhandled riscv64-linux syscall: 258\n--2755-- You may be able to write your own handler.\n--2755-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2755-- Nevertheless we consider this a bug.  Please report\n--2755-- it at http://valgrind.org/support/bug_reports.html.\n--2755-- WARNING: unhandled riscv64-linux syscall: 258\n--2755-- You may be able to write your own handler.\n--2755-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2755-- Nevertheless we consider this a bug.  Please report\n--2755-- it at http://valgrind.org/support/bug_reports.html.\n--2755-- WARNING: unhandled riscv64-linux syscall: 258\n--2755-- You may be able to write your own handler.\n--2755-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2755-- Nevertheless we consider this a bug.  Please report\n--2755-- it at http://valgrind.org/support/bug_reports.html.\n--2755-- WARNING: unhandled riscv64-linux syscall: 258\n--2755-- You may be able to write your own handler.\n--2755-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2755-- Nevertheless we consider this a bug.  Please report\n--2755-- it at http://valgrind.org/support/bug_reports.html.\n--2755-- WARNING: unhandled riscv64-linux syscall: 258\n--2755-- You may be able to write your own handler.\n--2755-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2755-- Nevertheless we consider this a bug.  Please report\n--2755-- it at http://valgrind.org/support/bug_reports.html.\n--2755-- WARNING: unhandled riscv64-linux syscall: 258\n--2755-- You may be able to write your own handler.\n--2755-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2755-- Nevertheless we consider this a bug.  Please report\n--2755-- it at http://valgrind.org/support/bug_reports.html.\n--2755-- WARNING: unhandled riscv64-linux syscall: 258\n--2755-- You may be able to write your own handler.\n--2755-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2755-- Nevertheless we consider this a bug.  Please report\n--2755-- it at http://valgrind.org/support/bug_reports.html.\n--2755-- WARNING: unhandled riscv64-linux syscall: 258\n--2755-- You may be able to write your own handler.\n--2755-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2755-- Nevertheless we consider this a bug.  Please report\n--2755-- it at http://valgrind.org/support/bug_reports.html.\n--2755-- WARNING: unhandled riscv64-linux syscall: 258\n--2755-- You may be able to write your own handler.\n--2755-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2755-- Nevertheless we consider this a bug.  Please report\n--2755-- it at http://valgrind.org/support/bug_reports.html.\n--2755-- WARNING: unhandled riscv64-linux syscall: 258\n--2755-- You may be able to write your own handler.\n--2755-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2755-- Nevertheless we consider this a bug.  Please report\n--2755-- it at http://valgrind.org/support/bug_reports.html.\n--2755-- WARNING: unhandled riscv64-linux syscall: 258\n--2755-- You may be able to write your own handler.\n--2755-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2755-- Nevertheless we consider this a bug.  Please report\n--2755-- it at http://valgrind.org/support/bug_reports.html.\n--2755-- WARNING: unhandled riscv64-linux syscall: 258\n--2755-- You may be able to write your own handler.\n--2755-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2755-- Nevertheless we consider this a bug.  Please report\n--2755-- it at http://valgrind.org/support/bug_reports.html.\n--2755-- WARNING: unhandled riscv64-linux syscall: 258\n--2755-- You may be able to write your own handler.\n--2755-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2755-- Nevertheless we consider this a bug.  Please report\n--2755-- it at http://valgrind.org/support/bug_reports.html.\n--2755-- WARNING: unhandled riscv64-linux syscall: 258\n--2755-- You may be able to write your own handler.\n--2755-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2755-- Nevertheless we consider this a bug.  Please report\n--2755-- it at http://valgrind.org/support/bug_reports.html.\n--2755-- WARNING: unhandled riscv64-linux syscall: 258\n--2755-- You may be able to write your own handler.\n--2755-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2755-- Nevertheless we consider this a bug.  Please report\n--2755-- it at http://valgrind.org/support/bug_reports.html.\n--2755-- WARNING: unhandled riscv64-linux syscall: 258\n--2755-- You may be able to write your own handler.\n--2755-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2755-- Nevertheless we consider this a bug.  Please report\n--2755-- it at http://valgrind.org/support/bug_reports.html.\n--2755-- WARNING: unhandled riscv64-linux syscall: 258\n--2755-- You may be able to write your own handler.\n--2755-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2755-- Nevertheless we consider this a bug.  Please report\n--2755-- it at http://valgrind.org/support/bug_reports.html.\n--2755-- WARNING: unhandled riscv64-linux syscall: 258\n--2755-- You may be able to write your own handler.\n--2755-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2755-- Nevertheless we consider this a bug.  Please report\n--2755-- 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:
'--2763-- WARNING: unhandled riscv64-linux syscall: 258\n--2763-- You may be able to write your own handler.\n--2763-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2763-- Nevertheless we consider this a bug.  Please report\n--2763-- it at http://valgrind.org/support/bug_reports.html.\n--2763-- WARNING: unhandled riscv64-linux syscall: 258\n--2763-- You may be able to write your own handler.\n--2763-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2763-- Nevertheless we consider this a bug.  Please report\n--2763-- it at http://valgrind.org/support/bug_reports.html.\n--2763-- WARNING: unhandled riscv64-linux syscall: 258\n--2763-- You may be able to write your own handler.\n--2763-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2763-- Nevertheless we consider this a bug.  Please report\n--2763-- it at http://valgrind.org/support/bug_reports.html.\n--2763-- WARNING: unhandled riscv64-linux syscall: 258\n--2763-- You may be able to write your own handler.\n--2763-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2763-- Nevertheless we consider this a bug.  Please report\n--2763-- it at http://valgrind.org/support/bug_reports.html.\n--2763-- WARNING: unhandled riscv64-linux syscall: 258\n--2763-- You may be able to write your own handler.\n--2763-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2763-- Nevertheless we consider this a bug.  Please report\n--2763-- it at http://valgrind.org/support/bug_reports.html.\n--2763-- WARNING: unhandled riscv64-linux syscall: 258\n--2763-- You may be able to write your own handler.\n--2763-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2763-- Nevertheless we consider this a bug.  Please report\n--2763-- it at http://valgrind.org/support/bug_reports.html.\n--2763-- WARNING: unhandled riscv64-linux syscall: 258\n--2763-- You may be able to write your own handler.\n--2763-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2763-- Nevertheless we consider this a bug.  Please report\n--2763-- it at http://valgrind.org/support/bug_reports.html.\n--2763-- WARNING: unhandled riscv64-linux syscall: 258\n--2763-- You may be able to write your own handler.\n--2763-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2763-- Nevertheless we consider this a bug.  Please report\n--2763-- it at http://valgrind.org/support/bug_reports.html.\n--2763-- WARNING: unhandled riscv64-linux syscall: 258\n--2763-- You may be able to write your own handler.\n--2763-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2763-- Nevertheless we consider this a bug.  Please report\n--2763-- it at http://valgrind.org/support/bug_reports.html.\n--2763-- WARNING: unhandled riscv64-linux syscall: 258\n--2763-- You may be able to write your own handler.\n--2763-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2763-- Nevertheless we consider this a bug.  Please report\n--2763-- it at http://valgrind.org/support/bug_reports.html.\n--2763-- WARNING: unhandled riscv64-linux syscall: 258\n--2763-- You may be able to write your own handler.\n--2763-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2763-- Nevertheless we consider this a bug.  Please report\n--2763-- it at http://valgrind.org/support/bug_reports.html.\n--2763-- WARNING: unhandled riscv64-linux syscall: 258\n--2763-- You may be able to write your own handler.\n--2763-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2763-- Nevertheless we consider this a bug.  Please report\n--2763-- it at http://valgrind.org/support/bug_reports.html.\n--2763-- WARNING: unhandled riscv64-linux syscall: 258\n--2763-- You may be able to write your own handler.\n--2763-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2763-- Nevertheless we consider this a bug.  Please report\n--2763-- it at http://valgrind.org/support/bug_reports.html.\n--2763-- WARNING: unhandled riscv64-linux syscall: 258\n--2763-- You may be able to write your own handler.\n--2763-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2763-- Nevertheless we consider this a bug.  Please report\n--2763-- it at http://valgrind.org/support/bug_reports.html.\n--2763-- WARNING: unhandled riscv64-linux syscall: 258\n--2763-- You may be able to write your own handler.\n--2763-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2763-- Nevertheless we consider this a bug.  Please report\n--2763-- it at http://valgrind.org/support/bug_reports.html.\n--2763-- WARNING: unhandled riscv64-linux syscall: 258\n--2763-- You may be able to write your own handler.\n--2763-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2763-- Nevertheless we consider this a bug.  Please report\n--2763-- it at http://valgrind.org/support/bug_reports.html.\n--2763-- WARNING: unhandled riscv64-linux syscall: 258\n--2763-- You may be able to write your own handler.\n--2763-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2763-- Nevertheless we consider this a bug.  Please report\n--2763-- it at http://valgrind.org/support/bug_reports.html.\n--2763-- WARNING: unhandled riscv64-linux syscall: 258\n--2763-- You may be able to write your own handler.\n--2763-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2763-- Nevertheless we consider this a bug.  Please report\n--2763-- 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:
'--2771-- WARNING: unhandled riscv64-linux syscall: 258\n--2771-- You may be able to write your own handler.\n--2771-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2771-- Nevertheless we consider this a bug.  Please report\n--2771-- it at http://valgrind.org/support/bug_reports.html.\n--2771-- WARNING: unhandled riscv64-linux syscall: 258\n--2771-- You may be able to write your own handler.\n--2771-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2771-- Nevertheless we consider this a bug.  Please report\n--2771-- it at http://valgrind.org/support/bug_reports.html.\n--2771-- WARNING: unhandled riscv64-linux syscall: 258\n--2771-- You may be able to write your own handler.\n--2771-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2771-- Nevertheless we consider this a bug.  Please report\n--2771-- it at http://valgrind.org/support/bug_reports.html.\n--2771-- WARNING: unhandled riscv64-linux syscall: 258\n--2771-- You may be able to write your own handler.\n--2771-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2771-- Nevertheless we consider this a bug.  Please report\n--2771-- it at http://valgrind.org/support/bug_reports.html.\n--2771-- WARNING: unhandled riscv64-linux syscall: 258\n--2771-- You may be able to write your own handler.\n--2771-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2771-- Nevertheless we consider this a bug.  Please report\n--2771-- it at http://valgrind.org/support/bug_reports.html.\n--2771-- WARNING: unhandled riscv64-linux syscall: 258\n--2771-- You may be able to write your own handler.\n--2771-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2771-- Nevertheless we consider this a bug.  Please report\n--2771-- it at http://valgrind.org/support/bug_reports.html.\n--2771-- WARNING: unhandled riscv64-linux syscall: 258\n--2771-- You may be able to write your own handler.\n--2771-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2771-- Nevertheless we consider this a bug.  Please report\n--2771-- it at http://valgrind.org/support/bug_reports.html.\n--2771-- WARNING: unhandled riscv64-linux syscall: 258\n--2771-- You may be able to write your own handler.\n--2771-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2771-- Nevertheless we consider this a bug.  Please report\n--2771-- it at http://valgrind.org/support/bug_reports.html.\n--2771-- WARNING: unhandled riscv64-linux syscall: 258\n--2771-- You may be able to write your own handler.\n--2771-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2771-- Nevertheless we consider this a bug.  Please report\n--2771-- it at http://valgrind.org/support/bug_reports.html.\n--2771-- WARNING: unhandled riscv64-linux syscall: 258\n--2771-- You may be able to write your own handler.\n--2771-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2771-- Nevertheless we consider this a bug.  Please report\n--2771-- it at http://valgrind.org/support/bug_reports.html.\n--2771-- WARNING: unhandled riscv64-linux syscall: 258\n--2771-- You may be able to write your own handler.\n--2771-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2771-- Nevertheless we consider this a bug.  Please report\n--2771-- it at http://valgrind.org/support/bug_reports.html.\n--2771-- WARNING: unhandled riscv64-linux syscall: 258\n--2771-- You may be able to write your own handler.\n--2771-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2771-- Nevertheless we consider this a bug.  Please report\n--2771-- it at http://valgrind.org/support/bug_reports.html.\n--2771-- WARNING: unhandled riscv64-linux syscall: 258\n--2771-- You may be able to write your own handler.\n--2771-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2771-- Nevertheless we consider this a bug.  Please report\n--2771-- it at http://valgrind.org/support/bug_reports.html.\n--2771-- WARNING: unhandled riscv64-linux syscall: 258\n--2771-- You may be able to write your own handler.\n--2771-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2771-- Nevertheless we consider this a bug.  Please report\n--2771-- it at http://valgrind.org/support/bug_reports.html.\n--2771-- WARNING: unhandled riscv64-linux syscall: 258\n--2771-- You may be able to write your own handler.\n--2771-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2771-- Nevertheless we consider this a bug.  Please report\n--2771-- it at http://valgrind.org/support/bug_reports.html.\n--2771-- WARNING: unhandled riscv64-linux syscall: 258\n--2771-- You may be able to write your own handler.\n--2771-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2771-- Nevertheless we consider this a bug.  Please report\n--2771-- it at http://valgrind.org/support/bug_reports.html.\n--2771-- WARNING: unhandled riscv64-linux syscall: 258\n--2771-- You may be able to write your own handler.\n--2771-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2771-- Nevertheless we consider this a bug.  Please report\n--2771-- it at http://valgrind.org/support/bug_reports.html.\n--2771-- WARNING: unhandled riscv64-linux syscall: 258\n--2771-- You may be able to write your own handler.\n--2771-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2771-- Nevertheless we consider this a bug.  Please report\n--2771-- 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:
'--2779-- WARNING: unhandled riscv64-linux syscall: 258\n--2779-- You may be able to write your own handler.\n--2779-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2779-- Nevertheless we consider this a bug.  Please report\n--2779-- it at http://valgrind.org/support/bug_reports.html.\n--2779-- WARNING: unhandled riscv64-linux syscall: 258\n--2779-- You may be able to write your own handler.\n--2779-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2779-- Nevertheless we consider this a bug.  Please report\n--2779-- it at http://valgrind.org/support/bug_reports.html.\n--2779-- WARNING: unhandled riscv64-linux syscall: 258\n--2779-- You may be able to write your own handler.\n--2779-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2779-- Nevertheless we consider this a bug.  Please report\n--2779-- it at http://valgrind.org/support/bug_reports.html.\n--2779-- WARNING: unhandled riscv64-linux syscall: 258\n--2779-- You may be able to write your own handler.\n--2779-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2779-- Nevertheless we consider this a bug.  Please report\n--2779-- it at http://valgrind.org/support/bug_reports.html.\n--2779-- WARNING: unhandled riscv64-linux syscall: 258\n--2779-- You may be able to write your own handler.\n--2779-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2779-- Nevertheless we consider this a bug.  Please report\n--2779-- it at http://valgrind.org/support/bug_reports.html.\n--2779-- WARNING: unhandled riscv64-linux syscall: 258\n--2779-- You may be able to write your own handler.\n--2779-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2779-- Nevertheless we consider this a bug.  Please report\n--2779-- it at http://valgrind.org/support/bug_reports.html.\n--2779-- WARNING: unhandled riscv64-linux syscall: 258\n--2779-- You may be able to write your own handler.\n--2779-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2779-- Nevertheless we consider this a bug.  Please report\n--2779-- it at http://valgrind.org/support/bug_reports.html.\n--2779-- WARNING: unhandled riscv64-linux syscall: 258\n--2779-- You may be able to write your own handler.\n--2779-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2779-- Nevertheless we consider this a bug.  Please report\n--2779-- it at http://valgrind.org/support/bug_reports.html.\n--2779-- WARNING: unhandled riscv64-linux syscall: 258\n--2779-- You may be able to write your own handler.\n--2779-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2779-- Nevertheless we consider this a bug.  Please report\n--2779-- it at http://valgrind.org/support/bug_reports.html.\n--2779-- WARNING: unhandled riscv64-linux syscall: 258\n--2779-- You may be able to write your own handler.\n--2779-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2779-- Nevertheless we consider this a bug.  Please report\n--2779-- it at http://valgrind.org/support/bug_reports.html.\n--2779-- WARNING: unhandled riscv64-linux syscall: 258\n--2779-- You may be able to write your own handler.\n--2779-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2779-- Nevertheless we consider this a bug.  Please report\n--2779-- it at http://valgrind.org/support/bug_reports.html.\n--2779-- WARNING: unhandled riscv64-linux syscall: 258\n--2779-- You may be able to write your own handler.\n--2779-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2779-- Nevertheless we consider this a bug.  Please report\n--2779-- it at http://valgrind.org/support/bug_reports.html.\n--2779-- WARNING: unhandled riscv64-linux syscall: 258\n--2779-- You may be able to write your own handler.\n--2779-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2779-- Nevertheless we consider this a bug.  Please report\n--2779-- it at http://valgrind.org/support/bug_reports.html.\n--2779-- WARNING: unhandled riscv64-linux syscall: 258\n--2779-- You may be able to write your own handler.\n--2779-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2779-- Nevertheless we consider this a bug.  Please report\n--2779-- it at http://valgrind.org/support/bug_reports.html.\n--2779-- WARNING: unhandled riscv64-linux syscall: 258\n--2779-- You may be able to write your own handler.\n--2779-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2779-- Nevertheless we consider this a bug.  Please report\n--2779-- it at http://valgrind.org/support/bug_reports.html.\n--2779-- WARNING: unhandled riscv64-linux syscall: 258\n--2779-- You may be able to write your own handler.\n--2779-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2779-- Nevertheless we consider this a bug.  Please report\n--2779-- it at http://valgrind.org/support/bug_reports.html.\n--2779-- WARNING: unhandled riscv64-linux syscall: 258\n--2779-- You may be able to write your own handler.\n--2779-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2779-- Nevertheless we consider this a bug.  Please report\n--2779-- it at http://valgrind.org/support/bug_reports.html.\n--2779-- WARNING: unhandled riscv64-linux syscall: 258\n--2779-- You may be able to write your own handler.\n--2779-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2779-- Nevertheless we consider this a bug.  Please report\n--2779-- 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:
'--2787-- WARNING: unhandled riscv64-linux syscall: 258\n--2787-- You may be able to write your own handler.\n--2787-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2787-- Nevertheless we consider this a bug.  Please report\n--2787-- it at http://valgrind.org/support/bug_reports.html.\n--2787-- WARNING: unhandled riscv64-linux syscall: 258\n--2787-- You may be able to write your own handler.\n--2787-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2787-- Nevertheless we consider this a bug.  Please report\n--2787-- it at http://valgrind.org/support/bug_reports.html.\n--2787-- WARNING: unhandled riscv64-linux syscall: 258\n--2787-- You may be able to write your own handler.\n--2787-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2787-- Nevertheless we consider this a bug.  Please report\n--2787-- it at http://valgrind.org/support/bug_reports.html.\n--2787-- WARNING: unhandled riscv64-linux syscall: 258\n--2787-- You may be able to write your own handler.\n--2787-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2787-- Nevertheless we consider this a bug.  Please report\n--2787-- it at http://valgrind.org/support/bug_reports.html.\n--2787-- WARNING: unhandled riscv64-linux syscall: 258\n--2787-- You may be able to write your own handler.\n--2787-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2787-- Nevertheless we consider this a bug.  Please report\n--2787-- it at http://valgrind.org/support/bug_reports.html.\n--2787-- WARNING: unhandled riscv64-linux syscall: 258\n--2787-- You may be able to write your own handler.\n--2787-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2787-- Nevertheless we consider this a bug.  Please report\n--2787-- it at http://valgrind.org/support/bug_reports.html.\n--2787-- WARNING: unhandled riscv64-linux syscall: 258\n--2787-- You may be able to write your own handler.\n--2787-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2787-- Nevertheless we consider this a bug.  Please report\n--2787-- it at http://valgrind.org/support/bug_reports.html.\n--2787-- WARNING: unhandled riscv64-linux syscall: 258\n--2787-- You may be able to write your own handler.\n--2787-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2787-- Nevertheless we consider this a bug.  Please report\n--2787-- it at http://valgrind.org/support/bug_reports.html.\n--2787-- WARNING: unhandled riscv64-linux syscall: 258\n--2787-- You may be able to write your own handler.\n--2787-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2787-- Nevertheless we consider this a bug.  Please report\n--2787-- it at http://valgrind.org/support/bug_reports.html.\n--2787-- WARNING: unhandled riscv64-linux syscall: 258\n--2787-- You may be able to write your own handler.\n--2787-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2787-- Nevertheless we consider this a bug.  Please report\n--2787-- it at http://valgrind.org/support/bug_reports.html.\n--2787-- WARNING: unhandled riscv64-linux syscall: 258\n--2787-- You may be able to write your own handler.\n--2787-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2787-- Nevertheless we consider this a bug.  Please report\n--2787-- it at http://valgrind.org/support/bug_reports.html.\n--2787-- WARNING: unhandled riscv64-linux syscall: 258\n--2787-- You may be able to write your own handler.\n--2787-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2787-- Nevertheless we consider this a bug.  Please report\n--2787-- it at http://valgrind.org/support/bug_reports.html.\n--2787-- WARNING: unhandled riscv64-linux syscall: 258\n--2787-- You may be able to write your own handler.\n--2787-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2787-- Nevertheless we consider this a bug.  Please report\n--2787-- it at http://valgrind.org/support/bug_reports.html.\n--2787-- WARNING: unhandled riscv64-linux syscall: 258\n--2787-- You may be able to write your own handler.\n--2787-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2787-- Nevertheless we consider this a bug.  Please report\n--2787-- it at http://valgrind.org/support/bug_reports.html.\n--2787-- WARNING: unhandled riscv64-linux syscall: 258\n--2787-- You may be able to write your own handler.\n--2787-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2787-- Nevertheless we consider this a bug.  Please report\n--2787-- it at http://valgrind.org/support/bug_reports.html.\n--2787-- WARNING: unhandled riscv64-linux syscall: 258\n--2787-- You may be able to write your own handler.\n--2787-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2787-- Nevertheless we consider this a bug.  Please report\n--2787-- it at http://valgrind.org/support/bug_reports.html.\n--2787-- WARNING: unhandled riscv64-linux syscall: 258\n--2787-- You may be able to write your own handler.\n--2787-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2787-- Nevertheless we consider this a bug.  Please report\n--2787-- it at http://valgrind.org/support/bug_reports.html.\n--2787-- WARNING: unhandled riscv64-linux syscall: 258\n--2787-- You may be able to write your own handler.\n--2787-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2787-- Nevertheless we consider this a bug.  Please report\n--2787-- 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:
'--2795-- WARNING: unhandled riscv64-linux syscall: 258\n--2795-- You may be able to write your own handler.\n--2795-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2795-- Nevertheless we consider this a bug.  Please report\n--2795-- it at http://valgrind.org/support/bug_reports.html.\n--2795-- WARNING: unhandled riscv64-linux syscall: 258\n--2795-- You may be able to write your own handler.\n--2795-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2795-- Nevertheless we consider this a bug.  Please report\n--2795-- it at http://valgrind.org/support/bug_reports.html.\n--2795-- WARNING: unhandled riscv64-linux syscall: 258\n--2795-- You may be able to write your own handler.\n--2795-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2795-- Nevertheless we consider this a bug.  Please report\n--2795-- it at http://valgrind.org/support/bug_reports.html.\n--2795-- WARNING: unhandled riscv64-linux syscall: 258\n--2795-- You may be able to write your own handler.\n--2795-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2795-- Nevertheless we consider this a bug.  Please report\n--2795-- it at http://valgrind.org/support/bug_reports.html.\n--2795-- WARNING: unhandled riscv64-linux syscall: 258\n--2795-- You may be able to write your own handler.\n--2795-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2795-- Nevertheless we consider this a bug.  Please report\n--2795-- it at http://valgrind.org/support/bug_reports.html.\n--2795-- WARNING: unhandled riscv64-linux syscall: 258\n--2795-- You may be able to write your own handler.\n--2795-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2795-- Nevertheless we consider this a bug.  Please report\n--2795-- it at http://valgrind.org/support/bug_reports.html.\n--2795-- WARNING: unhandled riscv64-linux syscall: 258\n--2795-- You may be able to write your own handler.\n--2795-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2795-- Nevertheless we consider this a bug.  Please report\n--2795-- it at http://valgrind.org/support/bug_reports.html.\n--2795-- WARNING: unhandled riscv64-linux syscall: 258\n--2795-- You may be able to write your own handler.\n--2795-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2795-- Nevertheless we consider this a bug.  Please report\n--2795-- it at http://valgrind.org/support/bug_reports.html.\n--2795-- WARNING: unhandled riscv64-linux syscall: 258\n--2795-- You may be able to write your own handler.\n--2795-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2795-- Nevertheless we consider this a bug.  Please report\n--2795-- it at http://valgrind.org/support/bug_reports.html.\n--2795-- WARNING: unhandled riscv64-linux syscall: 258\n--2795-- You may be able to write your own handler.\n--2795-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2795-- Nevertheless we consider this a bug.  Please report\n--2795-- it at http://valgrind.org/support/bug_reports.html.\n--2795-- WARNING: unhandled riscv64-linux syscall: 258\n--2795-- You may be able to write your own handler.\n--2795-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2795-- Nevertheless we consider this a bug.  Please report\n--2795-- it at http://valgrind.org/support/bug_reports.html.\n--2795-- WARNING: unhandled riscv64-linux syscall: 258\n--2795-- You may be able to write your own handler.\n--2795-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2795-- Nevertheless we consider this a bug.  Please report\n--2795-- it at http://valgrind.org/support/bug_reports.html.\n--2795-- WARNING: unhandled riscv64-linux syscall: 258\n--2795-- You may be able to write your own handler.\n--2795-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2795-- Nevertheless we consider this a bug.  Please report\n--2795-- it at http://valgrind.org/support/bug_reports.html.\n--2795-- WARNING: unhandled riscv64-linux syscall: 258\n--2795-- You may be able to write your own handler.\n--2795-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2795-- Nevertheless we consider this a bug.  Please report\n--2795-- it at http://valgrind.org/support/bug_reports.html.\n--2795-- WARNING: unhandled riscv64-linux syscall: 258\n--2795-- You may be able to write your own handler.\n--2795-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2795-- Nevertheless we consider this a bug.  Please report\n--2795-- it at http://valgrind.org/support/bug_reports.html.\n--2795-- WARNING: unhandled riscv64-linux syscall: 258\n--2795-- You may be able to write your own handler.\n--2795-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2795-- Nevertheless we consider this a bug.  Please report\n--2795-- it at http://valgrind.org/support/bug_reports.html.\n--2795-- WARNING: unhandled riscv64-linux syscall: 258\n--2795-- You may be able to write your own handler.\n--2795-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2795-- Nevertheless we consider this a bug.  Please report\n--2795-- it at http://valgrind.org/support/bug_reports.html.\n--2795-- WARNING: unhandled riscv64-linux syscall: 258\n--2795-- You may be able to write your own handler.\n--2795-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2795-- Nevertheless we consider this a bug.  Please report\n--2795-- 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:
'--2804-- WARNING: unhandled riscv64-linux syscall: 258\n--2804-- You may be able to write your own handler.\n--2804-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2804-- Nevertheless we consider this a bug.  Please report\n--2804-- it at http://valgrind.org/support/bug_reports.html.\n--2804-- WARNING: unhandled riscv64-linux syscall: 258\n--2804-- You may be able to write your own handler.\n--2804-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2804-- Nevertheless we consider this a bug.  Please report\n--2804-- it at http://valgrind.org/support/bug_reports.html.\n--2804-- WARNING: unhandled riscv64-linux syscall: 258\n--2804-- You may be able to write your own handler.\n--2804-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2804-- Nevertheless we consider this a bug.  Please report\n--2804-- it at http://valgrind.org/support/bug_reports.html.\n--2804-- WARNING: unhandled riscv64-linux syscall: 258\n--2804-- You may be able to write your own handler.\n--2804-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2804-- Nevertheless we consider this a bug.  Please report\n--2804-- it at http://valgrind.org/support/bug_reports.html.\n--2804-- WARNING: unhandled riscv64-linux syscall: 258\n--2804-- You may be able to write your own handler.\n--2804-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2804-- Nevertheless we consider this a bug.  Please report\n--2804-- it at http://valgrind.org/support/bug_reports.html.\n--2804-- WARNING: unhandled riscv64-linux syscall: 258\n--2804-- You may be able to write your own handler.\n--2804-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2804-- Nevertheless we consider this a bug.  Please report\n--2804-- it at http://valgrind.org/support/bug_reports.html.\n--2804-- WARNING: unhandled riscv64-linux syscall: 258\n--2804-- You may be able to write your own handler.\n--2804-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2804-- Nevertheless we consider this a bug.  Please report\n--2804-- it at http://valgrind.org/support/bug_reports.html.\n--2804-- WARNING: unhandled riscv64-linux syscall: 258\n--2804-- You may be able to write your own handler.\n--2804-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2804-- Nevertheless we consider this a bug.  Please report\n--2804-- it at http://valgrind.org/support/bug_reports.html.\n--2804-- WARNING: unhandled riscv64-linux syscall: 258\n--2804-- You may be able to write your own handler.\n--2804-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2804-- Nevertheless we consider this a bug.  Please report\n--2804-- it at http://valgrind.org/support/bug_reports.html.\n--2804-- WARNING: unhandled riscv64-linux syscall: 258\n--2804-- You may be able to write your own handler.\n--2804-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2804-- Nevertheless we consider this a bug.  Please report\n--2804-- it at http://valgrind.org/support/bug_reports.html.\n--2804-- WARNING: unhandled riscv64-linux syscall: 258\n--2804-- You may be able to write your own handler.\n--2804-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2804-- Nevertheless we consider this a bug.  Please report\n--2804-- it at http://valgrind.org/support/bug_reports.html.\n--2804-- WARNING: unhandled riscv64-linux syscall: 258\n--2804-- You may be able to write your own handler.\n--2804-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2804-- Nevertheless we consider this a bug.  Please report\n--2804-- it at http://valgrind.org/support/bug_reports.html.\n--2804-- WARNING: unhandled riscv64-linux syscall: 258\n--2804-- You may be able to write your own handler.\n--2804-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2804-- Nevertheless we consider this a bug.  Please report\n--2804-- it at http://valgrind.org/support/bug_reports.html.\n--2804-- WARNING: unhandled riscv64-linux syscall: 258\n--2804-- You may be able to write your own handler.\n--2804-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2804-- Nevertheless we consider this a bug.  Please report\n--2804-- it at http://valgrind.org/support/bug_reports.html.\n--2804-- WARNING: unhandled riscv64-linux syscall: 258\n--2804-- You may be able to write your own handler.\n--2804-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2804-- Nevertheless we consider this a bug.  Please report\n--2804-- it at http://valgrind.org/support/bug_reports.html.\n--2804-- WARNING: unhandled riscv64-linux syscall: 258\n--2804-- You may be able to write your own handler.\n--2804-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2804-- Nevertheless we consider this a bug.  Please report\n--2804-- it at http://valgrind.org/support/bug_reports.html.\n--2804-- WARNING: unhandled riscv64-linux syscall: 258\n--2804-- You may be able to write your own handler.\n--2804-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2804-- Nevertheless we consider this a bug.  Please report\n--2804-- it at http://valgrind.org/support/bug_reports.html.\n--2804-- WARNING: unhandled riscv64-linux syscall: 258\n--2804-- You may be able to write your own handler.\n--2804-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2804-- Nevertheless we consider this a bug.  Please report\n--2804-- 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:
'--2814-- WARNING: unhandled riscv64-linux syscall: 258\n--2814-- You may be able to write your own handler.\n--2814-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2814-- Nevertheless we consider this a bug.  Please report\n--2814-- it at http://valgrind.org/support/bug_reports.html.\n--2814-- WARNING: unhandled riscv64-linux syscall: 258\n--2814-- You may be able to write your own handler.\n--2814-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2814-- Nevertheless we consider this a bug.  Please report\n--2814-- it at http://valgrind.org/support/bug_reports.html.\n--2814-- WARNING: unhandled riscv64-linux syscall: 258\n--2814-- You may be able to write your own handler.\n--2814-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2814-- Nevertheless we consider this a bug.  Please report\n--2814-- it at http://valgrind.org/support/bug_reports.html.\n--2814-- WARNING: unhandled riscv64-linux syscall: 258\n--2814-- You may be able to write your own handler.\n--2814-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2814-- Nevertheless we consider this a bug.  Please report\n--2814-- it at http://valgrind.org/support/bug_reports.html.\n--2814-- WARNING: unhandled riscv64-linux syscall: 258\n--2814-- You may be able to write your own handler.\n--2814-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2814-- Nevertheless we consider this a bug.  Please report\n--2814-- it at http://valgrind.org/support/bug_reports.html.\n--2814-- WARNING: unhandled riscv64-linux syscall: 258\n--2814-- You may be able to write your own handler.\n--2814-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2814-- Nevertheless we consider this a bug.  Please report\n--2814-- it at http://valgrind.org/support/bug_reports.html.\n--2814-- WARNING: unhandled riscv64-linux syscall: 258\n--2814-- You may be able to write your own handler.\n--2814-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2814-- Nevertheless we consider this a bug.  Please report\n--2814-- it at http://valgrind.org/support/bug_reports.html.\n--2814-- WARNING: unhandled riscv64-linux syscall: 258\n--2814-- You may be able to write your own handler.\n--2814-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2814-- Nevertheless we consider this a bug.  Please report\n--2814-- it at http://valgrind.org/support/bug_reports.html.\n--2814-- WARNING: unhandled riscv64-linux syscall: 258\n--2814-- You may be able to write your own handler.\n--2814-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2814-- Nevertheless we consider this a bug.  Please report\n--2814-- it at http://valgrind.org/support/bug_reports.html.\n--2814-- WARNING: unhandled riscv64-linux syscall: 258\n--2814-- You may be able to write your own handler.\n--2814-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2814-- Nevertheless we consider this a bug.  Please report\n--2814-- it at http://valgrind.org/support/bug_reports.html.\n--2814-- WARNING: unhandled riscv64-linux syscall: 258\n--2814-- You may be able to write your own handler.\n--2814-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2814-- Nevertheless we consider this a bug.  Please report\n--2814-- it at http://valgrind.org/support/bug_reports.html.\n--2814-- WARNING: unhandled riscv64-linux syscall: 258\n--2814-- You may be able to write your own handler.\n--2814-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2814-- Nevertheless we consider this a bug.  Please report\n--2814-- it at http://valgrind.org/support/bug_reports.html.\n--2814-- WARNING: unhandled riscv64-linux syscall: 258\n--2814-- You may be able to write your own handler.\n--2814-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2814-- Nevertheless we consider this a bug.  Please report\n--2814-- it at http://valgrind.org/support/bug_reports.html.\n--2814-- WARNING: unhandled riscv64-linux syscall: 258\n--2814-- You may be able to write your own handler.\n--2814-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2814-- Nevertheless we consider this a bug.  Please report\n--2814-- it at http://valgrind.org/support/bug_reports.html.\n--2814-- WARNING: unhandled riscv64-linux syscall: 258\n--2814-- You may be able to write your own handler.\n--2814-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2814-- Nevertheless we consider this a bug.  Please report\n--2814-- it at http://valgrind.org/support/bug_reports.html.\n--2814-- WARNING: unhandled riscv64-linux syscall: 258\n--2814-- You may be able to write your own handler.\n--2814-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2814-- Nevertheless we consider this a bug.  Please report\n--2814-- it at http://valgrind.org/support/bug_reports.html.\n--2814-- WARNING: unhandled riscv64-linux syscall: 258\n--2814-- You may be able to write your own handler.\n--2814-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2814-- Nevertheless we consider this a bug.  Please report\n--2814-- it at http://valgrind.org/support/bug_reports.html.\n--2814-- WARNING: unhandled riscv64-linux syscall: 258\n--2814-- You may be able to write your own handler.\n--2814-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2814-- Nevertheless we consider this a bug.  Please report\n--2814-- 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:
'--2822-- WARNING: unhandled riscv64-linux syscall: 258\n--2822-- You may be able to write your own handler.\n--2822-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2822-- Nevertheless we consider this a bug.  Please report\n--2822-- it at http://valgrind.org/support/bug_reports.html.\n--2822-- WARNING: unhandled riscv64-linux syscall: 258\n--2822-- You may be able to write your own handler.\n--2822-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2822-- Nevertheless we consider this a bug.  Please report\n--2822-- it at http://valgrind.org/support/bug_reports.html.\n--2822-- WARNING: unhandled riscv64-linux syscall: 258\n--2822-- You may be able to write your own handler.\n--2822-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2822-- Nevertheless we consider this a bug.  Please report\n--2822-- it at http://valgrind.org/support/bug_reports.html.\n--2822-- WARNING: unhandled riscv64-linux syscall: 258\n--2822-- You may be able to write your own handler.\n--2822-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2822-- Nevertheless we consider this a bug.  Please report\n--2822-- it at http://valgrind.org/support/bug_reports.html.\n--2822-- WARNING: unhandled riscv64-linux syscall: 258\n--2822-- You may be able to write your own handler.\n--2822-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2822-- Nevertheless we consider this a bug.  Please report\n--2822-- it at http://valgrind.org/support/bug_reports.html.\n--2822-- WARNING: unhandled riscv64-linux syscall: 258\n--2822-- You may be able to write your own handler.\n--2822-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2822-- Nevertheless we consider this a bug.  Please report\n--2822-- it at http://valgrind.org/support/bug_reports.html.\n--2822-- WARNING: unhandled riscv64-linux syscall: 258\n--2822-- You may be able to write your own handler.\n--2822-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2822-- Nevertheless we consider this a bug.  Please report\n--2822-- it at http://valgrind.org/support/bug_reports.html.\n--2822-- WARNING: unhandled riscv64-linux syscall: 258\n--2822-- You may be able to write your own handler.\n--2822-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2822-- Nevertheless we consider this a bug.  Please report\n--2822-- it at http://valgrind.org/support/bug_reports.html.\n--2822-- WARNING: unhandled riscv64-linux syscall: 258\n--2822-- You may be able to write your own handler.\n--2822-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2822-- Nevertheless we consider this a bug.  Please report\n--2822-- it at http://valgrind.org/support/bug_reports.html.\n--2822-- WARNING: unhandled riscv64-linux syscall: 258\n--2822-- You may be able to write your own handler.\n--2822-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2822-- Nevertheless we consider this a bug.  Please report\n--2822-- it at http://valgrind.org/support/bug_reports.html.\n--2822-- WARNING: unhandled riscv64-linux syscall: 258\n--2822-- You may be able to write your own handler.\n--2822-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2822-- Nevertheless we consider this a bug.  Please report\n--2822-- it at http://valgrind.org/support/bug_reports.html.\n--2822-- WARNING: unhandled riscv64-linux syscall: 258\n--2822-- You may be able to write your own handler.\n--2822-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2822-- Nevertheless we consider this a bug.  Please report\n--2822-- it at http://valgrind.org/support/bug_reports.html.\n--2822-- WARNING: unhandled riscv64-linux syscall: 258\n--2822-- You may be able to write your own handler.\n--2822-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2822-- Nevertheless we consider this a bug.  Please report\n--2822-- it at http://valgrind.org/support/bug_reports.html.\n--2822-- WARNING: unhandled riscv64-linux syscall: 258\n--2822-- You may be able to write your own handler.\n--2822-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2822-- Nevertheless we consider this a bug.  Please report\n--2822-- it at http://valgrind.org/support/bug_reports.html.\n--2822-- WARNING: unhandled riscv64-linux syscall: 258\n--2822-- You may be able to write your own handler.\n--2822-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2822-- Nevertheless we consider this a bug.  Please report\n--2822-- it at http://valgrind.org/support/bug_reports.html.\n--2822-- WARNING: unhandled riscv64-linux syscall: 258\n--2822-- You may be able to write your own handler.\n--2822-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2822-- Nevertheless we consider this a bug.  Please report\n--2822-- it at http://valgrind.org/support/bug_reports.html.\n--2822-- WARNING: unhandled riscv64-linux syscall: 258\n--2822-- You may be able to write your own handler.\n--2822-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2822-- Nevertheless we consider this a bug.  Please report\n--2822-- it at http://valgrind.org/support/bug_reports.html.\n--2822-- WARNING: unhandled riscv64-linux syscall: 258\n--2822-- You may be able to write your own handler.\n--2822-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2822-- Nevertheless we consider this a bug.  Please report\n--2822-- 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:
'--2830-- WARNING: unhandled riscv64-linux syscall: 258\n--2830-- You may be able to write your own handler.\n--2830-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2830-- Nevertheless we consider this a bug.  Please report\n--2830-- it at http://valgrind.org/support/bug_reports.html.\n--2830-- WARNING: unhandled riscv64-linux syscall: 258\n--2830-- You may be able to write your own handler.\n--2830-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2830-- Nevertheless we consider this a bug.  Please report\n--2830-- it at http://valgrind.org/support/bug_reports.html.\n--2830-- WARNING: unhandled riscv64-linux syscall: 258\n--2830-- You may be able to write your own handler.\n--2830-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2830-- Nevertheless we consider this a bug.  Please report\n--2830-- it at http://valgrind.org/support/bug_reports.html.\n--2830-- WARNING: unhandled riscv64-linux syscall: 258\n--2830-- You may be able to write your own handler.\n--2830-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2830-- Nevertheless we consider this a bug.  Please report\n--2830-- it at http://valgrind.org/support/bug_reports.html.\n--2830-- WARNING: unhandled riscv64-linux syscall: 258\n--2830-- You may be able to write your own handler.\n--2830-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2830-- Nevertheless we consider this a bug.  Please report\n--2830-- it at http://valgrind.org/support/bug_reports.html.\n--2830-- WARNING: unhandled riscv64-linux syscall: 258\n--2830-- You may be able to write your own handler.\n--2830-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2830-- Nevertheless we consider this a bug.  Please report\n--2830-- it at http://valgrind.org/support/bug_reports.html.\n--2830-- WARNING: unhandled riscv64-linux syscall: 258\n--2830-- You may be able to write your own handler.\n--2830-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2830-- Nevertheless we consider this a bug.  Please report\n--2830-- it at http://valgrind.org/support/bug_reports.html.\n--2830-- WARNING: unhandled riscv64-linux syscall: 258\n--2830-- You may be able to write your own handler.\n--2830-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2830-- Nevertheless we consider this a bug.  Please report\n--2830-- it at http://valgrind.org/support/bug_reports.html.\n--2830-- WARNING: unhandled riscv64-linux syscall: 258\n--2830-- You may be able to write your own handler.\n--2830-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2830-- Nevertheless we consider this a bug.  Please report\n--2830-- it at http://valgrind.org/support/bug_reports.html.\n--2830-- WARNING: unhandled riscv64-linux syscall: 258\n--2830-- You may be able to write your own handler.\n--2830-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2830-- Nevertheless we consider this a bug.  Please report\n--2830-- it at http://valgrind.org/support/bug_reports.html.\n--2830-- WARNING: unhandled riscv64-linux syscall: 258\n--2830-- You may be able to write your own handler.\n--2830-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2830-- Nevertheless we consider this a bug.  Please report\n--2830-- it at http://valgrind.org/support/bug_reports.html.\n--2830-- WARNING: unhandled riscv64-linux syscall: 258\n--2830-- You may be able to write your own handler.\n--2830-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2830-- Nevertheless we consider this a bug.  Please report\n--2830-- it at http://valgrind.org/support/bug_reports.html.\n--2830-- WARNING: unhandled riscv64-linux syscall: 258\n--2830-- You may be able to write your own handler.\n--2830-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2830-- Nevertheless we consider this a bug.  Please report\n--2830-- it at http://valgrind.org/support/bug_reports.html.\n--2830-- WARNING: unhandled riscv64-linux syscall: 258\n--2830-- You may be able to write your own handler.\n--2830-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2830-- Nevertheless we consider this a bug.  Please report\n--2830-- it at http://valgrind.org/support/bug_reports.html.\n--2830-- WARNING: unhandled riscv64-linux syscall: 258\n--2830-- You may be able to write your own handler.\n--2830-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2830-- Nevertheless we consider this a bug.  Please report\n--2830-- it at http://valgrind.org/support/bug_reports.html.\n--2830-- WARNING: unhandled riscv64-linux syscall: 258\n--2830-- You may be able to write your own handler.\n--2830-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2830-- Nevertheless we consider this a bug.  Please report\n--2830-- it at http://valgrind.org/support/bug_reports.html.\n--2830-- WARNING: unhandled riscv64-linux syscall: 258\n--2830-- You may be able to write your own handler.\n--2830-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2830-- Nevertheless we consider this a bug.  Please report\n--2830-- it at http://valgrind.org/support/bug_reports.html.\n--2830-- WARNING: unhandled riscv64-linux syscall: 258\n--2830-- You may be able to write your own handler.\n--2830-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2830-- Nevertheless we consider this a bug.  Please report\n--2830-- 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:
'--2838-- WARNING: unhandled riscv64-linux syscall: 258\n--2838-- You may be able to write your own handler.\n--2838-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2838-- Nevertheless we consider this a bug.  Please report\n--2838-- it at http://valgrind.org/support/bug_reports.html.\n--2838-- WARNING: unhandled riscv64-linux syscall: 258\n--2838-- You may be able to write your own handler.\n--2838-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2838-- Nevertheless we consider this a bug.  Please report\n--2838-- it at http://valgrind.org/support/bug_reports.html.\n--2838-- WARNING: unhandled riscv64-linux syscall: 258\n--2838-- You may be able to write your own handler.\n--2838-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2838-- Nevertheless we consider this a bug.  Please report\n--2838-- it at http://valgrind.org/support/bug_reports.html.\n--2838-- WARNING: unhandled riscv64-linux syscall: 258\n--2838-- You may be able to write your own handler.\n--2838-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2838-- Nevertheless we consider this a bug.  Please report\n--2838-- it at http://valgrind.org/support/bug_reports.html.\n--2838-- WARNING: unhandled riscv64-linux syscall: 258\n--2838-- You may be able to write your own handler.\n--2838-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2838-- Nevertheless we consider this a bug.  Please report\n--2838-- it at http://valgrind.org/support/bug_reports.html.\n--2838-- WARNING: unhandled riscv64-linux syscall: 258\n--2838-- You may be able to write your own handler.\n--2838-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2838-- Nevertheless we consider this a bug.  Please report\n--2838-- it at http://valgrind.org/support/bug_reports.html.\n--2838-- WARNING: unhandled riscv64-linux syscall: 258\n--2838-- You may be able to write your own handler.\n--2838-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2838-- Nevertheless we consider this a bug.  Please report\n--2838-- it at http://valgrind.org/support/bug_reports.html.\n--2838-- WARNING: unhandled riscv64-linux syscall: 258\n--2838-- You may be able to write your own handler.\n--2838-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2838-- Nevertheless we consider this a bug.  Please report\n--2838-- it at http://valgrind.org/support/bug_reports.html.\n--2838-- WARNING: unhandled riscv64-linux syscall: 258\n--2838-- You may be able to write your own handler.\n--2838-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2838-- Nevertheless we consider this a bug.  Please report\n--2838-- it at http://valgrind.org/support/bug_reports.html.\n--2838-- WARNING: unhandled riscv64-linux syscall: 258\n--2838-- You may be able to write your own handler.\n--2838-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2838-- Nevertheless we consider this a bug.  Please report\n--2838-- it at http://valgrind.org/support/bug_reports.html.\n--2838-- WARNING: unhandled riscv64-linux syscall: 258\n--2838-- You may be able to write your own handler.\n--2838-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2838-- Nevertheless we consider this a bug.  Please report\n--2838-- it at http://valgrind.org/support/bug_reports.html.\n--2838-- WARNING: unhandled riscv64-linux syscall: 258\n--2838-- You may be able to write your own handler.\n--2838-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2838-- Nevertheless we consider this a bug.  Please report\n--2838-- it at http://valgrind.org/support/bug_reports.html.\n--2838-- WARNING: unhandled riscv64-linux syscall: 258\n--2838-- You may be able to write your own handler.\n--2838-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2838-- Nevertheless we consider this a bug.  Please report\n--2838-- it at http://valgrind.org/support/bug_reports.html.\n--2838-- WARNING: unhandled riscv64-linux syscall: 258\n--2838-- You may be able to write your own handler.\n--2838-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2838-- Nevertheless we consider this a bug.  Please report\n--2838-- it at http://valgrind.org/support/bug_reports.html.\n--2838-- WARNING: unhandled riscv64-linux syscall: 258\n--2838-- You may be able to write your own handler.\n--2838-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2838-- Nevertheless we consider this a bug.  Please report\n--2838-- it at http://valgrind.org/support/bug_reports.html.\n--2838-- WARNING: unhandled riscv64-linux syscall: 258\n--2838-- You may be able to write your own handler.\n--2838-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2838-- Nevertheless we consider this a bug.  Please report\n--2838-- it at http://valgrind.org/support/bug_reports.html.\n--2838-- WARNING: unhandled riscv64-linux syscall: 258\n--2838-- You may be able to write your own handler.\n--2838-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2838-- Nevertheless we consider this a bug.  Please report\n--2838-- it at http://valgrind.org/support/bug_reports.html.\n--2838-- WARNING: unhandled riscv64-linux syscall: 258\n--2838-- You may be able to write your own handler.\n--2838-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2838-- Nevertheless we consider this a bug.  Please report\n--2838-- 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:
'--2846-- WARNING: unhandled riscv64-linux syscall: 258\n--2846-- You may be able to write your own handler.\n--2846-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2846-- Nevertheless we consider this a bug.  Please report\n--2846-- it at http://valgrind.org/support/bug_reports.html.\n--2846-- WARNING: unhandled riscv64-linux syscall: 258\n--2846-- You may be able to write your own handler.\n--2846-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2846-- Nevertheless we consider this a bug.  Please report\n--2846-- it at http://valgrind.org/support/bug_reports.html.\n--2846-- WARNING: unhandled riscv64-linux syscall: 258\n--2846-- You may be able to write your own handler.\n--2846-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2846-- Nevertheless we consider this a bug.  Please report\n--2846-- it at http://valgrind.org/support/bug_reports.html.\n--2846-- WARNING: unhandled riscv64-linux syscall: 258\n--2846-- You may be able to write your own handler.\n--2846-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2846-- Nevertheless we consider this a bug.  Please report\n--2846-- it at http://valgrind.org/support/bug_reports.html.\n--2846-- WARNING: unhandled riscv64-linux syscall: 258\n--2846-- You may be able to write your own handler.\n--2846-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2846-- Nevertheless we consider this a bug.  Please report\n--2846-- it at http://valgrind.org/support/bug_reports.html.\n--2846-- WARNING: unhandled riscv64-linux syscall: 258\n--2846-- You may be able to write your own handler.\n--2846-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2846-- Nevertheless we consider this a bug.  Please report\n--2846-- it at http://valgrind.org/support/bug_reports.html.\n--2846-- WARNING: unhandled riscv64-linux syscall: 258\n--2846-- You may be able to write your own handler.\n--2846-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2846-- Nevertheless we consider this a bug.  Please report\n--2846-- it at http://valgrind.org/support/bug_reports.html.\n--2846-- WARNING: unhandled riscv64-linux syscall: 258\n--2846-- You may be able to write your own handler.\n--2846-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2846-- Nevertheless we consider this a bug.  Please report\n--2846-- it at http://valgrind.org/support/bug_reports.html.\n--2846-- WARNING: unhandled riscv64-linux syscall: 258\n--2846-- You may be able to write your own handler.\n--2846-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2846-- Nevertheless we consider this a bug.  Please report\n--2846-- it at http://valgrind.org/support/bug_reports.html.\n--2846-- WARNING: unhandled riscv64-linux syscall: 258\n--2846-- You may be able to write your own handler.\n--2846-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2846-- Nevertheless we consider this a bug.  Please report\n--2846-- it at http://valgrind.org/support/bug_reports.html.\n--2846-- WARNING: unhandled riscv64-linux syscall: 258\n--2846-- You may be able to write your own handler.\n--2846-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2846-- Nevertheless we consider this a bug.  Please report\n--2846-- it at http://valgrind.org/support/bug_reports.html.\n--2846-- WARNING: unhandled riscv64-linux syscall: 258\n--2846-- You may be able to write your own handler.\n--2846-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2846-- Nevertheless we consider this a bug.  Please report\n--2846-- it at http://valgrind.org/support/bug_reports.html.\n--2846-- WARNING: unhandled riscv64-linux syscall: 258\n--2846-- You may be able to write your own handler.\n--2846-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2846-- Nevertheless we consider this a bug.  Please report\n--2846-- it at http://valgrind.org/support/bug_reports.html.\n--2846-- WARNING: unhandled riscv64-linux syscall: 258\n--2846-- You may be able to write your own handler.\n--2846-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2846-- Nevertheless we consider this a bug.  Please report\n--2846-- it at http://valgrind.org/support/bug_reports.html.\n--2846-- WARNING: unhandled riscv64-linux syscall: 258\n--2846-- You may be able to write your own handler.\n--2846-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2846-- Nevertheless we consider this a bug.  Please report\n--2846-- it at http://valgrind.org/support/bug_reports.html.\n--2846-- WARNING: unhandled riscv64-linux syscall: 258\n--2846-- You may be able to write your own handler.\n--2846-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2846-- Nevertheless we consider this a bug.  Please report\n--2846-- it at http://valgrind.org/support/bug_reports.html.\n--2846-- WARNING: unhandled riscv64-linux syscall: 258\n--2846-- You may be able to write your own handler.\n--2846-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2846-- Nevertheless we consider this a bug.  Please report\n--2846-- it at http://valgrind.org/support/bug_reports.html.\n--2846-- WARNING: unhandled riscv64-linux syscall: 258\n--2846-- You may be able to write your own handler.\n--2846-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2846-- Nevertheless we consider this a bug.  Please report\n--2846-- 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:
'--2854-- WARNING: unhandled riscv64-linux syscall: 258\n--2854-- You may be able to write your own handler.\n--2854-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2854-- Nevertheless we consider this a bug.  Please report\n--2854-- it at http://valgrind.org/support/bug_reports.html.\n--2854-- WARNING: unhandled riscv64-linux syscall: 258\n--2854-- You may be able to write your own handler.\n--2854-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2854-- Nevertheless we consider this a bug.  Please report\n--2854-- it at http://valgrind.org/support/bug_reports.html.\n--2854-- WARNING: unhandled riscv64-linux syscall: 258\n--2854-- You may be able to write your own handler.\n--2854-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2854-- Nevertheless we consider this a bug.  Please report\n--2854-- it at http://valgrind.org/support/bug_reports.html.\n--2854-- WARNING: unhandled riscv64-linux syscall: 258\n--2854-- You may be able to write your own handler.\n--2854-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2854-- Nevertheless we consider this a bug.  Please report\n--2854-- it at http://valgrind.org/support/bug_reports.html.\n--2854-- WARNING: unhandled riscv64-linux syscall: 258\n--2854-- You may be able to write your own handler.\n--2854-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2854-- Nevertheless we consider this a bug.  Please report\n--2854-- it at http://valgrind.org/support/bug_reports.html.\n--2854-- WARNING: unhandled riscv64-linux syscall: 258\n--2854-- You may be able to write your own handler.\n--2854-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2854-- Nevertheless we consider this a bug.  Please report\n--2854-- it at http://valgrind.org/support/bug_reports.html.\n--2854-- WARNING: unhandled riscv64-linux syscall: 258\n--2854-- You may be able to write your own handler.\n--2854-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2854-- Nevertheless we consider this a bug.  Please report\n--2854-- it at http://valgrind.org/support/bug_reports.html.\n--2854-- WARNING: unhandled riscv64-linux syscall: 258\n--2854-- You may be able to write your own handler.\n--2854-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2854-- Nevertheless we consider this a bug.  Please report\n--2854-- it at http://valgrind.org/support/bug_reports.html.\n--2854-- WARNING: unhandled riscv64-linux syscall: 258\n--2854-- You may be able to write your own handler.\n--2854-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2854-- Nevertheless we consider this a bug.  Please report\n--2854-- it at http://valgrind.org/support/bug_reports.html.\n--2854-- WARNING: unhandled riscv64-linux syscall: 258\n--2854-- You may be able to write your own handler.\n--2854-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2854-- Nevertheless we consider this a bug.  Please report\n--2854-- it at http://valgrind.org/support/bug_reports.html.\n--2854-- WARNING: unhandled riscv64-linux syscall: 258\n--2854-- You may be able to write your own handler.\n--2854-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2854-- Nevertheless we consider this a bug.  Please report\n--2854-- it at http://valgrind.org/support/bug_reports.html.\n--2854-- WARNING: unhandled riscv64-linux syscall: 258\n--2854-- You may be able to write your own handler.\n--2854-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2854-- Nevertheless we consider this a bug.  Please report\n--2854-- it at http://valgrind.org/support/bug_reports.html.\n--2854-- WARNING: unhandled riscv64-linux syscall: 258\n--2854-- You may be able to write your own handler.\n--2854-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2854-- Nevertheless we consider this a bug.  Please report\n--2854-- it at http://valgrind.org/support/bug_reports.html.\n--2854-- WARNING: unhandled riscv64-linux syscall: 258\n--2854-- You may be able to write your own handler.\n--2854-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2854-- Nevertheless we consider this a bug.  Please report\n--2854-- it at http://valgrind.org/support/bug_reports.html.\n--2854-- WARNING: unhandled riscv64-linux syscall: 258\n--2854-- You may be able to write your own handler.\n--2854-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2854-- Nevertheless we consider this a bug.  Please report\n--2854-- it at http://valgrind.org/support/bug_reports.html.\n--2854-- WARNING: unhandled riscv64-linux syscall: 258\n--2854-- You may be able to write your own handler.\n--2854-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2854-- Nevertheless we consider this a bug.  Please report\n--2854-- it at http://valgrind.org/support/bug_reports.html.\n--2854-- WARNING: unhandled riscv64-linux syscall: 258\n--2854-- You may be able to write your own handler.\n--2854-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2854-- Nevertheless we consider this a bug.  Please report\n--2854-- it at http://valgrind.org/support/bug_reports.html.\n--2854-- WARNING: unhandled riscv64-linux syscall: 258\n--2854-- You may be able to write your own handler.\n--2854-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2854-- Nevertheless we consider this a bug.  Please report\n--2854-- 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:
'--2862-- WARNING: unhandled riscv64-linux syscall: 258\n--2862-- You may be able to write your own handler.\n--2862-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2862-- Nevertheless we consider this a bug.  Please report\n--2862-- it at http://valgrind.org/support/bug_reports.html.\n--2862-- WARNING: unhandled riscv64-linux syscall: 258\n--2862-- You may be able to write your own handler.\n--2862-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2862-- Nevertheless we consider this a bug.  Please report\n--2862-- it at http://valgrind.org/support/bug_reports.html.\n--2862-- WARNING: unhandled riscv64-linux syscall: 258\n--2862-- You may be able to write your own handler.\n--2862-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2862-- Nevertheless we consider this a bug.  Please report\n--2862-- it at http://valgrind.org/support/bug_reports.html.\n--2862-- WARNING: unhandled riscv64-linux syscall: 258\n--2862-- You may be able to write your own handler.\n--2862-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2862-- Nevertheless we consider this a bug.  Please report\n--2862-- it at http://valgrind.org/support/bug_reports.html.\n--2862-- WARNING: unhandled riscv64-linux syscall: 258\n--2862-- You may be able to write your own handler.\n--2862-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2862-- Nevertheless we consider this a bug.  Please report\n--2862-- it at http://valgrind.org/support/bug_reports.html.\n--2862-- WARNING: unhandled riscv64-linux syscall: 258\n--2862-- You may be able to write your own handler.\n--2862-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2862-- Nevertheless we consider this a bug.  Please report\n--2862-- it at http://valgrind.org/support/bug_reports.html.\n--2862-- WARNING: unhandled riscv64-linux syscall: 258\n--2862-- You may be able to write your own handler.\n--2862-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2862-- Nevertheless we consider this a bug.  Please report\n--2862-- it at http://valgrind.org/support/bug_reports.html.\n--2862-- WARNING: unhandled riscv64-linux syscall: 258\n--2862-- You may be able to write your own handler.\n--2862-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2862-- Nevertheless we consider this a bug.  Please report\n--2862-- it at http://valgrind.org/support/bug_reports.html.\n--2862-- WARNING: unhandled riscv64-linux syscall: 258\n--2862-- You may be able to write your own handler.\n--2862-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2862-- Nevertheless we consider this a bug.  Please report\n--2862-- it at http://valgrind.org/support/bug_reports.html.\n--2862-- WARNING: unhandled riscv64-linux syscall: 258\n--2862-- You may be able to write your own handler.\n--2862-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2862-- Nevertheless we consider this a bug.  Please report\n--2862-- it at http://valgrind.org/support/bug_reports.html.\n--2862-- WARNING: unhandled riscv64-linux syscall: 258\n--2862-- You may be able to write your own handler.\n--2862-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2862-- Nevertheless we consider this a bug.  Please report\n--2862-- it at http://valgrind.org/support/bug_reports.html.\n--2862-- WARNING: unhandled riscv64-linux syscall: 258\n--2862-- You may be able to write your own handler.\n--2862-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2862-- Nevertheless we consider this a bug.  Please report\n--2862-- it at http://valgrind.org/support/bug_reports.html.\n--2862-- WARNING: unhandled riscv64-linux syscall: 258\n--2862-- You may be able to write your own handler.\n--2862-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2862-- Nevertheless we consider this a bug.  Please report\n--2862-- it at http://valgrind.org/support/bug_reports.html.\n--2862-- WARNING: unhandled riscv64-linux syscall: 258\n--2862-- You may be able to write your own handler.\n--2862-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2862-- Nevertheless we consider this a bug.  Please report\n--2862-- it at http://valgrind.org/support/bug_reports.html.\n--2862-- WARNING: unhandled riscv64-linux syscall: 258\n--2862-- You may be able to write your own handler.\n--2862-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2862-- Nevertheless we consider this a bug.  Please report\n--2862-- it at http://valgrind.org/support/bug_reports.html.\n--2862-- WARNING: unhandled riscv64-linux syscall: 258\n--2862-- You may be able to write your own handler.\n--2862-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2862-- Nevertheless we consider this a bug.  Please report\n--2862-- it at http://valgrind.org/support/bug_reports.html.\n--2862-- WARNING: unhandled riscv64-linux syscall: 258\n--2862-- You may be able to write your own handler.\n--2862-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2862-- Nevertheless we consider this a bug.  Please report\n--2862-- it at http://valgrind.org/support/bug_reports.html.\n--2862-- WARNING: unhandled riscv64-linux syscall: 258\n--2862-- You may be able to write your own handler.\n--2862-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2862-- Nevertheless we consider this a bug.  Please report\n--2862-- 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:
'--2870-- WARNING: unhandled riscv64-linux syscall: 258\n--2870-- You may be able to write your own handler.\n--2870-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2870-- Nevertheless we consider this a bug.  Please report\n--2870-- it at http://valgrind.org/support/bug_reports.html.\n--2870-- WARNING: unhandled riscv64-linux syscall: 258\n--2870-- You may be able to write your own handler.\n--2870-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2870-- Nevertheless we consider this a bug.  Please report\n--2870-- it at http://valgrind.org/support/bug_reports.html.\n--2870-- WARNING: unhandled riscv64-linux syscall: 258\n--2870-- You may be able to write your own handler.\n--2870-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2870-- Nevertheless we consider this a bug.  Please report\n--2870-- it at http://valgrind.org/support/bug_reports.html.\n--2870-- WARNING: unhandled riscv64-linux syscall: 258\n--2870-- You may be able to write your own handler.\n--2870-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2870-- Nevertheless we consider this a bug.  Please report\n--2870-- it at http://valgrind.org/support/bug_reports.html.\n--2870-- WARNING: unhandled riscv64-linux syscall: 258\n--2870-- You may be able to write your own handler.\n--2870-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2870-- Nevertheless we consider this a bug.  Please report\n--2870-- it at http://valgrind.org/support/bug_reports.html.\n--2870-- WARNING: unhandled riscv64-linux syscall: 258\n--2870-- You may be able to write your own handler.\n--2870-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2870-- Nevertheless we consider this a bug.  Please report\n--2870-- it at http://valgrind.org/support/bug_reports.html.\n--2870-- WARNING: unhandled riscv64-linux syscall: 258\n--2870-- You may be able to write your own handler.\n--2870-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2870-- Nevertheless we consider this a bug.  Please report\n--2870-- it at http://valgrind.org/support/bug_reports.html.\n--2870-- WARNING: unhandled riscv64-linux syscall: 258\n--2870-- You may be able to write your own handler.\n--2870-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2870-- Nevertheless we consider this a bug.  Please report\n--2870-- it at http://valgrind.org/support/bug_reports.html.\n--2870-- WARNING: unhandled riscv64-linux syscall: 258\n--2870-- You may be able to write your own handler.\n--2870-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2870-- Nevertheless we consider this a bug.  Please report\n--2870-- it at http://valgrind.org/support/bug_reports.html.\n--2870-- WARNING: unhandled riscv64-linux syscall: 258\n--2870-- You may be able to write your own handler.\n--2870-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2870-- Nevertheless we consider this a bug.  Please report\n--2870-- it at http://valgrind.org/support/bug_reports.html.\n--2870-- WARNING: unhandled riscv64-linux syscall: 258\n--2870-- You may be able to write your own handler.\n--2870-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2870-- Nevertheless we consider this a bug.  Please report\n--2870-- it at http://valgrind.org/support/bug_reports.html.\n--2870-- WARNING: unhandled riscv64-linux syscall: 258\n--2870-- You may be able to write your own handler.\n--2870-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2870-- Nevertheless we consider this a bug.  Please report\n--2870-- it at http://valgrind.org/support/bug_reports.html.\n--2870-- WARNING: unhandled riscv64-linux syscall: 258\n--2870-- You may be able to write your own handler.\n--2870-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2870-- Nevertheless we consider this a bug.  Please report\n--2870-- it at http://valgrind.org/support/bug_reports.html.\n--2870-- WARNING: unhandled riscv64-linux syscall: 258\n--2870-- You may be able to write your own handler.\n--2870-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2870-- Nevertheless we consider this a bug.  Please report\n--2870-- it at http://valgrind.org/support/bug_reports.html.\n--2870-- WARNING: unhandled riscv64-linux syscall: 258\n--2870-- You may be able to write your own handler.\n--2870-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2870-- Nevertheless we consider this a bug.  Please report\n--2870-- it at http://valgrind.org/support/bug_reports.html.\n--2870-- WARNING: unhandled riscv64-linux syscall: 258\n--2870-- You may be able to write your own handler.\n--2870-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2870-- Nevertheless we consider this a bug.  Please report\n--2870-- it at http://valgrind.org/support/bug_reports.html.\n--2870-- WARNING: unhandled riscv64-linux syscall: 258\n--2870-- You may be able to write your own handler.\n--2870-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2870-- Nevertheless we consider this a bug.  Please report\n--2870-- it at http://valgrind.org/support/bug_reports.html.\n--2870-- WARNING: unhandled riscv64-linux syscall: 258\n--2870-- You may be able to write your own handler.\n--2870-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2870-- Nevertheless we consider this a bug.  Please report\n--2870-- 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:
'--2878-- WARNING: unhandled riscv64-linux syscall: 258\n--2878-- You may be able to write your own handler.\n--2878-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2878-- Nevertheless we consider this a bug.  Please report\n--2878-- it at http://valgrind.org/support/bug_reports.html.\n--2878-- WARNING: unhandled riscv64-linux syscall: 258\n--2878-- You may be able to write your own handler.\n--2878-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2878-- Nevertheless we consider this a bug.  Please report\n--2878-- it at http://valgrind.org/support/bug_reports.html.\n--2878-- WARNING: unhandled riscv64-linux syscall: 258\n--2878-- You may be able to write your own handler.\n--2878-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2878-- Nevertheless we consider this a bug.  Please report\n--2878-- it at http://valgrind.org/support/bug_reports.html.\n--2878-- WARNING: unhandled riscv64-linux syscall: 258\n--2878-- You may be able to write your own handler.\n--2878-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2878-- Nevertheless we consider this a bug.  Please report\n--2878-- it at http://valgrind.org/support/bug_reports.html.\n--2878-- WARNING: unhandled riscv64-linux syscall: 258\n--2878-- You may be able to write your own handler.\n--2878-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2878-- Nevertheless we consider this a bug.  Please report\n--2878-- it at http://valgrind.org/support/bug_reports.html.\n--2878-- WARNING: unhandled riscv64-linux syscall: 258\n--2878-- You may be able to write your own handler.\n--2878-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2878-- Nevertheless we consider this a bug.  Please report\n--2878-- it at http://valgrind.org/support/bug_reports.html.\n--2878-- WARNING: unhandled riscv64-linux syscall: 258\n--2878-- You may be able to write your own handler.\n--2878-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2878-- Nevertheless we consider this a bug.  Please report\n--2878-- it at http://valgrind.org/support/bug_reports.html.\n--2878-- WARNING: unhandled riscv64-linux syscall: 258\n--2878-- You may be able to write your own handler.\n--2878-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2878-- Nevertheless we consider this a bug.  Please report\n--2878-- it at http://valgrind.org/support/bug_reports.html.\n--2878-- WARNING: unhandled riscv64-linux syscall: 258\n--2878-- You may be able to write your own handler.\n--2878-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2878-- Nevertheless we consider this a bug.  Please report\n--2878-- it at http://valgrind.org/support/bug_reports.html.\n--2878-- WARNING: unhandled riscv64-linux syscall: 258\n--2878-- You may be able to write your own handler.\n--2878-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2878-- Nevertheless we consider this a bug.  Please report\n--2878-- it at http://valgrind.org/support/bug_reports.html.\n--2878-- WARNING: unhandled riscv64-linux syscall: 258\n--2878-- You may be able to write your own handler.\n--2878-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2878-- Nevertheless we consider this a bug.  Please report\n--2878-- it at http://valgrind.org/support/bug_reports.html.\n--2878-- WARNING: unhandled riscv64-linux syscall: 258\n--2878-- You may be able to write your own handler.\n--2878-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2878-- Nevertheless we consider this a bug.  Please report\n--2878-- it at http://valgrind.org/support/bug_reports.html.\n--2878-- WARNING: unhandled riscv64-linux syscall: 258\n--2878-- You may be able to write your own handler.\n--2878-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2878-- Nevertheless we consider this a bug.  Please report\n--2878-- it at http://valgrind.org/support/bug_reports.html.\n--2878-- WARNING: unhandled riscv64-linux syscall: 258\n--2878-- You may be able to write your own handler.\n--2878-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2878-- Nevertheless we consider this a bug.  Please report\n--2878-- it at http://valgrind.org/support/bug_reports.html.\n--2878-- WARNING: unhandled riscv64-linux syscall: 258\n--2878-- You may be able to write your own handler.\n--2878-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2878-- Nevertheless we consider this a bug.  Please report\n--2878-- it at http://valgrind.org/support/bug_reports.html.\n--2878-- WARNING: unhandled riscv64-linux syscall: 258\n--2878-- You may be able to write your own handler.\n--2878-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2878-- Nevertheless we consider this a bug.  Please report\n--2878-- it at http://valgrind.org/support/bug_reports.html.\n--2878-- WARNING: unhandled riscv64-linux syscall: 258\n--2878-- You may be able to write your own handler.\n--2878-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2878-- Nevertheless we consider this a bug.  Please report\n--2878-- it at http://valgrind.org/support/bug_reports.html.\n--2878-- WARNING: unhandled riscv64-linux syscall: 258\n--2878-- You may be able to write your own handler.\n--2878-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2878-- Nevertheless we consider this a bug.  Please report\n--2878-- 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:
'--2886-- WARNING: unhandled riscv64-linux syscall: 258\n--2886-- You may be able to write your own handler.\n--2886-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2886-- Nevertheless we consider this a bug.  Please report\n--2886-- it at http://valgrind.org/support/bug_reports.html.\n--2886-- WARNING: unhandled riscv64-linux syscall: 258\n--2886-- You may be able to write your own handler.\n--2886-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2886-- Nevertheless we consider this a bug.  Please report\n--2886-- it at http://valgrind.org/support/bug_reports.html.\n--2886-- WARNING: unhandled riscv64-linux syscall: 258\n--2886-- You may be able to write your own handler.\n--2886-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2886-- Nevertheless we consider this a bug.  Please report\n--2886-- it at http://valgrind.org/support/bug_reports.html.\n--2886-- WARNING: unhandled riscv64-linux syscall: 258\n--2886-- You may be able to write your own handler.\n--2886-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2886-- Nevertheless we consider this a bug.  Please report\n--2886-- it at http://valgrind.org/support/bug_reports.html.\n--2886-- WARNING: unhandled riscv64-linux syscall: 258\n--2886-- You may be able to write your own handler.\n--2886-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2886-- Nevertheless we consider this a bug.  Please report\n--2886-- it at http://valgrind.org/support/bug_reports.html.\n--2886-- WARNING: unhandled riscv64-linux syscall: 258\n--2886-- You may be able to write your own handler.\n--2886-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2886-- Nevertheless we consider this a bug.  Please report\n--2886-- it at http://valgrind.org/support/bug_reports.html.\n--2886-- WARNING: unhandled riscv64-linux syscall: 258\n--2886-- You may be able to write your own handler.\n--2886-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2886-- Nevertheless we consider this a bug.  Please report\n--2886-- it at http://valgrind.org/support/bug_reports.html.\n--2886-- WARNING: unhandled riscv64-linux syscall: 258\n--2886-- You may be able to write your own handler.\n--2886-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2886-- Nevertheless we consider this a bug.  Please report\n--2886-- it at http://valgrind.org/support/bug_reports.html.\n--2886-- WARNING: unhandled riscv64-linux syscall: 258\n--2886-- You may be able to write your own handler.\n--2886-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2886-- Nevertheless we consider this a bug.  Please report\n--2886-- it at http://valgrind.org/support/bug_reports.html.\n--2886-- WARNING: unhandled riscv64-linux syscall: 258\n--2886-- You may be able to write your own handler.\n--2886-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2886-- Nevertheless we consider this a bug.  Please report\n--2886-- it at http://valgrind.org/support/bug_reports.html.\n--2886-- WARNING: unhandled riscv64-linux syscall: 258\n--2886-- You may be able to write your own handler.\n--2886-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2886-- Nevertheless we consider this a bug.  Please report\n--2886-- it at http://valgrind.org/support/bug_reports.html.\n--2886-- WARNING: unhandled riscv64-linux syscall: 258\n--2886-- You may be able to write your own handler.\n--2886-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2886-- Nevertheless we consider this a bug.  Please report\n--2886-- it at http://valgrind.org/support/bug_reports.html.\n--2886-- WARNING: unhandled riscv64-linux syscall: 258\n--2886-- You may be able to write your own handler.\n--2886-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2886-- Nevertheless we consider this a bug.  Please report\n--2886-- it at http://valgrind.org/support/bug_reports.html.\n--2886-- WARNING: unhandled riscv64-linux syscall: 258\n--2886-- You may be able to write your own handler.\n--2886-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2886-- Nevertheless we consider this a bug.  Please report\n--2886-- it at http://valgrind.org/support/bug_reports.html.\n--2886-- WARNING: unhandled riscv64-linux syscall: 258\n--2886-- You may be able to write your own handler.\n--2886-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2886-- Nevertheless we consider this a bug.  Please report\n--2886-- it at http://valgrind.org/support/bug_reports.html.\n--2886-- WARNING: unhandled riscv64-linux syscall: 258\n--2886-- You may be able to write your own handler.\n--2886-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2886-- Nevertheless we consider this a bug.  Please report\n--2886-- it at http://valgrind.org/support/bug_reports.html.\n--2886-- WARNING: unhandled riscv64-linux syscall: 258\n--2886-- You may be able to write your own handler.\n--2886-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2886-- Nevertheless we consider this a bug.  Please report\n--2886-- it at http://valgrind.org/support/bug_reports.html.\n--2886-- WARNING: unhandled riscv64-linux syscall: 258\n--2886-- You may be able to write your own handler.\n--2886-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2886-- Nevertheless we consider this a bug.  Please report\n--2886-- 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:
'--2894-- WARNING: unhandled riscv64-linux syscall: 258\n--2894-- You may be able to write your own handler.\n--2894-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2894-- Nevertheless we consider this a bug.  Please report\n--2894-- it at http://valgrind.org/support/bug_reports.html.\n--2894-- WARNING: unhandled riscv64-linux syscall: 258\n--2894-- You may be able to write your own handler.\n--2894-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2894-- Nevertheless we consider this a bug.  Please report\n--2894-- it at http://valgrind.org/support/bug_reports.html.\n--2894-- WARNING: unhandled riscv64-linux syscall: 258\n--2894-- You may be able to write your own handler.\n--2894-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2894-- Nevertheless we consider this a bug.  Please report\n--2894-- it at http://valgrind.org/support/bug_reports.html.\n--2894-- WARNING: unhandled riscv64-linux syscall: 258\n--2894-- You may be able to write your own handler.\n--2894-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2894-- Nevertheless we consider this a bug.  Please report\n--2894-- it at http://valgrind.org/support/bug_reports.html.\n--2894-- WARNING: unhandled riscv64-linux syscall: 258\n--2894-- You may be able to write your own handler.\n--2894-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2894-- Nevertheless we consider this a bug.  Please report\n--2894-- it at http://valgrind.org/support/bug_reports.html.\n--2894-- WARNING: unhandled riscv64-linux syscall: 258\n--2894-- You may be able to write your own handler.\n--2894-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2894-- Nevertheless we consider this a bug.  Please report\n--2894-- it at http://valgrind.org/support/bug_reports.html.\n--2894-- WARNING: unhandled riscv64-linux syscall: 258\n--2894-- You may be able to write your own handler.\n--2894-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2894-- Nevertheless we consider this a bug.  Please report\n--2894-- it at http://valgrind.org/support/bug_reports.html.\n--2894-- WARNING: unhandled riscv64-linux syscall: 258\n--2894-- You may be able to write your own handler.\n--2894-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2894-- Nevertheless we consider this a bug.  Please report\n--2894-- it at http://valgrind.org/support/bug_reports.html.\n--2894-- WARNING: unhandled riscv64-linux syscall: 258\n--2894-- You may be able to write your own handler.\n--2894-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2894-- Nevertheless we consider this a bug.  Please report\n--2894-- it at http://valgrind.org/support/bug_reports.html.\n--2894-- WARNING: unhandled riscv64-linux syscall: 258\n--2894-- You may be able to write your own handler.\n--2894-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2894-- Nevertheless we consider this a bug.  Please report\n--2894-- it at http://valgrind.org/support/bug_reports.html.\n--2894-- WARNING: unhandled riscv64-linux syscall: 258\n--2894-- You may be able to write your own handler.\n--2894-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2894-- Nevertheless we consider this a bug.  Please report\n--2894-- it at http://valgrind.org/support/bug_reports.html.\n--2894-- WARNING: unhandled riscv64-linux syscall: 258\n--2894-- You may be able to write your own handler.\n--2894-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2894-- Nevertheless we consider this a bug.  Please report\n--2894-- it at http://valgrind.org/support/bug_reports.html.\n--2894-- WARNING: unhandled riscv64-linux syscall: 258\n--2894-- You may be able to write your own handler.\n--2894-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2894-- Nevertheless we consider this a bug.  Please report\n--2894-- it at http://valgrind.org/support/bug_reports.html.\n--2894-- WARNING: unhandled riscv64-linux syscall: 258\n--2894-- You may be able to write your own handler.\n--2894-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2894-- Nevertheless we consider this a bug.  Please report\n--2894-- it at http://valgrind.org/support/bug_reports.html.\n--2894-- WARNING: unhandled riscv64-linux syscall: 258\n--2894-- You may be able to write your own handler.\n--2894-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2894-- Nevertheless we consider this a bug.  Please report\n--2894-- it at http://valgrind.org/support/bug_reports.html.\n--2894-- WARNING: unhandled riscv64-linux syscall: 258\n--2894-- You may be able to write your own handler.\n--2894-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2894-- Nevertheless we consider this a bug.  Please report\n--2894-- it at http://valgrind.org/support/bug_reports.html.\n--2894-- WARNING: unhandled riscv64-linux syscall: 258\n--2894-- You may be able to write your own handler.\n--2894-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2894-- Nevertheless we consider this a bug.  Please report\n--2894-- it at http://valgrind.org/support/bug_reports.html.\n--2894-- WARNING: unhandled riscv64-linux syscall: 258\n--2894-- You may be able to write your own handler.\n--2894-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2894-- Nevertheless we consider this a bug.  Please report\n--2894-- 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:
'--2902-- WARNING: unhandled riscv64-linux syscall: 258\n--2902-- You may be able to write your own handler.\n--2902-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2902-- Nevertheless we consider this a bug.  Please report\n--2902-- it at http://valgrind.org/support/bug_reports.html.\n--2902-- WARNING: unhandled riscv64-linux syscall: 258\n--2902-- You may be able to write your own handler.\n--2902-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2902-- Nevertheless we consider this a bug.  Please report\n--2902-- it at http://valgrind.org/support/bug_reports.html.\n--2902-- WARNING: unhandled riscv64-linux syscall: 258\n--2902-- You may be able to write your own handler.\n--2902-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2902-- Nevertheless we consider this a bug.  Please report\n--2902-- it at http://valgrind.org/support/bug_reports.html.\n--2902-- WARNING: unhandled riscv64-linux syscall: 258\n--2902-- You may be able to write your own handler.\n--2902-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2902-- Nevertheless we consider this a bug.  Please report\n--2902-- it at http://valgrind.org/support/bug_reports.html.\n--2902-- WARNING: unhandled riscv64-linux syscall: 258\n--2902-- You may be able to write your own handler.\n--2902-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2902-- Nevertheless we consider this a bug.  Please report\n--2902-- it at http://valgrind.org/support/bug_reports.html.\n--2902-- WARNING: unhandled riscv64-linux syscall: 258\n--2902-- You may be able to write your own handler.\n--2902-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2902-- Nevertheless we consider this a bug.  Please report\n--2902-- it at http://valgrind.org/support/bug_reports.html.\n--2902-- WARNING: unhandled riscv64-linux syscall: 258\n--2902-- You may be able to write your own handler.\n--2902-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2902-- Nevertheless we consider this a bug.  Please report\n--2902-- it at http://valgrind.org/support/bug_reports.html.\n--2902-- WARNING: unhandled riscv64-linux syscall: 258\n--2902-- You may be able to write your own handler.\n--2902-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2902-- Nevertheless we consider this a bug.  Please report\n--2902-- it at http://valgrind.org/support/bug_reports.html.\n--2902-- WARNING: unhandled riscv64-linux syscall: 258\n--2902-- You may be able to write your own handler.\n--2902-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2902-- Nevertheless we consider this a bug.  Please report\n--2902-- it at http://valgrind.org/support/bug_reports.html.\n--2902-- WARNING: unhandled riscv64-linux syscall: 258\n--2902-- You may be able to write your own handler.\n--2902-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2902-- Nevertheless we consider this a bug.  Please report\n--2902-- it at http://valgrind.org/support/bug_reports.html.\n--2902-- WARNING: unhandled riscv64-linux syscall: 258\n--2902-- You may be able to write your own handler.\n--2902-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2902-- Nevertheless we consider this a bug.  Please report\n--2902-- it at http://valgrind.org/support/bug_reports.html.\n--2902-- WARNING: unhandled riscv64-linux syscall: 258\n--2902-- You may be able to write your own handler.\n--2902-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2902-- Nevertheless we consider this a bug.  Please report\n--2902-- it at http://valgrind.org/support/bug_reports.html.\n--2902-- WARNING: unhandled riscv64-linux syscall: 258\n--2902-- You may be able to write your own handler.\n--2902-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2902-- Nevertheless we consider this a bug.  Please report\n--2902-- it at http://valgrind.org/support/bug_reports.html.\n--2902-- WARNING: unhandled riscv64-linux syscall: 258\n--2902-- You may be able to write your own handler.\n--2902-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2902-- Nevertheless we consider this a bug.  Please report\n--2902-- it at http://valgrind.org/support/bug_reports.html.\n--2902-- WARNING: unhandled riscv64-linux syscall: 258\n--2902-- You may be able to write your own handler.\n--2902-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2902-- Nevertheless we consider this a bug.  Please report\n--2902-- it at http://valgrind.org/support/bug_reports.html.\n--2902-- WARNING: unhandled riscv64-linux syscall: 258\n--2902-- You may be able to write your own handler.\n--2902-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2902-- Nevertheless we consider this a bug.  Please report\n--2902-- it at http://valgrind.org/support/bug_reports.html.\n--2902-- WARNING: unhandled riscv64-linux syscall: 258\n--2902-- You may be able to write your own handler.\n--2902-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2902-- Nevertheless we consider this a bug.  Please report\n--2902-- it at http://valgrind.org/support/bug_reports.html.\n--2902-- WARNING: unhandled riscv64-linux syscall: 258\n--2902-- You may be able to write your own handler.\n--2902-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2902-- Nevertheless we consider this a bug.  Please report\n--2902-- 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:
'--2910-- WARNING: unhandled riscv64-linux syscall: 258\n--2910-- You may be able to write your own handler.\n--2910-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2910-- Nevertheless we consider this a bug.  Please report\n--2910-- it at http://valgrind.org/support/bug_reports.html.\n--2910-- WARNING: unhandled riscv64-linux syscall: 258\n--2910-- You may be able to write your own handler.\n--2910-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2910-- Nevertheless we consider this a bug.  Please report\n--2910-- it at http://valgrind.org/support/bug_reports.html.\n--2910-- WARNING: unhandled riscv64-linux syscall: 258\n--2910-- You may be able to write your own handler.\n--2910-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2910-- Nevertheless we consider this a bug.  Please report\n--2910-- it at http://valgrind.org/support/bug_reports.html.\n--2910-- WARNING: unhandled riscv64-linux syscall: 258\n--2910-- You may be able to write your own handler.\n--2910-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2910-- Nevertheless we consider this a bug.  Please report\n--2910-- it at http://valgrind.org/support/bug_reports.html.\n--2910-- WARNING: unhandled riscv64-linux syscall: 258\n--2910-- You may be able to write your own handler.\n--2910-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2910-- Nevertheless we consider this a bug.  Please report\n--2910-- it at http://valgrind.org/support/bug_reports.html.\n--2910-- WARNING: unhandled riscv64-linux syscall: 258\n--2910-- You may be able to write your own handler.\n--2910-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2910-- Nevertheless we consider this a bug.  Please report\n--2910-- it at http://valgrind.org/support/bug_reports.html.\n--2910-- WARNING: unhandled riscv64-linux syscall: 258\n--2910-- You may be able to write your own handler.\n--2910-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2910-- Nevertheless we consider this a bug.  Please report\n--2910-- it at http://valgrind.org/support/bug_reports.html.\n--2910-- WARNING: unhandled riscv64-linux syscall: 258\n--2910-- You may be able to write your own handler.\n--2910-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2910-- Nevertheless we consider this a bug.  Please report\n--2910-- it at http://valgrind.org/support/bug_reports.html.\n--2910-- WARNING: unhandled riscv64-linux syscall: 258\n--2910-- You may be able to write your own handler.\n--2910-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2910-- Nevertheless we consider this a bug.  Please report\n--2910-- it at http://valgrind.org/support/bug_reports.html.\n--2910-- WARNING: unhandled riscv64-linux syscall: 258\n--2910-- You may be able to write your own handler.\n--2910-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2910-- Nevertheless we consider this a bug.  Please report\n--2910-- it at http://valgrind.org/support/bug_reports.html.\n--2910-- WARNING: unhandled riscv64-linux syscall: 258\n--2910-- You may be able to write your own handler.\n--2910-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2910-- Nevertheless we consider this a bug.  Please report\n--2910-- it at http://valgrind.org/support/bug_reports.html.\n--2910-- WARNING: unhandled riscv64-linux syscall: 258\n--2910-- You may be able to write your own handler.\n--2910-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2910-- Nevertheless we consider this a bug.  Please report\n--2910-- it at http://valgrind.org/support/bug_reports.html.\n--2910-- WARNING: unhandled riscv64-linux syscall: 258\n--2910-- You may be able to write your own handler.\n--2910-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2910-- Nevertheless we consider this a bug.  Please report\n--2910-- it at http://valgrind.org/support/bug_reports.html.\n--2910-- WARNING: unhandled riscv64-linux syscall: 258\n--2910-- You may be able to write your own handler.\n--2910-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2910-- Nevertheless we consider this a bug.  Please report\n--2910-- it at http://valgrind.org/support/bug_reports.html.\n--2910-- WARNING: unhandled riscv64-linux syscall: 258\n--2910-- You may be able to write your own handler.\n--2910-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2910-- Nevertheless we consider this a bug.  Please report\n--2910-- it at http://valgrind.org/support/bug_reports.html.\n--2910-- WARNING: unhandled riscv64-linux syscall: 258\n--2910-- You may be able to write your own handler.\n--2910-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2910-- Nevertheless we consider this a bug.  Please report\n--2910-- it at http://valgrind.org/support/bug_reports.html.\n--2910-- WARNING: unhandled riscv64-linux syscall: 258\n--2910-- You may be able to write your own handler.\n--2910-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2910-- Nevertheless we consider this a bug.  Please report\n--2910-- it at http://valgrind.org/support/bug_reports.html.\n--2910-- WARNING: unhandled riscv64-linux syscall: 258\n--2910-- You may be able to write your own handler.\n--2910-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2910-- Nevertheless we consider this a bug.  Please report\n--2910-- 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:
'--2918-- WARNING: unhandled riscv64-linux syscall: 258\n--2918-- You may be able to write your own handler.\n--2918-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2918-- Nevertheless we consider this a bug.  Please report\n--2918-- it at http://valgrind.org/support/bug_reports.html.\n--2918-- WARNING: unhandled riscv64-linux syscall: 258\n--2918-- You may be able to write your own handler.\n--2918-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2918-- Nevertheless we consider this a bug.  Please report\n--2918-- it at http://valgrind.org/support/bug_reports.html.\n--2918-- WARNING: unhandled riscv64-linux syscall: 258\n--2918-- You may be able to write your own handler.\n--2918-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2918-- Nevertheless we consider this a bug.  Please report\n--2918-- it at http://valgrind.org/support/bug_reports.html.\n--2918-- WARNING: unhandled riscv64-linux syscall: 258\n--2918-- You may be able to write your own handler.\n--2918-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2918-- Nevertheless we consider this a bug.  Please report\n--2918-- it at http://valgrind.org/support/bug_reports.html.\n--2918-- WARNING: unhandled riscv64-linux syscall: 258\n--2918-- You may be able to write your own handler.\n--2918-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2918-- Nevertheless we consider this a bug.  Please report\n--2918-- it at http://valgrind.org/support/bug_reports.html.\n--2918-- WARNING: unhandled riscv64-linux syscall: 258\n--2918-- You may be able to write your own handler.\n--2918-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2918-- Nevertheless we consider this a bug.  Please report\n--2918-- it at http://valgrind.org/support/bug_reports.html.\n--2918-- WARNING: unhandled riscv64-linux syscall: 258\n--2918-- You may be able to write your own handler.\n--2918-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2918-- Nevertheless we consider this a bug.  Please report\n--2918-- it at http://valgrind.org/support/bug_reports.html.\n--2918-- WARNING: unhandled riscv64-linux syscall: 258\n--2918-- You may be able to write your own handler.\n--2918-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2918-- Nevertheless we consider this a bug.  Please report\n--2918-- it at http://valgrind.org/support/bug_reports.html.\n--2918-- WARNING: unhandled riscv64-linux syscall: 258\n--2918-- You may be able to write your own handler.\n--2918-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2918-- Nevertheless we consider this a bug.  Please report\n--2918-- it at http://valgrind.org/support/bug_reports.html.\n--2918-- WARNING: unhandled riscv64-linux syscall: 258\n--2918-- You may be able to write your own handler.\n--2918-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2918-- Nevertheless we consider this a bug.  Please report\n--2918-- it at http://valgrind.org/support/bug_reports.html.\n--2918-- WARNING: unhandled riscv64-linux syscall: 258\n--2918-- You may be able to write your own handler.\n--2918-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2918-- Nevertheless we consider this a bug.  Please report\n--2918-- it at http://valgrind.org/support/bug_reports.html.\n--2918-- WARNING: unhandled riscv64-linux syscall: 258\n--2918-- You may be able to write your own handler.\n--2918-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2918-- Nevertheless we consider this a bug.  Please report\n--2918-- it at http://valgrind.org/support/bug_reports.html.\n--2918-- WARNING: unhandled riscv64-linux syscall: 258\n--2918-- You may be able to write your own handler.\n--2918-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2918-- Nevertheless we consider this a bug.  Please report\n--2918-- it at http://valgrind.org/support/bug_reports.html.\n--2918-- WARNING: unhandled riscv64-linux syscall: 258\n--2918-- You may be able to write your own handler.\n--2918-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2918-- Nevertheless we consider this a bug.  Please report\n--2918-- it at http://valgrind.org/support/bug_reports.html.\n--2918-- WARNING: unhandled riscv64-linux syscall: 258\n--2918-- You may be able to write your own handler.\n--2918-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2918-- Nevertheless we consider this a bug.  Please report\n--2918-- it at http://valgrind.org/support/bug_reports.html.\n--2918-- WARNING: unhandled riscv64-linux syscall: 258\n--2918-- You may be able to write your own handler.\n--2918-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2918-- Nevertheless we consider this a bug.  Please report\n--2918-- it at http://valgrind.org/support/bug_reports.html.\n--2918-- WARNING: unhandled riscv64-linux syscall: 258\n--2918-- You may be able to write your own handler.\n--2918-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2918-- Nevertheless we consider this a bug.  Please report\n--2918-- it at http://valgrind.org/support/bug_reports.html.\n--2918-- WARNING: unhandled riscv64-linux syscall: 258\n--2918-- You may be able to write your own handler.\n--2918-- Read the file README_MISSING_SYSCALL_OR_IOCTL.\n--2918-- Nevertheless we consider this a bug.  Please report\n--2918-- 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

























































204: passed	'e?e&&'
205: passed	'e?e&'
206: passed	'e?e&&&&&&&&&&&&&&&&&&&&&'
207: passed	'e?e&&&&&&&&&&a&&&&&&&&&&&'
Finished:
Failed! - Failed: 197, Passed: 10, Skipped: 0, Total: 207
make: *** [Makefile:80: test-memory] Error 1
==> ERROR: A failure occurred in check().
    Aborting...
==> ERROR: Build failed, check /var/lib/archbuild/extra-riscv64/felix-9/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,655 bytes  43,434.00 bytes/sec
total size is 1,099,590  speedup is 50.63