User Activity

  • Posted a comment on ticket #52 on bash debugger

    Sure, we'll go with our first 1.0.0 release. Probably will do over the upcoming weekend. Just to be sure that I understand and we are talking abou the same. It looks like you created a not yet published "4.4-0.95" tag for the test attachment but there is already a published release-4.4-1.0.0 tag (https://sourceforge.net/p/bashdb/code/ref/master/tags/). So when you are going to release something new over the upcoming weekend please make sure to release "4.4-1.0.1" for example. :)

  • Posted a comment on ticket #52 on bash debugger

    Looks good aside test-file-with-spaces: make check-TESTS [207/95825] make[3]: Entering directory '/var/tmp/portage/app-shells/bashdb-4.4.1.0.0/work/bashdb-4.4-0.95/test/integration' make[4]: Entering directory '/var/tmp/portage/app-shells/bashdb-4.4.1.0.0/work/bashdb-4.4-0.95/test/integration' PASS: test-bug-set-e SKIP: test-file-with-spaces PASS: test-bug-step-subshell PASS: test-complete PASS: test-export PASS: test-info-args SKIP: test-sig PASS: test-delete PASS: test-debug PASS: test-setshow...

  • Posted a comment on ticket #52 on bash debugger

    There's more than just one file missing in bashdb-4.4.1.0.0 release tarball: missing-files/ ├── data │ ├── file with spaces.cmd │ ├── file with spaces.right │ ├── sig-44.cmd │ └── sig-bug.cmd └── example ├── bug-set-e.sh ├── dir with spaces │ └── bug.sh ├── file with spaces.sh └── sig-bug.sh Not sure if the sig-* files are required but with these files added we get full test coverage in Gentoo: PASS: test-bug-step-subshell PASS: test-complete PASS: test-file-with-spaces PASS: test-export PASS: test-info-args...

  • Modified ticket #848 on Enigmail

    test failure: errorHandling.jsm: MISSING PROPERTY: missingMdcError

  • Created ticket #848 on Enigmail

    test failure: errorHandling.jsm: MISSING PROPERTY: missingMdcError

  • Posted a comment on ticket #3 on dd_rescue

    Well, I am seeing this on ext3, ext4 and XFS. $ hexdump -C TEST 00000000 2d 6e 20 77 68 61 74 20 64 6f 20 79 61 20 77 61 |-n what do ya wa| 00000010 6e 74 20 66 6f 72 20 6e 6f 74 68 69 6e 67 3f 0a |nt for nothing?.| 00000020 This helped me to find the issue: It only happens when /bin/sh is linked to /bin/dash. Tests are passing with /bin/bash. But this is Gentoo specific (sorry about that! I should have noticed...), we carry https://gitweb.gentoo.org/repo/gentoo.git/tree/app-shells/dash/files/dash-0.5.9.1-dumb-echo.patch...

  • Posted a comment on ticket #3 on dd_rescue

    I hope that I have everything included. Still reproducible. But you need glibc-2.25... make MACH=x86_64 OS=Linux HAVE_SSE42=1 HAVE_AVX2=0 HAVE_AES=1 check

  • Posted a comment on ticket #3 on dd_rescue

    Don't read too much into Interesting, it is passing tests on [...] I was on a different architecture. I.e. it passing on Gentoo x86 stable. I upgraded to same gcc and binutils version and it is still passing. I am out of ideas at the moment (maybe caused by different CPU features). If you have any idea what I can test please share.

View All

Personal Data

Username:
whissi
Joined:
2003-07-06 15:37:36
Location:
Germany / CET
Gender:
Male

Projects

  • No projects to display.