Bug 313 - mconf segmentation fault when selecting X Window System Server and !BR2_USE_WCHAR
Summary: mconf segmentation fault when selecting X Window System Server and !BR2_USE_W...
Status: RESOLVED DUPLICATE of bug 105
Alias: None
Product: buildroot
Classification: Unclassified
Component: Other (show other bugs)
Version: unspecified
Hardware: PC Linux
: P5 normal
Target Milestone: ---
Assignee: unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-04 09:39 UTC by Jim Persson
Modified: 2009-05-04 10:00 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jim Persson 2009-05-04 09:39:07 UTC
Buildroot version: v2009.02
Distributor ID:	Ubuntu
Description:	Ubuntu 8.10
Release:	8.10
Codename:	intrepid
Running on x86 32bit Intel P4

Steps to reproduce:

$ tar xjf ../buildroot-2009.02.tar.bz2
$ cd buildroot-2009.02/
$ make menuconfig

Do the following selections:
Package Selection for the target  --->
Graphic libraries and applications (graphic/text)  --->
X Window System server (none)  --->

Select xorg or tinyx
This results in a segmentation fault

---------------------------- SNIP ----------------------------
/bin/sh: line 4: 20924 Segmentation fault      KCONFIG_AUTOCONFIG=package/config/buildroot-config/auto.conf KCONFIG_AUTOHEADER=package/config/buildroot-config/autoconf.h package/config/mconf Config.in


Program received signal SIGSEGV, Segmentation fault
sym_set_tristate_value (sym=0x0, val=yes) at lkc.h:116
116             return sym->curr.tri;

(gdb) bt
#0  sym_set_tristate_value (sym=0x0, val=yes) at lkc.h:116
#1  0x0804b170 in conf (menu=0x9d6d338) at mconf.c:790
#2  0x0804af7e in conf (menu=0x9d33540) at mconf.c:718
#3  0x0804af7e in conf (menu=0x8066520) at mconf.c:718
#4  0x0804b3d5 in main (ac=Cannot access memory at address 0x0
) at mconf.c:932

114     static inline tristate sym_get_tristate_value(struct symbol *sym)
115     {
116             return sym->curr.tri;
117     }

---------------------------- SNIP ----------------------------


I have not checked if this problem exists upstream
Comment 1 Peter Korsgaard 2009-05-04 10:00:25 UTC
Thanks, but this was already reported as #105 and fixed in svn (r25316). The soon-to-be-released 2009.05 version will have the fix.


*** This bug has been marked as a duplicate of bug 105 ***