Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Pan ruochen <panruochen@gmail.com>
To: gdb@sourceware.org
Subject: Fwd: gdb on Cygwin cannot give correct call stacks for segment faults
Date: Mon, 28 Oct 2013 04:00:00 -0000	[thread overview]
Message-ID: <CALX7UOiD9AxWH2aqPsDdwOHQj3wAOsOXA+qSCJv4LTOuoND96g@mail.gmail.com> (raw)
In-Reply-To: <CALX7UOgBuWzx_8dO+Aev=1MfLLSma6CQdcQqi6iURCA1HR7snA@mail.gmail.com>

Hi All,

I find that my gdb on Cygwin cannot dump correct call stacks while
segment faults arise.

Test code is as follows:
--------------------------------------------------------------
#include <stdio.h>
#include <stdlib.h>

void foo()
{
    FILE * volatile dev =NULL;
    fprintf(dev, "Hello World!\n");
}

int main()
{
    foo();
    return 0;
}
--------------------------------------------------------------

And backtrace information is as follows:
Program received signal SIGSEGV, Segmentation fault.
0x61138b61 in _fwrite_r () from /usr/bin/cygwin1.dll
(gdb) backtrace
#0  0x61138b61 in _fwrite_r () from /usr/bin/cygwin1.dll
#1  0x76bd1194 in WaitForSingleObjectEx ()
   from /cygdrive/c/windows/syswow64/kernel32.dll
#2  0x76bd1148 in WaitForSingleObject ()
   from /cygdrive/c/windows/syswow64/kernel32.dll
#3  0x610dd558 in sig_send(_pinfo*, siginfo_t&, _cygtls*) ()
   from /usr/bin/cygwin1.dll
#4  0x610303b4 in exception::handle(_EXCEPTION_RECORD*,
_exception_list*, _CONTEXT*, void*) () from /usr/bin/cygwin1.dll
#5  0x77a5b499 in ntdll!LdrRemoveLoadAsDataTable ()
   from /cygdrive/c/windows/system32/ntdll.dll
#6  0x0028a6ac in ?? ()
#7  0x77a5b46b in ntdll!LdrRemoveLoadAsDataTable ()
   from /cygdrive/c/windows/system32/ntdll.dll
#8  0x0028a6ac in ?? ()
#9  0x77a10133 in ntdll!KiUserExceptionDispatcher ()
   from /cygdrive/c/windows/system32/ntdll.dll
#10 0x0028a6ac in ?? ()
#11 0x61138c75 in fwrite () from /usr/bin/cygwin1.dll
#12 0x610d75e5 in _sigfe () from /usr/bin/cygwin1.dll
#13 0x0000000d in ?? ()
#14 0x00000000 in ?? ()

does not give any useful clues where the segment faults arise.
So what is wrong?

-- BR, Ruochen


       reply	other threads:[~2013-10-28  4:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CALX7UOgBuWzx_8dO+Aev=1MfLLSma6CQdcQqi6iURCA1HR7snA@mail.gmail.com>
2013-10-28  4:00 ` Pan ruochen [this message]
2013-10-28 16:12   ` Eli Zaretskii
2013-10-28 18:00   ` Christopher Faylor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CALX7UOiD9AxWH2aqPsDdwOHQj3wAOsOXA+qSCJv4LTOuoND96g@mail.gmail.com \
    --to=panruochen@gmail.com \
    --cc=gdb@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox