Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: "Tedeschi, Walfred" <walfred.tedeschi@intel.com>
Cc: "Mark Kettenis (mark.kettenis@xs4all.nl)"
	<mark.kettenis@xs4all.nl>,
	       "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [pushed] [PATCH V7 0/8] Intel(R) MPX register support
Date: Thu, 21 Nov 2013 20:48:00 -0000	[thread overview]
Message-ID: <528E62B3.7080005@redhat.com> (raw)
In-Reply-To: <AC542571535E904D8E8ADAE745D60B191B1D8BC7@IRSMSX104.ger.corp.intel.com>

Hi Fred,

Unfortunately, this caused PR16193 - gdbserver aborts.

Could you take a look, please?

 <https://sourceware.org/bugzilla/show_bug.cgi?id=16193>

((
BTW, while bisecting this, I found that the MPX series as
committed 1dbcd68 fails in early initialization with:

 ../../src/gdb/amd64-linux-nat.c:1180: internal-error: _initialize_amd64_linux_nat: Assertion `ARRAY_SIZE (amd64_linux_gregset32_reg_offset) == amd64_native_gregset32_num_regs' failed.
 A problem internal to GDB has been detected,
 further debugging may prove unreliable.
 Quit this debugging session? (y or n) [answered Y; input not from terminal]

nothing we can do now, but just a friendly note to point out
that it's a good idea to try to avoid this, to make bisects
easier.
))

Thanks!

-- 
Pedro Alves


  reply	other threads:[~2013-11-21 19:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-20 13:11 Tedeschi, Walfred
2013-11-21 20:48 ` Pedro Alves [this message]
2013-11-22  8:41   ` Tedeschi, Walfred
2013-11-22 12:50   ` Tedeschi, Walfred
2013-11-22 13:41     ` Yao Qi
2013-11-22 13:51     ` Pedro Alves
2013-11-22 13:57       ` Tedeschi, Walfred
2013-11-22 14:31       ` Tedeschi, Walfred
2013-11-22 17:23     ` Tom Tromey
     [not found]       ` <AC542571535E904D8E8ADAE745D60B191B1DACC6@IRSMSX104.ger.corp.intel.com>
2013-11-25 12:24         ` FYI: gdbserver crash due to: " Joel Brobecker
2013-11-25 12:51           ` Tedeschi, Walfred

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=528E62B3.7080005@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    --cc=walfred.tedeschi@intel.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