Bug 102726 - signal list in Eclipse is botched when using japanese locale
Summary: signal list in Eclipse is botched when using japanese locale
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: eclipse   
(Show other bugs)
Version: 3.0
Hardware: i686 Linux
Target Milestone: ---
Assignee: eclipse-bugs
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2003-08-20 11:17 UTC by Anthony Green
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-10-19 19:35:14 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Anthony Green 2003-08-20 11:17:26 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225

Description of problem:
When you log in using the japanese language and start gdb in the console, "info
signals" produces a nice list in english.

But the list is completely botched when you look at the signals page in an
Eclipse C debugging session.  There's an extra entry at the top with a single
Japanese character.  Most of the descriptions are blank, although a small number
contain partial descriptions. 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Log in using japanese language
2.Start a C debugging session in Eclipse
3.Look at the signals page


Additional info:

Comment 1 Tom Tromey 2003-09-19 22:46:08 UTC
For the time being, I've set up the gcj-eclipse to force
LANG=C.  This also works around bugs reported on the public
compiled-eclipse list about locale-related failures.
BTW, these reports should be pushed to the upstream
eclipse.org bugzilla.

Comment 2 RHEL Product and Program Management 2007-10-19 19:35:14 UTC
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.

Note You need to log in before you can comment on or make changes to this bug.