Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Luis Machado <lgustavo@codesourcery.com>,
	       "Maciej W. Rozycki" <macro@imgtec.com>
Cc: gdb-patches@sourceware.org, jan.kratochvil@redhat.com
Subject: Re: [PATCH] Handle loading improper core files gracefully in the mips backend.
Date: Thu, 19 Jan 2017 16:56:00 -0000	[thread overview]
Message-ID: <d840d9c2-100d-f436-861f-e3ae93bb9ba3@redhat.com> (raw)
In-Reply-To: <bcf5a426-6448-63a7-ce18-850e611e1b5a@codesourcery.com>

On 01/09/2017 07:56 PM, Luis Machado wrote:

> Reading the thread once again, is my understanding correct that the
> first patch is more suitable now? Possibly with some cleanups?
> 
> https://sourceware.org/ml/gdb-patches/2016-01/msg00134.html

I think a summary of the discussion would help.

I think it'd be very interesting to come up with a combination
of "set mips abi n64/o64" etc, and maybe "set gnutarget" that
exposes the problem.  I've since added the
bit gdb.base/all-architectures*.exp testcase, and that does
try all sorts of combinations, including mips ones, but it
evidently isn't catching this for some reason.

Thanks,
Pedro Alves


  reply	other threads:[~2017-01-19 16:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-08 18:32 Luis Machado
2016-01-09  3:02 ` Maciej W. Rozycki
2016-01-11 15:47   ` Luis Machado
2016-01-12 12:46     ` Pedro Alves
2016-01-12 13:25       ` Luis Machado
2016-01-12 14:10         ` Pedro Alves
2016-01-12 15:43           ` Luis Machado
2016-01-12 16:00             ` Pedro Alves
2016-01-12 18:30             ` Maciej W. Rozycki
2016-01-12 19:08               ` Pedro Alves
2016-02-02 12:58               ` Luis Machado
2016-02-02 14:19                 ` Pedro Alves
2016-02-02 14:22                   ` Pedro Alves
2016-02-04 21:01                     ` Maciej W. Rozycki
2016-02-05 11:29                       ` Luis Machado
2016-02-05 14:10                         ` Maciej W. Rozycki
2017-01-09 19:57               ` Luis Machado
2017-01-19 16:56                 ` Pedro Alves [this message]
2017-01-19 17:05                   ` 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=d840d9c2-100d-f436-861f-e3ae93bb9ba3@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=lgustavo@codesourcery.com \
    --cc=macro@imgtec.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