search for: udrepper

Hi, I just wanted to brought you attention to the glibc 2.10 changelog. Take a special attention to the bottom (to the 'Automatic use of optimized function' section). URL: http://udrepper.livejournal.com/20948.html This seems to be a nice way to make fat binaries. Not in the apple lingo, but to make binaries with code optimized for different archs. This sounds great to, at least, bundle different versions of some functions like strlen and the likes. Nuno

...e.g., .bashrc: export MALLOC_PERTURB_=$(($RANDOM % 255 + 1)) This change ensures that it's enabled for anyone running "make check" and in particular for koji. There's probably documentation somewhere, but I don't know where off hand, so this will have to do: http://udrepper.livejournal.com/11429.html >From e7ee94be7e929d8aa94e3e360d1d1ca3711dd01e Mon Sep 17 00:00:00 2001 From: Jim Meyering <meyering at redhat.com> Date: Thu, 13 Aug 2009 18:29:59 +0200 Subject: [PATCH libguestfs] tests: increase likelihood that heap abuse triggers failure * regressions/Make...

"Nuno Lopes" <nunoplopes at sapo.pt> writes: > Hi, Hello, > I just wanted to brought you attention to the glibc 2.10 changelog. Take a > special attention to the bottom (to the 'Automatic use of optimized > function' section). URL: http://udrepper.livejournal.com/20948.html > This seems to be a nice way to make fat binaries. IMO, fat binaries should go away and be replaced by LLVM bitcode, with code generation performed by the OS at load time. This would have many advantages: the compatibility with all current and future architectures wo...

Is this the right mailing list ? I want to compile llvm-2.5 under Fedora 11 with gcc (GCC) 4.4.0 20090506 (Red Hat 4.4.0-4) and get In file included from Signals.cpp:31: Unix/Signals.inc: In function ‘void<unnamed>::PrintStackTrace()’: Unix/Signals.inc:81: error: invalid conversion from ‘const char*’ to ‘char*’ Unix/Signals.inc:96: error: invalid conversion from ‘const char*’ to ‘char*’

...le glibc functions and use whatever is available (for danpb). (4) Removed the old shell_quote function instead of just commenting it out. Can anyone decode from Uli's message[1] whether these new functions are going to be added to POSIX 2008? It's not very clear to me. Rich. [1] http://udrepper.livejournal.com/20948.html -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://et.redhat.com/~rjones/virt-top --------------...

...struct printf_info *info, size_t n, int *argtypes, int *size); + /* Location to mount root device. */ const char *sysroot = "/sysroot"; /* No trailing slash. */ int sysroot_len = 8; @@ -76,6 +81,10 @@ main (int argc, char *argv[]) uint32_t len; struct sigaction sa; + /* http://udrepper.livejournal.com/20948.html */ + register_printf_specifier ('Q', print_shell_quote, print_arginfo); + register_printf_specifier ('R', print_sysroot_shell_quote, print_arginfo); + for (;;) { c = getopt_long (argc, argv, options, long_options, NULL); if (c == -1) break;...

Two ideas, one more controversial than the other. First: auto-killing bloated workers.?My current app has some memory leakage that wasn''t really visible on our older passenger setup, since the auto-scaling meant that bloated workers got killed periodically. In a perfect world, we''d find and patch all of the leaks, but in the meantime (and as a safety net) I''d like to get