On 2025-02-07 23:51, Samuel Thibault wrote:
Yuqian Yang, le ven. 07 févr. 2025 23:27:01 +0800, a ecrit:
I know this is due to the way of our kernel to handle file and memory.
Do we have a good way to fix this,
Not a trivial way. It'd need adding names to the kernel map entries,
and
setting t
On Sat, Feb 08, 2025 at 08:55:31AM +0800, Zhaoming Luo wrote:
> On Fri, Feb 07, 2025 at 01:57:01PM +0100, Samuel Thibault wrote:
> > Zhaoming Luo, le ven. 07 févr. 2025 18:44:50 +0800, a ecrit:
> > > This is V2 of figuring out the issue. V1 is abandoned due to my mistake,
> > > but this time I can
On Fri, Feb 07, 2025 at 03:00:08PM +0300, Sergey Bugaev wrote:
> On Fri, Feb 7, 2025 at 2:36 PM Zhaoming Luo wrote:
> > Hi,
>
> Hi,
>
> > Thread 4 hit Breakpoint 1, __GI___select (nfds=0, readfds=0x103cc20,
> > writefds=0x103cc40, exceptfds=0x103cc60, timeout=0x103cc84)
> > at ../sysdeps/ma
On Fri, Feb 07, 2025 at 01:57:01PM +0100, Samuel Thibault wrote:
> Zhaoming Luo, le ven. 07 févr. 2025 18:44:50 +0800, a ecrit:
> > This is V2 of figuring out the issue. V1 is abandoned due to my mistake,
> > but this time I can confirm the source of issue. This time I ran
> > rpctrace directly on
On Fri, Feb 7, 2025 at 6:51 PM Samuel Thibault wrote:
> Yuqian Yang, le ven. 07 févr. 2025 23:27:01 +0800, a ecrit:
> > I know this is due to the way of our kernel to handle file and memory.
> > Do we have a good way to fix this,
>
> Not a trivial way. It'd need adding names to the kernel map entr
Yuqian Yang, le ven. 07 févr. 2025 23:27:01 +0800, a ecrit:
> I know this is due to the way of our kernel to handle file and memory.
> Do we have a good way to fix this,
Not a trivial way. It'd need adding names to the kernel map entries, and
setting them from mmap() and such functions that map fi
When I fixed abseil[1] for Hurd, I disabled its debugging feature
of finding the symbol of current functions or any other symbols.[2]
It does not work on Hurd and its unit tests failed. It can be safely
disabled and does not affect other functions of lib just like
platforms that do not support it,
Zhaoming Luo, le ven. 07 févr. 2025 18:44:50 +0800, a ecrit:
> This is V2 of figuring out the issue. V1 is abandoned due to my mistake,
> but this time I can confirm the source of issue. This time I ran
> rpctrace directly on vim, and used two printfs to locate the isatty().
>
> ```
> printf ("Sta
On Fri, Feb 7, 2025 at 2:36 PM Zhaoming Luo wrote:
> Hi,
Hi,
> Thread 4 hit Breakpoint 1, __GI___select (nfds=0, readfds=0x103cc20,
> writefds=0x103cc40, exceptfds=0x103cc60, timeout=0x103cc84)
> at ../sysdeps/mach/hurd/select.c:31
> ```
>
> When I continue, it hangs at mach_msg[0]:
>
> gdb
Hi,
When I'm checking curl test 546. I found that it went into a situation
that:
```
Thread 4 hit Breakpoint 1, __GI___select (nfds=0, readfds=0x103cc20,
writefds=0x103cc40, exceptfds=0x103cc60, timeout=0x103cc84)
at ../sysdeps/mach/hurd/select.c:31
```
When I continue, it hangs at mach_msg
Hi,
This is V2 of figuring out the issue. V1 is abandoned due to my mistake,
but this time I can confirm the source of issue. This time I ran
rpctrace directly on vim, and used two printfs to locate the isatty().
```
printf ("Start isatty!\n");
if (mch_isatty(in))
channel->ch_to_be_closed |=
11 matches
Mail list logo
