Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Kei Sakamoto <sakamoto.kei@renesas.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/testcase] fix gdb.base/relocate.c
Date: Tue, 08 Jul 2003 02:58:00 -0000	[thread overview]
Message-ID: <20030708025830.GA27558@nevyn.them.org> (raw)
In-Reply-To: <014401c344fc$7b0972d0$5169910a@KEI>

On Tue, Jul 08, 2003 at 11:56:07AM +0900, Kei Sakamoto wrote:
> The attached patch fixes gdb.base/relocate.c.
> 
> "relocate.exp: get address of function_bar" fails with m32r-elf-gdb
> as the following:
> 
> print &function_bar
> $6 = (int (*)(void)) 0xc <global_bar>
> (gdb) FAIL: gdb.base/relocate.exp: get address of function_bar (unknown output)
> 
> Both function_bar and global_bar have the same address, 0xc.
> Though they belong to different sections, gdb considers they
> are the same and prints global_bar's data instead of
> function_bar's.
> 
> The same error happens with i386 if line 4 and 5 of relocate.c
> are modified as the following:
> 
> short global_foo = 3;
> short global_bar = 4;
> 
> I guess this is not gdb's bug but a feature and the testcase
> should be modified. So I made a patch file.
> 
> The attached patch inserts a definition of a dummy array so that
> global_bar and function_bar should not have the same address.
> 
> Kei
> 
> 2003-07-08    Kei Sakamoto  <sakamoto.kei@renesas.com>
> 
>  * gdb.base/relocate.c : Add a dummy array to make global_bar
>         and function_bar have different addresses.

Ugh, this is OK, since the test can only reliably specify an offset for
.text.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-07-08  2:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-08  2:53 Kei Sakamoto
2003-07-08  2:58 ` Daniel Jacobowitz [this message]
2003-07-24 18:47   ` Daniel Jacobowitz

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=20030708025830.GA27558@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=sakamoto.kei@renesas.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