* [Buildroot] [Bug 5018] New: dialog broken: exits with assert in uClibc
@ 2012-04-04 7:55 bugzilla at busybox.net
2012-04-14 21:04 ` [Buildroot] [Bug 5018] " bugzilla at busybox.net
0 siblings, 1 reply; 2+ messages in thread
From: bugzilla at busybox.net @ 2012-04-04 7:55 UTC (permalink / raw)
To: buildroot
https://bugs.busybox.net/show_bug.cgi?id=5018
Summary: dialog broken: exits with assert in uClibc
Product: buildroot
Version: 2012.02
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: zkdigisec at gmail.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
dialog can easily be made do abort with an assert, leaving the terminal in an
undefined state.
For example:
1. Start dialog: "dialog --yesno test 0 0"
2. Hit the right arrow key
Results in:
dialog: libc/misc/ctype/ctype.c: 320: toupper: Assertion '...' failed. Aborted
The reason is that dialog calls the uClibc function toupper() with a character
code > 255, resulting in an assert and fatal exit.
This could be seen as a problem in dialog.
But it could also be fixed in buildroot by changing the default uClibc
configuration in uClibc-0.9.33.config:
-UCLIBC_HAS_CTYPE_ENFORCED=y
+# UCLIBC_HAS_CTYPE_ENFORCED is not set
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2012-04-14 21:04 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-04-04 7:55 [Buildroot] [Bug 5018] New: dialog broken: exits with assert in uClibc bugzilla at busybox.net
2012-04-14 21:04 ` [Buildroot] [Bug 5018] " bugzilla at busybox.net
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox