Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>,
	       gdb-patches@sourceware.org
Subject: Re: [PATCH v4 2/2] Eliminate make_cleanup_ui_file_delete / make ui_file a class hierarchy
Date: Tue, 07 Mar 2017 14:02:00 -0000	[thread overview]
Message-ID: <28282f40-5d24-774e-3fe7-de477d054e95@redhat.com> (raw)
In-Reply-To: <09bae426-d169-6300-0850-eb5d3d87da25@linux.vnet.ibm.com>

Hi Edjunior,

On 02/27/2017 07:43 PM, Edjunior Barbosa Machado wrote:

> Hi Pedro,
> 
> from bisect, it seems commit d7e747 introduced a problem when using
> layout regs, that leads gdb to crash when issuing:
> 
> ./gdb ./a.out -ex 'layout regs' -ex start
> 
> From the backtrace, it's caused by this 'delete' on tui_restore_gdbout(): 

Thanks for the bisect.  This is fixed in master now.

Thanks,
Pedro Alves


      reply	other threads:[~2017-03-07 14:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-01  0:30 [PATCH v4 0/2] Eliminate cleanups & make ui_file a C++ " Pedro Alves
2017-02-01  0:30 ` [PATCH v4 1/2] Add back gdb_pretty_print_insn Pedro Alves
2017-02-01 17:01   ` Luis Machado
2017-02-01 18:10   ` Simon Marchi
2017-02-01 18:26     ` Simon Marchi
2017-02-02  0:00       ` Pedro Alves
2017-02-01 20:02     ` Pedro Alves
2017-02-01 20:31       ` Pedro Alves
2017-02-01 23:50         ` Pedro Alves
2017-02-02  1:20           ` Simon Marchi
2017-02-02 11:37             ` [pushed] Reuse buffers across gdb_pretty_print_insn calls (Re: [PATCH v4 1/2] Add back gdb_pretty_print_insn) Pedro Alves
2017-02-01  0:31 ` [PATCH v4 2/2] Eliminate make_cleanup_ui_file_delete / make ui_file a class hierarchy Pedro Alves
2017-02-01 17:37   ` Luis Machado
2017-02-01 22:49     ` Pedro Alves
2017-02-01 23:24       ` Luis Machado
2017-02-02  0:02         ` Pedro Alves
2017-02-27 19:43           ` Edjunior Barbosa Machado
2017-03-07 14:02             ` Pedro Alves [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=28282f40-5d24-774e-3fe7-de477d054e95@redhat.com \
    --to=palves@redhat.com \
    --cc=emachado@linux.vnet.ibm.com \
    --cc=gdb-patches@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