Re: [Buildroot] uClibc build verbosity control

Hi Vineet, Vineet Gupta wrote, Hi, uClibc verbosity control V=xx is different from other mainstream projects: namely Busybox and Linux kernel. To print full cmdlines (when debugging obscure toolchain issues) we need to pass V=2 whereas kernel/busybox take V=1. Can this be changed (I

Re: [RFC] Cannot notify GDB when a new thread is created

On April 27, 2015 3:33:35 AM GMT+02:00, Sheng Yong shengyo...@huawei.com wrote: Hi, folks, When we testing GDB on uClibc, we find that some GDB testcases cannot pass. Here is one of them, no-unwaited-for-left.c, could be fount here,

Re: [Buildroot] uClibc build verbosity control

On April 27, 2015 11:21:10 AM GMT+02:00, Waldemar Brodkorb w...@openadk.org wrote: Hi Vineet, Vineet Gupta wrote, Hi, uClibc verbosity control V=xx is different from other mainstream projects: namely Busybox and Linux kernel. To print full cmdlines (when debugging obscure toolchain issues)

[PATCH] init.c (__nptl_initial_report_events): New variable.

From: Roland McGrath rol...@gnu.org (__pthread_initialize_minimal_internal): Initialize pd-report_events to that. This patch helps NPTL report TD_CREATE event, so that GDB could catch the event and update its thread_list. Link:

[PATCH] _scanf.c: Implement 'm' modifier for 'c' and '[' conversions.

From: Will Newton will.new...@imgtec.com The current code implements the 'm' modifier only for 's' conversions and would cause a segfault if it was used for 'c' or '[' conversions. This patch extends the code to cover these cases too. The original version could write scanned data outside the