search for: __size

We created a 64bit SLES11 SP1 guest, and then used a script to change memory (using mem-set command) periodically (in 1 second): set 1G, set 2G, set 1G, set 2G, and so on. After a few minutes, we encountered QEMU exit due to SIGBUS error. Below is the call trace captured by gdb: The call trace: Program received signal SIGBUS, Bus error. 0x00007f94f74773d7 in memcpy () from /lib64/libc.so.6 (gdb)

...fines at_quick_exit. > > include/cstdlib: > > #include <__config> > #include <stdlib.h> > #ifdef _LIBCPP_HAS_C11_FEATURES > using ::aligned_alloc; > #endif And yes my stdlib.h has /usr/include/stdlib.h:extern void *aligned_alloc (size_t __alignment, size_t __size) I am guessing you are running on this on an old system. My glibc version is 2.17 Regards. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130513/dad2fbf7/attachment.html>

...n __error (); } unsigned long int __strtoul_internal(const char *__nptr, char **__endptr, int __base, int __group) { return strtoul (__nptr, __endptr, __base); } void __terminate() { fprintf (stderr, "terminate!\n"); } ssize_t __write (int __fd, const void *__buf, size_t __size) { return write (__fd, __buf, __size); } int __fxstat(int __ver, int __filedesc, struct stat *__stat_buf) { return fstat (__filedesc, __stat_buf); } int __xstat(int __ver, const char *__filename, struct stat *__stat_buf) { return stat (__filename, __stat_buf); } I installed this new ver...

A recent change added defined(__linux__) condition to the code below. Now it says that on linux with --std=c++0x (or --std=c++11) the system stdlib.h header must define aligned_alloc(). Really? include/__config: #if ( defined(__FreeBSD__) || defined(__linux__) ) && (__ISO_C_VISIBLE >= 2011 || __cplusplus >= 201103L) #define _LIBCPP_HAS_QUICK_EXIT #define _LIBCPP_HAS_C11_FEATURES

I have a new problem: Register RBP is used in a function foo. (I am not allocating RBP to any virtual register, the instances of RBP in function foo are in the machine code when my register allocator starts.) Function foo calls function bar. Register RBP is not saved across the call, though it is live after the call. Function bar includes a virtual register. The code that I'm using to

