Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Adam Fedor <fedor@doc.com>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: GDB Patches <gdb-patches@sources.redhat.com>
Subject: Re: [RFA]: Fix objc/1236 - printing non-debuggable symbols
Date: Mon, 22 Mar 2004 04:30:00 -0000	[thread overview]
Message-ID: <1079929809.1190.0.camel@localhost.localdomain> (raw)
In-Reply-To: <1077638167.19364.8.camel@localhost.localdomain>

On Tue, 2004-02-24 at 08:56, Adam Fedor wrote:
> On Mon, 2004-02-16 at 17:01, Elena Zannoni wrote:
> > Adam Fedor writes:
> >  > Fixes PR objc/1236
> >  > 
> >  > 2003-06-06  Adam Fedor  <fedor@gnu.org>
> >  > 
> >  > 	Fix objc/1236.
> >  > 	* gdb/linespec.c (decode_line_2): Print non-debuggable (minimal)
> >  > 	symbols.
> >  > 	(decode_objc): Update for change in arguments to decode_line_2
> >  > 	(find_methods): Likewise.
> >  > 
> > 
> > 
> > sorry for the delay, this got lost in my pile.  I see what you are
> > doing, but could you have 2 separate arrays of symbol pointers and of
> > msymbol pointers instead of concatenating the two? This way you would
> > also simplify the find_imps code (no need to swap the symbols and the
> > msymbols) and also the call to decode_line_2 in the c++ code would
> > look less weird, it could just pass NULL's.
> > 
> 
> Well I looked into doing this, but splitting up the arrays looks pretty
> ugly and more error prone than the other approach. Plus the arrays have
> to be combined eventually in decode_line_2 anyway. 

Ping.


      reply	other threads:[~2004-03-22  4:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-07  2:41 Adam Fedor
2003-06-17  3:30 ` Adam Fedor
2004-02-17  0:05 ` Elena Zannoni
2004-02-24 15:56   ` Adam Fedor
2004-03-22  4:30     ` Adam Fedor [this message]

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=1079929809.1190.0.camel@localhost.localdomain \
    --to=fedor@doc.com \
    --cc=ezannoni@redhat.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