Hi Vyacheslav, On 5 May 2015 at 08:10, Vyacheslav Barinov <[email protected]> wrote: > Hello, > > Actually I can't say which exact environment change caused the problem, it > was detected after > migration our distro (Tizen) from glibc 2.18 to glibc 2.20. > > But that could be just a coincidence and the problem showed itself due to > some combination of > other factors.
Thanks for the inputs. I'm not able to reproduce and check that the issue is fixed, but for me the patch is okay and there is no regression. Is it ok for you Arun ? Thanks, Yvan > Best Regards, > Vyacheslav Barinov > > Yvan Roux <[email protected]> writes: > >> Hi, >> >> On 29 April 2015 at 09:45, Yvan Roux <[email protected]> wrote: >>> Hi, >>> >>> On 29 April 2015 at 05:36, Arun Sharma <[email protected]> wrote: >>>> On Wed, Apr 15, 2015 at 4:34 AM, <[email protected]> wrote: >>>>> From 20355c6dd143ea295256da17d6edd334ba754120 Mon Sep 17 00: 00:00 2001 >>>>> From: Vyacheslav Barinov <[email protected]> >>>>> Date: Wed, 15 Apr 2015 14:08:06 +0300 >>>>> Subject: [PATCH] arm: Validate memory before access >>>>> >>>>> Prevent SIGSEGV due to accessing addresses now mapped to current process >>>>> >>>> >>>> The patch looks good, but I don't have an ARM machine to test. Yvan, >>>> do you mind taking a look? >>> >>> Sure, I'll try to do it quickly. >> >> Sorry for the delay. Patch looks okay for me as well, and no >> regression observed on a ARM box, but do you have a way to reproduce >> the initial problem ? >> >> Thanks, >> Yvan _______________________________________________ Libunwind-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/libunwind-devel
