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 this question I've posted
repeatedly even if it is just to say slag off

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 architecture: No error

I would *love* to get around this problem and be able to examine cores.

Thanks,
Mark

-----Original Message-----
From: Jon A. Lambert [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, February 26, 2003 11:02 AM
To: Cygwin Mail List
Subject: Can someone please answer this question I've posted repeatedly
even if it is just to say slag off

Does dumper.exe work?

I am unable to get the dumper utility to produce a core dump.
I have read the FAQ, the webpages and searched the mailing lists.

My cygwin.bat startup file contains the following:
  set CYGWIN=error_start=c:\cygwin\bin\dumper.bat

My dumper.bat file contains the following:
  dumper.exe -d %1 %2 %3
  pause

The program in question was compiled with the gcc -g option:
  main() {
    int h;
    h = 1 / 0;
  }

Upon execution I see the following in the cygwin console:
  $ ./div.exe
        7 [main] div 2296 handle_exceptions: Error while dumping state
(probably corrupted stack)
  Arithmetic exception (core dumped)

In the cmd.exe console window that dumper.bat starts I see the
following:
  C:\cygwin\home\jlambert>dumper.exe -d C:/cygwin/home/jlambert/div.exe
1884
  dumping process #1884 to div.exe.core
  setting bfd architecture: No error

  C:\cygwin\home\jlambert>pause
  Press any key to continue . . .

  Yet no .core file is produced anywhere.  
  I have also tried using dumper.exe directly with the following setting
with the same results.
    set CYGWIN=error_start=c:\cygwin\bin\dumper.exe

  And I have verified that the process number above is correct.
  What am I doing wrong?  

 Thank you

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Reply via email to