Re: Using LD_PRELOAD wrappers to identify problem use of shared library functions

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 03/10/2011 08:25 AM, William Cohen wrote:
> git repo at:
> 
> http://fedorapeople.org/gitweb?p=wcohen/public_git/memstomp;a=summary

Actually: git clone git://fedorapeople.org/home/fedora/wcohen/public_git/memstomp

The implementation has some properties:
1.  Not async signal safe [malloc, fprintf], as noted previously by Daniel Berrange.
2.  Not thread safe: unguarded top-level static variables in backtrace-symbols.c.
3.  Essentially bundles a private copy of libbfd.
4.  Needs work for a process tree that uses a mixture of 32-bit and 64-bit programs.
5.  Does not catch violations in compile-time inlined expansions.
6.  SIGSEGVs for violations from just-in-time compiled code: uninit local
    variables in backtrace_symbols() not set by calls to dl_iterate_phdr.

-- 
-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux