From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-patches@cygwin.com
Cc: Jon Turney <jon.turney@dronecode.org.uk>
Subject: [PATCH 1/3] Cygwin: Tidy up formatting of stackdump
Date: Fri, 28 Oct 2022 16:05:56 +0100 [thread overview]
Message-ID: <20221028150558.2300-2-jon.turney@dronecode.org.uk> (raw)
In-Reply-To: <20221028150558.2300-1-jon.turney@dronecode.org.uk>
Resize stackdump headers for b9e97f58
Consistently use \r\n line endings
---
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);
}
--
2.38.1
next prev parent reply other threads:[~2022-10-28 15:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 15:05 [PATCH 0/3] Stackdump improvements Jon Turney
2022-10-28 15:05 ` Jon Turney [this message]
2022-10-28 15:05 ` [PATCH 2/3] Cygwin: Add addresses as module offsets in .stackdump file Jon Turney
2022-10-28 15:05 ` [PATCH 3/3] Cygwin: Add loaded module base address list to stackdump Jon Turney
2022-10-29 8:32 ` Corinna Vinschen
2022-11-03 17:02 ` Jon Turney
2022-11-04 10:34 ` Corinna Vinschen
2022-10-29 8:34 ` [PATCH 0/3] Stackdump improvements Corinna Vinschen
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=20221028150558.2300-2-jon.turney@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-patches@cygwin.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).