diff options
author | Andrew Burgess <aburgess@redhat.com> | 2022-12-12 14:09:40 +0000 |
---|---|---|
committer | Andrew Burgess <aburgess@redhat.com> | 2022-12-15 13:09:51 +0000 |
commit | 38665d717a3e65c70e6432243d5eed9728a4888a (patch) | |
tree | 0ed4534c4164e1ee25bee742046e7f45521989bb /gdb/python/py-breakpoint.c | |
parent | c896441822c9c5a506dfe302a292aaa41412058a (diff) | |
download | binutils-38665d717a3e65c70e6432243d5eed9728a4888a.zip binutils-38665d717a3e65c70e6432243d5eed9728a4888a.tar.gz binutils-38665d717a3e65c70e6432243d5eed9728a4888a.tar.bz2 |
gdb: use gdb_assert not internal_error
Spotted a couple of places in findvar.c where we use:
if ( ! CONDITION )
internal_error ("...");
this commit changes these to be:
gdb_assert ( CONDITION );
which I think is better.
Unless we happen to hit the internal_error calls (which was bad) there
should be no user visible changes after this commit.
Diffstat (limited to 'gdb/python/py-breakpoint.c')
0 files changed, 0 insertions, 0 deletions