diff options
| author | Tom Tromey <tom@tromey.com> | 2020-03-25 10:26:38 -0600 |
|---|---|---|
| committer | Tom Tromey <tom@tromey.com> | 2020-03-25 11:24:08 -0600 |
| commit | 33aa3c10f663b834c9573ede439b2df3c92f0cfe (patch) | |
| tree | 3b69a7d88375519a703a8fbe75312c6a84fcbd6e /bfd | |
| parent | d503b685c6b7384b389767d5153235039e2b8fc4 (diff) | |
| download | gdb-33aa3c10f663b834c9573ede439b2df3c92f0cfe.zip gdb-33aa3c10f663b834c9573ede439b2df3c92f0cfe.tar.gz gdb-33aa3c10f663b834c9573ede439b2df3c92f0cfe.tar.bz2 | |
Fix error message in compile-object-load.c
I noticed that an error message in compile-object-load.c mentions the
wrong symbol name. The loop just above the error is looking for
COMPILE_I_EXPR_VAL, but the error references COMPILE_I_EXPR_PTR_TYPE.
I'm checking this in as obvious. I don't have a test case -- I
noticed it because another patch I'm working on caused this error to
be thrown, but that was due to regression in my patch.
gdb/ChangeLog
2020-03-25 Tom Tromey <tom@tromey.com>
* compile/compile-object-load.c (get_out_value_type): Mention
correct symbol name in error message.
Diffstat (limited to 'bfd')
0 files changed, 0 insertions, 0 deletions