On 2021-12-08 11:49, Achim Gratz wrote:
Achim Gratz writes:
The root cause of this mystery is almost surely in binutils, this area
was touched when they moved the default base address past the 4GiB
boundary (obviously that's a 64bit only change and it only affects PE
targets). I still have to
Achim Gratz writes:
> The root cause of this mystery is almost surely in binutils, this area
> was touched when they moved the default base address past the 4GiB
> boundary (obviously that's a 64bit only change and it only affects PE
> targets). I still have to figure out if I need to pull in a
Brian Inglis writes:
> The problem with Cygwin weak symbols is apparently that ld expects
> there to be a runtime dynamic loader to resolve NULL weak dynamic
> library references, but unlike ELF neither Cygwin nor Windows does so,
> and PE may not retain the information to do so, or this project
Ken Brown via Cygwin-apps writes:
> You're right, I was wrong. Here's the gnulib test program for anyone
> else who wants to look at this:
>
> #include
> #pragma weak fputs
> int main ()
> {
> return (fputs == NULL);
> }
>
> As you said, this used to return 1, but now it returns 0 on 64-bit.
On 2021-11-28 09:23, Achim Gratz wrote:
Achim Gratz writes:
I'd rather know why the bleeping heck the test suddenly succeeds when it
clearly doesn't actually work. In other words, I think the linker
should complain, but since it obviously did that before Cygwin 3.2.0 and
not after, something
On 11/28/2021 11:33 AM, Achim Gratz wrote:
Ken Brown via Cygwin-apps writes:
It's gnulib that changed, not Cygwin or gcc/binutils. This is
actually an old issue:
https://cygwin.com/pipermail/cygwin/2010-April/186342.html
I've built the exact same package (man-db) this Febrary without
Ken Brown via Cygwin-apps writes:
> It's gnulib that changed, not Cygwin or gcc/binutils. This is
> actually an old issue:
>
> https://cygwin.com/pipermail/cygwin/2010-April/186342.html
I've built the exact same package (man-db) this Febrary without that
problem and now again with that problem
Achim Gratz writes:
> I'd rather know why the bleeping heck the test suddenly succeeds when it
> clearly doesn't actually work. In other words, I think the linker
> should complain, but since it obviously did that before Cygwin 3.2.0 and
> not after, something must have changed somewhere that
On 11/28/2021 10:42 AM, Achim Gratz wrote:
Yaakov Selkowitz via Cygwin-apps writes:
For anyone else who bumps into this, gdb and strace are of no use in
debugging this crash. I finally thought to look at the stackdump
file, and the second address from the top was in a gnulib file. That
was
Yaakov Selkowitz via Cygwin-apps writes:
>> For anyone else who bumps into this, gdb and strace are of no use in
>> debugging this crash. I finally thought to look at the stackdump
>> file, and the second address from the top was in a gnulib file. That
>> was the key clue.
>
> Add
On 11/26/2021 12:34 PM, Brian Inglis wrote:
On 2021-11-26 06:08, Ken Brown via Cygwin-apps wrote:
On 11/25/2021 1:25 PM, Yaakov Selkowitz via Cygwin-apps wrote:
Add gl_cv_have_weak=no to cygconf?
Are you suggesting maintainers should do this, or are you talking about
patching cygport, like
On 2021-11-26 06:08, Ken Brown via Cygwin-apps wrote:
On 11/25/2021 1:25 PM, Yaakov Selkowitz via Cygwin-apps wrote:
Add gl_cv_have_weak=no to cygconf?
Are you suggesting maintainers should do this, or are you talking about
patching cygport, like this:
diff --git
On 11/25/2021 1:25 PM, Yaakov Selkowitz via Cygwin-apps wrote:
Add gl_cv_have_weak=no to cygconf?
Are you suggesting maintainers should do this, or are you talking about patching
cygport, like this:
diff --git a/cygclass/autotools.cygclass b/cygclass/autotools.cygclass
index
On 2021-11-25 11:25, Yaakov Selkowitz via Cygwin-apps wrote:
On Thu, 2021-11-25 at 11:26 -0500, Ken Brown via Cygwin-apps wrote:
On 9/29/2021 7:46 PM, Brian Inglis wrote:
There is a gnulib bug in threadlib.m4 from at least serial 29 to serial
31 that incorrectly configures Cygwin support of
On Thu, 2021-11-25 at 11:26 -0500, Ken Brown via Cygwin-apps wrote:
> On 9/29/2021 7:46 PM, Brian Inglis wrote:
> > There is a gnulib bug in threadlib.m4 from at least serial 29 to serial
> > 31 that incorrectly configures Cygwin support of weak references.
> >
> > This leads to SIGSEGV stack
On 9/29/2021 7:46 PM, Brian Inglis wrote:
There is a gnulib bug in threadlib.m4 from at least serial 29 to serial
31 that incorrectly configures Cygwin support of weak references.
This leads to SIGSEGV stack smashing crashes with no backtrace
@ 0x1 or 0x0005 etc.
There is a gnulib bug in threadlib.m4 from at least serial 29 to serial
31 that incorrectly configures Cygwin support of weak references.
This leads to SIGSEGV stack smashing crashes with no backtrace
@ 0x1 or 0x0005 etc. normally during tests.
Akim Demaille on
17 matches
Mail list logo
