public inbox for cygwin-cvs@sourceware.org help / color / mirror / Atom feed
From: Jon TURNEY <jturney@sourceware.org> To: cygwin-cvs@sourceware.org Subject: [newlib-cygwin] Cygwin: Tidy up formatting of stackdump Date: Sat, 29 Oct 2022 17:34:31 +0000 (GMT) [thread overview] Message-ID: <20221029173431.E2E2E38582A1@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=4a67f89ced019f540714964ece4374a6f5e112d8 commit 4a67f89ced019f540714964ece4374a6f5e112d8 Author: Jon Turney <jon.turney@dronecode.org.uk> Date: Fri Oct 28 13:43:54 2022 +0100 Cygwin: Tidy up formatting of stackdump Resize stackdump headers for b9e97f58 Consistently use \r\n line endings Diff: --- winsup/cygwin/exceptions.cc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/winsup/cygwin/exceptions.cc b/winsup/cygwin/exceptions.cc index e6f868511..a15bc16c5 100644 --- a/winsup/cygwin/exceptions.cc +++ b/winsup/cygwin/exceptions.cc @@ -342,7 +342,7 @@ cygwin_exception::dumpstack () int i; thestack.init (framep, 1, ctx); /* Initialize from the input CONTEXT */ - small_printf ("Stack trace:\r\nFrame Function Args\r\n"); + small_printf ("Stack trace:\r\nFrame Function Args\r\n"); for (i = 0; i < DUMPSTACK_FRAME_LIMIT && thestack++; i++) { small_printf ("%012X %012X", thestack.sf.AddrFrame.Offset, @@ -352,9 +352,9 @@ cygwin_exception::dumpstack () thestack.sf.Params[j]); small_printf (")\r\n"); } - small_printf ("End of stack trace%s\n", + small_printf ("End of stack trace%s\r\n", i == DUMPSTACK_FRAME_LIMIT ? - " (more stack frames may be present)" : ""); + " (more stack frames may be present)" : ""); if (h) NtClose (h); }
reply other threads:[~2022-10-29 17:34 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=20221029173431.E2E2E38582A1@sourceware.org \ --to=jturney@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).