Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Luis Machado <lgustavo@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Make gdb.arch/i386-biarch-core.exp more robust
Date: Mon, 06 Feb 2017 18:03:00 -0000	[thread overview]
Message-ID: <85a7d55f-368e-8443-6346-df94e6be813f@redhat.com> (raw)
In-Reply-To: <dc8d3662-2aad-e754-4b50-47409745ec36@codesourcery.com>

On 02/06/2017 05:58 PM, Luis Machado wrote:

> Yes, indeed. This test should never try to force a gdb that doesn't
> understand i386/x86-64 core files to load one.

TBC, I think it should, to make sure gdb doesn't crash.

Thanks,
Pedro Alves


  reply	other threads:[~2017-02-06 18:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-31 13:55 Luis Machado
2017-02-06 17:28 ` Pedro Alves
2017-02-06 17:59   ` Luis Machado
2017-02-06 18:03     ` Pedro Alves [this message]
2017-02-07 10:11 ` [PATCH,v2] " Luis Machado
2017-02-07 10:51   ` Pedro Alves
2017-02-07 11:18     ` Luis Machado
2017-02-07 11:26 ` [PATCH, v3] " Luis Machado
2017-02-07 11:29   ` Pedro Alves
2017-02-13 13:15     ` Luis Machado

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=85a7d55f-368e-8443-6346-df94e6be813f@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=lgustavo@codesourcery.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