diff options
| author | Andrew Burgess <aburgess@redhat.com> | 2025-08-20 10:45:09 +0100 |
|---|---|---|
| committer | Andrew Burgess <aburgess@redhat.com> | 2025-08-21 11:47:17 +0100 |
| commit | dbd05b9edcf760a7001985f89bc760358a3c19d7 (patch) | |
| tree | 58b47b9fb55f36eed931c768dbd17e48f53e8d9d /gdb/testsuite/gdb.fortran/pointer-to-pointer.f90 | |
| parent | 8186f0d31ddf339ba6803cde97ef6a6310ca2587 (diff) | |
| download | gdb-dbd05b9edcf760a7001985f89bc760358a3c19d7.zip gdb-dbd05b9edcf760a7001985f89bc760358a3c19d7.tar.gz gdb-dbd05b9edcf760a7001985f89bc760358a3c19d7.tar.bz2 | |
gdb/python: check return value of PyObject_New in all cases
I spotted a few cases where the return value of PyObject_New was not
being checked against nullptr, but we were dereferencing the result.
All fixed here. The fixed functions can now return NULL, so I checked
all the callers, and I believe there will handle a return of NULL
correctly.
Assuming calls to PyObject_New never fail, there should be no user
visible changes after this commit.
No tests here as I don't know how we'd go about causing a Python
object allocation to fail.
Approved-By: Simon Marchi <simon.marchi@efficios.com>
Diffstat (limited to 'gdb/testsuite/gdb.fortran/pointer-to-pointer.f90')
0 files changed, 0 insertions, 0 deletions