public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "mstraub at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/9144] gdb assumes 4 byte separation between 64 bit "long long" and "unsigned long long" stack allocated (not pointers) data member types within a C++ class
Date: Tue, 19 Jan 2010 12:28:00 -0000	[thread overview]
Message-ID: <20100119122830.16700.qmail@sourceware.org> (raw)
In-Reply-To: <20051129155801.9144.mstraub@gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1503 bytes --]


------- Additional Comments From mstraub at gmail dot com  2010-01-19 12:28 -------
Subject: Re:  gdb assumes 4 byte separation between 64 bit "long 
	long" and "unsigned long long" stack allocated (not pointers) data member 
	types within a C++ class

We as an org upgraded to a more recent version of redhat as well as
SuSE a while back.  The problem disappeared at that time.
So its definitely not an issue on more recent versions of gdb.

If you haven't already, you can consider this bug unverifiable/fixed/closed.

Thanks
Michael Straub

On Mon, Jan 18, 2010 at 9:08 PM, tromey at redhat dot com
<sourceware-bugzilla@sourceware.org> wrote:
>
> ------- Additional Comments From tromey at redhat dot com  2010-01-19 02:08 -------
> Waiting for feedback for 4 years.
> Also, I tried this with recent gcc+gdb, and it worked fine.
>
>
> --
>           What    |Removed                     |Added
> ----------------------------------------------------------------------------
>             Status|ASSIGNED                    |RESOLVED
>         Resolution|                            |WORKSFORME
>
>
> http://sourceware.org/bugzilla/show_bug.cgi?id=9144
>
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
>


-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=9144

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


      parent reply	other threads:[~2010-01-19 12:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20051129155801.9144.mstraub@gmail.com>
2010-01-19  2:08 ` tromey at redhat dot com
2010-01-19 12:28 ` mstraub at gmail dot com [this message]

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=20100119122830.16700.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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).