This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: i18n and internal errors
- From: "Eli Zaretskii" <eliz at gnu dot org>
- To: "M.M. Kettenis" <m dot m dot kettenis at alumnus dot utwente dot nl>
- Cc: kevinb at redhat dot com, kettenis at gnu dot org, gdb at sources dot redhat dot com, cagney at gnu dot org
- Date: Tue, 15 Feb 2005 06:54:37 +0200
- Subject: Re: i18n and internal errors
- References: <731992780126277@weblx058.utsp.utwente.nl>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> From: "M.M. Kettenis" <m.m.kettenis@alumnus.utwente.nl>
> Date: Tue, 15 Feb 2005 02:10:01 +0000
> Cc: cagney@gnu.org
>
> > As for the difficulty in fixing the bugs, the fatal messages typically
> > include a file name and a line number which point to the place where
> > the bug was caught. I think that alleviates some of the difficulties.
>
> Although line numbers might be a bit off compared to the current CVS version or even compared to the release.
True, but hopefully not by a lot.
> > Also, it is customary for users to translate the messages into English
> > when reporting bugs (a case in point is messages from the OS utilities
> > that have some relevance to the bug being reported), since the users
> > generally understand that English is a better language to talk to
> > maintainers.
>
> So we should update the bug reporting instructions to instruct users to run gdb with env LC_ALL="C". Hmm, hopefully that doesn't make the bug
> disappear.
We should indeed ask them to reproduce in the C locale, and if the bug
disappears, to translate the message(s) into English as best as they
can.