Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Paul Bolle <pebolle@tiscali.nl>
Subject: Re: [PATCH] tui-out: don't "inherit" redirect from CLI
Date: Mon, 30 Aug 2010 11:29:00 -0000	[thread overview]
Message-ID: <201008301229.12412.pedro@codesourcery.com> (raw)
In-Reply-To: <1283160550.10594.1.camel@localhost.localdomain>

On Monday 30 August 2010 10:29:10, Paul Bolle wrote:
> Since revision 1.17 tui_ui_out_impl "inherits" from cli_ui_out_impl (ie,
> it starts as a copy of that struct). tui_ui_out_impl.redirect is never
> redefined after that so it points to cli_redirect(). (Before revision
> 1.17 it was NULL.)

That was the main reason that tui_ui_out_impl was made to inherit
cli_ui_out_impl in the first place.
See <http://sourceware.org/ml/gdb-patches/2010-04/msg00540.html>.

> As a consequence, uo_redirect() will actually try to redirect if passed
> a tui_ui_out_impl. That will probably crash gdb (as
> tui_ui_out_impl->data->stream and tui_ui_out_impl->data->original_stream
> don't exist).

Yes they do exist, because tui_ui_out_data "inherits" cli_ui_out_data.
See:

struct tui_ui_out_data
  {
    struct cli_ui_out_data base;
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^

    int line;
    int start_of_line;
  };
typedef struct tui_ui_out_data tui_out_data;

"base" is the first field of tui_ui_out_data, so you can
pass a pointer to a tui_ui_out_data to a function that expects
a cli_ui_out_data pointer.  This is legal, and a common idiom on C,
as means to implementing "is-a" inheritance.

> 
> So set tui_ui_out_impl.redirect to NULL after "inheriting".

Nope, sorry, this isn't correct.

> (Just something I noticed while trying to understand the ui code.)

-- 
Pedro Alves


  reply	other threads:[~2010-08-30 11:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-30  9:29 Paul Bolle
2010-08-30 11:29 ` Pedro Alves [this message]
2010-08-30 11:49   ` Paul Bolle

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=201008301229.12412.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pebolle@tiscali.nl \
    /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