From: Mike Frysinger <vapier@gentoo.org>
To: tromey@redhat.com
Cc: Stan Shebs <stan@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Do partial xfers from trace file
Date: Tue, 13 Apr 2010 20:21:00 -0000 [thread overview]
Message-ID: <201004131620.03155.vapier@gentoo.org> (raw)
In-Reply-To: <m3aat7co8x.fsf@fleche.redhat.com>
[-- Attachment #1: Type: Text/Plain, Size: 866 bytes --]
On Tuesday 13 April 2010 12:26:38 Tom Tromey wrote:
> >>>>> "Stan" == Stan Shebs <stan@codesourcery.com> writes:
> >> tracepoint.c:3895: error: ignoring return value of ‘read’, declared
> >> with attribute warn_unused_result
>
> Stan> It's a little weird that some people get a complaint and others
> Stan> don't... In any case, it's just an oversight, all the other read
> Stan> results are being checked, and so I just committed the fix below.
>
> There is a distro difference here. Some distros have warn_unused_result
> enabled by default on some functions.
not exactly ... all distros that keep up with mainline glibc have this
enumeration. some distros (like Ubuntu and Gentoo) enable _FORTIFY_SOURCE by
default in their gcc which signals glibc to apply the warn_unused_result
attribute to a lot of functions (like read()).
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2010-04-13 20:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-05 22:11 Stan Shebs
2010-04-13 3:05 ` Mike Frysinger
2010-04-13 3:58 ` Stan Shebs
2010-04-13 16:27 ` Tom Tromey
2010-04-13 20:21 ` Mike Frysinger [this message]
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=201004131620.03155.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gdb-patches@sourceware.org \
--cc=stan@codesourcery.com \
--cc=tromey@redhat.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