From: Diego Novillo <dnovillo@google.com>
To: Justin Lebar <justin.lebar@gmail.com>
Cc: Tom Tromey <tromey@redhat.com>, Lawrence Crowl <crowl@google.com>,
gdb-patches@sourceware.org
Subject: Re: Status of 'blacklist' patch?
Date: Thu, 06 Oct 2011 17:19:00 -0000 [thread overview]
Message-ID: <CAD_=9DSzgE58GQLRDD6OSTpQKB7PsOyoH7RzEp22bKudnKMwDw@mail.gmail.com> (raw)
In-Reply-To: <CAFWcpZ7z8NjJ1T-cL2=JQO=5a+8e9t4r=_7aA1Nnds-gQZc74A@mail.gmail.com>
On Thu, Oct 6, 2011 at 10:07, Justin Lebar <justin.lebar@gmail.com> wrote:
> I last pinged gdb-patches about the patch on May 16 and got no response.
>
> I imagine the patch has bitrotted by now. I'd be happy to bring it up
> to date if there were a reasonable chance it would get reviewed this
> time.
Thanks. I would very much like to see it in GDB but I have no real
way of making it happen other than to generate user demand for it.
Over on GCC, we are discussing converting some macros into one-liner
inline functions and we want to avoid the mess this would cause for
'step' in the presence of things like foo(f(g()), h()).
One additional request that came up in the thread I pointed you to
(http://gcc.gnu.org/ml/gcc-patches/2011-10/msg00324.html) is Jakub's
request to blacklist DW_AT_artificial functions by default. I think
that's a good idea.
Thanks. Diego.
next prev parent reply other threads:[~2011-10-06 17:19 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-06 12:12 Diego Novillo
2011-10-06 14:08 ` Justin Lebar
2011-10-06 15:51 ` Stan Shebs
2011-10-06 20:16 ` Justin Lebar
2011-10-10 12:34 ` Stan Shebs
2011-10-11 21:34 ` Justin Lebar
2011-10-11 23:54 ` Doug Evans
2011-10-16 19:22 ` Justin Lebar
2011-10-20 19:46 ` Tom Tromey
2011-10-25 20:07 ` Justin Lebar
2011-10-25 20:41 ` Pedro Alves
2011-10-25 21:25 ` Justin Lebar
2011-10-20 20:40 ` Eli Zaretskii
2011-10-25 16:47 ` Justin Lebar
2011-10-25 16:53 ` Eli Zaretskii
2011-10-25 19:52 ` Justin Lebar
2011-10-25 20:13 ` Eli Zaretskii
2011-10-25 20:30 ` Justin Lebar
2011-10-26 1:06 ` Stan Shebs
2011-10-26 3:45 ` Justin Lebar
2011-10-26 5:37 ` Stan Shebs
2011-10-26 8:10 ` Joel Brobecker
2011-10-26 13:28 ` Eli Zaretskii
2011-10-26 15:11 ` Justin Lebar
2011-10-28 18:18 ` Tom Tromey
2011-10-28 19:48 ` Justin Lebar
2011-10-28 19:53 ` Tom Tromey
2011-10-28 19:49 ` Tom Tromey
2011-10-28 19:55 ` Justin Lebar
2011-10-28 20:37 ` Tom Tromey
2011-10-31 15:52 ` Justin Lebar
[not found] ` <4EAF2E0E.7080508@earthlink.net>
2011-11-01 14:53 ` Justin Lebar
2011-11-02 22:43 ` Maciej W. Rozycki
2011-11-02 23:52 ` Stan Shebs
2011-11-03 0:20 ` Maciej W. Rozycki
2011-11-03 3:54 ` Eli Zaretskii
2011-11-03 14:32 ` Tom Tromey
2011-11-03 16:54 ` Eli Zaretskii
2011-11-03 18:04 ` Maciej W. Rozycki
2011-11-03 18:25 ` Eli Zaretskii
2011-11-03 19:01 ` Stan Shebs
2011-10-06 17:19 ` Diego Novillo [this message]
2011-10-06 17:33 ` Tom Tromey
2011-10-06 17:37 ` Diego Novillo
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='CAD_=9DSzgE58GQLRDD6OSTpQKB7PsOyoH7RzEp22bKudnKMwDw@mail.gmail.com' \
--to=dnovillo@google.com \
--cc=crowl@google.com \
--cc=gdb-patches@sourceware.org \
--cc=justin.lebar@gmail.com \
--cc=tromey@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