This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: exe.stackdump is always empty


On Apr  4 22:07, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
> Any ideas, please?
> 
> > http://cygwin.com/problems.html
> > http://cygwin.com/acronyms/#STC
> 
> $ cat assert.c
> #include <assert.h>
> 
> int main(void)
> { assert(0);
>   return 0;
> }
> 
> $ ulimit -a
> core file size          (blocks, -c) unlimited
> data seg size           (kbytes, -d) unlimited
> file size               (blocks, -f) unlimited
> open files                      (-n) 256
> pipe size            (512 bytes, -p) 8
> stack size              (kbytes, -s) 2025
> cpu time               (seconds, -t) unlimited
> max user processes              (-u) 256
> virtual memory          (kbytes, -v) unlimited
> 
> $ gcc -g assert.c
> 
> $ ./a.exe
> assertion "0" failed: file "assert.c", line 4, function: main
> Aborted (core dumped)
> 
> $ cat a.exe.stackdump
> Stack trace:
> Frame     Function  Args

Hmm, not me.  In my case a stackdump is generated, albeit not very
complete:

  $ cat assert.exe.stackdump
  Stack trace:
  Frame     Function  Args
  0028A898  610303D2 (000000B4, 0000EA60, 000000A4, 0028A8E8)
  0028A9A8  610DA4DD (75D2E158, 00000000, 6E00016F, 00000000)

The 64 bit stackdump looks better:

  $ cat assert.exe.stackdump
  Stack trace:
  Frame        Function    Args
  0000023A480  0018006F733 (7FF9E9680EBF, 00000000000, 00000000003, 00000000016)
  00000000006  00180070C6A (0000023A940, 00000000000, 0000000009C, 00000000000)
  0000023A660  0018011AEE8 (00000341B10, 00000000000, 00000000000, 00000000000)
  000000000C1  00180117FEE (00300000000, 00000000000, 00000000000, 00000000000)
  0000023AAB0  001801184BB (7FF9E967ED89, 00000000000, 00100403032, 00000000006)
  0000023AAB0  0018011868C (7FF9E6A9151B, 00000004048, 001801EE0D8, 0018011CB7C)
  0000023AAB0  0018011894F (00100403030, 00100403032, 00000000004, 001801EE02F)
  0000023AAB0  00180041B45 (00000000000, 00000000000, 00000000000, 0000023AB90)
  0000023AAE0  001004010FC (00000000020, 30001000000FF00, 0018004819A, 00000000000)
  0000023AB90  0018004820B (00000000000, 00000000000, 00000000000, 00000000000)
  00000000000  0018004611B (00000000000, 00000000000, 00000000000, 00000000000)
  00000000000  00180046274 (00000000000, 00000000000, 00000000000, 00000000000)
  00000000000  00100401111 (00000000000, 00000000000, 00000000000, 00000000000)
  00000000000  00100401010 (00000000000, 00000000000, 00000000000, 00000000000)
  00000000000  7FF9E93115DD (00000000000, 00000000000, 00000000000, 00000000000)
  00000000000  7FF9E96B43D1 (00000000000, 00000000000, 00000000000, 00000000000)
  End of stack trace (more stack frames may be present)

but I'm not exactly an expert in how to generate a stackdump on i686.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

Attachment: pgplL0ak1mgnv.pgp
Description: PGP signature


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]