From: jose.marchesi@oracle.com (Jose E. Marchesi)
To: Pedro Alves <palves@redhat.com>
Cc: Steve Ellcey <sellcey@imgtec.com>,
Sergio Durigan Junior <sergiodj@redhat.com>,
gdb-patches@sourceware.org
Subject: Re: Build failure with probe patch
Date: Thu, 19 Feb 2015 20:11:00 -0000 [thread overview]
Message-ID: <87lhjtzmf2.fsf@oracle.com> (raw)
In-Reply-To: <54E62BCB.80600@redhat.com> (Pedro Alves's message of "Thu, 19 Feb 2015 18:30:35 +0000")
> Yes, but not the other way around... it is not allowed to alias a
> character type with a non-character type like in the following call to
> dtrace_process_dof:
Ah, right.
> gdb_byte *buf;
> [...]
> dtrace_process_dof (sect, objfile, probesp, (struct dtrace_dof_hdr *) buf);
Hmm, still, but I think this may be alright.
gdb_bfd_map_section and bfd_get_full_section_contents return
allocated objects, which have no declared type to begin with
(C99 6.5/6, footnote 75).
Then per C99 6.5/6, since the allocated object is never written
through an lvalue with a type that is not a character type, then
the effective type of the object is "simply the type of the
lvalue used for the access."
So it seems to me that casting to struct dtrace_dof_hdr * and then
reading from that lvalue is OK: from that point on, the object
pointed at by BUF has effective type struct dtrace_dof_hdr.
Good point! Yes, I agree. Both bfd_byte and gdb_byte are character
types, so the object returned by either bfd_malloc_and_get_section or
gdb_bfd_map_section must retain the property of not having a declared
type.
next prev parent reply other threads:[~2015-02-19 20:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-18 17:51 Steve Ellcey
2015-02-18 23:58 ` Sergio Durigan Junior
2015-02-19 0:48 ` Steve Ellcey
2015-02-19 4:39 ` Sergio Durigan Junior
2015-02-19 15:55 ` Jose E. Marchesi
2015-02-19 16:53 ` Pedro Alves
2015-02-19 17:32 ` Jose E. Marchesi
2015-02-19 17:48 ` Steve Ellcey
2015-02-19 20:41 ` Jose E. Marchesi
2015-02-19 21:18 ` Sergio Durigan Junior
2015-02-19 21:48 ` Steve Ellcey
2015-02-19 21:52 ` Sergio Durigan Junior
2015-02-19 21:59 ` Steve Ellcey
2015-02-19 18:30 ` Pedro Alves
2015-02-19 20:11 ` Jose E. Marchesi [this message]
2015-02-19 10:43 ` Pedro Alves
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=87lhjtzmf2.fsf@oracle.com \
--to=jose.marchesi@oracle.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=sellcey@imgtec.com \
--cc=sergiodj@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