* Re: B20.1: windows reports illegal instruction, when using many arguments
@ 1999-09-25 16:14 Jorgo Bakker
1999-09-30 23:42 ` Jorgo Bakker
0 siblings, 1 reply; 4+ messages in thread
From: Jorgo Bakker @ 1999-09-25 16:14 UTC (permalink / raw)
To: Cygnus Mailing List
>Jorgo,
>
>Please don't send HTML to this list.
>
>Thanks,
>David
>
Sorry about that! Here is the original message (hopefully not in html this
time), as I am still having trouble with it:
Hi All,
Running the script below gives a window message "illegal
instruction...restart computer", if too many characters are on the command
line.
BASH.EXE-2.02$ ./run_ 998
trying length= 9980
BASH.EXE-2.02$ ./run__ 998
trying length= 9980
BASH.EXE-2.02$
Is the problem above a general one, or specific to my computer set-up?
Problem created using CygWin32 with the gcc-2.95 release installed on a
Win98 platform.
Note that this gives problems when porting code. Makefiles may have a
'rm -rf $(OBJECTS)'. Of course it is possible to split the list of
$(OBJECTS) up into smaller pieces (which I am doing right now), but I would
like to minimize modifications.
Jorgo
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: B20.1: windows reports illegal instruction, when using many arguments
1999-09-25 16:14 B20.1: windows reports illegal instruction, when using many arguments Jorgo Bakker
@ 1999-09-30 23:42 ` Jorgo Bakker
0 siblings, 0 replies; 4+ messages in thread
From: Jorgo Bakker @ 1999-09-30 23:42 UTC (permalink / raw)
To: Cygnus Mailing List
>Jorgo,
>
>Please don't send HTML to this list.
>
>Thanks,
>David
>
Sorry about that! Here is the original message (hopefully not in html this
time), as I am still having trouble with it:
Hi All,
Running the script below gives a window message "illegal
instruction...restart computer", if too many characters are on the command
line.
BASH.EXE-2.02$ ./run_ 998
trying length= 9980
BASH.EXE-2.02$ ./run__ 998
trying length= 9980
BASH.EXE-2.02$
Is the problem above a general one, or specific to my computer set-up?
Problem created using CygWin32 with the gcc-2.95 release installed on a
Win98 platform.
Note that this gives problems when porting code. Makefiles may have a
'rm -rf $(OBJECTS)'. Of course it is possible to split the list of
$(OBJECTS) up into smaller pieces (which I am doing right now), but I would
like to minimize modifications.
Jorgo
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 4+ messages in thread
* B20.1: windows reports illegal instruction, when using many arguments
1999-09-24 4:40 Jorgo Bakker
@ 1999-09-30 23:42 ` Jorgo Bakker
0 siblings, 0 replies; 4+ messages in thread
From: Jorgo Bakker @ 1999-09-30 23:42 UTC (permalink / raw)
To: cygwin
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1068 bytes --]
Hi All,
Â
Running the script below gives a window message "illegal instruction...restart computer", if
too many characters are on the command line.
BASH.EXE-2.02$ ./run_ 998 trying
length=Â Â 9980 BASH.EXE-2.02$ ./run__ 998 trying
length=Â Â 9980 BASH.EXE-2.02$
Is the problem above a
general one, or specific to my computer set-up? Problem created
using CygWin32 with the gcc-2.95 release installed on a Win98
platform.
Â
Note that this gives problems when porting code. Makefiles may
have a 'rm -rf $(OBJECTS)'. Of course it is possible to split the list of
$(OBJECTS) up into smaller pieces (which I am doing right now), but I would like
to minimize modifications.
Â
Jorgo
Â
-------
#!/bin/bash
Â
number=0 numbers=
Â
limit=1000 if [ x$1 != x ] ; then limit=$1 ;
fi
Â
while [ "x$number" != "x$limit" ];
do  number=$[ number + 1 ] # numbers="$numbers
DummyLongFileName.$number" Â numbers="$numbers
234567890" done
Â
length=`echo $numbers|wc -c` echo "trying
length=$length" rm -f $numbers
Â
^ permalink raw reply [flat|nested] 4+ messages in thread
* B20.1: windows reports illegal instruction, when using many arguments
@ 1999-09-24 4:40 Jorgo Bakker
1999-09-30 23:42 ` Jorgo Bakker
0 siblings, 1 reply; 4+ messages in thread
From: Jorgo Bakker @ 1999-09-24 4:40 UTC (permalink / raw)
To: cygwin
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1068 bytes --]
Hi All,
Â
Running the script below gives a window message "illegal instruction...restart computer", if
too many characters are on the command line.
BASH.EXE-2.02$ ./run_ 998 trying
length=Â Â 9980 BASH.EXE-2.02$ ./run__ 998 trying
length=Â Â 9980 BASH.EXE-2.02$
Is the problem above a
general one, or specific to my computer set-up? Problem created
using CygWin32 with the gcc-2.95 release installed on a Win98
platform.
Â
Note that this gives problems when porting code. Makefiles may
have a 'rm -rf $(OBJECTS)'. Of course it is possible to split the list of
$(OBJECTS) up into smaller pieces (which I am doing right now), but I would like
to minimize modifications.
Â
Jorgo
Â
-------
#!/bin/bash
Â
number=0 numbers=
Â
limit=1000 if [ x$1 != x ] ; then limit=$1 ;
fi
Â
while [ "x$number" != "x$limit" ];
do  number=$[ number + 1 ] # numbers="$numbers
DummyLongFileName.$number" Â numbers="$numbers
234567890" done
Â
length=`echo $numbers|wc -c` echo "trying
length=$length" rm -f $numbers
Â
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~1999-09-30 23:42 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1999-09-25 16:14 B20.1: windows reports illegal instruction, when using many arguments Jorgo Bakker
1999-09-30 23:42 ` Jorgo Bakker
-- strict thread matches above, loose matches on Subject: below --
1999-09-24 4:40 Jorgo Bakker
1999-09-30 23:42 ` Jorgo Bakker
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).