Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Otto Wyss <otto.wyss@orpatec.ch>
To: gdb@sources.redhat.com
Subject: Re: GDB doesn't show the correct line
Date: Sat, 13 Nov 2004 20:55:00 -0000	[thread overview]
Message-ID: <41967379.F2BD27D2@orpatec.ch> (raw)
In-Reply-To: <20041113201803.GA21320@nevyn.them.org>

Daniel Jacobowitz wrote:
> 
> On Mon, Jun 21, 2004 at 08:15:10PM +0200, Otto Wyss wrote:
> > Daniel Jacobowitz wrote:
> > >
> > Can't this line number problem somehow detected within GDB? Sorry if I
> > ask this as someone without knowing any internals but IMO this would be
> > the best solution. My app is now working so I'm not in a hurry but a
> > good debugger is _essential_  for any development.
> 
> 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.  But it's easiest to just fix the source
> file to be consistent.
> 
Of course I check all my sources but I fear it's in some header file
(most probably wxWidgets). I've never edited any of my sources on the Mac.

IMO it would be best if GDB would handle line separators equally as GCC.
So the behaviour would be consistent an easier understandable by the user.

O. Wyss

-- 
Development of frame buffer drivers: http://linux-fbdev.sf.net
Sample code snippets for wxWidgets: http://wxcode.sf.net
How to build well-designed applications: http://wxguide.sf.net
Desktop with a consistent look and feel: http://wyodesktop.sf.net


  reply	other threads:[~2004-11-13 20:50 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 [this message]
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
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=41967379.F2BD27D2@orpatec.ch \
    --to=otto.wyss@orpatec.ch \
    --cc=gdb@sources.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