* GCC 3.3-Signal 11
@ 2003-02-05 0:39 Robert McNulty Junior
2003-02-07 4:19 ` Kelley Cook
0 siblings, 1 reply; 4+ messages in thread
From: Robert McNulty Junior @ 2003-02-05 0:39 UTC (permalink / raw)
To: gcc
This is where the fault is at.
____________________________________________________________________________
________________
for f in $gf; do \
echo "\"$f\", "; done >> tmp-gtyp.h
echo " NULL};" >> tmp-gtyp.h
echo "static const char *lang_dir_names[] = { \"c\", " >> tmp-gtyp.h
gf="cp f java objc"; \
for l in $gf; do \
echo "\"$l\", "; done >> tmp-gtyp.h
echo "NULL};" >> tmp-gtyp.h
/bin/sh ../../gcc/gcc/move-if-change tmp-gtyp.h gtyp-gen.h
gcc -c -g -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissi
ng-p
rototypes -Wtraditional -pedantic -Wno-long-long -DHAVE_CONFIG_H -DGENERAT
OR_F
ILE -DCYGWIN_CROSS_DIR=\"/usr/local/i686-pc-cygwin\" -I. -I. -I../../gcc/g
cc -
I../../gcc/gcc/. -I../../gcc/gcc/config -I../../gcc/gcc/../include \
../../gcc/gcc/gengtype.c -o gengtype.o
gcc -c -g -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissi
ng-p
rototypes -Wtraditional -pedantic -Wno-long-long -DHAVE_CONFIG_H -DGENERAT
OR_F
ILE -DCYGWIN_CROSS_DIR=\"/usr/local/i686-pc-cygwin\" -I. -I. -I../../gcc/g
cc -
I../../gcc/gcc/. -I../../gcc/gcc/config -I../../gcc/gcc/../include \
../../gcc/gcc/gengtype-lex.c -o gengtype-lex.o
gcc -c -g -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissi
ng-p
rototypes -Wtraditional -pedantic -Wno-long-long -DHAVE_CONFIG_H -DGENERAT
OR_F
ILE -DCYGWIN_CROSS_DIR=\"/usr/local/i686-pc-cygwin\" -I. -I. -I../../gcc/g
cc -
I../../gcc/gcc/. -I../../gcc/gcc/config -I../../gcc/gcc/../include \
../../gcc/gcc/gengtype-yacc.c -o gengtype-yacc.o
gcc -g -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-
prot
otypes -Wtraditional -pedantic -Wno-long-long -DHAVE_CONFIG_H -DGENERATOR_
FILE
-o gengtype.exe \
gengtype.o gengtype-lex.o gengtype-yacc.o ../libiberty/libiberty.a
./gengtype
Signal 11
make[2]: *** [s-gtype] Error 139
make[2]: Leaving directory `/home/Robert/gcc-3.3/o/gcc'
make[1]: *** [stage1_build] Error 2
make[1]: Leaving directory `/home/Robert/gcc-3.3/o/gcc'
make: *** [bootstrap] Error 2
Robert@bobby ~/gcc-3.3/o
$
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: GCC 3.3-Signal 11
2003-02-05 0:39 GCC 3.3-Signal 11 Robert McNulty Junior
@ 2003-02-07 4:19 ` Kelley Cook
2003-02-07 5:15 ` Kelley Cook
0 siblings, 1 reply; 4+ messages in thread
From: Kelley Cook @ 2003-02-07 4:19 UTC (permalink / raw)
To: gcc; +Cc: cygwin
[This followup was posted to gmane.comp.gcc.devel and a copy
was sent to the cited author.]
In article <GGEKKFKDCKKAHNCJOFCNGEDMCAAA.bmj2001
@bellsouth.net>, bmj2001@bellsouth.net says...
>
> This is where the fault is at.
>
>
> ____________________________________________________________________________
> ________________
> for f in $gf; do \
> echo "\"$f\", "; done >> tmp-gtyp.h
> echo " NULL};" >> tmp-gtyp.h
> echo "static const char *lang_dir_names[] = { \"c\", " >> tmp-gtyp.h
> gf="cp f java objc"; \
> for l in $gf; do \
> echo "\"$l\", "; done >> tmp-gtyp.h
> echo "NULL};" >> tmp-gtyp.h
> /bin/sh ../../gcc/gcc/move-if-change tmp-gtyp.h gtyp-gen.h
> gcc -c -g -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissi
> ng-p
> rototypes -Wtraditional -pedantic -Wno-long-long -DHAVE_CONFIG_H -DGENERAT
> OR_F
> ILE -DCYGWIN_CROSS_DIR=\"/usr/local/i686-pc-cygwin\" -I. -I. -I../../gcc/g
> cc -
> I../../gcc/gcc/. -I../../gcc/gcc/config -I../../gcc/gcc/../include \
> ../../gcc/gcc/gengtype.c -o gengtype.o
> gcc -c -g -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissi
> ng-p
> rototypes -Wtraditional -pedantic -Wno-long-long -DHAVE_CONFIG_H -DGENERAT
> OR_F
> ILE -DCYGWIN_CROSS_DIR=\"/usr/local/i686-pc-cygwin\" -I. -I. -I../../gcc/g
> cc -
> I../../gcc/gcc/. -I../../gcc/gcc/config -I../../gcc/gcc/../include \
> ../../gcc/gcc/gengtype-lex.c -o gengtype-lex.o
> gcc -c -g -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissi
> ng-p
> rototypes -Wtraditional -pedantic -Wno-long-long -DHAVE_CONFIG_H -DGENERAT
> OR_F
> ILE -DCYGWIN_CROSS_DIR=\"/usr/local/i686-pc-cygwin\" -I. -I. -I../../gcc/g
> cc -
> I../../gcc/gcc/. -I../../gcc/gcc/config -I../../gcc/gcc/../include \
> ../../gcc/gcc/gengtype-yacc.c -o gengtype-yacc.o
> gcc -g -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-
> prot
> otypes -Wtraditional -pedantic -Wno-long-long -DHAVE_CONFIG_H -DGENERATOR_
> FILE
> -o gengtype.exe \
> gengtype.o gengtype-lex.o gengtype-yacc.o ../libiberty/libiberty.a
> ./gengtype
> Signal 11
> make[2]: *** [s-gtype] Error 139
> make[2]: Leaving directory `/home/Robert/gcc-3.3/o/gcc'
> make[1]: *** [stage1_build] Error 2
It's not a GCC problem.
Cygwin 1.3.19 added in support for vasprintf (previously GCC
would use the version included in libiberty).
Unfortunately, Cygwin's (actually newlib's) vasprintf is not
quite right and it bombs under certain circumstances.
Supposedly that bug has been corrected, but it still crashes
for me with the Feb 3rd cygwin snapshot.
Kelley Cook
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: GCC 3.3-Signal 11
2003-02-07 4:19 ` Kelley Cook
@ 2003-02-07 5:15 ` Kelley Cook
2003-02-07 5:58 ` Robert McNulty Junior
0 siblings, 1 reply; 4+ messages in thread
From: Kelley Cook @ 2003-02-07 5:15 UTC (permalink / raw)
To: gcc; +Cc: cygwin
[This followup was posted to gmane.comp.gcc.devel and a copy
was sent to the cited author.]
In article <MPG.18acf893146192bc989686@news.gmane.org>,
KelleyCook=Wuw85uim5zDR7s880joybQ@public.gmane.org says...
> It's not a GCC problem.
>
> Cygwin 1.3.19 added in support for vasprintf (previously GCC
> would use the version included in libiberty).
>
> Unfortunately, Cygwin's (actually newlib's) vasprintf is not
> quite right and it bombs under certain circumstances.
> Supposedly that bug has been corrected, but it still crashes
> for me with the Feb 3rd cygwin snapshot.
Namely since after checking the changelog that particular
patch wasn't put in until the Feb 5th snapshot.
It works now.
Kelley Cook
^ permalink raw reply [flat|nested] 4+ messages in thread
* RE: GCC 3.3-Signal 11
2003-02-07 5:15 ` Kelley Cook
@ 2003-02-07 5:58 ` Robert McNulty Junior
0 siblings, 0 replies; 4+ messages in thread
From: Robert McNulty Junior @ 2003-02-07 5:58 UTC (permalink / raw)
To: Kelley Cook, gcc; +Cc: cygwin
I know. 20030502 works fine for now.
No more signal 11 (error 123 I think was the other one)
Going further, you can see where some names are used, but not defined.
-----Original Message-----
From: gcc-owner@gcc.gnu.org [mailto:gcc-owner@gcc.gnu.org]On Behalf Of
Kelley Cook
Sent: Thursday, February 06, 2003 11:15 PM
To: gcc@gcc.gnu.org
Cc: cygwin@cygwin.com
Subject: Re: GCC 3.3-Signal 11
[This followup was posted to gmane.comp.gcc.devel and a copy
was sent to the cited author.]
In article <MPG.18acf893146192bc989686@news.gmane.org>,
KelleyCook=Wuw85uim5zDR7s880joybQ@public.gmane.org says...
> It's not a GCC problem.
>
> Cygwin 1.3.19 added in support for vasprintf (previously GCC
> would use the version included in libiberty).
>
> Unfortunately, Cygwin's (actually newlib's) vasprintf is not
> quite right and it bombs under certain circumstances.
> Supposedly that bug has been corrected, but it still crashes
> for me with the Feb 3rd cygwin snapshot.
Namely since after checking the changelog that particular
patch wasn't put in until the Feb 5th snapshot.
It works now.
Kelley Cook
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2003-02-07 5:58 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-02-05 0:39 GCC 3.3-Signal 11 Robert McNulty Junior
2003-02-07 4:19 ` Kelley Cook
2003-02-07 5:15 ` Kelley Cook
2003-02-07 5:58 ` Robert McNulty Junior
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).