> > The new test fails for me like this:
> > 
> >     (gdb) info exceptions
> >     All defined Ada exceptions:
> >     const.aint_global_e: 0x608120
> >     (gdb) FAIL: gdb.ada/info_exc.exp: info exceptions
> > 
> > The test case expects there to be more exceptions:
> > 
> >     gdb_test "info exceptions" \
> >         [multi_line "All defined Ada exceptions:" \
> >                     "constraint_error: $hex" \
> >                     "program_error: $hex" \
> >                     "storage_error: $hex" \
> >                     "tasking_error: $hex" \
> >                     "const.aint_global_e: $hex"]
> > 
> > Any ideas why this may happen?

I think I have an idea, now. It is similar to what we need to do
in the "catch exception" testcases, where we start the program
in order to be certain that we can find the symbols from the GNAT
runtime. On Fedora, and I suspect may other distros, the default
for gnatmake is to like against the shared libgnat, whereas the
gnatmake I use links against the static libgnat - this is why
I didn't see that omission. Can you try the attached?

gdb/ChangeLog:

        * gdb.ada/info_exc.exp: Start inferior before starting
        the "info exceptions" tests.
        * gdb.ada/mi_exc_info.exp: Start inferior before starting
        the "-info-ada-exceptions" tests.

Tested on x86_64-linux.

-- 
Joel