Re: about cygwin_stackdump()

2014-01-09 Thread KIMURA Masaru
> You made it harder than necessary to debug your problem. > > If you had created a very small test case which demonstrated the issue > with clear instructions for building it, then this back and forth > wouldn't be necessary. > > Actually, even that would likely not have been necessary if you had

Re: about cygwin_stackdump()

2014-01-08 Thread Christopher Faylor
On Wed, Jan 08, 2014 at 06:06:59PM +0900, KIMURA Masaru wrote: >2014/1/8 Christopher Faylor wrote: >> On Tue, Jan 07, 2014 at 11:35:57AM +0900, KIMURA Masaru wrote: >>>fopen() stackdump file immediately after cygwin_stackdump() calling in >>>signle process fails. >>>is this intentional? >>>https://

Re: about cygwin_stackdump()

2014-01-08 Thread KIMURA Masaru
2014/1/8 Christopher Faylor wrote: > On Tue, Jan 07, 2014 at 11:35:57AM +0900, KIMURA Masaru wrote: >>fopen() stackdump file immediately after cygwin_stackdump() calling in >>signle process fails. >>is this intentional? >>https://github.com/hiyuh/cygwin-stackdump-example > > I rewrote your example

Re: about cygwin_stackdump()

2014-01-07 Thread Christopher Faylor
On Tue, Jan 07, 2014 at 11:35:57AM +0900, KIMURA Masaru wrote: >fopen() stackdump file immediately after cygwin_stackdump() calling in >signle process fails. >is this intentional? >https://github.com/hiyuh/cygwin-stackdump-example I rewrote your example slightly to make it work with any executable

about cygwin_stackdump()

2014-01-06 Thread KIMURA Masaru
Hi, fopen() stackdump file immediately after cygwin_stackdump() calling in signle process fails. is this intentional? https://github.com/hiyuh/cygwin-stackdump-example Peace, -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: