public inbox for insight-prs@sourceware.org
help / color / mirror / Atom feed
From: Ari.Kauppi@pac.fi
To: insight-gnats@sources.redhat.com
Subject: insight/122: Function browser problem with C++ const functions
Date: Mon, 28 Jan 2002 09:03:00 -0000	[thread overview]
Message-ID: <20020128165824.3436.qmail@sources.redhat.com> (raw)


>Number:         122
>Category:       insight
>Synopsis:       Function browser problem with C++ const functions
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Jan 28 09:03:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Ari.Kauppi@pac.fi
>Release:        Insight-5.1.1, CVS snapshot at 11-28-2001 16:40 GMT
>Organization:
>Environment:
Redhat Linux 7.1 on i386 running on AMD Athlon 1Ghz
>Description:
Function selector doesn't work correctly for functions like int foo() const; Appears at least at function browser and source browser. See attachment with functions returnA and returnB. Probably trivial to fix but don't know enough tcl and gdb internals.
>How-To-Repeat:
g++ -g -o foo foo.C && gdb foo
Try function browsing for int returnA(); and int returnB() const;
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="foo.C"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="foo.C"

Y2xhc3MgZm9vCnsKcHVibGljOgogIGludCByZXR1cm5BKCk7CiAgaW50IHJldHVybkIoKSBjb25z
dDsKCn07CgppbnQgZm9vOjpyZXR1cm5BKCkKewogIHJldHVybiAxOwp9CgppbnQgZm9vOjpyZXR1
cm5CKCkgY29uc3QKewogIHJldHVybiAxOwp9CgppbnQgbWFpbihpbnQgYXJnYywgY2hhciAqYXJn
dltdKQp7CiAgcmV0dXJuIDA7Cn0K


                 reply	other threads:[~2002-01-28 17:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20020128165824.3436.qmail@sources.redhat.com \
    --to=ari.kauppi@pac.fi \
    --cc=insight-gnats@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).