On Apr 7 15:03, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
> > Does it still occur after update?
>
> Haven't tried it yet; is the new snapshot out already? -- can't see it on
> the website...
http://cygwin.com/ml/cygwin-announce/2014-04/msg5.html
Corinna
--
Corinna Vinschen
> Does it still occur after update?
Haven't tried it yet; is the new snapshot out already? -- can't see it on the
website...
Anton Lavrentiev
Contractor NIH/NLM/NCBI
On Apr 7 14:21, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
> > Hmm, not me. In my case a stackdump is generated...
>
> There seems to be an access denied condition "C05" along the lines of the
> strace output that I've sent.
> What could have caused that? Can that be a reason for me not g
> Hmm, not me. In my case a stackdump is generated...
There seems to be an access denied condition "C05" along the lines of the
strace output that I've sent.
What could have caused that? Can that be a reason for me not getting the core
dump at all?
Thanks,
Anton Lavrentiev
Contractor NIH
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
>
> int main(void)
> { assert(0);
> return 0;
> }
>
> $ ulimit -a
> core file size (blocks, -c) u
On Mar 31 11:36, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
> > If your process crashes with a thoroughly scrambled stack, there's
> > a good chance that Cygwin won't be able to create a stackdump file
> > because it crashes again while producing the stackdump.
>
> I don't think it's all that bad
> If your process crashes with a thoroughly scrambled stack, there's
> a good chance that Cygwin won't be able to create a stackdump file
> because it crashes again while producing the stackdump.
I don't think it's all that bad -- it was merely an assert()
triggering app's abort...
On Mar 29 05:00, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
> Hello List,
>
> I wonder, if there any special setup was necessary to make coredumps
> non-empty.
>
> When my program crashes it leaves only the following:
>
> Stack trace:
> Frame Function Args
>
> despite is was built and li
Hello List,
I wonder, if there any special setup was necessary to make coredumps non-empty.
When my program crashes it leaves only the following:
Stack trace:
Frame Function Args
despite is was built and linked with -g (so should have all the debugging info
intact). I did not modify any s
9 matches
Mail list logo
