Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Aleksandar Ristovski <aristovski@qnx.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [patch] cleanup: Wunused corefile.c
Date: Fri, 01 Feb 2013 21:54:00 -0000	[thread overview]
Message-ID: <510C3998.5050309@qnx.com> (raw)
In-Reply-To: <510C3418.4040802@qnx.com>

On 13-02-01 04:31 PM, Aleksandar Ristovski wrote:
> On 13-02-01 02:25 PM, Tom Tromey wrote:
>>
>> I understand, but I think the hard part of this work is also the most
>> useful part.  What I mean is that it is certainly valuable to get all
>> the simple cases fixed; but going through the trickier cases and writing
>> proper fixes is the real benefit of enabling this warning -- finding and
>> fixing real bugs.  Making these warnings disappear is contrary to that.
>>
>
> I agree and I don't agree. I'm not shy from hard work, but I simply have
> limited time resources for contributing back to FSF.
>
> I really believe making warnings disappear and turning on Wunused by
> default would make a big difference worth "obscuring" a bug or two (they
> are already obscure as we are not aware of them). Once Wunused is on by
> default, there will not be creeping in of unused stuff any more.
>
>
> But here is revised patch for corefile.c. Not that it represents any
> hard work or anything, but since I was at...
>
>
> Thanks,
>
> Aleksandar Ristovski
> QNX Software Systems
>
>
>
> ChangeLog:
>   Aleksandar Ristovski  <aristovski@qnx.com>
>
>          * corefile.c (reopen_exec_file): Check return value from stat.
>


Sorry it should have been errno for strerror not res:

Index: gdb/corefile.c
===================================================================
RCS file: /cvs/src/src/gdb/corefile.c,v
retrieving revision 1.71
diff -u -p -r1.71 corefile.c
--- gdb/corefile.c      14 Jan 2013 21:03:54 -0000      1.71
+++ gdb/corefile.c      1 Feb 2013 21:48:42 -0000
@@ -149,7 +149,11 @@ reopen_exec_file (void)
    cleanups = make_cleanup (xfree, filename);
    res = stat (filename, &st);

-  if (exec_bfd_mtime && exec_bfd_mtime != st.st_mtime)
+  if (res != 0 && info_verbose)
+    warning (_("File %s could not be stat-ed (%s)\n"), filename,
+            strerror (errno));
+
+  if (res == 0 && exec_bfd_mtime && exec_bfd_mtime != st.st_mtime)
      exec_file_attach (filename, 0);
    else
      /* If we accessed the file since last opening it, close it now;




  reply	other threads:[~2013-02-01 21:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-31 19:36 Aleksandar Ristovski
2013-01-31 20:24 ` Tom Tromey
2013-01-31 20:29   ` Aleksandar Ristovski
2013-02-01 21:16     ` Tom Tromey
2013-02-01 21:31       ` Aleksandar Ristovski
2013-02-01 21:54         ` Aleksandar Ristovski [this message]
2013-02-03  0:05           ` Sergio Durigan Junior

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=510C3998.5050309@qnx.com \
    --to=aristovski@qnx.com \
    --cc=gdb-patches@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