...trict __stream, char *__restrict __buf) __attribute__ ((__nothrow__)); extern int setvbuf (FILE *__restrict __stream, char *__restrict __buf, int __modes, size_t __n) __attribute__ ((__nothrow__)); extern void setbuffer (FILE *__restrict __stream, char *__restrict __buf, size_t __size) __attribute__ ((__nothrow__)); extern void setlinebuf (FILE *__stream) __attribute__ ((__nothrow__)); extern int fprintf (FILE *__restrict __stream, __const char *__restrict __format, ...); extern int printf (__const char *__restrict __format, ...); extern int sprintf (char *_...

...1 in2=4 conf=`ADDCOMP_SUB WMEM in=r2 in_addr=r1 conf=`WMEM_SI CONST_16B out=r3 conf=12 JUMP nl_out=r2/*RA*/ addr_in=&_malloc conf=`JUMP_ALWAYS_ABS // Call In case this is important, here is the relevant declarations from the 'stdlib.h' that is in use: _PTR _EXFUN(malloc,(size_t __size)); _VOID _EXFUN(free,(_PTR)); where: #define _PTR void * #define _EXFUN(name, proto) name proto and from 'newlib.c': void * malloc (size_t sz) { ... } i.e. They look like any other function call, which is why I suspect it has something to do with special behav...

as the next klibc release 1.5.16 looks like shaping up, I have a trouble to build that for Debian. currently I build depent on linux-libc-dev, I don't know what against I can build latest klibc, see klibc fails to build due too: make -C linux/ ARCH=x86_64 INSTALL_HDR_PATH=debian/tmp/usr/lib/klibc/ headers_install make[3]: *** No rule to make target `headers_install'. Stop. make[2]: ***

...>> >> #include <__config> >> #include <stdlib.h> >> #ifdef _LIBCPP_HAS_C11_FEATURES >> using ::aligned_alloc; >> #endif > > > And yes my stdlib.h has > > /usr/include/stdlib.h:extern void *aligned_alloc (size_t __alignment, size_t > __size) > > I am guessing you are running on this on an old system. My glibc version is > 2.17 Yes. Ubuntu 12.04 LTS with glibc 2.15 does not have aligned_alloc.

...0x00007f793b09cd0c in virMutexLock (m=0x7f78d80edd30) at util/virthread.c:89 89 pthread_mutex_lock(&m->lock); (gdb) p *m $5 = {lock = {__data = {__lock = 2, __count = 0, __owner = 1312, __nusers = 1, __kind = 512, __spins = 0, __elision = 0, __list = {__prev = 0x0, __next = 0x0}}, __size = "\002\000\000\000\000\000\000\000 \005\000\000\001\000\000\000\000\002", '\000' <repeats 21 times>, __align = 2}} i switch to frame 21 (LWP1312) i taek a look to the bt: (gdb) bt #0 __lll_lock_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135 #1 0x0000...

...; make: *** [install-tools] Error 2 The posix_memalign function is declared in /usr/include/stdlib.h (which is included in xenpaging.c): #ifdef __USE_XOPEN2K /* Allocate memory of SIZE bytes with an alignment of ALIGNMENT. */ extern int posix_memalign (void **__memptr, size_t __alignment, size_t __size) __THROW __nonnull ((1)); #endif So, I edit the Makefile in tools/xenpaging and add the line: CFLAGS += -D__USE_XOPEN2K However, when I recompile, I get the same error. There also seems to be another condition in stdlib.h that must be satisfied before the __USE_XOPEN2K one will be checked:...

...2 in_addr=r1 conf=`WMEM_SI > CONST_16B out=r3 conf=12 > JUMP nl_out=r2/*RA*/ addr_in=&_malloc conf=`JUMP_ALWAYS_ABS // Call > > > In case this is important, here is the relevant declarations from the > 'stdlib.h' that is in use: > > _PTR _EXFUN(malloc,(size_t __size)); > _VOID _EXFUN(free,(_PTR)); > > > where: > > #define _PTR void * > #define _EXFUN(name, proto) name proto > > > and from 'newlib.c': > > void * > malloc (size_t sz) > { > ... > } > > > i.e. They loo...

...ta' refers to type 0x10bb1e99 which extends beyond the bounds of 0x10b9a901* *error: biggrep_master_server_async 0x10b98edc: DW_TAG_member 'small_' refers to type 0x10bb1d9f which extends beyond the bounds of 0x10b98ed3* *error: biggrep_master_server_async 0x10baf034: DW_TAG_member '__size' refers to type 0x10baf04d which extends beyond the bounds of 0x10baefae* (facebook::biggrep::BigGrepMasterAsync *) this = 0x00007fd14d374fd0 (const string &const) corpus = error: summary string parsing error: { store_ = { = { small_ = {} *ml_ = (data_ = "��UH\x89�H�...

...pe 0x10bb1e99 which extends beyond the bounds of > 0x10b9a901* > *error: biggrep_master_server_async 0x10b98edc: DW_TAG_member 'small_' > refers to type 0x10bb1d9f which extends beyond the bounds of 0x10b98ed3* > *error: biggrep_master_server_async 0x10baf034: DW_TAG_member '__size' > refers to type 0x10baf04d which extends beyond the bounds of 0x10baefae* > (facebook::biggrep::BigGrepMasterAsync *) this = 0x00007fd14d374fd0 > (const string &const) corpus = error: summary string parsing error: { > store_ = { > = { > small_ = {} >...

On 13 January 2010 12:05, Mark Muir <mark.i.r.muir at gmail.com> wrote: > On 13 Jan 2010, at 16:43, Nick Lewycky wrote: > > > Mark Muir wrote: > >> - Run the existing Clang tool on each source file, using -emit-llvm to > generate a .bc file for each module. > >> - Run llvm-link to merge them into a single .bc file. > >> - Run llc to generate a

...urns valid, not truncated ancillary object + * HEADER. But caller still MUST check, that cmsg->cmsg_len is + * inside range, given by msg->msg_controllen before using + * ancillary object DATA. --ANK (980731) + */ + +static inline struct cmsghdr * __cmsg_nxthdr(void *__ctl, __kernel_size_t __size, + struct cmsghdr *__cmsg) +{ + struct cmsghdr * __ptr; + + __ptr = (struct cmsghdr*)(((unsigned char *) __cmsg) + CMSG_ALIGN(__cmsg->cmsg_len)); + if ((unsigned long)((char*)(__ptr+1) - (char *) __ctl) > __size) + return (struct cmsghdr *)0; + + return __ptr; +} + +static inline...

...ich extends beyond the bounds of >> 0x10b9a901* >> *error: biggrep_master_server_async 0x10b98edc: DW_TAG_member 'small_' >> refers to type 0x10bb1d9f which extends beyond the bounds of 0x10b98ed3* >> *error: biggrep_master_server_async 0x10baf034: DW_TAG_member '__size' >> refers to type 0x10baf04d which extends beyond the bounds of 0x10baefae* >> (facebook::biggrep::BigGrepMasterAsync *) this = 0x00007fd14d374fd0 >> (const string &const) corpus = error: summary string parsing error: { >> store_ = { >> = { >>...

On 13 Jan 2010, at 16:43, Nick Lewycky wrote: > Mark Muir wrote: >> - Run the existing Clang tool on each source file, using -emit-llvm to generate a .bc file for each module. >> - Run llvm-link to merge them into a single .bc file. >> - Run llc to generate a complete machine assembly. >> >> However, with optimisations enabled, the resulting code is not as

...nd the bounds of >>> 0x10b9a901* >>> *error: biggrep_master_server_async 0x10b98edc: DW_TAG_member 'small_' >>> refers to type 0x10bb1d9f which extends beyond the bounds of 0x10b98ed3* >>> *error: biggrep_master_server_async 0x10baf034: DW_TAG_member '__size' >>> refers to type 0x10baf04d which extends beyond the bounds of 0x10baefae* >>> (facebook::biggrep::BigGrepMasterAsync *) this = 0x00007fd14d374fd0 >>> (const string &const) corpus = error: summary string parsing error: { >>> store_ = { >>>...

...39;size_t'' /usr/src/xen-3.3.0/stubdom/newlib-1.16.0/newlib/libc/include/stdlib.h:77: erreur: expected '')'' before ''__nmemb'' /usr/src/xen-3.3.0/stubdom/newlib-1.16.0/newlib/libc/include/stdlib.h:87: erreur: expected '')'' before ''__size'' /usr/src/xen-3.3.0/stubdom/newlib-1.16.0/newlib/libc/include/stdlib.h:88: erreur: expected declaration specifiers or ''...'' before ''size_t'' /usr/src/xen-3.3.0/stubdom/newlib-1.16.0/newlib/libc/include/stdlib.h:89: erreur: expected declaration specifier...