From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Tvrtko Ursulin <tursulin@ursulin.net>, Intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH i-g-t 3/5] lib/core: Avoid unused result in backtrace printing
Date: Wed, 22 Nov 2017 17:44:23 +0000 [thread overview]
Message-ID: <90a52c2f-1d9c-b0e8-6bbb-af00f3ea1f37@linux.intel.com> (raw)
In-Reply-To: <20171108120654.680-4-tvrtko.ursulin@linux.intel.com>
Ping on this one - do we want to squash these compile warnings, yes? :)
On 08/11/2017 12:06, Tvrtko Ursulin wrote:
> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>
> Add helpers for direct write to stderr to consolidate the code
> and avoid the unused result warning in build.
>
> v2: Use igt_ignore_warn since it is questionable whether igt_assert
> is safe in signal handlers. (Chris Wilson)
>
> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> ---
> lib/igt_core.c | 23 ++++++++++++++++-------
> 1 file changed, 16 insertions(+), 7 deletions(-)
>
> diff --git a/lib/igt_core.c b/lib/igt_core.c
> index 538a4472e209..e866bf995872 100644
> --- a/lib/igt_core.c
> +++ b/lib/igt_core.c
> @@ -1239,7 +1239,7 @@ static const char hex[] = "0123456789abcdef";
> static void
> xputch(int c)
> {
> - write(STDERR_FILENO, (const void *) &c, 1);
> + igt_ignore_warn(write(STDERR_FILENO, (const void *) &c, 1));
> }
>
> static int
> @@ -1384,13 +1384,23 @@ xprintf(const char *fmt, ...)
> va_end(ap);
> }
>
> +static void __write_stderr(const char *str, size_t len)
> +{
> + igt_ignore_warn(write(STDERR_FILENO, str, len));
> +}
> +
> +static void write_stderr(const char *str)
> +{
> + __write_stderr(str, strlen(str));
> +}
> +
> static void print_backtrace_sig_safe(void)
> {
> unw_cursor_t cursor;
> unw_context_t uc;
> int stack_num = 0;
>
> - write(STDERR_FILENO, "Stack trace: \n", 15);
> + write_stderr("Stack trace: \n");
>
> unw_getcontext(&uc);
> unw_init_local(&cursor, &uc);
> @@ -1899,11 +1909,10 @@ static void fatal_sig_handler(int sig)
> continue;
>
> if (handled_signals[i].name_len) {
> - igt_assert_eq(write(STDERR_FILENO, "Received signal ", 16),
> - 16);
> - igt_assert_eq(write(STDERR_FILENO, handled_signals[i].name, handled_signals[i].name_len),
> - handled_signals[i].name_len);
> - igt_assert_eq(write(STDERR_FILENO, ".\n", 2), 2);
> + write_stderr("Received signal ");
> + __write_stderr(handled_signals[i].name,
> + handled_signals[i].name_len);
> + write_stderr(".\n");
> }
>
> if (crash_signal(sig)) {
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-11-22 17:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 12:06 [PATCH i-g-t 0/5] Assorted compile warnings fixes Tvrtko Ursulin
2017-11-08 12:06 ` [PATCH i-g-t 1/5] intel-gpu-overlay: Avoid theoretical string overflow Tvrtko Ursulin
2017-11-08 12:25 ` Petri Latvala
2017-11-08 12:06 ` [PATCH i-g-t 2/5] aubdump: Avoid mixing declarations and code Tvrtko Ursulin
2017-11-08 12:06 ` [PATCH i-g-t 3/5] lib/core: Avoid unused result in backtrace printing Tvrtko Ursulin
2017-11-22 17:44 ` Tvrtko Ursulin [this message]
2017-11-22 17:52 ` Chris Wilson
2017-11-08 12:06 ` [PATCH i-g-t 4/5] gem_syslatency: Avoid arithmetic on void * warning Tvrtko Ursulin
2017-11-08 12:28 ` Petri Latvala
2017-11-09 10:18 ` Tvrtko Ursulin
2017-11-08 12:06 ` [PATCH i-g-t 5/5] intel_gvtg_test: Handle system(3) return value Tvrtko Ursulin
2017-11-08 12:19 ` Chris Wilson
2017-11-08 12:50 ` Tvrtko Ursulin
2017-11-08 12:22 ` Petri Latvala
2017-11-08 12:47 ` [PATCH i-g-t v2] " Tvrtko Ursulin
2017-11-08 12:52 ` Petri Latvala
2017-11-09 10:16 ` Tvrtko Ursulin
2017-11-08 18:09 ` ✗ Fi.CI.BAT: warning for " Patchwork
2017-11-08 20:14 ` ✗ Fi.CI.IGT: " Patchwork
2017-11-08 17:36 ` ✗ Fi.CI.BAT: failure for Assorted compile warnings fixes Patchwork
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=90a52c2f-1d9c-b0e8-6bbb-af00f3ea1f37@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=tursulin@ursulin.net \
/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