On Sun, Jul 5, 2009 at 6:58 PM, Dave Korn wrote:
> It's not a full core dump, it's just a stack backtrace in human-readable
> format. If you copy and paste the addresses in the second column (Function)
> into "addr2line --exe " (and assuming you compiled
> with debug info), it'll turn them into a
Roman Werpachowski wrote:
> On Sun, Jul 5, 2009 at 1:50 PM, Dave Korn wrote:
>> Well, what happened was that there's a bug somewhere, and while cygwin was
>> in the process of dumping the stack trace for the abort caused by your
>> assertion firing,
>
> One more question: how can I use this stack
On Sun, Jul 05, 2009 at 05:21:50PM +0100, Roman Werpachowski wrote:
>On Sun, Jul 5, 2009 at 1:50 PM, Dave Korn wrote:
>> ?Well, what happened was that there's a bug somewhere, and while cygwin was
>> in the process of dumping the stack trace for the abort caused by your
>> assertion firing,
>
>One
On Sun, Jul 5, 2009 at 1:50 PM, Dave Korn wrote:
> Well, what happened was that there's a bug somewhere, and while cygwin was
> in the process of dumping the stack trace for the abort caused by your
> assertion firing,
One more question: how can I use this stack trace to debug genuine
errors? "gd
On Sun, Jul 5, 2009 at 3:28 PM, Dave Korn wrote:
> Right, well that shows you're using 1.5.25, which is known to have bugs in
> this area, and is at end-of-life and won't be fixed. It's a minor
> inconvenience, sorry, but it only affects things that happen after your
> program crashes anyway, so
On Sun, Jul 5, 2009 at 3:28 PM, Dave Korn wrote:
> Roman Werpachowski wrote:
>> On Sun, Jul 5, 2009 at 1:50 PM, Dave
>
> Please don't quote the "From:" address in your email.
Extremely sorry, won't happen again. BTW, couldn't the mailing
software automatically remove these addresses?
> Tried 1
Roman Werpachowski wrote:
> On Sun, Jul 5, 2009 at 1:50 PM, Dave
> Korn wrote:
Please don't quote the "From:" address in your email. Getting someone
spammed is no way to thank them for helping you! (See
http://cygwin.com/acronyms/#PCYMTNQREAIYR for a full explanation.)
>> Actually even more
On Sun, Jul 5, 2009 at 1:50 PM, Dave
Korn wrote:
> Actually even more useful would be to know what Cygwin DLL version you're
> running. The problems page that CGF directed you to contains in particular
> the advice to run "cygcheck -s -v -r > cygcheck.out" and then send the
> cygcheck.out file **
Roman Werpachowski wrote:
> Some more details about my problem
> (http://cygwin.com/ml/cygwin/2009-07/msg00150.html)
>
> $ gcc -v
Actually even more useful would be to know what Cygwin DLL version you're
running. The problems page that CGF directed you to contains in particular
the advice to r
Some more details about my problem
(http://cygwin.com/ml/cygwin/2009-07/msg00150.html)
$ gcc -v
Reading specs from /usr/lib/gcc/i686-pc-cygwin/3.4.4/specs
Configured with: /managed/gcc-build/final-v3-bootstrap/gcc-3.4.4-999/configure -
-verbose --program-suffix=-3 --prefix=/usr --exec-prefix=/usr
On Sun, Jul 05, 2009 at 04:18:44AM +0100, Roman Werpachowski wrote:
>I get the following output:
>
> 4 [sig] a 1408 _cygtls::handle_exceptions: Error while dumping
>state (probably corrupted stack)
>Segmentation fault (core dumped)
>
>When running the following test programs:
>
>#include
>
>i
I get the following output:
4 [sig] a 1408 _cygtls::handle_exceptions: Error while dumping
state (probably corrupted stack)
Segmentation fault (core dumped)
When running the following test programs:
#include
int main(void)
{
assert( 1 == 0 );
return 0;
}
or
#include
#include
12 matches
Mail list logo
