Package: gnat-4.4
Version: 4.4.3-1
Severity: normal
Under some conditions, using GNAT.Expect.Non_Blocking_Spawn in
conjunction with GNAT.Expect.Close leads to memory corruption.
Given the following small reproducer:
-- expect_test.adb
with Ada.Text_IO;
with GNAT.Expect;
with GNAT.OS_Lib;
with
--- Comment #30 from mikpe at it dot uu dot se 2010-03-30 15:09 ---
(In reply to comment #29)
> Wouldn't it be better to just remove _Unwind_GetRegionStart?
> This function is not part of the ARM EABI, and removing it would expose any
> (already broken) users at compile time.
No.
First
--- Comment #29 from pbrook at gcc dot gnu dot org 2010-03-30 14:04 ---
Wouldn't it be better to just remove _Unwind_GetRegionStart?
This function is not part of the ARM EABI, and removing it would expose any
(already broken) users at compile time.
--
http://gcc.gnu.org/bugzilla/sho
--- Comment #28 from mikpe at it dot uu dot se 2010-03-30 13:21 ---
I've looked at the amount of .ARM.exidx entry merging being done and its
consequences for the various unwinders in gcc. Currently only table entries
with immediate (inlined) data are merged, and for that all of gcc exce
4 matches
Mail list logo
