From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: tromey@redhat.com
Cc: Doug Evans <dje@google.com>, gdb-patches@sourceware.org
Subject: Re: [RFA] Handle older iconv programs
Date: Fri, 11 Dec 2009 21:03:00 -0000 [thread overview]
Message-ID: <8ac60eac0912111303h5ae32fbbk3ad1851e584deddf@mail.gmail.com> (raw)
In-Reply-To: <m3my1u8qsq.fsf@fleche.redhat.com>
On Mon, Dec 7, 2009 at 12:36 PM, Tom Tromey <tromey@redhat.com> wrote:
>>>>>> "Doug" == Doug Evans <dje@google.com> writes:
>
> Doug> + set_in_environ (iconv_env, "LANGUAGE", "en");
>
> I think "C" would be preferable here.
> Or, just remove LANGUAGE from the environment.
I am seeing a crash which I think directly relates to this patch:
(top) r
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/grte/v1/lib64/libthread_db.so.1".
Program received signal SIGSEGV, Segmentation fault.
*__GI_getenv (name=0x7ffff6cb8f85 "NGUAGE") at ../sysdeps/generic/getenv.c:93
93 if (name_start == ep_start && !strncmp (*ep + 2, name, len)
(top) bt
#0 *__GI_getenv (name=0x7ffff6cb8f85 "NGUAGE") at
../sysdeps/generic/getenv.c:93
#1 0x00007ffff6bcbf8f in guess_category_value (domainname=0x9cffb0 "gdb",
msgid1=0x77d8a0 "The `host character set' is the one used by the
system GDB is running on.\nYou may only use supersets of ASCII for
your host character set; GDB does\nnot support any others.\nTo see a
list of the charact"..., msgid2=0x0, plural=0, n=0,
category=8) at dcigettext.c:1107
#2 __dcigettext (domainname=0x9cffb0 "gdb",
msgid1=0x77d8a0 "The `host character set' is the one used by the
system GDB is running on.\nYou may only use supersets of ASCII for
your host character set; GDB does\nnot support any others.\nTo see a
list of the charact"..., msgid2=0x0, plural=0, n=0,
category=8) at dcigettext.c:533
#3 0x00000000004abd33 in _initialize_charset () at ../../src/gdb/charset.c:898
#4 0x000000000041d5d8 in initialize_all_files () at init.c:160
#5 0x000000000040c289 in gdb_init (argv0=0x7fffffffddf2
"/home/ppluzhnikov/bin/gdb64-cvs") at ../../src/gdb/top.c:1729
#6 0x0000000000400fa5 in captured_main (data=0x7fffffffd940) at
../../src/gdb/main.c:688
#7 0x00000000004fdbd9 in catch_errors (func=0x40068d <captured_main>,
func_args=0x7fffffffd940, errstring=0x74f01f "", mask=6) at
../../src/gdb/exceptions.c:510
#8 0x00000000004016d4 in gdb_main (args=0x7fffffffd940) at
../../src/gdb/main.c:911
#9 0x00000000004003a4 in main (argc=1, argv=0x7fffffffda38) at
../../src/gdb/gdb.c:33
Environment has been stepped on:
(top) p __environ[0]
$4 = 0x6e0a73656f642042 <Address 0x6e0a73656f642042 out of bounds>
(top) x/s __environ
0x9fa370: "B does\nnot support any others.\nTo see a list of
the character sets GDB supports, type `set charset <TAB>'."
Still digging into the cause ...
--
Paul Pluzhnikov
next prev parent reply other threads:[~2009-12-11 21:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-07 17:57 Doug Evans
2009-12-07 20:36 ` Tom Tromey
2009-12-11 21:03 ` Paul Pluzhnikov [this message]
2009-12-11 21:06 ` Doug Evans
2009-12-11 21:35 ` Paul Pluzhnikov
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=8ac60eac0912111303h5ae32fbbk3ad1851e584deddf@mail.gmail.com \
--to=ppluzhnikov@google.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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