search for: logerrors

Hello, I get a crash in my program that uses exceptions and the LLVM JIT, even though the exceptions are controlled and thrown/catched in a part that doesn't deal with LLVM. I noticed that llvm-config --cxxflags includes the -fno-exceptions flag. Do I need to throw no exceptions whatsoever in my application to use LLVM JIT? As a minimal example, I modified the code in

Hi I've got a script like this exten => s,1,SetVar(CALLFILENAME=/var/www/recordings/${TIMESTAMP:0:8:7}/${UNIQUEID}) exten => s,2,AGI(recordstart.py,${ARG1},${CALLERIDNUM},${CALLFILENAME},Ind) exten => s,3,DIAL(ZAP/g2/${ARG1},70) exten => s,4,AGI(logerror.py,${ARG1},${CALLERIDNUM},${CHANNEL},${DIALSTATUS},${DATETIME}, ${CAUSECODE}) exten => s,5,hangup exten =>

sysklogd in RH4.2 always opens a UDP listen socket, even when -r is not specified on the command line. It doesn''t check the file descriptor when -r is off though, but the behaviour still irritates the system administrator greatly (see also the recent bugtraq messages about this). Here is a patch to fix this: --- sysklogd-1.3/syslogd.c-o Wed Sep 3 22:19:26 1997 +++

Hi, Not sure if this should be in the dev or users list, but here goes. I am using the FLAC seekable stream decoder in my MACH3 laser games emulation in MAME (www.boldtower.com/mach3). The game has a soundtrack (originally on a laser disk) which I have flac encoded and play back in the game. I did the implementation under Linux which works fine, the callbacks are easy to set up and I've

...e" out of INVALID macro. Great. Committed in r186805. I propose two more patches: 1) Transform the INVALID macro into function calls, that format the text and that set LastFailure. 2) Add checks at the beginning of those function calls and continue only if LogErrors is set The second one is slightly more involved as we would like to turn this option on automatically either in -debug mode or if -polly-show or -polly-show-only is set. What do you think? Does this sound right? Cheers, Tobias

...should translate INVALID macro into a serial of functions like "invalid_CFG, invalid_IndVar, invalid_IndEdge, ... ? In that case, I could provide a small patch file for this purpose -:) > 2) Add checks at the beginning of those function calls and > continue only if LogErrors is set Those invalid log strings are used for two separate cases: 1) The first case is for detailed debugging, which is controlled by the macro DEBUG(dbgs() << MESSAGE). In such a case, string operations will automatically skipped in normal execution mode with the following if-statement: if (...

I made a quick change to syslogd(8) so that it can drop root privileges immediately after starting up. It opens up the log sockets (UNIX and network domains) and writes the PID files before dropping privs. It drops privs before openning log files and writing to users. Therefore, you would need to modify your log file permissions appropriately. As for writing to users, ttys generally are writeable

...ike it. Also noticed the spew looks simular to the contents of the "initlog.conf" file, attched also. I'm guessing it's an upstream problem? I also don't this is a big concern? Any thoughts? -------------- next part -------------- A non-text attachment was scrubbed... Name: logerrors Type: application/octet-stream Size: 1641 bytes Desc: not available URL: <http://lists.centos.org/pipermail/centos/attachments/20051113/df26bf90/attachment.obj> -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: initlog.conf URL: <http://...

Hi, I was trying to print out a 128 bit result at runtime using a call to printf in LLVM. I am able to print 32 uptil 64 bit integers using the format string "%d" in printf . Please see the code in red below , as I am having a bit difficulty in trying to print the 128 bit value computed at runtime. The code in red is never executed since the value may never be casted to a

...main scop detection. However, this issue is not directly related to the speedup work, so you are welcome to skip it for now. (Btw. thanks for not blindly following my suggestions!) >> 2) Add checks at the beginning of those function calls and >> continue only if LogErrors is set > Those invalid log strings are used for two separate cases: > 1) The first case is for detailed debugging, which is controlled by the macro DEBUG(dbgs() << MESSAGE). In such a case, string operations will automatically skipped in normal execution mode with the following if-state...

...owever, this issue is not directly related to the speedup work, so >you are welcome to skip it for now. > >(Btw. thanks for not blindly following my suggestions!) > >>> 2) Add checks at the beginning of those function calls and >>> continue only if LogErrors is set >> Those invalid log strings are used for two separate cases: >> 1) The first case is for detailed debugging, which is controlled by the macro DEBUG(dbgs() << MESSAGE). In such a case, string operations will automatically skipped in normal execution mode with the following...

At 2013-07-22 01:40:31,"Tobias Grosser" <tobias at grosser.es> wrote: >On 07/21/2013 09:49 AM, Star Tan wrote: >> Hi all, >> >> >> I have attached a patch file to reduce the polly-detect overhead. > >Great. > >> My idea is to avoid calling TypeFinder in Non-DEBUG mode, so >> TypeFinder is only called in DEBUG mode with the DEBUG

On 07/21/2013 09:49 AM, Star Tan wrote: > Hi all, > > > I have attached a patch file to reduce the polly-detect overhead. Great. > My idea is to avoid calling TypeFinder in Non-DEBUG mode, so > TypeFinder is only called in DEBUG mode with the DEBUG macro. This > patch file did this work with following modifications: > > > First, it keeps most of string information