Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org
Subject: Re: Alternative to deprecated_init_ui_hook?
Date: Tue, 01 Nov 2005 16:25:00 -0000	[thread overview]
Message-ID: <20051101162503.GA29820@nevyn.them.org> (raw)
In-Reply-To: <20051101143724.GB6427@trixie.casa.cgf.cx>

On Tue, Nov 01, 2005 at 09:37:24AM -0500, Christopher Faylor wrote:
> On Tue, Nov 01, 2005 at 08:52:52AM -0500, Daniel Jacobowitz wrote:
> >On Tue, Nov 01, 2005 at 12:35:36AM -0500, Christopher Faylor wrote:
> >>In cleaning up the cygwin gdb shared library handling, I'm now able to
> >>use the "info sharedlibrary" command from solib.c.  Previously this
> >>command was implemented in win32-nat.c but now that is no longer
> >>necessary.
> >>
> >>There was previously an alias for this command -- "info dll".  I'm not
> >>having much luck adding this alias now because "info sharedlibrary" is
> >>set up after _initialize_win32 is called in init.cc -- a standard
> >>problem, IIRC.
> >>
> >>I've resorted to using deprecated_init_ui_hook to set this alias and
> >>that works but, given that the function begins with the word
> >>"deprectated", I would rather not use this method.
> >>
> >>Is there any other way to add this alias, though?  I don't see anything
> >>obvious and I don't want to remove a command that cygwin gdb users may
> >>have become accustomed to.
> >
> >Could you register it as a command rather than an alias, by exporting
> >the implementing function from solib.c?
> 
> Yes, if the function in solib.c was made global, I could just call it in
> win32-nat.c.  That seems "wrong" somehow, though.

I think you need to either do that, or else add the "info dll" alias in
solib.c.  Neither pretty.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


      reply	other threads:[~2005-11-01 16:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-01  5:35 Christopher Faylor
2005-11-01 13:53 ` Daniel Jacobowitz
2005-11-01 14:37   ` Christopher Faylor
2005-11-01 16:25     ` Daniel Jacobowitz [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=20051101162503.GA29820@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb@sourceware.org \
    /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