Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Avi Gozlan <avi@checkpoint.com>
Cc: "'gdb\@sourceware.org'" <gdb@sourceware.org>,
	       Matan Ben Gur <matanbg@checkpoint.com>
Subject: Re: Differentiating symbols in multiple copies of shared libraries
Date: Thu, 27 Jan 2011 20:52:00 -0000	[thread overview]
Message-ID: <m339oem5n0.fsf@fleche.redhat.com> (raw)
In-Reply-To: <9C4E85B61203CD419BB3A638E5F6833301A393C916FA@il-ex01.ad.checkpoint.com>	(Avi Gozlan's message of "Sun, 23 Jan 2011 14:07:21 +0200")

>>>>> "Avi" == Avi Gozlan <avi@checkpoint.com> writes:

Avi> A developer in our organization added some code to allow
Avi> differentiation between symbols with the same name in different
Avi> object files. This feature is enabled once a GDB variable called
Avi> symlib is set.

Avi> Presumably this addition is not written according to GNU policy or
Avi> GDB conventions, yet this feature is important as discussed below.

Avi> Could you recommend on a procedure for promoting this required
Avi> feature (or anyway merge the source code to GDB)? Is there any
Avi> contact for working with for forwarding the implementation
Avi> (currently diff in 4 files: minsym.c, stack.c, symtab.h, symtab.c)?

I think the best thing to do is to follow the usual patch submission
rules: do your best to make it conform to GNU style guidelines, write a
ChangeLog entry, etc, then send it to the gdb-patches list.

Since it sounds like a big(-ish) patch, I will get you started on the
copyright assignment paperwork.  I'll send a note off-list about this.


I would warn you to expect some push-back on the details of your
approach.  If you want to work out the user interface details before
submitting, that would be fine too -- just post your plan to this list.

Tom


      reply	other threads:[~2011-01-27 20:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-09 15:50 Avi Gozlan
2010-12-09 21:53 ` Tom Tromey
2011-01-23 12:07   ` Avi Gozlan
2011-01-27 20:52     ` Tom Tromey [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=m339oem5n0.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=avi@checkpoint.com \
    --cc=gdb@sourceware.org \
    --cc=matanbg@checkpoint.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