diff options
| author | Tom Tromey <tom@tromey.com> | 2023-01-18 16:36:52 -0700 |
|---|---|---|
| committer | Tom Tromey <tom@tromey.com> | 2023-01-20 11:02:23 -0700 |
| commit | 6ec27270ff995940ffa532ee15414300782c30e8 (patch) | |
| tree | b998ec938089ca2fe192b5bd5d9cda7587f83521 /gdb/thread.c | |
| parent | 42938c1a5b84207e9b6526e56d8e57e1ad3bab5f (diff) | |
| download | gdb-6ec27270ff995940ffa532ee15414300782c30e8.zip gdb-6ec27270ff995940ffa532ee15414300782c30e8.tar.gz gdb-6ec27270ff995940ffa532ee15414300782c30e8.tar.bz2 | |
Use bool in pc_in_* functions
I noticed that pc_in_unmapped_range had a weird return type -- it was
returning a CORE_ADDR but intending to return a bool. This patch
changes all the pc_in_* functions to return bool instead.
Diffstat (limited to 'gdb/thread.c')
| -rw-r--r-- | gdb/thread.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/gdb/thread.c b/gdb/thread.c index 3ce7048..efcbe64 100644 --- a/gdb/thread.c +++ b/gdb/thread.c @@ -968,7 +968,7 @@ can_access_registers_thread (thread_info *thread) return true; } -int +bool pc_in_thread_step_range (CORE_ADDR pc, struct thread_info *thread) { return (pc >= thread->control.step_range_start |