Hi.
I'm using the 20051227-snapshot of cygwin1.dll. This is my Windows 98SE
environment as told by the 'set' command:
TMP=C:\WINDOWS\TEMP
TEMP=C:\WINDOWS\TEMP
PROMPT=$p$g
winbootdir=C:\WINDOWS
PATH=C:\WINDOWS;C:\WINDOWS\COMMAND
COMSPEC=C:\WINDOWS\COMMAND.COM
DIRCMD=/o:gne
windir=C
On Mon, 05 Sep 2005, Sean Gugler wrote:
> Score! Snapshot 20050905 did the trick.
Unfortunately, there is still a crash with:
#include
#include
#include
#include
int cygwinsystem (const char *cmd)
{
pid_t pid;
int rc;
static int result;
if (!(pid = fork()))
Christopher Faylor writes:
> as would some indication of what you mean by "crash", i.e., maybe
> even running this under gdb to find out precisely where the "crash" is
> happening.
This dialog appears:
"This program has performed an illegal operation and will be shut down."
Confirming the d
Christopher Faylor writes:
> cygcheck output would help.
cygcheck -s crashes itself (but only with option -s, other options work):
"This program has performed an illegal operation and will be shut down."
Details>>:
CYGCHECK caused an invalid page fault
in module KERNEL32.DLL at 0167:bff7b992.
In the meantime I could reproduce the bug (which was described the first time
in http://www.cygwin.com/ml/cygwin/2005-09/msg00058.html and then in
http://www.cygwin.com/ml/cygwin/2005-12/msg01038.html) on a Windows 98SE PC
which never had anything to do with cygwin before and where I only copied th
An observation which should help.
See http://www.cygwin.com/ml/cygwin/2005-12/msg01037.html for the problem. As
said, COMSPEC is set:
TMP=C:\WINDOWS\TEMP
TEMP=C:\WINDOWS\TEMP
PROMPT=$p$g
winbootdir=C:\WINDOWS
PATH=C:\WINDOWS;C:\WINDOWS\COMMAND
COMSPEC=C:\WINDOWS\COMMAND.COM
DIRCMD=/
Christopher Faylor writes:
> Can anyone confirm if this actually plays a beep?
Windows 98SE here. Unfortunately, since I have the soundcard, my console beep
has become a kind of crackle, but I can confirm that it crackles with
echo -e "\007"
as well as with MessageBeep (-1) using the program
Christopher Faylor wrote:
> The above would indicate that you don't actually have cygwin installed
> since there is nothing in your mount table and no packages listed. So,
> this doesn't really help.
It was from the cygwin-free W98 machine. Here is the output from the PC with
cygwin installed (bu
Larry Hall wrote:
> Warning: There are multiple cygwin1.dlls on your path
^
Yikes!
So what shall I do? There is one in cygwin\bin (which was the current
directory at this time) and a copy in C:\WINDOWS\SYSTEM for my cygwin
programs to run
Just tried the 20060104 snapshot. Bug is fixed.
Thanks a lot.
Ingo
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
Christopher Faylor writes:
> maybe even running this under gdb to find out precisely where the "crash"
> is happening
Is there a "How track down bugs with gdb HOWTO for dummies"? I'd like to
help, but don't have experience with gdb.
Ingo
--
Unsubscribe info: http://cygwin.com/ml/#unsubscr
Just tried the 20060110 snapshot, the bug is fixed.
Thanks a lot (, Christopher?)!
Ingo
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwi
12 matches
Mail list logo
