Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Catalin-Dan Udma <catalin-dan.udma@nxp.com>
To: Pedro Alves <palves@redhat.com>,
	Catalin Udma	<catalin.udma@freescale.com>,
	"gdb-patches@sourceware.org"	<gdb-patches@sourceware.org>
Subject: RE: [PATCH] testsuite: Update py-mi-objfile to expect console format print
Date: Tue, 05 Apr 2016 13:36:00 -0000	[thread overview]
Message-ID: <VI1PR0401MB17762335B84846945C11C65BDA9E0@VI1PR0401MB1776.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <5703BA12.2090602@redhat.com>

> On 04/05/2016 02:11 PM, Pedro Alves wrote:
> > On 04/05/2016 02:08 PM, Catalin-Dan Udma wrote:
> >
> >> [Catalin Udma]
> >> gdb.execute ("interpreter-exec mi \"-gdb-show width\"", to_string = True)
> >> would crash the gdb with or without any of the patches in discussion.
> >> (MI patch for crash redirection, and use console for python gdb.execute)
> >
> > Bah...
> 
> Looking again, note I suggested:
> 
>  gdb.execute ("interpreter-exec mi \"-gdb-show width\"")
> 
> not:
> 
>  gdb.execute ("interpreter-exec mi \"-gdb-show width\"", to_string = True)
> 
> TBC, does the former also likewise crash with or without patches?
> 
> Thanks,
> Pedro Alves
The former gdb.execute ("interpreter-exec mi \"-gdb-show width\"") does not crash the gdb
in any combination of the two patches in discussion.
Regards,
Catalin


  reply	other threads:[~2016-04-05 13:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-05 10:16 Catalin Udma
2016-04-05 10:59 ` Pedro Alves
2016-04-05 11:46   ` Catalin-Dan Udma
2016-04-05 11:59     ` Pedro Alves
2016-04-05 13:08       ` Catalin-Dan Udma
2016-04-05 13:11         ` Pedro Alves
2016-04-05 13:13           ` Pedro Alves
2016-04-05 13:36             ` Catalin-Dan Udma [this message]
2016-04-05 13:47               ` Pedro Alves

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=VI1PR0401MB17762335B84846945C11C65BDA9E0@VI1PR0401MB1776.eurprd04.prod.outlook.com \
    --to=catalin-dan.udma@nxp.com \
    --cc=catalin.udma@freescale.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    /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