| commit | 076488bfbb80142ce014fffc8d65db05b4e2818a | |
| author | hjk <qtc-committer@nokia.com> | |
| Wed, 21 Jan 2009 10:12:12 +0000 (21 11:12 +0100) | ||
| committer | hjk <qtc-committer@nokia.com> | |
| Wed, 21 Jan 2009 10:12:12 +0000 (21 11:12 +0100) | ||
| tree | a168ec78805ac4b9481f03de037cd98d8f2bcbff | treesnapshot (tar.gz zip) |
| parent | f1a7c95813322a5988e7e3f0396a2e745a29419c | commitdiff |
Use gdb's 'print' command to access dumper output.
Simple solution after all. This idea got initially dropped early in the
process because it does not handle binary data and using x/x was
way to slow. But since we use only printable characters now thanks
to base64 encoding etc using 'p' becomes feasible again and simplifies
the process vastly as no additional communication channel is needed anymore.
Simple solution after all. This idea got initially dropped early in the
process because it does not handle binary data and using x/x was
way to slow. But since we use only printable characters now thanks
to base64 encoding etc using 'p' becomes feasible again and simplifies
the process vastly as no additional communication channel is needed anymore.