Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Martin Sebor <msebor@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [patchv2] PR gdb/17968 - [ppc64] SEGV in ppc64_elf_get_synthetic_symtab reading a separate debug file
Date: Thu, 26 Feb 2015 11:51:00 -0000	[thread overview]
Message-ID: <54EF08D1.4050703@redhat.com> (raw)
In-Reply-To: <20150226114101.GA6813@host1.jankratochvil.net>

On 02/26/2015 11:41 AM, Jan Kratochvil wrote:
> On Thu, 26 Feb 2015 12:33:10 +0100, Pedro Alves wrote:
>> On 02/25/2015 09:04 PM, Jan Kratochvil wrote:
>>
>>> +# This test won't work properly if system debuginfo is installed.
>>> +gdb_test_no_output "set debug-file-directory" ""
>>
>> I suspect this "" here would be for "no expected output", but
>> given this is gdb_test_no_output, it actually means the test has
>> no associated message.  I think you want to remove that.
> 
> I do not care if "" gets removed or not but it was intentional this way.
> 
> (1) Some people prefer no gdb.sum line for testcases which really should never
>     FAIL and/or which are not a subject of the testfile.  I am do not belong
>     between these people (if I care at all), though.
> 
> (2) Here I used it as the only other testcase will be often UNTESTED (due to
>     no ppc64 target support compiled in) - and it looks better if there is
>     only one UNTESTED result than one PASS + one UNTESTED which may give
>     a false feeling something got tested - which it was not.
> 
> 
>> Otherwise this (patch and test) looks good to me.
> 
> So just if "" should be there or not.

Fine with to me leave it, but please add the (2) comment above
in the test then.

Thanks,
Pedro Alves


  reply	other threads:[~2015-02-26 11:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-17 20:06 [PATCH] " Martin Sebor
2015-02-17 23:40 ` Martin Sebor
2015-02-25 21:04   ` [patchv2] " Jan Kratochvil
2015-02-26  4:43     ` Jan Kratochvil
2015-02-26 11:33     ` Pedro Alves
2015-02-26 11:41       ` Jan Kratochvil
2015-02-26 11:51         ` Pedro Alves [this message]
2015-02-26 13:10           ` [commit] " Jan Kratochvil
2015-02-26 16:45     ` Martin Sebor

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=54EF08D1.4050703@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=msebor@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