public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "richard_sharman at mitel dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/19068] gdb cannot handle operator= if both const access (as rhs) and non-const (lhs) methods defined
Date: Mon, 05 Oct 2015 18:13:00 -0000	[thread overview]
Message-ID: <bug-19068-4717-ss0dctoo2I@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-19068-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=19068

--- Comment #2 from Richard Sharman <richard_sharman at mitel dot com> ---
If a class is defined with a single operator[] method,
then gdb can invoke this method with the normal x[i] syntax.

If, however,  there are separate const "rhs" and non-const "lhs" 
methods defined,  then trying to print or assign using x[i] syntax
produces the message "Could not find operator[].".

See example t.c.  When compiled as is (SEPARATE_SUB_METHODS defined)
there are methods 
        const T& operator[](const int index) const 
and
        T& operator[](const int index) {

Running gdb shows:

(gdb) b 53
Breakpoint 1 at 0x40076a: file t.cc, line 53.
(gdb) r
(gdb) p x
$1 = {storage = {10, 20, 30, 40, 50, 60, 70, 80, 90, 100}}
(gdb) p x[3]
Could not find operator[].
(gdb) show version
GNU gdb (GDB) 7.10
Copyright (C) 2015 Free Software Foundation, Inc.


When SEPARATE_SUB_METHODS is undefined there is only one method
        T& operator[](const int index)  {
and gdb works fine with this:

(gdb) b 53
Breakpoint 1 at 0x40076a: file t2.cc, line 53.
(gdb) r
Starting program: /localhome/sharman/tmp/c++test/t2 

Breakpoint 1, main (NameError: Installation error: gdb.execute_unwinders
function is missing

argc=1, argv=0x7fffffffdbc8) at t2.cc:53
53              printf("%2d: %d\n", i, x[i]);
(gdb) p x
$1 = {storage = {10, 20, 30, 40, 50, 60, 70, 80, 90, 100}}
(gdb) p x[3]
NameError: Installation error: gdb.execute_unwinders function is missing
$2 = (int &) @0x7fffffffdab8: 30
(gdb) set var x[3] = 33
(gdb) p x[3]
$3 = (int &) @0x7fffffffdab8: 33
(gdb) p x
$4 = {storage = {10, 20, 33, 40, 50, 60, 70, 80, 90, 100}}
(gdb)

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2015-10-05 18:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-05 18:11 [Bug c++/19068] New: " richard_sharman at mitel dot com
2015-10-05 18:12 ` [Bug c++/19068] " richard_sharman at mitel dot com
2015-10-05 18:13 ` richard_sharman at mitel dot com [this message]
2023-12-27 16:46 ` ssbssa at sourceware dot org

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-19068-4717-ss0dctoo2I@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).