Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: David Cogen <cogen@ll.mit.edu>
To: dan@cgsoftware.com
Cc: dan@cgsoftware.com, kettenis@wins.uva.nl,
	gdb@sourceware.cygnus.com, cogen@poblano
Subject: Re: gdb seg violation during print command
Date: Fri, 05 May 2000 13:16:00 -0000	[thread overview]
Message-ID: <200005052013.QAA23447@ll.mit.edu> (raw)
In-Reply-To: <66st9c39.fsf@dynamic-addr-88-42.resnet.rochester.edu>

> If C++ is your main language, i would suggest using the 5.0 branch until
> 5.0 is released (we are in release mode, have been for a few weeks. So 5.0
> is quite stable).  

I just downloaded, built, and tried GNU gdb 20000503. Now when I do print
tteesstt11(1) I no longer get the seg violation in gdb. 

:)

But now the other problem surfaces: "Cannot resolve function tteesstt11 to any
overloaded instance."

Apparently this problem was not related to class member functions (as I
implied earlier) but is an inability to evaluate any call to a C++ function,
even globals.

I also tried print ::tteesstt11(1); same error.

:(

Any idea what this might mean? Should I write this up as a detailed bug
report?

-- DavidC



       reply	other threads:[~2000-05-05 13:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <66st9c39.fsf@dynamic-addr-88-42.resnet.rochester.edu>
2000-05-05 13:16 ` David Cogen [this message]
     [not found] <bt2ne3cq.fsf@dynamic-addr-88-117.resnet.rochester.edu>
2000-05-04 11:06 ` David Cogen
     [not found] <200005041655.MAA10513@ll.mit.edu>
2000-05-04 10:41 ` Daniel Berlin
2000-05-04 10:42 ` Daniel Berlin
2000-05-04 12:40   ` David Cogen
     [not found] <200005031637.MAA25467@ll.mit.edu>
2000-05-03 10:59 ` Mark Kettenis

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=200005052013.QAA23447@ll.mit.edu \
    --to=cogen@ll.mit.edu \
    --cc=cogen@poblano \
    --cc=dan@cgsoftware.com \
    --cc=gdb@sourceware.cygnus.com \
    --cc=kettenis@wins.uva.nl \
    /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