Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: tromey@redhat.com, drow@false.org, otto.wyss@orpatec.ch,
	gdb@sources.redhat.com
Subject: Re: GDB doesn't show the correct line
Date: Mon, 15 Nov 2004 04:41:00 -0000	[thread overview]
Message-ID: <je6548dny4.fsf@sykes.suse.de> (raw)
In-Reply-To: <01c4ca99$Blat.v2.2.2$124c16c0@zahav.net.il> (Eli Zaretskii's message of "Mon, 15 Nov 2004 00:26:02 +0200")

"Eli Zaretskii" <eliz@gnu.org> writes:

>> Cc: tromey@redhat.com, drow@false.org, otto.wyss@orpatec.ch,
>> 	gdb@sources.redhat.com
>> From: Andreas Schwab <schwab@suse.de>
>> Date: Sun, 14 Nov 2004 22:24:28 +0100
>> 
>> But the more problematic cases would be \n\r or \r\r\n.
>
> Why are these more problematic?

Because they look like non-canonical line endings, but can be interpreted
as two line endings when using a strict interpretation.  The first one
could be a Unix newline followed by a Mac newline, or a non-canonical DOS
newline (should non-canonical DOS newlines be recognized?).  The second
one could be a Mac newline followed by a DOS newline, or a spurious CR
followed by a DOS newline (should spurious CRs be ignored?).

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."


  reply	other threads:[~2004-11-14 23:37 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-20 19:24 Otto Wyss
2004-06-20 20:29 ` Daniel Jacobowitz
2004-06-21 17:56   ` Otto Wyss
2004-06-21 17:59     ` Daniel Jacobowitz
2004-06-21 18:15       ` Otto Wyss
2004-06-21 19:41         ` Daniel Jacobowitz
2004-11-13 20:50         ` Daniel Jacobowitz
2004-11-13 20:55           ` Otto Wyss
2004-11-13 21:43             ` Daniel Jacobowitz
2004-11-14  4:36               ` Otto Wyss
2004-11-13 21:46           ` Eli Zaretskii
2004-11-13 21:59             ` Daniel Jacobowitz
2004-11-14  5:30               ` Eli Zaretskii
2004-11-14 14:38               ` Tom Tromey
2004-11-14 21:43                 ` Eli Zaretskii
2004-11-14 22:29                   ` Andreas Schwab
2004-11-14 22:39                     ` Eli Zaretskii
2004-11-15  4:41                       ` Andreas Schwab [this message]
2004-11-15 16:06                         ` Eli Zaretskii
2004-11-14 23:37                   ` Felix Lee
2004-11-15  4:45                     ` Eli Zaretskii
2004-06-23 11:54   ` Tarjei Knapstad

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=je6548dny4.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=otto.wyss@orpatec.ch \
    --cc=tromey@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