From: Siva Chandra <sivachandra@google.com>
To: gdb-patches@sourceware.org
Subject: Re: [RFC - Python Scripting] Add 'end' attribute to gdb.Symtab_and_line
Date: Mon, 11 Jun 2012 09:17:00 -0000 [thread overview]
Message-ID: <CAGyQ6gw=o0-_CZYuACusuJzo1gKfOvHnjG8=QUtP6DYzTEoREw@mail.gmail.com> (raw)
In-Reply-To: <CAGyQ6gw7JP3Mz+nabiTGcnC4oP7d9iQ3W8miHOs3NnDyFqiF0g@mail.gmail.com>
I ping again.
Is it a good idea to expose the 'end' attribute in the Python API at all?
> 2012-05-21 Siva Chandra Reddy <sivachandra@google.com>
>
> New attribute 'end' for gdb.Symtab_and_line.
> * NEWS (Python Scripting): Add entry about the new attribute.
> * python/py-symtab.c (salpy_get_end): New function which
> implements the get method for the 'end' attribute of
> gdb.Symtab_and_line.
> (sal_object_getset): Add entry for the 'end' attribute.
>
> doc/
> * gdb.texinfo (Symbol Tables In Python): Add description about
> the new 'end' attribute of gdb.Symtab_and line.
>
> testsuite/
> * gdb.python/py-symtab.exp: Add tests to test the new attribute
> 'end' of gdb.Symtab_and_line.
> * gdb.python/py-symbol.c: Move break point comment to enable
> testing of gdb.Symtab_and_line.end.
>
> Thanks,
> Siva Chandra
next prev parent reply other threads:[~2012-06-11 9:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 8:40 Siva Chandra
2012-05-21 16:27 ` Eli Zaretskii
2012-06-01 19:57 ` Siva Chandra
2012-06-11 9:17 ` Siva Chandra [this message]
2012-06-11 21:22 ` Doug Evans
2012-06-12 18:41 ` Siva Chandra
2012-06-12 19:43 ` Eli Zaretskii
2012-06-13 7:24 ` Siva Chandra
2012-06-13 15:15 ` Eli Zaretskii
2012-06-13 13:29 ` Siva Chandra
2012-06-13 17:08 ` Doug Evans
2012-06-13 18:15 ` Siva Chandra
2012-06-22 9:21 ` Siva Chandra
2012-06-22 17:12 ` Tom Tromey
2012-06-22 21:12 ` Doug Evans
2012-06-24 17:03 ` Siva Chandra
2012-06-26 22:12 ` Doug Evans
2012-06-27 0:23 ` Siva Chandra
2012-06-22 17:10 ` Tom Tromey
2012-06-22 18:43 ` Siva Chandra
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='CAGyQ6gw=o0-_CZYuACusuJzo1gKfOvHnjG8=QUtP6DYzTEoREw@mail.gmail.com' \
--to=sivachandra@google.com \
--cc=gdb-patches@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