Re: Calling 'abort' on bounds violations in libmpx

2016-12-26 Thread Alexander Ivchenko
Submitted as r243928. Thank you 2016-12-08 20:22 GMT+03:00 Ilya Enkovich : > 2016-12-08 12:21 GMT+03:00 Alexander Ivchenko : >> I've tested the patch on MPX HW, no new regressions. Attached the >> final version below, would that be ok to submit? > >

Re: Calling 'abort' on bounds violations in libmpx

2016-12-08 Thread Ilya Enkovich
2016-12-08 12:21 GMT+03:00 Alexander Ivchenko : > I've tested the patch on MPX HW, no new regressions. Attached the > final version below, would that be ok to submit? The patch is OK. Ilya > > > 2016-11-29 Alexander Ivchenko > > *

Re: Calling 'abort' on bounds violations in libmpx

2016-12-08 Thread Alexander Ivchenko
I've tested the patch on MPX HW, no new regressions. Attached the final version below, would that be ok to submit? 2016-11-29 Alexander Ivchenko * mpxrt/libtool-version: New version. * mpxrt/mpxrt-utils.c (set_mpx_rt_stop_handler): New function. (print_help):

Re: Calling 'abort' on bounds violations in libmpx

2016-12-01 Thread Alexander Ivchenko
Should changing minor version of the library be enough? diff --git a/libmpx/mpxrt/libtool-version b/libmpx/mpxrt/libtool-version index 7d99255..736d763 100644 --- a/libmpx/mpxrt/libtool-version +++ b/libmpx/mpxrt/libtool-version @@ -3,4 +3,4 @@ # a separate file so that version updates don't

Re: Calling 'abort' on bounds violations in libmpx

2016-11-29 Thread Ilya Enkovich
2016-11-29 17:43 GMT+03:00 Alexander Ivchenko : > Hi, > > Attached patch is addressing PR67520. Would that approach work for the > problem? Should I also change the version of the library? Hi! Overall patch is OK. But you need to change version because you change default