search for: libc

...3.0/stubdom/../extras/mini-os/include/mini-os/time.h:22, à partir de /usr/src/xen-3.3.0/stubdom/../extras/mini-os/include/mini-os/sched.h:5, à partir de /usr/src/xen-3.3.0/stubdom/../extras/mini-os/include/errno.h:116, à partir de ../../../../../newlib-1.16.0/newlib/libc/argz/argz_add.c:7: /usr/src/xen-3.3.0/stubdom/../extras/mini-os/include/mini-os/types.h:22:20: erreur: stddef.h : Aucun fichier ou répertoire de ce type In file included from /usr/src/xen-3.3.0/stubdom/newlib-1.16.0/newlib/libc/include/sys/types.h:61, from /usr/src/xen-3.3.0/stu...

I have found that pid provider can not create memcpy:return probe for 64bit process on snv_110. For example, the pid is 10603, I will have following output for dtrace command: #dtrace -n pid10603:libc.so.1:memcpy:return dtrace: invalid probe specifier pid10603:libc.so.1:memcpy:return: probe description pid10603:libc.so.1:memcpy:return does not match any probes This just happens for 64bit process, 32bit process has no such a issue. Following is dtrace output for 32bit-process...

On Fri, Jun 28, 2019 at 9:29 AM JF Bastien <jfbastien at apple.com> wrote: > > I think I now understand some of the disconnect you and I are having, and I think some of the pushback you’re getting from the community is the same. You’re talking about where you want to start with an LLVM libc. Many in the community (myself included) want to understand where we’ll get with this libc. At steady-state, what does it do? To a certain degree I don’t care about how you get to the steady state: sure the implementation approach is important, and which contributor cares about what parts is import...

Somehow I wish not all parts of a libc but parts that can be provided without a JavaScript wrapper for .wasm can be provided from llvm's libc (leaving a stab implementation for the rest like file system). I've put together a minimal libc on [1] so using a 26kb .wasm binary file one can decode both PNG and JPG using this [2] simp...

Hello again, I would like to announce that we now have dedicated mailing lists for the llvm-libc project: 1. libc-dev - https://lists.llvm.org/cgi-bin/mailman/listinfo/libc-dev 2. libc-commits - https://lists.llvm.org/cgi-bin/mailman/listinfo/libc-commits A brief README.txt and LICENSE.txt have been added: https://github.com/llvm/llvm-project/tree/master/libc I will soon share or put out de...

...xff122d58: strlen+0x0058: sethi %hi(0x80808000), %o5 0xff122d5c: strlen+0x005c: bset 257, %o4 0xff122d60: strlen+0x0060: bset 128, %o5 % truss -f ./test-http-url <--- cut out the beginning of output ---> 28884: open("/platform/SUNW,SPARC-Enterprise-T5220/lib/libc_psr.so.1", O_RDONLY) = 3 28884: mmap(0x00010000, 9244, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_ALIGN, 3, 0) = 0xFF0E0000 28884: munmap(0xFF0E2000, 1052) = 0 28884: close(3) = 0 28884: getpid()...

http://dovecot.org/releases/2.2/dovecot-2.2.15.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.15.tar.gz.sig Some small fixes and changes to v2.2.14. This release is mainly in the hope that it could still make it into the next Debian stable instead of v2.2.14 - mainly because of a couple of new assert crashes that started happening in v2.2.14 and should be fixed now. * Plugins can now print

http://dovecot.org/releases/2.2/dovecot-2.2.15.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.15.tar.gz.sig Some small fixes and changes to v2.2.14. This release is mainly in the hope that it could still make it into the next Debian stable instead of v2.2.14 - mainly because of a couple of new assert crashes that started happening in v2.2.14 and should be fixed now. * Plugins can now print

I too am having this problem reported by Frank Hoonhout. Asterisk runs fine for a few minutes and then stops accepting new calls. (I have a standalone server with SIP phones and I'm not doing any external registration). Asterisk CVS-04/07/03-09:28:50 0x420e0037 in poll () from /lib/i686/libc.so.6 (gdb) info threads 16 Thread 14351 (LWP 7258) 0x420e187e in select () from /lib/i686/libc.so.6 15 Thread 16398 (LWP 7371) 0x420292e5 in sigsuspend () from /lib/i686/libc.so.6 14 Thread 12301 (LWP 7256) 0x420e0037 in poll () from /lib/i686/libc.so.6 13 Thread 11276 (LWP 7255) 0x4...

...8c90b95efeaf01a) Target: armv7l-unknown-linux-gnueabihf Thread model: posix InstalledDir: /opt/clang-latest/bin ... Expected Passes : 22688 Expected Failures : 141 Unsupported Tests : 422 Unexpected Passes : 13 Unexpected Failures: 31 ... ******************** Failing Tests (31): libc++abi :: catch_array_01.pass.cpp libc++abi :: catch_array_02.pass.cpp libc++abi :: catch_class_01.pass.cpp libc++abi :: catch_class_02.pass.cpp libc++abi :: catch_class_03.pass.cpp libc++abi :: catch_class_04.pass.cpp libc++abi :: catch_const_pointer_nullptr.pass.cpp libc...

