Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc] Relax "printf" function name check in annota* test cases
Date: Thu, 15 May 2008 12:09:00 -0000	[thread overview]
Message-ID: <20080515003926.GA3331@caradoc.them.org> (raw)
In-Reply-To: <200805142245.m4EMjopF021777@d12av02.megacenter.de.ibm.com>

On Thu, May 15, 2008 at 12:45:50AM +0200, Ulrich Weigand wrote:
> B.t.w. even if we were to handle versioned symbols (I have a patch
> for that), the original annota test cases would still break -- 
> because the function would then be called printf@GLIBC...

Ok, thanks.  This patch sounds like the right thing to me then!

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-05-15  0:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-15  0:37 Ulrich Weigand
2008-05-15  0:45 ` Daniel Jacobowitz
2008-05-15  0:54   ` Ulrich Weigand
2008-05-15 12:09     ` Daniel Jacobowitz [this message]
2008-05-16 15:27       ` Ulrich Weigand

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=20080515003926.GA3331@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=uweigand@de.ibm.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