Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Yao Qi <qiyaoltc@gmail.com>,  Pedro Alves <palves@redhat.com>,
	 gdb-patches@sourceware.org,
	 Andreas Arnez <arnez@linux.vnet.ibm.com>
Subject: Re: ping: [testsuite patch] for: [PATCH] [PR corefiles/17808] i386: Fix internal error when prstatus in core file is too big
Date: Thu, 16 Jul 2015 15:35:00 -0000	[thread overview]
Message-ID: <86380ojeth.fsf@gmail.com> (raw)
In-Reply-To: <20150716143750.GA27870@host1.jankratochvil.net> (Jan	Kratochvil's message of "Thu, 16 Jul 2015 16:37:50 +0200")

Jan Kratochvil <jan.kratochvil@redhat.com> writes:

> Because this testcase comes from a different bug from 2009:
> 	https://bugzilla.redhat.com/show_bug.cgi?id=457187
> 	http://pkgs.fedoraproject.org/cgit/gdb.git/commit/?id=94cd124608bf0dd359cb48a710800d72c21b30c3
>
> That bug has been fixed in the meantime but the same testcase was reproducing
> this new different bug - internal error regression - so I submitted
> it.

I see, that is clear to me now.

>
> We can remove the "x/i $address" test but it was useful for the previous bug
> from 2009 as that time the internal error regression did not happen, just the
> core file was not recognized (which would not be detected by the proposed
> ignoring of the "core-file" command output) and so the core file was not
> available.  That can be tested by the "x/i $address" test.
>

Yeah, I agree it is useful to keep this test there, but we need comments
on the purpose of such test, for example,

# Test bug https://bugzilla.redhat.com/show_bug.cgi?id=457187
gdb_test "x/i $address" "\r\n\[ \t\]*$address:\[ \t\]*hlt\[ \t\]*" ".text is readable"

>
> But we could be upstreaming much more Fedora testcases which I do not plan to.
> Fedora contains many testcases - 49
> 	grep '^#=' gdb.spec|sed 's/[:+].*//'|sort|uniq -c
> 	49 #=fedoratest
> for various bugs already fixed upstream.  But given there isn't enough work
> resources to upstream even Fedora fixes (hacks) I have never much attempted to
> upstream all the testcases there.
> 	http://pkgs.fedoraproject.org/cgit/gdb.git/tree/
> (Some/few of the testcases are also a different form of the upstreamed variant
> of the same testcase kept to be really sure no regressions are needlessly
> missed in Fedora/RHEL.)

I don't work on any distribution, so I don't know.

-- 
Yao (齐尧)


  reply	other threads:[~2015-07-16 15:35 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-08 16:16 Andreas Arnez
2015-01-08 16:43 ` [testsuite patch] for: " Jan Kratochvil
2015-01-09  9:47   ` Andreas Arnez
2015-01-09 16:45     ` Pedro Alves
2015-01-09 16:59       ` Mark Kettenis
2015-01-09 17:19         ` Pedro Alves
2015-01-09 19:35           ` Mark Kettenis
2015-01-09 20:11             ` Pedro Alves
2015-01-09 20:30               ` Mark Kettenis
2015-01-12 14:30                 ` Andreas Arnez
2015-01-09 19:27       ` Andreas Arnez
2015-02-05  7:38   ` ping: " Jan Kratochvil
2015-02-05  9:47     ` Pedro Alves
2015-02-14 15:12       ` Jan Kratochvil
2015-02-17 12:56         ` Pedro Alves
2015-02-17 16:56           ` Jan Kratochvil
2015-02-21 14:28             ` [commit] " Jan Kratochvil
2015-07-14  8:52             ` ping: " Yao Qi
2015-07-14 18:07               ` Jan Kratochvil
2015-07-15 16:14                 ` Yao Qi
2015-07-15 16:58                   ` Jan Kratochvil
2015-07-16 14:15                     ` Yao Qi
2015-07-16 14:37                       ` Jan Kratochvil
2015-07-16 15:35                         ` Yao Qi [this message]
2015-07-16 16:10                           ` [commit] " Jan Kratochvil

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=86380ojeth.fsf@gmail.com \
    --to=qiyaoltc@gmail.com \
    --cc=arnez@linux.vnet.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --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