search for: __errno_location

...w is the output of ltrace and gdb on the offending smbd process. I tried upgrading to 3.0.11 and the problem still exists. Anyone have any suggestions? [ltrace output] After about 20 seconds on the processes ltrace loops this iconv(0x82cecc8, 0xbffff218, 0xbffff21c, 0xbffff220, 0xbffff224) = -1 __errno_location() = 0x403ac560 iconv(0x82cecc8, 0, 0, 0, 0) = 0 __errno_location() = 0x403ac560 iconv(0x82cecc8, 0xbffff218, 0xbffff21c, 0xbffff220, 0xbffff224) = -1 __errno_location() = 0x403ac560 iconv(0...

...d ...> [pid 9977] SYS_write(3, "se a serial interface.\n\n\nThe one thing I'm not sure about is whether or not they will support a\nspecialied printer like a Dymo l"..., 262144) = -5 [pid 9977] <... write resumed> ) = -1 [pid 9977] __errno_location() = 0x40030b00 [pid 9977] __errno_location() = 0x40030b00 [pid 9977] strerror(5) = "Input/output error" [pid 9977] asprintf(0x08077584, 0x0806e507, 0x...

...rading to 3.0.11 and the problem still exists. Anyone have > > any suggestions? > > > > > > [ltrace output] > > After about 20 seconds on the processes ltrace loops this > > > > iconv(0x82cecc8, 0xbffff218, 0xbffff21c, 0xbffff220, 0xbffff224) = -1 > > __errno_location() = 0x403ac560 > > iconv(0x82cecc8, 0, 0, 0, 0) = 0 > > __errno_location() = 0x403ac560 > > iconv(0x82cecc8, 0xbffff218, 0xbffff21c, 0xbffff220, 0xbffff224) = -1 > > __errno_location()...

...ail is sent out before I complete it due to my mistake. Please read this I am using the LLVM function pass to help me to do code analysis. However, I found that the block LLVM identified will ignore the function call. For example, the below IR should not be a basic block. %call17 = call i32* @__errno_location() #14, !dbg !1384 %18 = load i32, i32* %call17, align 4, !dbg !1384 %19 = load i8*, i8** %dest_dirname, align 4, !dbg !1386 call void (i32, i32, i8*, ...) @error(i32 1, i32 %18, i8* getelementptr inbounds ([3 x i8], [3 x i8]* @.str.389, i32 0, i 32 0), i8* %19), !dbg !1387 br label %if.e...

Hi I am using the LLVM function pass to help me to do code analysis. I use -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180529/a617b2c6/attachment.html>

...>> We only need a convenient global data pointer here, and the address of >>> ‘errno’ should be fine. >> >> errno is often implemented as a dereference of a function call in order >> to get thread-safe semantics; for example, your patch produces >> '&(*__errno_location())' on glibc. That should be okay (especially >> since it silenced the warning). > > Yeah, I was aware of this and looking for some other global variable > but couldn't think of one at the time. > > Hmm, how about optind? <getopt.h> is not portable, and I'...

...due to my mistake. Please read this > > I am using the LLVM function pass to help me to do code analysis. However, I found that the block LLVM identified will ignore the function call. > > For example, the below IR should not be a basic block. > > > %call17 = call i32* @__errno_location() #14, !dbg !1384 > %18 = load i32, i32* %call17, align 4, !dbg !1384 > %19 = load i8*, i8** %dest_dirname, align 4, !dbg !1386 > call void (i32, i32, i8*, ...) @error(i32 1, i32 %18, i8* getelementptr inbounds ([3 x i8], [3 x i8]* @.str.389, i32 0, i 32 0), i8* %19), !dbg !1387 &...

...nd data pointers were > incompatible. > > We only need a convenient global data pointer here, and the address of > ‘errno’ should be fine. errno is often implemented as a dereference of a function call in order to get thread-safe semantics; for example, your patch produces '&(*__errno_location())' on glibc. That should be okay (especially since it silenced the warning). Another option, instead of referencing an actual variable, could be writing ((void*)(intptr_t)1). Either way, this patch makes sense. > @@ -78,7 +79,7 @@ extern char *nbdkit_realpath (const char *path); > /...

...s 37 entries: Offset Info Type Sym. Value Sym. Name + Addend 000000604c60 000100000007 R_X86_64_JUMP_SLO 0000000000000000 free + 0 000000604c68 000200000007 R_X86_64_JUMP_SLO 0000000000000000 abort + 0 000000604c70 000300000007 R_X86_64_JUMP_SLO 0000000000000000 __errno_location + 0 000000604c78 000400000007 R_X86_64_JUMP_SLO 0000000000000000 _exit + 0 000000604c80 000500000007 R_X86_64_JUMP_SLO 0000000000000000 __fpending + 0 ... (The list for .rela.plt has been truncated for brevity.) If we now run "llvm-objdump-3.1 -r /bin/true", we will get a list of entr...

...; > > > I am using the LLVM function pass to help me to do code analysis. > However, I found that the block LLVM identified will ignore the function > call. > > > > For example, the below IR should not be a basic block. > > > > > > %call17 = call i32* @__errno_location() #14, !dbg !1384 > > %18 = load i32, i32* %call17, align 4, !dbg !1384 > > %19 = load i8*, i8** %dest_dirname, align 4, !dbg !1386 > > call void (i32, i32, i8*, ...) @error(i32 1, i32 %18, i8* > getelementptr inbounds ([3 x i8], [3 x i8]* @.str.389, i32 0, i 32 0), &g...

...ace, and got the following: 24079 write(2, "debug3: channel_setup_fwd_listen"..., 78) = 78 24079 umask(0177) = 02 24079 socket(1, 1, 0) = 8 24079 bind(8, 0x7ffc4f8915c0, 110, -1) = -1 24079 __errno_location() = 0x7f03f55a5710 24079 strerror(98) = "Address already in use" >From this, it appears that there is no attempt to unlink the socket if it already exists, as would be expected from this code (https://github.com...

...ional POSIX (not thread safe): extern int errno; - DragonFly libc: extern __thread int errno; - Android libc: extern volatile int* __errno(void); #define errno (*__errno()) - Darwin libc: int * __error(void); #define errno (*__error()) - musl libc: extern int *__errno_location(void); #define errno (*__errno_location()) Does anyone see any problems with making stronger (type-based) assumptions re: errno (and, thus, on what things may alias with calls to errno-setting-libm functions)? Also, I don't know if we support LTO-ing the libc implementation, and if that cou...

...;& /home/laguest/src/mine-new/llvm/llvm-project/build/bin/clang-tidy --extra-arg=-fno-caret-diagnostics --quiet -p /home/laguest/src/mine-new/llvm/llvm-project/build errno_location.cpp && /usr/bin/cmake -E touch /home/laguest/src/mine-new/llvm/llvm-project/build/projects/libc/src/errno/.__errno_location.__lint_timestamp__ FAILED: projects/libc/src/errno/.__errno_location.__lint_timestamp__ cd /home/laguest/src/mine-new/llvm/llvm-project/libc/src/errno && /home/laguest/src/mine-new/llvm/llvm-project/build/bin/clang-tidy --extra-arg=-fno-caret-diagnostics --quiet -p /home/laguest/src/mine-ne...

...(2, "debug3: channel_setup_fwd_listen"..., 78) = 78 > > 24079 umask(0177) = 02 > > 24079 socket(1, 1, 0) = 8 > > 24079 bind(8, 0x7ffc4f8915c0, 110, -1) = -1 > > 24079 __errno_location() = 0x7f03f55a5710 > > 24079 strerror(98) = "Address > > already in use" > > > > From this, it appears that there is no attempt to unlink the socket if > > it already exists, as would b...

...ible. > > > > We only need a convenient global data pointer here, and the address of > > ‘errno’ should be fine. > > errno is often implemented as a dereference of a function call in order > to get thread-safe semantics; for example, your patch produces > '&(*__errno_location())' on glibc. That should be okay (especially > since it silenced the warning). Yeah, I was aware of this and looking for some other global variable but couldn't think of one at the time. Hmm, how about optind? Rich. > Another option, instead of referencing an actual variable, co...

...r *file, unsigned int line, const char *function) { fprint (stderr, "%s:%d:%s: %s\n", file, line, function, assertion); abort (); } #include <ctype.h> int __ctype_toupper(int c) { return toupper (c); } unsigned short int __ctype_b[256]; #include <errno.h> int *__errno_location(void) { return __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 voi...

...e copy of libsysfs with a few modifications to make it work on klibc. What's the easiest path for getting the master libsysfs copy working on klibc? libsysfs needs two calls: setmntent, getmntent These are used to locate the mount point of /sys It also uses errno so I get link errors for '__errno_location' libsysfs is at http://linux-diag.sourceforge.net/Sysfsutils.html in the sysfsutils project. ===== Jon Smirl jonsmirl@yahoo.com __________________________________ Do you Yahoo!? Yahoo! Small Business $15K Web Design Giveaway http://promotions.yahoo.com/design_giveaway/

https://bugzilla.samba.org/show_bug.cgi?id=2766 ------- Additional Comments From paul@debian.org 2005-06-02 08:47 ------- It seems to be looping in userspace (no system calls, hence strace doesn't show anything). Could you try ltrace instead of strace, that should show what library functions (if any) are being called which may help. -- Configure bugmail:

Hello all, Pardon me if this has already been covered elsewhere, however I have not been able to find such documentation. Is there a consolidated set of documentation that clearly explains what's necessary to port LLVM to other OSes & how to add support for building executables (& libraries) for those OSes? I'm searching through the source in an attempt to understand what needs to

We previously discussed allowing the plugin API to be consumed by non-GCC/non-Clang/old compilers. This implements a test. Rich.