public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "eric+sourceware at vangyzen dot net" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/13342] insufficient memory is fetched from the inferior for partially destroyed C++ objects
Date: Thu, 03 Nov 2011 19:17:00 -0000	[thread overview]
Message-ID: <bug-13342-4717-JGODF38Rmx@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13342-4717@http.sourceware.org/bugzilla/>

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

--- Comment #5 from Eric van Gyzen <eric+sourceware at vangyzen dot net> 2011-11-03 19:17:00 UTC ---
(In reply to comment #4)
> What is odd is that my 7.2 does exactly what my later builds do.

Woah.

> Does your build have local patches that might affect this?

I built via the FreeBSD ports collection, so it has local patches, but they're
mostly for FreeBSD threading.  I don't think any of the patches would affect
this, but I'm not a GDB expert (nor do I play one on TV).  You can see the
patches here:

    http://www.freebsd.org/cgi/cvsweb.cgi/ports/devel/gdb/files/

> Could you possibly try 7.3.1 or CVS HEAD?

I get the same behavior with 7.3.1, also built via the FreeBSD port.

CVS HEAD (as of five minutes ago) won't compile; it breaks in amd64-tdep.c. 
The FreeBSD port includes a patch for this file, but I didn't try applying it.

> Otherwise I am wondering whether it is somehow a compiler difference.

I get the same behavior with:
 - GCC 4.2.1 in the FreeBSD base system
 - GCC 4.5.3 from FreeBSD ports
 - LLVM/Clang 2.9 from FreeBSD ports

In all cases, I'm using GNU libstdc++ from GCC 4.2.1 (in the FreeBSD base
system).

I also get the same behavior on two other systems:
 - Ubuntu 10.04.2  x86_64  GCC 4.4.3  GDB 7.1
 - CentOS 5.3      x86_64  GCC 4.1.2  GDB 6.8

I get the same behavior whether I run with a live inferior with a breakpoint on
the abort(), or I run on an "Apple core" (nyuk nyuk).

Curiouser and curiouser.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  parent reply	other threads:[~2011-11-03 19:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-25 14:54 [Bug c++/13342] New: " eric+sourceware at vangyzen dot net
2011-10-25 15:16 ` [Bug c++/13342] " eric+sourceware at vangyzen dot net
2011-10-25 15:16 ` eric+sourceware at vangyzen dot net
2011-10-25 15:17 ` eric+sourceware at vangyzen dot net
2011-11-02 14:53 ` tromey at redhat dot com
2011-11-02 15:22 ` eric+sourceware at vangyzen dot net
2011-11-03 16:57 ` tromey at redhat dot com
2011-11-03 19:17 ` eric+sourceware at vangyzen dot net [this message]
2011-11-08 14:17 ` peter.schauer at mytum dot de
2011-11-08 15:51 ` tromey at redhat dot com
2011-11-08 16:39 ` eric+sourceware at vangyzen dot net
2011-11-09 19:24 ` tromey at redhat dot com
2011-11-09 19:50 ` cvs-commit at gcc dot gnu.org
2011-11-09 19:53 ` tromey at redhat dot com
2011-11-09 20:38 ` eric+sourceware at vangyzen dot net

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=bug-13342-4717-JGODF38Rmx@http.sourceware.org/bugzilla/ \
    --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).