Your message dated Sat, 2 Feb 2013 15:11:22 -0800 with message-id <[email protected]> and subject line Re: awk segfaults when trying to configure linux 2.4.0 has caused the Debian Bug report #81487, regarding mawk: stack overflow in scripts/Menuconfig from Linux 2.4.x to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 81487: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=81487 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: mawk Version: 1.3.3-5 Severity: normal Hi, After `make menuconfig' in the kernel 2.4.0, which hadn't worked, I found file core in the kernel dir. gdb shows that: This GDB was configured as "i686-pc-linux-gnu". Core was generated by `awk BEGIN { menu_no = 0 comment_is_option = 0 parser("arch/i386/config.in",'. Program terminated with signal 11, Segmentation fault. #0 0x1c2db0 in ?? () [502]> /usr/sbin/update-alternatives --display awk awk - status is auto. link currently points to /usr/bin/mawk /usr/bin/mawk - priority 20 If I switch awk alternative to gawk, `make menuconfig' in 2.4.0 will work. `make menuconfig' from 2.2.16 works even when awk points to mawk. -- System Information Debian Release: testing/unstable Architecture: i386 Kernel: Linux vox 2.2.16+defvs #2 Sun Jul 2 23:24:58 CEST 2000 i586 Versions of packages mawk depends on: ii libc6 2.2-9 GNU C Library: Shared libraries an
--- End Message ---
--- Begin Message ---In 2010, Jonathan Nieder wrote: > So I tried to reproduce. With either v2.4.0 or v2.5.45~1^2~57 and > mawk as awk I was able to ‘make menuconfig’, choose some options, and > save the .config without trouble. I didn’t try Willy Tarreau’s modern > 2.4, but I would assume it has the same behavior. > > Any tips for reproducing (e.g., a .config from the time of failure)? It's not clear how to move forward on this without that, so closing.
--- End Message ---
