[Bug gdb/34047] gdb Fatal signal: Bus error | SIGBUS (Misaligned address error)
k4lizen at proton dot me via Gdb-prs <[email protected]>
| Newsgroups | gmane.comp.gdb.bugs.discuss |
|---|---|
| Message-ID | <[email protected]/bugzilla/> |
https://sourceware.org/bugzilla/show_bug.cgi?id=34047 --- Comment #12 from k4lizen <k4lizen at proton dot me> --- > This shows GDB hitting an internal error. To investigate it, we'd probably have > to be able to reproduce it with a GDB compiled with debug info, so we can debug > it properly. You may compile GDB inside the docker (or share a volume of a compiled GDB into the docker from the host). Then you can put it ahead in PATH so it's picked up before /venv/bin/gdb . E.g. if the compiled GDB with debug info is in the home dir you can: ```bash cd ~ PATH=$(pwd):$PATH ./exploit.py ``` Alternatively, you can: ```bash pip install -U pwntools ``` and put ```python context.gdb_binary = "path/to/my/gdb" ``` near the top of the `./exploit.py` file. In this case you don't need to touch PATH. > I don't recall if I used debuginfod, but anyway I would need DEBUGINFOD_URLS to > point to the right server, I have no idea which server has the debug info for > these specific artifacts. I'm on arch, so https://debuginfod.archlinux.org/ , though not sure if the debug info for packages that get updated is kept. -- You are receiving this mail because: You are on the CC list for the bug.