Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: Marc Khouzam <marc.khouzam@ericsson.com>,
	       "'gdb-patches@sourceware.org'"
	<gdb-patches@sourceware.org>
Subject: Re: [patch] [gdbserver] Do not crash on file load without inferior
Date: Sat, 05 Mar 2011 04:11:00 -0000	[thread overview]
Message-ID: <20110305041102.GA16509@host1.jankratochvil.net> (raw)
In-Reply-To: <201103042205.51281.pedro@codesourcery.com>

On Fri, 04 Mar 2011 23:05:50 +0100, Pedro Alves wrote:
> Are you saying you didn't have a chance of thinking about
> my rationale, or that you don't agree with my rationale,
> or that you wanted to write a better test, or?

I could find some examples from the past (not sure if specifically for your
fixes or not - I do not find relevant whether such case happened or not with
your fixes) when even despite serious thinking about the problem on the list
the testsuite then found for the commit a regression and/or incomplete fix.

Given how cheap is to run the testsuite I do not think it is worth spending
any human effort on coding without having the testsuite results available.


Thanks,
Jan


  parent reply	other threads:[~2011-03-05  4:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-24 12:42 Jan Kratochvil
2011-02-24 14:26 ` Pedro Alves
2011-03-04 21:25   ` Marc Khouzam
2011-03-04 21:32     ` Pedro Alves
2011-03-04 21:37       ` Jan Kratochvil
2011-03-04 22:05         ` Pedro Alves
2011-03-04 22:14           ` Michael Snyder
2011-03-05  4:11           ` Jan Kratochvil [this message]
2011-03-05 11:18             ` Pedro Alves
2011-03-05 12:19               ` Jan Kratochvil
2011-03-08 13:37                 ` Pedro Alves

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=20110305041102.GA16509@host1.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=marc.khouzam@ericsson.com \
    --cc=pedro@codesourcery.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