public inbox for cygwin-cvs@sourceware.org help / color / mirror / Atom feed
From: Corinna Vinschen <corinna@sourceware.org> To: cygwin-cvs@sourceware.org Subject: [newlib-cygwin] Cygwin: Raise dumpstack frame limit to 32 Date: Fri, 08 Nov 2019 09:23:00 -0000 [thread overview] Message-ID: <20191108092353.77114.qmail@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=7c9c94b9c8af34152d18cf2264e5c723e9e61ab7 commit 7c9c94b9c8af34152d18cf2264e5c723e9e61ab7 Author: Mark Geisert <mark@maxrnd.com> Date: Thu Nov 7 16:13:34 2019 -0800 Cygwin: Raise dumpstack frame limit to 32 Create a #define for the limit and raise it from 16 to 32. Diff: --- winsup/cygwin/exceptions.cc | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/winsup/cygwin/exceptions.cc b/winsup/cygwin/exceptions.cc index 132fea4..3e7d727 100644 --- a/winsup/cygwin/exceptions.cc +++ b/winsup/cygwin/exceptions.cc @@ -42,6 +42,7 @@ details. */ #define CALL_HANDLER_RETRY_OUTER 10 #define CALL_HANDLER_RETRY_INNER 10 +#define DUMPSTACK_FRAME_LIMIT 32 PWCHAR debugger_command; extern uint8_t _sigbe; @@ -382,7 +383,7 @@ cygwin_exception::dumpstack () #else small_printf ("Stack trace:\r\nFrame Function Args\r\n"); #endif - for (i = 0; i < 16 && thestack++; i++) + for (i = 0; i < DUMPSTACK_FRAME_LIMIT && thestack++; i++) { small_printf (_AFMT " " _AFMT, thestack.sf.AddrFrame.Offset, thestack.sf.AddrPC.Offset); @@ -392,7 +393,8 @@ cygwin_exception::dumpstack () small_printf (")\r\n"); } small_printf ("End of stack trace%s\n", - i == 16 ? " (more stack frames may be present)" : ""); + i == DUMPSTACK_FRAME_LIMIT ? + " (more stack frames may be present)" : ""); if (h) NtClose (h); }
reply other threads:[~2019-11-08 9:23 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20191108092353.77114.qmail@sourceware.org \ --to=corinna@sourceware.org \ --cc=cygwin-cvs@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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).