similar to: Driver macosx-ups failing on Yosemite

On Jun 27, 2015, at 9:17 AM, Charles Lepple <clepple at gmail.com> wrote: > On Jun 26, 2015, at 11:07 PM, Sundeep Mediratta <smedius at gmail.com> wrote: > >> 0.000233 upsdrv_initups(): Power Sources blob: >> <CFArray 0x7ffd18605480 [0x7fff7443bed0]>{type = immutable, count = 1, values = ( >> 0 : <CFBasicHash 0x7ffd18605360 [0x7fff7443bed0]>{type

> On Jun 26, 2015, at 9:25 PM, Charles Lepple <clepple at gmail.com> wrote: > > On Jun 26, 2015, at 8:35 AM, Sundeep Mediratta <smedius at gmail.com> wrote: > >> OSX Yosemite 10.10.3 >> Nut version 2.6.5 >> Installed via Macports >> Device is Cyberpower CP1000AVRLCD >> Device is visible and is monitored in the OSX control panel >>

Hello, I am trying to enable call forwarding feature on asterisk 1.6.0.9 with asterisk-gui. Sure there is no menu for that on gui but, when i try to write some example scripts to extensions.conf to make it work. I totally failed. I dont wanna install smthing like freepbx etc on the system so, i need help to add unconditional etc call forwarding feature for 1.6 Thanks

(forgot to CC llvmdev) On Thu, Mar 21, 2013 at 5:54 PM, Alexander Potapenko <glider at google.com> wrote: > Hey Anna, Nick, Ted, > > We've the following problem with string literals under ASan on Mac. > Some global string constants end up being put into the .cstring > section, for which the following rules apply: > - the strings can't contain zeroes in their

Hi all, int main() { t(""); return 0; } On Mac OS X, llvm-gcc compiles the zero-sized string to: .lcomm LC,1,0 gcc: .cstring LC0: .ascii "\0" The difference seems innocent enough. However, in objc if the zero- sized string is part of a cfstring, it causes a problem. The linker expects it in the readonly __cstring section, but llvm puts it in the

Alexander, On Darwin the "__cstring" section (really section with type S_CSTRING_LITERAL) is defined to contain zero terminate strings of bytes that the linker can merge and re-order. If you want pad bytes before and after the string, you need to put the strings in a different section (e.g. __TEXT, __const). But, CF/NSString literals will be problematic. The compiler emits a static

There is a problem with Objective-C code where a null string is placed in the wrong section. If we have this code: #include <Foundation/Foundation.h> void foo() { NSLog(@""); } The null string is defined like this: .const .lcomm LC,1,0 ## LC Causing our linker to go nuts, because it expects anonymous strings to be in the __cstring section. I came up with the attached

On Fri, Jan 9, 2009 at 5:40 PM, Evan Cheng <evan.cheng at apple.com> wrote: > The difference seems innocent enough. However, in objc if the zero- > sized string is part of a cfstring, it causes a problem. The linker > expects it in the readonly __cstring section, but llvm puts it in the > read / write bss section. That seems extremely weird... what sort of magic is objc using

On Nov 24, 2008, at 11:07 AM, Chris Lattner wrote: > > On Nov 24, 2008, at 11:01 AM, Bill Wendling wrote: > >> The symbols I'm interested in already have internal linkage (as you >> would expect). But because the mangler is in charge of assigning them >> names, they never seem to be decorated with the 'L' in front. . . . > > If you use

The source for the samba components in MacOS X Server is located at: http://www.opensource.apple.com/tools/cvs ('samba' module) The latest vendor branch is samba2.2.1a. The main branch includes the following modifications (see diffs below).. 1) DirectoryService suport (encrypted authentication) 2) CFString usage (DOS code page <-> decomposed UTF8) 3) smbstatus -r (raw dump of user

On Jan 26, 2009, at 4:07 PMPST, Bill Wendling wrote: > There is a problem with Objective-C code where a null string is placed > in the wrong section. If we have this code: > > #include <Foundation/Foundation.h> > void foo() { > NSLog(@""); > } > > The null string is defined like this: > > .const > .lcomm LC,1,0 ## LC > > Causing our

Hi all, Right now the Mangler::getValueName() method will produce something like "__unnamed_1_37" for a global value that doesn't have a name. This is wrong for Objective-C where CFStrings will get these labels, thus preventing the linker from coalescing them. [/tmp]> nm -s __DATA __cfstring -m foo.o 00000000000244d0 (__DATA,__cfstring) non-external __unnamed_1_0

On Jun 26, 2015, at 11:07 PM, Sundeep Mediratta <smedius at gmail.com> wrote: > 0.000233 upsdrv_initups(): Power Sources blob: > <CFArray 0x7ffd18605480 [0x7fff7443bed0]>{type = immutable, count = 1, values = ( > 0 : <CFBasicHash 0x7ffd18605360 [0x7fff7443bed0]>{type = immutable dict, count = 10, > entries => Thanks. There is a subtle difference in the

I think the high CPU usage was caused by the native OS X driver crashing and not working properly. The native driver was not sensing the UPS going on battery or any change in battery percentage. Unplugging the USB and then plugging it back again made the native driver come back up again properly. Restarting the macosx-ups driver seems to get back to normal CPU usage. I will monitor and see how it

Can symbols with external linkage but no name be converted to have internal linkage? Would that solve the problem? Dan On Nov 23, 2008, at 2:15 AM, Bill Wendling wrote: > Hi all, > > Right now the Mangler::getValueName() method will produce something > like "__unnamed_1_37" for a global value that doesn't have a name. > This is wrong for Objective-C where CFStrings

On Fri, Oct 31, 2008 at 10:38:50AM -0700, Mike Stump wrote: > On Oct 31, 2008, at 9:40 AM, Jack Howarth wrote: >> However in current llvm svn, when I compile code with llvm-gfortran, I >> get these warning >> flags passed by default so that I get bogus warnings of... >> >> f951: warning: command line option "-Wformat" is valid for C/C++/ >>

On Mon, Jan 26, 2009 at 4:45 PM, Dale Johannesen <dalej at apple.com> wrote: > > On Jan 26, 2009, at 4:07 PMPST, Bill Wendling wrote: > >> There is a problem with Objective-C code where a null string is placed >> in the wrong section. If we have this code: >> >> #include <Foundation/Foundation.h> >> void foo() { >> NSLog(@"");

The symbols I'm interested in already have internal linkage (as you would expect). But because the mangler is in charge of assigning them names, they never seem to be decorated with the 'L' in front. . . . -bw On Mon, Nov 24, 2008 at 10:48 AM, Dan Gohman <gohman at apple.com> wrote: > Can symbols with external linkage but no name be converted > to have internal linkage?

Le 19 janv. 09 ? 21:53, tim lindner a ?crit : > > Thanks for this. Everything has been working fine. I did encounter > one problem. It didn't like it when colons were in filenames. Rsync > would spit out an error and move to the next file. > > I remember (sorry I don't have a reference) that HFS disallows a ":" > in the file name. So when a filename is