When I run an application that uses the cygwin1.dll from either a Windows Service and
then from the command line I get different results when trying to read a text file.
As a Windows Service:
I use fopen and fgets to read a DOS text file and the CR/LF combinations are handled
properly. Meaning
local file system, (C:/.../file.txt) so I don't know
if that applies here.
-Mark
-Original Message-
From: Dan Vasaru [mailto:dvasaru@;broadpark.no]
Sent: Wed 10/16/2002 5:09 PM
To: Madsen, Mark; [EMAIL PROTECTED]
Cc:
Subject:RE: starting a CYGWIN app from a Windo
I failed to mention that this occurs in both 1.3.14 and 1.3.17.
I'm using W2K Pro and select ( I think it is there ) is dumping core.
The reason
I am not sure is that when I run the app in gdb, the crash is not in the
main
thread but the addresses on the stack match those of the main thread
after
it is
taking time. ;)
-Mark
-Original Message-
From: Corinna Vinschen [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 11, 2002 10:03 AM
To: [EMAIL PROTECTED]
Subject: Re: crashing in select
On Wed, Dec 11, 2002 at 08:25:34AM -0600, Madsen, Mark wrote:
> Any thoughts or comments
This is another problem that I encountered while looking into the
segment fault in select() (see thread: crash in select).
The following code will run until it generates a segmentation fault
somewhere in the call to socket(). The final few lines of the resulting
output are after the code sample.
I experience the same problem on several different machines (all W2K),
and on different versions of cygwin.
I can not even force a core dump of a process that is just a simple
infinite loop. This is the result of that:
$ dumper -d c:/fcore 872
dumping process #872 to fcore.core
setting bfd archit
I failed to mention that the process never exits when I force a core
dump so it appears that the dumper never actually attaches to the
process.
-Original Message-
From: Madsen, Mark
Sent: Thursday, February 27, 2003 9:14 AM
To: [EMAIL PROTECTED]
Subject: RE: Can someone please answer
7 matches
Mail list logo
