Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: "Robert Norton" <rnorton@broadcom.com>
Cc: gdb@sourceware.org
Subject: RE: Segfault in varobj.c
Date: Fri, 27 Jul 2007 12:52:00 -0000	[thread overview]
Message-ID: <18089.57854.615639.287461@kahikatea.snap.net.nz> (raw)
In-Reply-To: <B0D822BFECD50F4991F2516EA50F273C01FEB539@NT-IRVA-0752.brcm.ad.broadcom.com>

 > > This is your port of GDB and it's based on an old version of FSF GDB.
 > > Does it happen with FSF GDB or, at least, your port based on up-to-date
 > > FSF GDB?
 > 
 > The port is based on GDB 6.6.

By up-to-date I meant GDB in CVS.  Presumably you could merge your changes to
that.  It may be that the problem has already been solved or no longer exists
in the repository.

-- 
Nick                                           http://www.inet.net.nz/~nickrob


  reply	other threads:[~2007-07-27 12:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-27 11:51 Robert Norton
2007-07-27 12:03 ` Nick Roberts
2007-07-27 12:16   ` Robert Norton
2007-07-27 12:52     ` Nick Roberts [this message]
2007-07-27 13:07       ` Robert Norton
2007-07-27 14:30         ` 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=18089.57854.615639.287461@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=gdb@sourceware.org \
    --cc=rnorton@broadcom.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