From: Andrew STUBBS <andrew.stubbs@st.com>
To: Andrew Stubbs <andrew.stubbs@st.com>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sources.redhat.com
Subject: Re: PATCH: Problem union comparision in TUI
Date: Thu, 20 Oct 2005 16:20:00 -0000 [thread overview]
Message-ID: <4357C346.8070400@st.com> (raw)
In-Reply-To: <43576E68.8080804@st.com>
Andrew Stubbs wrote:
> Eli Zaretskii wrote:
>> Yes, I've read the code before I replied, so I know all that already.
>> Having read the code, I'm not sure that addresses are used only for
>> disassembly windows and line numbers only for source windows. We
>> could have more bugs; that's why I think cleaning the code is
>> important.
>
>
> Indeed, it isn't as simple as addresses for assembly and lines for
> sources. That's what the original problem was - i686-pc-linux-gnu native
> uses one and sh-elf cross (also running on i686-pc-linux-gnu) uses the
> other while both are supposedly running the same simple program .
Apologies, please ignore this. I have just done some experiments to try
to understand this better.
It would appear that both are using line numbers for the source window.
The difference is that, for reasons unknown, sh-elf has a 64 bit
CORE_ADDR, but i686-pc-linux-gnu has a 32 bit CORE_ADDR. line_no remains
32 bit on both platforms. Hence I only see the problem on targets with
mismatched types, and then only when random data manages to find its way
into the unused half of the union.
Therefore, an alternative fix for this problem would be to figure out
which window we are in for the problem comparison. I an not sure whether
that would be a better solution or not.
Sorry for the confusion.
Andrew Stubbs
next prev parent reply other threads:[~2005-10-20 16:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-17 14:52 Andrew STUBBS
2005-10-17 15:02 ` Andrew STUBBS
2005-10-19 9:15 ` Eli Zaretskii
2005-10-19 9:51 ` Andrew STUBBS
2005-10-19 12:28 ` Daniel Jacobowitz
2005-10-19 16:22 ` Andrew STUBBS
2005-10-19 20:03 ` Eli Zaretskii
2005-10-19 20:08 ` Daniel Jacobowitz
2005-10-19 20:22 ` Mark Kettenis
2005-10-20 8:43 ` Eli Zaretskii
2005-10-20 10:18 ` Andrew STUBBS
2005-10-20 16:20 ` Andrew STUBBS [this message]
2005-10-20 17:56 ` Daniel Jacobowitz
2005-10-20 19:41 ` Eli Zaretskii
2005-10-21 14:55 ` Andrew STUBBS
2005-10-21 16:39 ` Daniel Jacobowitz
2005-10-21 22:03 ` Eli Zaretskii
2005-10-21 22:13 ` Eli Zaretskii
2005-10-24 10:28 ` Andrew STUBBS
2005-10-24 11:06 ` Eli Zaretskii
2005-10-24 12:56 ` Andrew STUBBS
2005-10-25 10:45 ` Eli Zaretskii
2005-11-01 16:24 ` Andrew STUBBS
2005-11-01 16:28 ` Daniel Jacobowitz
2005-11-01 17:43 ` Andrew STUBBS
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=4357C346.8070400@st.com \
--to=andrew.stubbs@st.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.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