Buy commercial curl support from WolfSSL. We help you work
out your issues, debug your libcurl applications, use the API, port to new
platforms, add new features and more. With a team lead by the curl founder
himself.
Re: Test 1452 failing on ElectroBSD when executed with valgrind
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Fabian Keil via curl-library <curl-library_at_lists.haxx.se>
Date: Thu, 29 Sep 2022 11:55:53 +0200
Daniel Stenberg <daniel_at_haxx.se> wrote on 2022-09-29 at 10:41:48:
> On Thu, 29 Sep 2022, Fabian Keil via curl-library wrote:
>
> > So it seems to me that the telnet server isn't at fault here.
>
> It's really hard to see or guess where the error is by just these
> observations. I would presume you need to dig deeper to find out. You can run
> the single test with gdb like this: './runtests.pl -g 1452'
Without valgrind, though.
Using gdb I get a different error:
fk_at_t520 ~/git/curl/tests $./runtests.pl -g 1452
[...]
Reading symbols from ../src/curl...
Argument list to give program being debugged when it is started is "--include --trace-ascii log/trace1452 --trace-time telnet://127.0.0.1:32151 --upload-file - <log/stdin-for-1452".
(gdb) r
Starting program: /home/fk/git/curl/src/curl --include --trace-ascii log/trace1452 --trace-time telnet://127.0.0.1:32151 --upload-file - <log/stdin-for-1452
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 29 0 20 0 9 18231 8204 --:--:-- --:--:-- --:--:-- 29000
test1452[Inferior 1 (process 26707) exited normally]
(gdb)
quit
1452: stdout FAILED:
--- log/check-expected 2022-09-29 11:47:11.956329000 +0200
+++ log/check-generated 2022-09-29 11:47:11.956121000 +0200
_at__at_ -1 +0,0 _at__at_
-test1452
- abort tests
TESTDONE: 1 tests were considered during 6 seconds.
TESTDONE: 0 tests out of 1 reported OK: 0%
TESTFAIL: These test cases failed: 1452
> Another data point is that our CI jobs run on two versions of FreeBSD (12.3
> and 13.1) and they run test 1452 successfully.
My impression after looking at .cirrus.yml is that they
don't use valgrind, though. Unfortunately cirrus-ci.com
doesn't seem to properly render on my system so I could
not confirm this.
Without valgrind the test seems to be reliable on ElectroBSD as well.
Would it be possible to (temporarily) push the attached patch
to enable valgrind?
If not I could also try to setup a FreeBSD system myself in
the next days.
Fabian
Received on 2022-09-29
Date: Thu, 29 Sep 2022 11:55:53 +0200
Daniel Stenberg <daniel_at_haxx.se> wrote on 2022-09-29 at 10:41:48:
> On Thu, 29 Sep 2022, Fabian Keil via curl-library wrote:
>
> > So it seems to me that the telnet server isn't at fault here.
>
> It's really hard to see or guess where the error is by just these
> observations. I would presume you need to dig deeper to find out. You can run
> the single test with gdb like this: './runtests.pl -g 1452'
Without valgrind, though.
Using gdb I get a different error:
fk_at_t520 ~/git/curl/tests $./runtests.pl -g 1452
[...]
Reading symbols from ../src/curl...
Argument list to give program being debugged when it is started is "--include --trace-ascii log/trace1452 --trace-time telnet://127.0.0.1:32151 --upload-file - <log/stdin-for-1452".
(gdb) r
Starting program: /home/fk/git/curl/src/curl --include --trace-ascii log/trace1452 --trace-time telnet://127.0.0.1:32151 --upload-file - <log/stdin-for-1452
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 29 0 20 0 9 18231 8204 --:--:-- --:--:-- --:--:-- 29000
test1452[Inferior 1 (process 26707) exited normally]
(gdb)
quit
1452: stdout FAILED:
--- log/check-expected 2022-09-29 11:47:11.956329000 +0200
+++ log/check-generated 2022-09-29 11:47:11.956121000 +0200
_at__at_ -1 +0,0 _at__at_
-test1452
- abort tests
TESTDONE: 1 tests were considered during 6 seconds.
TESTDONE: 0 tests out of 1 reported OK: 0%
TESTFAIL: These test cases failed: 1452
> Another data point is that our CI jobs run on two versions of FreeBSD (12.3
> and 13.1) and they run test 1452 successfully.
My impression after looking at .cirrus.yml is that they
don't use valgrind, though. Unfortunately cirrus-ci.com
doesn't seem to properly render on my system so I could
not confirm this.
Without valgrind the test seems to be reliable on ElectroBSD as well.
Would it be possible to (temporarily) push the attached patch
to enable valgrind?
If not I could also try to setup a FreeBSD system myself in
the next days.
Fabian
-- Unsubscribe: https://lists.haxx.se/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.html
- text/x-patch attachment: 0001-.cirrus.yml-install-valgrind-devel-on-FreeBSD.patch
- application/pgp-signature attachment: OpenPGP digital signature