diff options
| author | Tom Tromey <tom@tromey.com> | 2018-10-25 09:00:52 -0600 |
|---|---|---|
| committer | Tom Tromey <tom@tromey.com> | 2018-10-30 07:06:17 -0600 |
| commit | 4d5d104997da3b7beaaf7920caee40dcff8a78d9 (patch) | |
| tree | 96b1046b159064892c977afe36ea362e209948e7 /ChangeLog | |
| parent | fd332753fa7050bb9d7c89147e32d285099fe402 (diff) | |
| download | gdb-4d5d104997da3b7beaaf7920caee40dcff8a78d9.zip gdb-4d5d104997da3b7beaaf7920caee40dcff8a78d9.tar.gz gdb-4d5d104997da3b7beaaf7920caee40dcff8a78d9.tar.bz2 | |
Check return value of bfd_init
Alan recently added a way for BFD library users to check whether they
were in fact loading a compatible version of BFD:
https://sourceware.org/ml/binutils/2018-10/msg00198.html
It seemed reasonable to me that gdb should do this check as well, in
case someone is dynamically linking against BFD.
Simon pointed out that an earlier version of the patch would cause a
gdb crash if the test failed. This version works around this by
lowering the call to bfd_init and adding a comment explaining where
'error' can safely be called in captured_main_1.
gdb/ChangeLog
2018-10-30 Tom Tromey <tom@tromey.com>
* main.c (captured_main_1): Check return value of bfd_init.
Diffstat (limited to 'ChangeLog')
0 files changed, 0 insertions, 0 deletions