On Fri, 23 May 2025, Yuyi Wang wrote:
> On Wed, 22 May 2025, Jeremy Drake wrote:
> > Ultimately, playing whack-a-mole in a 64-bit address space hoping that the
> > DLL will load in the same place as the parent is an exercise in futility,
> > especially in only 6 attempts.
>
> Outside cygwin, rustc
On Wed, 22 May 2025, Jeremy Drake wrote:
> Ultimately, playing whack-a-mole in a 64-bit address space hoping that the
> DLL will load in the same place as the parent is an exercise in futility,
> especially in only 6 attempts.
Outside cygwin, rustc also try 5 times to load the proc macro DLL, so t
On Thu, May 22, 2025 at 1:58 PM lostbits via Cygwin wrote:
>
> Win 11-64
>
> Are the version numbers for gcc correct? You have listed the latest gcc
> (version 15.1) when I search packages but:
>
> > gcc --version
>
> shows version 12.4.0. My setup-x86_64.exe version is 2.933.
>
> The version show
On 22/05/2025 19:55, Brian Inglis via Cygwin wrote:
On 2025-05-22 10:07, ASSI via Cygwin wrote:
Gary Liddle via Cygwin writes:
Thanks for the link, but all the .dbg programmes segfault in:-
ie bash.exe.dbg
mainCRTStartup () at /usr/src/debug/cygwin-3.4.10-1/winsup/
cygwin/crt0.c:16
fo
On 2025-05-22 12:37, Arthur Schwarz via Cygwin wrote:
I can't figure this one out.
> clear;g++ -flinker-output=dyn -o slip.dll *.o
generates:
/usr/lib/gcc/x86_64-pc-cygwin/12/../../../../x86_64-pc-cygwin/bin/ld: /usr/lib/
gcc/x86_64-pc-cygwin/12/../../../../lib/libcygwin.a(libcmain.o): in fu
Operator error. Looked at download tool (setup-x86-64.exe) and found
that the listing shows the current version and extra steps are needed to
show updates. The (really old) setup showed the update version and
provided a choice.
Sorry for the bother.
On 5/22/2025 10:58 AM, lostbits wrote:
Win
On 02/05/2025 12:16, Takashi Yano via Cygwin wrote:
On Wed, 30 Apr 2025 21:30:16 +
Christian Lupien wrote:
On a recent system install, I tried to install cygserver by executing
cygserver-config
but it failed saying that cygserver was already running.
I have done that same install for many
On 2025-05-22 10:07, ASSI via Cygwin wrote:
Gary Liddle via Cygwin writes:
Thanks for the link, but all the .dbg programmes segfault in:-
ie bash.exe.dbg
mainCRTStartup () at
/usr/src/debug/cygwin-3.4.10-1/winsup/cygwin/crt0.c:16
for all versions (which might be a clue?).
Did
I can't figure this one out.
> clear;g++ -flinker-output=dyn -o slip.dll *.o
generates:
/usr/lib/gcc/x86_64-pc-cygwin/12/../../../../x86_64-pc-cygwin/bin/ld:
/usr/lib/gcc/x86_64-pc-cygwin/12/../../../../lib/libcygwin.a(libcmain.o):
in function `main':
/usr/src/debug/cygwin-3.6.1-1/winsup/cygw
Win 11-64
Are the version numbers for gcc correct? You have listed the latest gcc
(version 15.1) when I search packages but:
> gcc --version
shows version 12.4.0. My setup-x86_64.exe version is 2.933.
The version shown in the local update pop-up is 12.4.0-3. How do I get
later versions?
t
On Wed, 21 May 2025, Jeremy Drake via Cygwin wrote:
> On Wed, 21 May 2025, Jeremy Drake via Cygwin wrote:
>
> > the child to not be very fruitful, but maybe there's some debugging to be
> > done there
>
> Well, found the bug that results in a 0 size. size is a DWORD, but
> mb.RegionSize is 0x2000
Gary Liddle via Cygwin writes:
> Thanks for the link, but all the .dbg programmes segfault in:-
> ie bash.exe.dbg
> mainCRTStartup () at
> /usr/src/debug/cygwin-3.4.10-1/winsup/cygwin/crt0.c:16
> for all versions (which might be a clue?).
Did you actually close all Cygwin programs an
> On 22 May 2025, at 14:30, Jon Turney wrote:
>
> On 22/05/2025 14:15, Gary Liddle via Cygwin wrote:
>> Yesterday I updated Cygwin using setup-x86_64 to the latest non test
>> release, and bash —login would no longer start.
>> It turns out bash won’t start for me when a .profile runs a sub-co
On 22/05/2025 14:15, Gary Liddle via Cygwin wrote:
Yesterday I updated Cygwin using setup-x86_64 to the latest non test release,
and bash —login would no longer start.
It turns out bash won’t start for me when a .profile runs a sub-command.
This is highlighted by:-
gdb bash
d
Yesterday I updated Cygwin using setup-x86_64 to the latest non test release,
and bash —login would no longer start.
It turns out bash won’t start for me when a .profile runs a sub-command.
This is highlighted by:-
gdb bash
dll cygwin1.dll
b timegm
run
b
15 matches
Mail list logo
