Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Simon Marchi <simark@simark.ca>
Cc: gdb@sourceware.org, gdb-patches@sourceware.org
Subject: Re: Breakpoint commands in MI mode and "backtrace"
Date: Sat, 21 Oct 2017 16:27:00 -0000	[thread overview]
Message-ID: <83mv4kbh61.fsf@gnu.org> (raw)
In-Reply-To: <f54ff4bc-fb7c-397f-153d-83cafb6966bd@simark.ca> (message from	Simon Marchi on Sat, 21 Oct 2017 10:13:20 -0400)

> Cc: gdb@sourceware.org, gdb-patches@sourceware.org
> From: Simon Marchi <simark@simark.ca>
> Date: Sat, 21 Oct 2017 10:13:20 -0400
> 
> > Since this worked for me, in GDB 8.0, can something similar be put in
> > the current master, so the next GDB release will have this bug fixed?
> > 
> > Thanks.
> 
> I'll look into it, but I'll try a slightly different patch.  The one I sent
> previously sets and restores the interpreter at every executed command, which
> is inefficient.  I'll try to set and restore only once at a higher level in
> the call stack.

Thank you.


  parent reply	other threads:[~2017-10-21 16:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8360bqt0im.fsf@gnu.org>
     [not found] ` <8a3d7153-7486-032f-aabc-6c3453f96459@simark.ca>
     [not found]   ` <83shetsdg2.fsf@gnu.org>
     [not found]     ` <e65519d3-37e8-06f0-cd5a-d7e6b7aaf31d@simark.ca>
     [not found]       ` <83o9phs8zw.fsf@gnu.org>
     [not found]         ` <b0ce9014-a231-6d57-8a72-6da1eb80f67b@simark.ca>
     [not found]           ` <83d15wsrvw.fsf@gnu.org>
     [not found]             ` <83bmlgsqpm.fsf@gnu.org>
     [not found]               ` <fb95da6b-2390-f486-0806-291d24fbe766@simark.ca>
2017-10-21  8:26                 ` Eli Zaretskii
     [not found]                   ` <f54ff4bc-fb7c-397f-153d-83cafb6966bd@simark.ca>
2017-10-21 16:27                     ` Eli Zaretskii [this message]
2017-10-21 18:41                   ` [PATCH] Use console uiout when executing breakpoint commands Simon Marchi
2017-11-01  1:37                     ` Simon Marchi
2017-11-01  3:45                       ` Eli Zaretskii

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=83mv4kbh61.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=gdb@sourceware.org \
    --cc=simark@simark.ca \
    /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