public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "hi-angel at yandex dot ru" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/27324] New: [REGRESSION] `exceptions.UnicodeEncodeError` upon loading a config with λ Date: Tue, 02 Feb 2021 21:52:18 +0000 [thread overview] Message-ID: <bug-27324-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=27324 Bug ID: 27324 Summary: [REGRESSION] `exceptions.UnicodeEncodeError` upon loading a config with λ Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: hi-angel at yandex dot ru Target Milestone: --- I built latest master to check something, and found there's a regression regarding configuration files. Works correctly on latest released 10.1. Not sure how to bisect, because there's too many commits, and the gdb python exception does not print any stacktrace to point out where's the code # Steps to reproduce (in terms of terminal commands) λ cat test-prompt set extended-prompt \[\e[31m\]gdb λ \[\e[0m\] λ gdb/gdb -q --nh -x test-prompt Python Exception <type 'exceptions.UnicodeEncodeError'> 'ascii' codec can't encode character u'\u03bb' in position 14: ordinal not in range(128): (gdb) ## Expected gdb gets loaded as usual and there's a λ prompt as assigned in config ## Actual gdb prints an error, and the prompt is left unchanged # Additional information gdb built from commit `e0bd9202fb: gdb/testsuite: use proc_with_prefix in gdb.base/scope.exp` -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2021-02-02 21:52 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-02 21:52 hi-angel at yandex dot ru [this message] 2021-02-14 17:08 ` [Bug gdb/27324] " hi-angel at yandex dot ru
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=bug-27324-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).