From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 2737] New: buildroot configuration tool crashing when the path exceeds 128 characters
Date: Wed, 27 Oct 2010 14:18:42 +0000 (UTC) [thread overview]
Message-ID: <bug-2737-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=2737
Summary: buildroot configuration tool crashing when the path
exceeds 128 characters
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: honyakeprt at centrum.cz
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Created attachment 2629
--> https://bugs.busybox.net/attachment.cgi?id=2629
quick fix
Install the buildroot to a directory, where the path length exceed 128
characters. Try to run "make oldconfig", the configuration tool is crashing
with message buffer overflow detected. The tool "make menuconfig" is probably
crashing as well.
The buggy file is located here:
..../package/config/confdata.c
Function:
int conf_write(const char *name)
uses arrays of size 128B for path.
Am sending you quick fix, which is working for us.
Regars
JK
--
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.
next reply other threads:[~2010-10-27 14:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-27 14:18 bugzilla at busybox.net [this message]
2010-11-07 18:54 ` [Buildroot] [Bug 2737] buildroot configuration tool crashing when the path exceeds 128 characters bugzilla at busybox.net
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-2737-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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