Re:Abusing GDB Features for Data Ingress and Egress
by overbytecode on Monday October 23, 2023 @02:44PM
(#37989853)
Iām confused, why would the debugging information file be an executable? These are just debugging symbols, no?
[ Parent
| on HN ]
Re:Abusing GDB Features for Data Ingress and Egress
by matthews2 on Monday October 23, 2023 @03:10PM
(#37990191)
The debug info is stored in an elf file, just like an executable. You can have them together in the same file, or you can use a tool like objcopy to make them separate.
Re:Abusing GDB Features for Data Ingress and Egress
by mschuster91 on Monday October 23, 2023 @04:34PM
(#37991208)
> or you can use a tool like objcopy to make them separate
which is how Debian generates the -debug packages [1].
[1] https://github.com/Debian/debhelper/blob/master/dh_strip
Re:Abusing GDB Features for Data Ingress and Egress
by brancz on Monday October 23, 2023 @05:08PM
(#37991613)
DWARF is touring complete and not the accidental kind, it has instructions and all. GDB implements the whole set so you can basically make GDB do arbitrary code execution if you control the DWARF data.
Re:Abusing GDB Features for Data Ingress and Egress
by jcranmer on Monday October 23, 2023 @11:52PM
(#37994704)
As far why it's not accidental, one of the primary purposes of DWARF is to be able to essentially describe "this source-level value is described by f(memory, registers)". Even if you wanted to restrict it to just the simple conditions like "this is described at stack offset N", there are cases where there might be variably-sized objects on the stack, and so you'd need to run a small function just to compute "N".