dwz is completely different thing. dwz optimizes dwarf data while objdump just compress (zlib)
whole sections. the difference is visible on non-trivial shared objects compiled with -g2 in few ways:
1). when you have a big application with 200+ big shared objects in use
then the gdb startup time is much shorter with compressed debug info.
this is a major benefit for debug/build/debug cycles.
2). relinking libraries is faster (linker reads/writes less data from deps
with compressed sections). one more benefit for debug/build cycles.
3). objdump compression is more effective than dwz.
dwz is completely different thing. dwz optimizes dwarf data while objdump just compress (zlib)
whole sections. the difference is visible on non-trivial shared objects compiled with -g2 in few ways:
1). when you have a big application with 200+ big shared objects in use
then the gdb startup time is much shorter with compressed debug info.
this is a major benefit for debug/build/debug cycles.
2). relinking libraries is faster (linker reads/writes less data from deps
with compressed sections). one more benefit for debug/build cycles.
3). objdump compression is more effective than dwz.
170M libgenChip.so so.zdebug
65M libgenChip.
148M libgenChip.so.dwz so.dwz. zdebug
60M libgenChip.