From: Elena Zannoni <ezannoni@redhat.com>
To: David Ayers <d.ayers@inode.at>
Cc: Adam Fedor <fedor@doc.com>,
"gdb-patches@sources.redhat.com" <gdb-patches@sources.redhat.com>
Subject: Re: [RFC]: Better ObjC symbol skipping in decode_line_1
Date: Mon, 08 Sep 2003 18:43:00 -0000 [thread overview]
Message-ID: <16220.53209.420727.819654@localhost.redhat.com> (raw)
In-Reply-To: <3F5C882D.4010208@inode.at>
David Ayers writes:
> Adam Fedor wrote:
>
> >This patch fixes a problem with ObjC symbols not being properly skipped
> >over during decode_line_1 processing. ObjC symbols can have spaces and
> >parenthesis in them, so they need special handling, otherwise you get
> >odd warnings like:
> >
> >Error in re-setting breakpoint 2:
> >Function "-[NSObject(NEXTSTEP)" not defined.
> >
> >or
> >
> >Error in re-setting breakpoint 2:
> >Function "" not defined.
> >
> >
> >
> >
> >
> >------------------------------------------------------------------------
> >
> >2003-07-31 Adam Fedor <fedor@gnu.org>
> >
> > * gdb/linespec.c (is_objc_method_format): New function
> > (decode_line_1, locate_first_half): Use it.
> >
> >
> I know Adam has asked this before, but I'm unsure if there was a
> definite reply, so let me reiterate...
>
> Can this patch go into 6.0? (Please... :-) )
>
> It really makes ObjC support look much better on its debut, and as
> Michael Chastain already mentioned, it has been on mainline for quite
> some time now working beautifully.
>
> Cheers,
> David Ayers
>
I don't think it would do any harm on gdb-6. So it could go in, if
changes are still allowed.
elena
next prev parent reply other threads:[~2003-09-08 18:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-31 15:05 Adam Fedor
2003-07-31 16:32 ` Elena Zannoni
2003-09-08 13:46 ` David Ayers
2003-09-08 18:43 ` Elena Zannoni [this message]
2003-09-08 18:58 ` Andrew Cagney
2003-09-09 3:58 ` Adam Fedor
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=16220.53209.420727.819654@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=d.ayers@inode.at \
--cc=fedor@doc.com \
--cc=gdb-patches@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