On Fri, 24 May 2024, Jeremy Drake wrote:
> On Fri, 24 May 2024, Jeremy Drake wrote:
>
> > Looking at !address, it seems Windows put the PEB, TEBs, and stacks in the
> > area where the cygheap should be. Way to go, ASLR :P
>
> I think the fix for this would be to add -Wl,--disable-high-entropy-va
On Fri, 24 May 2024, Jeremy Drake wrote:
> Looking at !address, it seems Windows put the PEB, TEBs, and stacks in the
> area where the cygheap should be. Way to go, ASLR :P
I think the fix for this would be to add -Wl,--disable-high-entropy-va to
ldh_LDFLAGS, as was done for strace and cygcheck
On Fri, 24 May 2024, Jeremy Drake wrote:
> On Fri, 24 May 2024, Jeremy Drake wrote:
>
> > Windbg reports that ldh.exe is already being debugged. I was able to do a
> > "non-invasive" attach to ldh.exe in windbg, but it doesn't seem to be able
> > to deal with the split debug symbols (gnulink?).
On 5/24/2024 3:26 PM, Jeremy Drake via Cygwin wrote:
On Sat, 25 May 2024, Takashi Yano wrote:
On Fri, 24 May 2024 14:46:40 -0700 (PDT)
Jeremy Drake wrote:
Thanks for the report. However, I cannot reproduce the issue.
If it always hangs in GetConsoleProcessList (), I doubt it is not a cygwin
bu
On Fri, 24 May 2024, Jeremy Drake wrote:
> Windbg reports that ldh.exe is already being debugged. I was able to do a
> "non-invasive" attach to ldh.exe in windbg, but it doesn't seem to be able
> to deal with the split debug symbols (gnulink?). I don't know if gdb can
> do a non-invasive attach
On Sat, 25 May 2024, Takashi Yano wrote:
> On Fri, 24 May 2024 14:46:40 -0700 (PDT)
> Jeremy Drake wrote:
> > > Thanks for the report. However, I cannot reproduce the issue.
> > > If it always hangs in GetConsoleProcessList (), I doubt it is not a cygwin
> > > bug but a windows bug.
> > >
> > > By
On 5/24/2024 3:17 PM, Takashi Yano via Cygwin wrote:
On Fri, 24 May 2024 14:46:40 -0700 (PDT)
Jeremy Drake wrote:
Thanks for the report. However, I cannot reproduce the issue.
If it always hangs in GetConsoleProcessList (), I doubt it is not a cygwin
bug but a windows bug.
By any chance, is the
On Fri, 24 May 2024 14:46:40 -0700 (PDT)
Jeremy Drake wrote:
> > Thanks for the report. However, I cannot reproduce the issue.
> > If it always hangs in GetConsoleProcessList (), I doubt it is not a cygwin
> > bug but a windows bug.
> >
> > By any chance, is the number of processes that attach to t
On Sat, 25 May 2024, Takashi Yano wrote:
> Thanks for the report. However, I cannot reproduce the issue.
> If it always hangs in GetConsoleProcessList (), I doubt it is not a cygwin
> bug but a windows bug.
>
> By any chance, is the number of processes that attach to the same pty more
> than 32768
On Sat, 25 May 2024 04:54:24 +0900
Takashi Yano wrote:
> By any chance, is the number of processes that attach to the same pty more
> than 32768 in your environment?
s/32768/8192/
--
Takashi Yano
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.co
On Fri, 24 May 2024 11:50:35 -0700 (PDT)
Jeremy Drake wrote:
> Seen on msys2, but doesn't seem specific to it.
>
> Frequently, when running ldd in a loop, it will hang. I managed to get a
> backtrace from gdb with symbols:
>
> (gdb) bt
> #0 0x7ffecea0fa34 in ntdll!ZwDeviceIoControlFile ()
>
Seen on msys2, but doesn't seem specific to it.
Frequently, when running ldd in a loop, it will hang. I managed to get a
backtrace from gdb with symbols:
(gdb) bt
#0 0x7ffecea0fa34 in ntdll!ZwDeviceIoControlFile ()
from /c/Windows/SYSTEM32/ntdll.dll
#1 0x7ffecbead7a9 in KERNELBASE!G
12 matches
Mail list logo