I foresee problems with this on both Windows and non-Windows. A typical libc implementation has a lot of internal state that is shared across API boundaries in a way that is considered an implementation detail. So making assumptions about which state is shared and which isn't is going to be a problem. How do you guarantee that if you implement method A and forward met...

...AMINI <joker.eph at gmail.com> wrote: > > Hi, > > What happened since you committed the doc? Is this now graduated from a "proposal to start a project" to a project? I think it has now. > Is there any update to be made to the doc: http://llvm.org/docs//Proposals/LLVMLibC.html ? Not sure what kind of update you have in mind. However, I am in the process of preparing the first patch containing some design docs and small illustrative implementations. I should have it out by the end of the day today or tomorrow. > > Thanks, > > -- > Mehdi > > On...

On Sun, Nov 22, 2015 at 8:09 AM, Renato Golin <renato.golin at linaro.org> wrote: > On 22 November 2015 at 03:59, Brian Cain <brian.cain at gmail.com> wrote: > > Should I expect the "-openmp" to work for this RC? > > Only if it worked before on the target you're building to in 3.7.0. > Ok, I'll check if I can get it to work on 3.7.0. > >

...ions being baked in early on that make things very difficult for people to come along later and contribute a Windows implementation. This happened with sanitizers for example (lack of support for weak functions on Windows), LLDB (posix api calls scattered throughout the codebase), and I worry with libc it will be even more difficult to correctly design the abstraction because we have to deal with executable file format, syscalls, operating system loaders, and various linkage models. The most immediate thing I think we will run into is that you mentioned wanting this to take shape as something th...

...5-- REDIR: 0x4018a90 (ld-linux-x86-64.so.2:index) redirected to 0x4c2c810 (index) --3135-- REDIR: 0x4018b10 (ld-linux-x86-64.so.2:strcmp) redirected to 0x4c2ddb0 (strcmp) --3135-- REDIR: 0x4019c40 (ld-linux-x86-64.so.2:mempcpy) redirected to 0x4c30950 (mempcpy) --3135-- Reading syms from /usr/lib64/libcap.so.2.22 --3135-- object doesn't have a symbol table --3135-- Reading syms from /usr/lib64/libidn.so.11.6.11 --3135-- object doesn't have a symbol table --3135-- Reading syms from /usr/lib64/libc-2.17.so --3135-- Reading syms from /usr/lib64/libattr.so.1.1.0 --3135-- object doesn&...

Hello LLVM Developers, Within Google, we have a growing range of needs that existing libc implementations don't quite address. This is pushing us to start working on a new libc implementation. Informal conversations with others within the LLVM community has told us that a libc in LLVM is actually a broader need, and we are increasingly consolidating our toolchains around LLVM. Henc...

Hi, I would like to avoid the following situation: SRC has: -rwxr-xr-x 1 root staff 1596328 2005-04-29 17:34 libc-2.3.3.so -rw-r--r-- 1 root staff 193 2005-04-29 17:34 libc.so lrwxrwxrwx 1 root staff 13 2007-02-05 15:06 libc.so.6 -> libc-2.3.3.so DEST has: -rwxr-xr-x 1 dale dale 1558836 2008-02-07 12:25 libc-2.3.6.so -rw-r--r-- 1 dale dale 193 2008-02-07 11:46 libc.so lrwxrwxrwx 1 dale dale...

...d) is: syscall::write:entry, fbt::write:entry, pid$1::write:entry, pid$1::write:return, pid$1::_write:entry /pid==$1/ { printf("%s:%s:%s:%s\n",probeprov,probemod,probefunc,probename); stack(100); ustack(100); } /////////////////////////////// when runs the script, the result is : pid17632:libc.so.1:write:entry libc.so.1`write a.out`main+0x43 a.out`_start+0x7a pid17632:libc.so.1:_write:entry [b] libc.so.1`_write [u]libc.so.1`write+0x75[/u][/b] a.out`main+0x43 a.out`_start+0x7a syscall::write:e...

...AWQ. The process hung and can't be terminated. >From my investigation, it seems signal handler 'Rf_onsigusr1' trigger a malloc/free deadlock. The calling stack is below. Thread 1 (Thread 0x7f4c93af48e0 (LWP 431263)): #0 0x00007f4c9015805e in __lll_lock_wait_private () from /lib64/libc.so.6 #1 0x00007f4c900dd16b in _L_lock_9503 () from /lib64/libc.so.6 #2 0x00007f4c900da6a6 in malloc () from /lib64/libc.so.6 #3 0x00007f4c9008fb39 in _nl_make_l10nflist () from /lib64/libc.so.6 #4 0x00007f4c9008ddf5 in _nl_find_domain () from /lib64/libc.so.6 #5 0x00007f4c9008d6e0 in __dcigett...

> On 6/25/19 7:22 PM, Zachary Turner via llvm-dev wrote: > > I foresee problems with this on both Windows and non-Windows. A > > typical libc implementation has a lot of internal state that is shared > > across API boundaries in a way that is considered an implementation > > detail. So making assumptions about which state is shared and which > > isn't is going to be a problem. +1 for what Hal Finkel has said below...