search for: __vfprintf

Michael Johnson via llvm-dev <llvm-dev at lists.llvm.org> writes: > Hi Rui, > > Are there any plans to support the -defsym command line option? It doesn't look that hard, it was just never requested. What project is using it? Cheers, Rafael

...ust never requested. What project is >> using it? > Not sure I understand what the project set is. It's not an uncommon > feature for a linker in the embedded world. > > It's the first problem I discovered when trying to use lld rather than > ld e.g. > > -defsym=__vfprintf=__vfprintf_float_long_long > > to select a particular implementation of printf. > > The second problem was failing to parse the .ld script - I can provide > it if required. If you could open bugs for both that would be awesome. Thanks, Rafael

...er(user at hostname): Indexed 1 messages in INBOX Dec 16 12:32:18 mail02 dovecot: indexer-worker: Fatal: master: service(indexer-worker): child 18977 killed with signal 11 (core dumped) == GDB == (gdb) bt #0 strlen () at /usr/src/lib/libc/arch/amd64/string/strlen.S:152 #1 0x0000093434d7c120 in __vfprintf (fp=0x7f7fffff96c0, fmt0=0x9343cef79ae "Timeout leak: %p (%s:%u)", ap=Variable "ap" is not available. ) at /usr/src/lib/libc/stdio/vfprintf.c:885 #2 0x0000093434d9b068 in *_libc_vsnprintf (str=0x933ab0940b8 "Timeout leak: 0x9342f652300", n=120, fmt=0x9343cef79ae &quot...

...reports bad format >> specifications. > > 2.7.2 is obsolete, but I can confirm a crash on Windows with a recent > R-devel. Can confirm as well on OSX with a fairly recent R-devel. (gdb) bt 10 #0 0x9575e299 in _UTF8_wcsnrtombs () #1 0x957bb3a0 in wcsrtombs_l () #2 0x956ebc1e in __vfprintf () #3 0x95711e66 in sprintf () #4 0x00492bb8 in do_sprintf (call=0x10cb470, op=0x1018924, args=<value temporarily unavailable, due to optimizations>, env=0x10a40b0) at ../../../../R-devel-all/src/main/sprintf.c:179 #5 0x003fe1af in do_internal (call=0x10cb4a8, op=0x100fc38, args=0x10a40e8,...

...#39; is missing: using /Users/hadley/Library/R/library/ Reading symbols for shared libraries . done Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_INVALID_ADDRESS at address: 0x5f4d4550 0x90002f48 in strlen () (gdb) where #0 0x90002f48 in strlen () #1 0x9000d7d0 in __vfprintf$LDBL128 () #2 0x900273cc in vsnprintf$LDBL128 () #3 0x0108ea1c in Rvsnprintf (buf=0xbfff35f4 "B", size=1000, format=0x3 <Address 0x3 out of bounds>, ap=0x34 <Address 0x34 out of bounds>) at ../../../../R-2.3.0/src/main/errors.c:211 #4 0x01092e68 in Rf_warning (format=0x3 &l...

...8 snprintf (in libsystem_c.dylib) + 156 [0x7ff8198c60d4] 8438 vsnprintf_l (in libsystem_c.dylib) + 41 [0x7ff8198c6020] 8438 _vsnprintf (in libsystem_c.dylib) + 256 [0x7ff8198e87ce] 8438 __vfprintf (in libsystem_c.dylib) + 113 [0x7ff8198b9ef7] 8438 localeconv_l (in libsystem_c.dylib) + 52 [0x7ff8198be2f4] 8438 _os_unfair_lock_lock_slow (in libsystem_platform.dylib) + 258 [0x7ff819a3cb67]...

FYI, looks like support for Racoon is ending. Does anyone have any experience with the version in ipsec-tools ? ---Mike >Racoon users, > >This is the announcement that the kame project will quit providing >a key management daemon, the racoon, and that "ipsec-tools" will become >the formal team to release the racoon. >The final release of the racoon in the