public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: Alon Bar-Lev <alon.barlev@gmail.com>
Cc: insight@sourceware.org
Subject: Re: gdb/gdbtk/generic/gdbtk-stack.c - fail due to strict aliasing
Date: Mon, 27 Oct 2008 18:43:00 -0000	[thread overview]
Message-ID: <49060B89.2000406@redhat.com> (raw)
In-Reply-To: <200810260107.31955.alon.barlev@gmail.com>

Alon Bar-Lev wrote:

> Reported as binutils bug#6986 [1]
> 
> arguments = *(int*) &clientData;

Thank you for the patch: it's not quite correct, but then the existing 
code is completely wrong. That got really botched somehow: clientData is 
an int, not an int*. I don't know how I messed that up. O:-)

I've committed a proper fix. Or at least I think I have, since gcc 4.4.0 
no longer complains about this. Let me know if this still presents 
problems for you.

I'm remaking the snapshot to include this patch.

Keith

  parent reply	other threads:[~2008-10-27 18:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-25 23:08 Alon Bar-Lev
2008-10-26 17:15 ` Martin Rakhmanov
2008-10-27 18:43 ` Keith Seitz [this message]
2008-10-30 23:11   ` Gene Smith

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=49060B89.2000406@redhat.com \
    --to=keiths@redhat.com \
    --cc=alon.barlev@gmail.com \
    --cc=insight@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).