Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <kettenis@gnu.org>
To: cagney@gnu.org
Cc: mec.gnu@mindspring.com, gdb-patches@sources.redhat.com
Subject: Re: [COMMIT] Accept "\r\n" line-endings on all hosts
Date: Thu, 14 Oct 2004 19:48:00 -0000	[thread overview]
Message-ID: <200410141948.i9EJmirp001178@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <416ECEE0.8010205@gnu.org> (message from Andrew Cagney on Thu, 14 Oct 2004 15:09:20 -0400)

   Date: Thu, 14 Oct 2004 15:09:20 -0400
   From: Andrew Cagney <cagney@gnu.org>

   I was actually more worried by human error.  I suspect a few lines of 
   tcl that just generate the file are easiest.

The attached seems to work on i386-unknown-freebsd4.7.  OK Michael?

Mark


Index: ChangeLog
from  Mark Kettenis  <kettenis@gnu.org>

	* gdb.base/crlf.exp: New file.

--- /dev/null	Thu Oct 14 21:44:00 2004
+++ gdb.base/crlf.exp	Thu Oct 14 21:42:51 2004
@@ -0,0 +1,45 @@
+# Copyright 2004 Free Software Foundation, Inc.
+
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 2 of the License, or
+# (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program; if not, write to the Free Software
+# Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.  
+
+# Please email any bugs, comments, and/or additions to this file to:
+# bug-gdb@gnu.org
+
+# This file is part of the gdb testsuite.
+
+if $tracelevel {
+    strace $tracelevel
+}
+
+# Test whether we can execute command files with \r\n line-endings.
+
+set prms_id 0
+set bug_id 0
+
+set file [open "crlf.gdb" "w"]
+puts -nonewline $file "info break\r\n"
+close $file
+
+set cmdfile [remote_download host "crlf.gdb"]
+
+gdb_exit
+gdb_start
+
+gdb_test "source $cmdfile" \
+	"No breakpoints or watchpoints." \
+	"execute command file"
+
+remote_file build delete "crlf.gdb"
+remote_file host delete $cmdfile


  reply	other threads:[~2004-10-14 19:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-14 12:44 Mark Kettenis
2004-10-14 13:47 ` Andrew Cagney
2004-10-14 18:37   ` Mark Kettenis
2004-10-14 19:09     ` Andrew Cagney
2004-10-14 19:48       ` Mark Kettenis [this message]
2004-10-14 19:59         ` Andrew Cagney
2004-10-15  2:16         ` Michael Chastain
2004-10-14 21:11     ` Eli Zaretskii
2004-10-14 23:03       ` Andreas Schwab
2004-10-15 12:43         ` Eli Zaretskii
2004-10-15 13:48           ` Andreas Schwab

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=200410141948.i9EJmirp001178@elgar.sibelius.xs4all.nl \
    --to=kettenis@gnu.org \
    --cc=cagney@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec.gnu@mindspring.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