On Sat, Aug 4, 2012 at 1:21 AM, Glyn wrote:
>
> > I'll either attempt to upgrade or seek a new maintainer, which might
> > take a bit of time, my apologies!
>
> > Bob
>
> Great, thanks. I'm glad to know it's not a mystery, because I
> imagine it would would have been quite a big one! I've found
> a
> Years ago I became maintainer of libgc only in order to get w3m
> working. And unfortunately I have not kept it current with the
> upstream libgc. Several newer versions back it was causing w3m to
> throw errors in my dev environment so I didn't proceed at that time.
> I'll either attempt to up
On Wed, Aug 1, 2012 at 2:47 AM, Glyn wrote:
>
> /*
> This small program causes a libgc error when compiled and run in Cygwin:
...
> Programs with libgc and this construct always work correctly in Debian
> Stable.
Years ago I became maintainer of libgc only in order to get w3m
working. And unfortu
/*
This small program causes a libgc error when compiled and run in Cygwin:
$ gcc gcerror.c -lgc -o x.exe
$ ./x.exe
42
GC Warning: Thread stack pointer 0x22aa98 out of range, pushing
everything
*/
#include
#include
void *dummy;
void f (void (*x)())
{
x();
}
int main ()
4 matches
Mail list logo
