[Bug 5954] New: res_nclose never returns
bugzilla at busybox.net
bugzilla at busybox.net
Tue Feb 19 16:58:24 UTC 2013
https://bugs.busybox.net/show_bug.cgi?id=5954
Host: arm-buildroot-linux-uclibcgnueabi
Target: arm-buildroot-linux-uclibcgnueabi
Build: x86_64-linux-gnu
Summary: res_nclose never returns
Product: uClibc
Version: 0.9.34
Platform: PC
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Networking
AssignedTo: unassigned at uclibc.org
ReportedBy: greg.beresford at zbdsolutions.com
CC: uclibc-cvs at uclibc.org
Estimated Hours: 0.0
Created attachment 4760
--> https://bugs.busybox.net/attachment.cgi?id=4760
demo program
The connman 1.10 package in buildroot uses the res_nclose function as part of
shutting down it's internal resolver representation. Since commit
1f9808dbf74fb771f6a631a4f37a2f2c3b9e4643 this function has a noreturn
attribute, and a while(1)..; at the end of it, causing it to spin forever and
use 100% cpu when res_nclose is called.
This doesn't seem correct and the noreturn attribute and the loop should
probably be removed.
I'm using uClibc daily snapshot 20120213, built by buildroot 2012.02_rc1, with
the attached .config. Specifically, gcc 4.6.3 and binutils 2.21.1.
Also attached is a little demo program which works when compiled with my host
toolchain, but hangs forever after printing 'Initialised' when compiled with
uClibc and run on my target.
--
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.
More information about the uClibc-cvs
mailing list