Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@redhat.com>
To: Adam Fedor <fedor@doc.com>
Cc: "gdb-patches@sources.redhat.com" <gdb-patches@sources.redhat.com>
Subject: Re: [RFC]: Better ObjC symbol skipping in decode_line_1
Date: Thu, 31 Jul 2003 16:32:00 -0000	[thread overview]
Message-ID: <16169.17992.496513.990509@localhost.redhat.com> (raw)
In-Reply-To: <1059663909.1116.23.camel@localhost.localdomain>

Adam Fedor writes:
 > 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 like this. A function clearly marked as objC only.  Another place
where language specific behavior is necessary. One day we'll move all
these to a proper place....

until then, ok.

elena


 > 
 > Index: linespec.c
 > ===================================================================
 > RCS file: /cvs/src/src/gdb/linespec.c,v
 > retrieving revision 1.49.4.1
 > diff -u -p -r1.49.4.1 linespec.c
 > --- linespec.c	23 Jul 2003 19:28:35 -0000	1.49.4.1
 > +++ linespec.c	31 Jul 2003 14:43:47 -0000
 > @@ -94,6 +94,8 @@ static void build_canonical_line_spec (s
 >  
 >  static char *find_toplevel_char (char *s, char c);
 >  
 > +static int is_objc_method_format (const char *s);
 > +
 >  static struct symtabs_and_lines decode_line_2 (struct symbol *[],
 >  					       int, int, char ***);
 >  
 > @@ -443,6 +445,25 @@ find_toplevel_char (char *s, char c)
 >    return 0;
 >  }
 >  
 > +/* Determines if the gives string corresponds to an Objective-C method
 > +   representation, such as -[Foo bar:] or +[Foo bar]. Objective-C symbols
 > +   are allowed to have spaces and parentheses in them.  */
 > +
 > +static int 
 > +is_objc_method_format (const char *s)
 > +{
 > +  if (s == NULL || *s == '\0')
 > +    return 0;
 > +  /* Handle arguments with the format FILENAME:SYMBOL.  */
 > +  if ((s[0] == ':') && (strchr ("+-", s[1]) != NULL) 
 > +      && (s[2] == '[') && strchr(s, ']'))
 > +    return 1;
 > +  /* Handle arguments that are just SYMBOL.  */
 > +  else if ((strchr ("+-", s[0]) != NULL) && (s[1] == '[') && strchr(s, ']'))
 > +    return 1;
 > +  return 0;
 > +}
 > +
 >  /* Given a list of NELTS symbols in SYM_ARR, return a list of lines to
 >     operate on (ask user if necessary).
 >     If CANONICAL is non-NULL return a corresponding array of mangled names
 > @@ -669,8 +690,7 @@ decode_line_1 (char **argptr, int funfir
 >  
 >    /* Check if this is an Objective-C method (anything that starts with
 >       a '+' or '-' and a '[').  */
 > -  if (*p && (p[0] == ':') && (strchr ("+-", p[1]) != NULL) 
 > -      && (p[2] == '['))
 > +  if (is_objc_method_format (p))
 >      {
 >        is_objc_method = 1;
 >        paren_pointer  = NULL; /* Just a category name.  Ignore it.  */
 > @@ -972,8 +992,7 @@ locate_first_half (char **argptr, int *i
 >  	}
 >        /* Check for a colon and a plus or minus and a [ (which
 >           indicates an Objective-C method) */
 > -      if (*p && (p[0] == ':') && (strchr ("+-", p[1]) != NULL) 
 > -	  && (p[2] == '['))
 > +      if (is_objc_method_format (p))
 >  	{
 >  	  break;
 >  	}


  reply	other threads:[~2003-07-31 16:32 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 [this message]
2003-09-08 13:46 ` David Ayers
2003-09-08 18:43   ` Elena Zannoni
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=16169.17992.496513.990509@localhost.redhat.com \
    --to=ezannoni@redhat.com \
    --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