Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Simon Marchi <simark@simark.ca>
Cc: gdb@sourceware.org
Subject: Re: Breakpoint commands in MI mode and "backtrace"
Date: Mon, 09 Oct 2017 12:59:00 -0000	[thread overview]
Message-ID: <831smcsci1.fsf@gnu.org> (raw)
In-Reply-To: <fb95da6b-2390-f486-0806-291d24fbe766@simark.ca> (message from	Simon Marchi on Mon, 9 Oct 2017 08:02:24 -0400)

> Cc: gdb@sourceware.org
> From: Simon Marchi <simark@simark.ca>
> Date: Mon, 9 Oct 2017 08:02:24 -0400
> 
> It's true that my patch seems to change how exceptions are handled, since
> safe_execute_command catches and prints exceptions.  However, that expression
> does indeed seem erroenous, and I'm surprised GDB doesn't complain about it
> currently.  How can you add a char* and a listp_Symbol*?

Sorry, that's my fault: actually $ptr at that point is just a number,
410072 in my case.  Apologies for confusing you.

> Anyhow, can you try this patch here?  It changes the uiout manually instead of
> going through safe_execute_command.

It works, thanks.  I tried both in CLI mode and in MI mode, and it
works with both.


  reply	other threads:[~2017-10-09 12:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-08 10:08 Eli Zaretskii
     [not found] ` <8a3d7153-7486-032f-aabc-6c3453f96459@simark.ca>
2017-10-08 18:27   ` Eli Zaretskii
2017-10-08 19:24     ` Simon Marchi
2017-10-08 20:03       ` Eli Zaretskii
2017-10-09  4:16         ` Simon Marchi
2017-10-09  7:27           ` Eli Zaretskii
2017-10-09  7:52             ` Eli Zaretskii
2017-10-09 12:02               ` Simon Marchi
2017-10-09 12:59                 ` Eli Zaretskii [this message]
2017-10-21  8:26                 ` Eli Zaretskii
2017-10-21 14:13                   ` Simon Marchi
2017-10-21 16:27                     ` 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=831smcsci1.fsf@gnu.org \
    --to=eliz@gnu.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