Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Antoine Tremblay <antoine.tremblay@ericsson.com>
To: Pedro Alves <palves@redhat.com>
Cc: Antoine Tremblay <antoine.tremblay@ericsson.com>,
	<gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix crash when loading a core with unexpected register section size
Date: Thu, 26 Jan 2017 14:31:00 -0000	[thread overview]
Message-ID: <wwok8tpx7v11.fsf@ericsson.com> (raw)
In-Reply-To: <3ac9874b-d4c9-8cb2-c4ab-81d20d41689d@redhat.com>


Pedro Alves writes:

> On 01/26/2017 01:54 PM, Antoine Tremblay wrote:
>> 
>> Pedro Alves writes:
>> 
>>> On 01/26/2017 01:17 PM, Antoine Tremblay wrote:
>>>> When loading a core without an executable like so:
>>>> gdb --core core for example often the gdbarch won't contain the
>>>> iterate_over_regset_sections method.
>>>
>>> Can you give an example?  That'd help a lot understand the issue
>>> better.
>>>
>> 
>> I can't share the core that I have that reproduced this :( 
>
> I meant an example gdbarch.  It sounded like this would
> happen with any core with that architecture?

Ho yes, see v2, I added "For example arch-arm." Like you suggested.


  reply	other threads:[~2017-01-26 14:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-26 13:17 Antoine Tremblay
2017-01-26 13:40 ` Pedro Alves
2017-01-26 13:56   ` Antoine Tremblay
2017-01-26 13:59     ` [PATCH v2] " Antoine Tremblay
2017-01-26 14:25     ` [PATCH] " Pedro Alves
2017-01-26 14:31       ` Antoine Tremblay [this message]
2017-01-26 14:35         ` Pedro Alves
2017-01-26 14:59           ` Antoine Tremblay
2017-01-26 15:20             ` Pedro Alves
2017-01-26 15:27               ` Antoine Tremblay
2017-01-26 15:53               ` [pushed][PATCH v2] " Antoine Tremblay

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=wwok8tpx7v11.fsf@ericsson.com \
    --to=antoine.tremblay@ericsson.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