Markus Metzger fb4f3f38e9 gdb, compile: unlink objfile stored in module ...

When cleaning up after a compile command, we iterate over all objfiles and
unlink the first objfile with the same name as the one we compiled.

Since we already store a pointer to that objfile in the module and use it
to get the name we're comparing against, there's no reason to iterate, at
all.  We can simply use that objfile.

This further avoids potential issues when an objfile with the same name is
loaded into a different linker namespace.

2022-10-18 14:16:09 +02:00

..

compile-c-support.c

gdb: remove TYPE_LENGTH

2022-09-21 11:05:21 -04:00

compile-c-symbols.c

Change GDB to use frame_info_ptr

2022-10-10 11:57:10 +02:00

compile-c-types.c

gdb: remove TYPE_LENGTH

2022-09-21 11:05:21 -04:00

compile-c.h

…

compile-cplus-symbols.c

Change GDB to use frame_info_ptr

2022-10-10 11:57:10 +02:00

compile-cplus-types.c

gdb: remove TYPE_LENGTH

2022-09-21 11:05:21 -04:00

compile-cplus.h

…

compile-internal.h

…

compile-loc2c.c

Change GDB to use frame_info_ptr

2022-10-10 11:57:10 +02:00

compile-object-load.c

gdb: remove TYPE_LENGTH

2022-09-21 11:05:21 -04:00

compile-object-load.h

…

compile-object-run.c

gdb, compile: unlink objfile stored in module

2022-10-18 14:16:09 +02:00

compile-object-run.h

…

compile.c

…

compile.h

…

gcc-c-plugin.h

…

gcc-cp-plugin.h

…