From: Pedro Alves <palves@redhat.com>
To: Andreas Arnez <arnez@linux.vnet.ibm.com>
Cc: Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>,
Jan Kratochvil <jan.kratochvil@redhat.com>,
gdb-patches@sourceware.org,
Ulrich Weigand <uweigand@de.ibm.com>,
Andreas Krebbel <krebbel@linux.vnet.ibm.com>,
Omair Javaid <omair.javaid@linaro.org>
Subject: Re: [PATCH] Fix possible alignment issue with dw2-dir-file-name test case
Date: Wed, 22 Jan 2014 13:15:00 -0000 [thread overview]
Message-ID: <52DFC458.4080105@redhat.com> (raw)
In-Reply-To: <87zjmq1lmv.fsf@br87z6lw.de.ibm.com>
On 01/20/2014 07:47 PM, Andreas Arnez wrote:
> * On s390x, the test case fails like this:
>
> Breakpoint 1, 0x00000000800005d2 in func (param=<error reading
> variable: Cannot access memory at address 0x0>)
> (gdb) p/x param
> Cannot access memory at address 0x0
>
> Note that the debug info looks correct, and all addresses fit into
> four bytes. Still, the failure disappears when changing the DWARF
> pointer size to 8. Thus it seems that the address size mismatch
> causes confusion somewhere in GDB on big-endian systems.
Hmm, yeah. A little odd that dw2-dir-file-name also uses .byte 4
and doesn't have this issue.
> * On PPC64, 'func' and 'main' are function descriptors and don't point
> to the actual code. Thus the usage of these symbols in
> dw2-ifort-parameter-debug.S is broken (similar to what has been
> discussed in the thread, I think).
Thanks. I believe this alone would fix Thumb. I think this bit should
go in as is (maybe with a comment), and independently of whatever
is the fix for the 64-bit issue.
--
Pedro Alves
next prev parent reply other threads:[~2014-01-22 13:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 18:00 Andreas Arnez
2014-01-10 11:29 ` Pedro Alves
2014-01-10 14:30 ` Andreas Arnez
2014-01-10 14:53 ` Jan Kratochvil
2014-01-10 16:39 ` Pedro Alves
2014-01-15 21:33 ` Edjunior Barbosa Machado
2014-01-16 14:37 ` Pedro Alves
2014-01-17 17:58 ` Andreas Arnez
2014-01-17 18:09 ` Pedro Alves
2014-01-17 18:20 ` Pedro Alves
2014-01-20 19:47 ` Andreas Arnez
2014-01-22 13:15 ` Pedro Alves [this message]
2014-01-17 18:21 ` Edjunior Barbosa Machado
2014-01-22 16:13 ` Andreas Krebbel
2014-01-10 15:32 ` 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=52DFC458.4080105@redhat.com \
--to=palves@redhat.com \
--cc=arnez@linux.vnet.ibm.com \
--cc=emachado@linux.vnet.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=krebbel@linux.vnet.ibm.com \
--cc=omair.javaid@linaro.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).