Zhaoming Luo, le mer. 04 déc. 2024 11:04:02 +0800, a ecrit:
> On 12/4/24 5:56 AM, Samuel Thibault wrote:
> > Zhaoming Luo, le mar. 03 déc. 2024 08:53:44 +0800, a ecrit:
> > > On 12/3/24 6:48 AM, Samuel Thibault wrote:
> > > > Zhaoming Luo, le mar. 03 déc. 2024 06:42:07 +0800, a ecrit:
> > > > > On
On Wed, Dec 4, 2024 at 12:11 AM Diego Nieto Cid wrote:
> 52<--47(pid1044)->io_write_request ("Hello World!\n" -1) = 0 15
On Wed, Dec 4, 2024 at 4:50 AM Diego Nieto Cid wrote:
> I traced it to the function `io_write` from `libhurduser.so.3` which
> is returning 1.
On Wed, Dec 4, 2024 at 6:09
Here is some stacktrace.
--->8>8
(gdb) frame
#0 _hurd_fd_write (fd=fd@entry=0x1012dde10,
buf=buf@entry=0x2dd0, nbytes=nbytes@entry=0x10103da78,
offset=offset@entry=-1)
at ./hurd/fd-write.c:39
39 *nbytes = wrote;
(gdb) bt
#0 _hurd_fd_write (fd=fd@entry=0x1012dde10
On 12/4/24 5:56 AM, Samuel Thibault wrote:
Zhaoming Luo, le mar. 03 déc. 2024 08:53:44 +0800, a ecrit:
On 12/3/24 6:48 AM, Samuel Thibault wrote:
Zhaoming Luo, le mar. 03 déc. 2024 06:42:07 +0800, a ecrit:
On 12/2/24 10:12 AM, Samuel Thibault wrote:
Please factorize these with the linux port,
El mar, 3 dic 2024 a las 22:50, Diego Nieto Cid () escribió:
>
> Also, it's quite difficult without the source code. I've downloaded
> glibc-source and extracted the tar.xz. How do I instruct gdb to use
> those files?
>
GDB's directory command helped in this front. I'll continue debugging :-)
El mar, 3 dic 2024 a las 18:33, Samuel Thibault
() escribió:
>
> And nothing else after that? fclose() would need to be run inside gdb to
> make sure where exactly it returns an error. Possibly it's simply
> _IO_do_flush that doesn't work for /dev/zero, but this doesn't show up
> in the RPCs above.
jbra...@dismail.de, le dim. 01 déc. 2024 21:39:20 -0500, a ecrit:
> +# Develop the Debian way
> +
> +You can develop the GNU/Hurd via Debian GNU/Hurd. The [Debian
> +developer's corner](https://salsa.debian.org/hurd-team/hurd.git) has
> +lots of Debian specific resources.
This is not what you wan
Hello,
jbra...@dismail.de, le dim. 01 déc. 2024 21:39:19 -0500, a ecrit:
> +[[!meta title="glibc error reporting"]]
> +
> +When reporting errors in the Hurd part of glibc, please use these
> +functions. They can be found in `$glibc-SRC/hurd/hurd/fd.h`.
> +
> + `__hurd_fail(error_t err)`
> +
>
Samuel Thibault, le mar. 03 déc. 2024 00:43:28 +0100, a ecrit:
> I also ran a script that checks for packages that fail on 64bit but
> doesn't on 32bit. Quite a few of them are related to dumb issues (symbol
> list and such), but a few of them are worth noticing:
>
> https://buildd.debian.org/libt
El mar, 3 dic 2024 a las 18:55, Samuel Thibault
() escribió:
>
> Maybe check how your /etc/adjtime is configured (see man hwclock),
> against how virtualbox considers the RTC time should be set.
>
/etc/adjtime says UTC and VirtualBox uses Local Time (Windows host).
But there's a switch to flip, so
Zhaoming Luo, le mar. 03 déc. 2024 08:53:44 +0800, a ecrit:
> On 12/3/24 6:48 AM, Samuel Thibault wrote:
> > Zhaoming Luo, le mar. 03 déc. 2024 06:42:07 +0800, a ecrit:
> > > On 12/2/24 10:12 AM, Samuel Thibault wrote:
> > > > Please factorize these with the linux port, by putting them into a
> > >
Diego Nieto Cid, le lun. 02 déc. 2024 23:35:24 -0300, a ecrit:
> Nevermind, I had to also set the date with `date -s ""`. It seems
> only changing the timezone is not enough as the time is not fixed.
Maybe check how your /etc/adjtime is configured (see man hwclock),
against how virtualbox consider
Diego Nieto Cid, le mar. 03 déc. 2024 18:32:07 -0300, a ecrit:
> BTW, the /dev/zero holds the following translator entry:
>
> $ showtrans /dev/zero
> /bin/nullauth -- /hurd/storeio -Tzero
Yes, that's expected.
> I'm having a hard time finding the code handling the "-Tzero"
> parameter.
Diego Nieto Cid, le mar. 03 déc. 2024 18:11:17 -0300, a ecrit:
> El mar, 3 dic 2024 a las 17:15, Samuel Thibault
> () escribió:
> >
> > Oh, that's odd indeed. Perhaps run it through rpctrace to see what
> > happens behind.
> >
>
> I attached the rpctrace log. I'm not sure what to look for but the
BTW, the /dev/zero holds the following translator entry:
$ showtrans /dev/zero
/bin/nullauth -- /hurd/storeio -Tzero
I'm having a hard time finding the code handling the "-Tzero"
parameter. But, from a quick look at the arguments of storeio, it is
readonly by default. Maybe that has somet
El mar, 3 dic 2024 a las 17:15, Samuel Thibault
() escribió:
>
> Oh, that's odd indeed. Perhaps run it through rpctrace to see what
> happens behind.
>
I attached the rpctrace log. I'm not sure what to look for but the
following lines seem relevant:
7<--38(pid1044)->dir_lookup ("dev/zero" 655
Diego Nieto Cid, le mar. 03 déc. 2024 17:11:58 -0300, a ecrit:
> El mar, 3 dic 2024 a las 12:47, Samuel Thibault
> () escribió:
> >
> > Yes, the current behavior is really odd, I don't see why zstd would try
> > to remove /dev/zero...
> >
>
> I managed to craft a small reproducer by doing the foll
El mar, 3 dic 2024 a las 12:47, Samuel Thibault
() escribió:
>
> Yes, the current behavior is really odd, I don't see why zstd would try
> to remove /dev/zero...
>
I managed to craft a small reproducer by doing the following steps:
1. open /dev/zero
2. write something into it
3. close it
H
Diego Nieto Cid, le mar. 03 déc. 2024 12:42:47 -0300, a ecrit:
> $ dd if=/dev/zero of=tmp bs=1k count=64 && ./programs/zstd tmp -f
> -o /dev/zero
> 64+0 records in
> 64+0 records out
> 65536 bytes (66 kB, 64 KiB) copied, 0 s, Infinity B/s
> tmp : 0.04% ( 64.
El mar, 3 dic 2024 a las 11:54, Samuel Thibault
() escribió:
>
> Diego Nieto Cid, le mar. 03 déc. 2024 11:47:08 -0300, a ecrit:
> > El mar, 3 dic 2024 a las 11:26, Samuel Thibault
> > () escribió:
> >
> > INTOVOID="/dev/null"
> > case "$UNAME" in
> > GNU) DEVDEVICE="/dev/random" ;;
>
Diego Nieto Cid, le mar. 03 déc. 2024 11:47:08 -0300, a ecrit:
> El mar, 3 dic 2024 a las 11:26, Samuel Thibault
> () escribió:
> >
> > Diego Nieto Cid, le mar. 03 déc. 2024 11:10:57 -0300, a ecrit:
> > > which produce the following piece of logs:
> > >
> > > $ cat tests/tmplog
> > > + '['
El mar, 3 dic 2024 a las 11:26, Samuel Thibault
() escribió:
>
> Diego Nieto Cid, le mar. 03 déc. 2024 11:10:57 -0300, a ecrit:
> > which produce the following piece of logs:
> >
> > $ cat tests/tmplog
> > + '[' -z '' ']'
> > + ../programs/zstd tmp -f -o /dev/random
> > zstd: /dev/r
Diego Nieto Cid, le mar. 03 déc. 2024 11:10:57 -0300, a ecrit:
> which produce the following piece of logs:
>
> $ cat tests/tmplog
> + '[' -z '' ']'
> + ../programs/zstd tmp -f -o /dev/random
> zstd: /dev/random: Permission denied
Eh? Why writing to random? What sense is this supp
Hello,
I was looking at the buildd failures of libzstd to try to fix it. It
compiles fine but one of the tests (so far...) fails to run
properly[1]:
test : should quietly not remove non-regular file
make[2]: *** [Makefile:352: test-zstd] Error 1
make[2]: Leaving directory '/<>/tests'
24 matches
Mail list logo
