Files
binutils-gdb/gdb/testsuite/gdb.python
Hannes Domani 80ffe72264 Fix gdb.FinishBreakpoint when returning to an inlined function
Currently, when creating a gdb.FinishBreakpoint in a function
called from an inline frame, it will never be hit:
```
(gdb) py fb=gdb.FinishBreakpoint()
Temporary breakpoint 1 at 0x13f1917b4: file C:/src/repos/binutils-gdb.git/gdb/testsuite/gdb.python/py-finish-breakpoint.c, line 47.
(gdb) c
Continuing.
Thread-specific breakpoint 1 deleted - thread 1 no longer in the thread list.
[Inferior 1 (process 1208) exited normally]
```

The reason is that the frame_id of a breakpoint has to be the
ID of a real frame, ignoring any inline frames.

With this fixed, it's working correctly:
```
(gdb) py fb=gdb.FinishBreakpoint()
Temporary breakpoint 1 at 0x13f5617b4: file C:/src/repos/binutils-gdb.git/gdb/testsuite/gdb.python/py-finish-breakpoint.c, line 47.
(gdb) c
Continuing.

Breakpoint 1, increase_inlined (a=0x40fa5c) at C:/src/repos/binutils-gdb.git/gdb/testsuite/gdb.python/py-finish-breakpoint.c:47
(gdb) py print(fb.return_value)
-8
```

Approved-By: Tom Tromey <tom@tromey.com>
2023-12-12 15:57:14 +01:00
..
2023-01-13 13:18:58 -07:00
2023-01-13 13:18:58 -07:00
2023-01-13 13:18:58 -07:00
2023-01-13 13:18:58 -07:00
2023-01-13 13:18:58 -07:00
2023-01-13 13:18:58 -07:00
2023-01-13 13:18:58 -07:00
2023-01-13 13:18:58 -07:00
2023-01-13 13:18:58 -07:00
2023-05-23 10:09:28 -06:00
2023-01-13 13:18:58 -07:00
2023-01-13 13:18:58 -07:00
2023-01-13 13:18:58 -07:00
2023-01-13 13:18:58 -07:00
2023-05-23 10:09:28 -06:00
2023-01-26 18:28:31 -07:00
2023-01-26 18:28:31 -07:00
2023-01-13 13:18:58 -07:00
2023-01-22 14:27:49 -07:00
2023-02-27 15:46:31 -07:00
2023-02-27 15:46:31 -07:00
2023-02-27 15:46:31 -07:00
2023-01-25 09:02:11 -07:00
2023-06-03 22:43:57 +02:00
2023-01-13 13:18:58 -07:00
2023-01-13 13:18:58 -07:00
2023-06-19 17:13:05 +02:00
2023-01-13 13:18:58 -07:00
2023-09-08 13:06:47 -06:00
2023-06-03 22:43:57 +02:00
2023-06-03 22:43:57 +02:00
2023-01-13 13:18:58 -07:00