GEF+GDB version

GEF: (Standalone)
Blob Hash([redacted].gdbinit-gef.py): 1a409c397646df9c0b8549d576cd7c7f8ec1ef47
SHA256([redacted].gdbinit-gef.py): f096ff3bf50df08dbbc698a919360014f86f1eea315011cdabebd72a30a5bce8
GDB: 13.2
GDB-Python: 3.11

Operating System

Distributor ID: Debian Description: Debian GNU/Linux rodete

Describe the issue you encountered

When ring a freshly built debug copy of chromium, I'm dealing with very very slow launch times. On a normal GDB, it launches within 5 seconds, but with GEF, it takes near 5 minutes to load what I'm assuming is the symbol files into memory. Worth noting that this occurs every run of the program, including relaunches in the same GDB session, meaning that GEF is unusable for my use case.

It also consumes about twice the memory, from 10G to 17G.

I have a feeling GEF just isn't built for this and this isn't fixable, but a confirmation on that would be nice.

Do you read the docs and look at previously closed issues/PRs for similar cases?

Yes

Architecture impacted

• X86
• X64
• ARM
• ARM64
• MIPS
• MIPS64
• PPC
• PPC64
• RISCV

Describe your issue. Without a proper reproduction step-by-step, your issue will be ignored.

Compile chromium, then run it.

The instructions to do this are in detail here:
https://chromium.googlesource.com/chromium/src/+/main/docs/linux/build_instructions.md
https://chromium.googlesource.com/chromium/src/+/0e94f26e8/docs/linux_debugging.md

However, if you wish to reproduce this, it will take many hours of your day - cloning the repo takes a half hour on a gigabit connection last I checked, and consumes 100G of hard drive space, and building the repo without a distributed compiler might take a few hours depending on your setup.

Minimalist test case

N/A

Additional context?

No response