From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org, gdb@sources.redhat.com
Subject: Re: text file formats
Date: Thu, 06 Apr 2006 04:30:00 -0000 [thread overview]
Message-ID: <20060406042913.GA16513@nevyn.them.org> (raw)
Message-ID: <20060406043000.LP2uvHAJTDDCYvgU0-vg92j9O_md4gOBvqAhNnIeTF8@z> (raw)
In-Reply-To: <uirpn74bl.fsf@gnu.org>
On Thu, Apr 06, 2006 at 06:47:42AM +0300, Eli Zaretskii wrote:
> > Well, usually. In search and reverse search it sometimes uses a
> > similar but slightly simpler algorithm: ignore '\r' if followed by
> > '\n'. I'm not sure why those are done in binary mode.
>
> I think it's because GDB counts characters and then lseeks to the
> point it thinks it should display. If the library's text-mode I/O
> converts \r\n to \n, this seeks will only work reliably in binary
> mode, since most DOS/Windows libraries don't seek to the correct place
> (the only exception from this rule I know of is the DJGPP library).
Oh, thanks. That's surely it.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-04-06 4:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-05 22:31 Bob Rossi
2006-04-05 23:39 ` Daniel Jacobowitz
2006-04-06 0:14 ` Bob Rossi
2006-04-06 1:17 ` Daniel Jacobowitz
2006-04-06 3:27 ` Bob Rossi
2006-04-06 3:35 ` Eli Zaretskii
2006-04-06 5:06 ` Daniel Jacobowitz
2006-04-06 13:03 ` Daniel Jacobowitz
2006-04-06 14:01 ` Bob Rossi
2006-04-06 14:41 ` Daniel Jacobowitz
2006-04-06 19:20 ` Eli Zaretskii
2006-04-06 19:32 ` Bob Rossi
2006-04-06 23:55 ` Daniel Jacobowitz
2006-04-07 13:33 ` Eli Zaretskii
2006-04-06 20:55 ` Paul Koning
2006-04-07 11:54 ` Eli Zaretskii
2006-04-06 19:07 ` Eli Zaretskii
2006-04-06 3:47 ` Eli Zaretskii
2006-04-06 4:29 ` Daniel Jacobowitz [this message]
2006-04-06 4:30 ` Daniel Jacobowitz
2006-04-06 3:43 ` Eli Zaretskii
2006-04-06 13:35 ` Bob Rossi
2006-04-06 19:01 ` Eli Zaretskii
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=20060406042913.GA16513@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=gdb@sourceware.org \
/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