From: "Eli Zaretskii" <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: otto.wyss@orpatec.ch, gdb@sources.redhat.com
Subject: Re: GDB doesn't show the correct line
Date: Sat, 13 Nov 2004 21:46:00 -0000 [thread overview]
Message-ID: <01c4c9c9$Blat.v2.2.2$913fbf20@zahav.net.il> (raw)
In-Reply-To: <20041113201803.GA21320@nevyn.them.org> (message from Daniel Jacobowitz on Sat, 13 Nov 2004 15:18:03 -0500)
> Date: Sat, 13 Nov 2004 15:18:03 -0500
> From: Daniel Jacobowitz <drow@false.org>
> Cc: gdb@sources.redhat.com
>
> It's no one's fault, I think. I tracked down the problem. You have
> mixed newline conventions in the file: mostly "\n" as a line separator,
> but in some places just "\r". GCC treats this as a line break for
> legacy reasons (MacOS). 'less' doesn't, which really confused me while
> trying to debug the problem. GDB doesn't, either.
>
> Should GDB? I have no idea.
As of today, GDB should treat \r\n (a.k.a. CR-LF) line endings
correctly, but not sole \r. Perhaps we should amend that code to
treat sole CRs as well.
> But it's easiest to just fix the source file to be consistent.
Indeed.
next prev parent reply other threads:[~2004-11-13 21:43 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 [this message]
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
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='01c4c9c9$Blat.v2.2.2$913fbf20@zahav.net.il' \
--to=eliz@gnu.org \
--cc=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=otto.wyss@orpatec.ch \
/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