lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 29 Dec 2020 10:56:08 -0800
From:   Joe Perches <>
To:     Jim Cromie <>,,,
Subject: Re: [RFC PATCH v2 00/19] dynamic debug diet plan

On Fri, 2020-12-25 at 13:19 -0700, Jim Cromie wrote:
> Well, we're mostly overeating, but we can all look forward to a diet
> in January.  And more exersize.
> dyndbg's compiled-in data-table currently uses 56 bytes per prdebug;
> this includes 3 pointers to hierarchical "decorator" data, which is
> primarily for adding "module:function:line:" prefixes to prdebug
> messages, and for enabling and modifying those prdebugs selectively.
> This patchset decouples "decorator" data, and makes it optional, and
> disposable.  By separating that data, it opens up possiblities to
> compress it, swap it out, map it selectively, etc.

While this may be somewhat useful, what debugging does it really help?
Are there really memory limited platforms that enable dynamic debug?

Powered by blists - more mailing lists