similar to: [LLVMdev] SlowOperationInformer.cpp:55: error:`SIGALRM' undeclared (first use this functi

There's simply no equivalent to signals on Windows. There is no way to asynchronously interrupt a thread's processing to execute some handler. The only thing you can asynchronously do to a thread is kill it, and that's generally frowned upon (who knows what critical sections it might be holding, etc...). Stuff like alarms is supposed to be done using the "event-driven"

To be more specific: Lines containing SIGALRM and alarm(). >From: "Henrik Bach" <henrik_bach_llvm at hotmail.com> >Date: Fri, 24 Sep 2004 23:21:58 +0200 > >>From: Reid Spencer <reid at x10sys.com> >>Date: Fri, 24 Sep 2004 13:03:44 -0700 >> >>I just discovered that the *only* place this is used is in the debugger >>when it is loading

Ultimately, this is another function that needs to go into lib/System. An alternate approach is to fork a thread, sleep, and when the thread wakes up, "ring the alarm". Reid. John Criswell wrote: > Henrik Bach wrote: > >> Hi >> >> I'm compiling: >> /usr/local/src/llvm/lib/Support/SlowOperationInformer.cpp on MinGW. >> However, it stops

Henrik Bach wrote: > Hi > > I'm compiling: /usr/local/src/llvm/lib/Support/SlowOperationInformer.cpp > on MinGW. However, it stops complaining about that SIGALRM is undeclared: Is there an alarm() syscall on MinGW? And if so, what signal does it send (according to the MinGW docs)? -- John T. > -------------------------- > @ /usr/local/build/llvm/mklib

Hi I'm compiling: /usr/local/src/llvm/lib/Support/SlowOperationInformer.cpp on MinGW. However, it stops complaining about that SIGALRM is undeclared: -------------------------- @ /usr/local/build/llvm/mklib --tag=disable-shared --silent --tag=CXX --mode=compile g++ -c -I/usr/local/build/llvm/lib/Support -I/usr/local/src/llvm/lib/Support -I/usr/local/build/llvm/include

llvmdev-request at cs.uiuc.edu wrote: >Send LLVMdev mailing list submissions to > llvmdev at cs.uiuc.edu > >To subscribe or unsubscribe via the World Wide Web, visit > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >or, via email, send a message with subject or body 'help' to > llvmdev-request at cs.uiuc.edu > >You can reach the person managing the list at

It's a shame this fine tool can't get better installation support for Windows. If it did I suspect it would get a lot more coverage. After 5 months or so I still have no way to compile the backend tools let alone the C frontend on windows. I have tried both Cygwin and Mingw so far. MingW is preferrable since distributions of the binaries would not require the cygwin.dll. It

llvmdev-request at cs.uiuc.edu wrote: >Send LLVMdev mailing list submissions to > llvmdev at cs.uiuc.edu > >To subscribe or unsubscribe via the World Wide Web, visit > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >or, via email, send a message with subject or body 'help' to > llvmdev-request at cs.uiuc.edu > >You can reach the person managing the list at

Hi, I am seeing a problem where in sshd gets terminated by SIGALRM. sshd was listening on the socket and was not restarted. I saw a recent bug fix in openBSD openssh CVS which mentions: Clear alarm() before restarting sshd on SIGHUP. Without this, if there's a SIGALRM pending (for SSH1 key regeneration) when sshd is SIGHUP'ed, the newly exec'ed sshd will get the SIGALRM and

Gidday everbody, We have just found an interesting issue regarding the sshd daemon on our SuSE system. For some reasons, the /usr/sbin/sshd process blocks SIGALRM as shown in the /proc/pid/status: $ cat /proc/`cat /var/run/sshd.init.pid`/status Name: sshd State: S (sleeping) SleepAVG: 0% [...] SigPnd: 0000000000000000 ShdPnd: 0000000000000000 SigBlk: 0000000000002000 <-- SIGALRM is

sshd will die from an unhandled SIGALRM if you allow SSH1 connections, ssh in, HUP sshd, and don't ssh in again for KeyRegenerationInterval. The HUP handler calls exec which resets signal handlers but persists alarm timers. Chapter and verse: http://www.opengroup.org/onlinepubs/000095399/functions/alarm.html -- Andrew Gaul http://gaul.org/ -------------- next part -------------- Index:

sshd will die from an unhandled SIGALRM if you allow SSH1 connections, ssh in, HUP sshd, and don't ssh in again for KeyRegenerationInterval. The HUP handler calls exec which resets signal handlers but persists alarm timers. Chapter and verse:

>From: "Reid Spencer" <reid at x10sys.com> >Date: Thu, 15 Jul 2004 18:33:30 -0400 > >On Thu, 15 Jul 2004 17:43:27 -0500 (CDT) > Chris Lattner <sabre at nondot.org> wrote: >>Sorry! LLVM 1.3 will probably be out in a few weeks... > >Speaking of which, what are your intentions for 1.3? Are you waiting on >CPR? Anything else? We're starting to

On Fri, 13 Apr 2007, Devang Patel wrote: >> I think libhello should drop its use of SlowOperationInformer. > > That'll fix Hello example. However, anyone trying to load their custom > pass will likely to run into this again. It is a long-standing issue. The deal is that libsupport (and many others) are .a files. If one of the .o files in the .a file is used by a plugin, but

Henrik Bach wrote: > Hi LLVM'ers > > When linking tblgen tool I get below error message on MinGW. > > I have put TOOLLINKOPTS=-ldbghelp in Makefile.config. > > However, when rearranging library dbghelp to the end of the g++ > line, tblgen gets linked. It seems that the -L path options are specified before the LLVM libraries (libSystem and libsupport) are linked in.

Hi LLVM'ers When linking tblgen tool I get below error message on MinGW. I have put TOOLLINKOPTS=-ldbghelp in Makefile.config. However, when rearranging library dbghelp to the end of the g++ line, tblgen gets linked. -------------------------- make[2]: Entering directory `/C/Projects/build/MinGW/llvm/utils/TableGen' Linking Debug executable tblgen /C/Projects/build/MinGW/llvm/mklib

Chris, On Fri, 2007-04-13 at 12:39 -0700, Chris Lattner wrote: > On Fri, 13 Apr 2007, Devang Patel wrote: > >> I think libhello should drop its use of SlowOperationInformer. > > > > That'll fix Hello example. However, anyone trying to load their custom > > pass will likely to run into this again. > > It is a long-standing issue. The deal is that

some header freebsd-announce Joerg Wunsch <joerg@FreeBSD.ORG> 1.92 When merging the new `ct' printcap functionality into 2.2-stable right before 2.2.5-RELEASE was due, it's now apparent that I didn't test it enough before. :-( I've introduced a fatal bug that causes all the lpd children sending jobs to remote printers to be killed after the `ct' timeout, even in case the

On Apr 13, 2007, at 12:28 PM, Chris Lattner wrote: > On Fri, 13 Apr 2007, Devang Patel wrote: >> And this brings back CommandLine Error: Arugment blah defined more >> than once! >> >> And without this, opt -load .../LLVMHello.dylib -hello does not work >> on Darwin because dyld is not able to find SlowerOperationInformer ;) > > I think libhello should drop

http://www.core-sdi.com/advisories/ssh1_sessionkey_recovery.htm includes the line of code: kill(SIGALRM, getppid()); This is contained within what is listed as an "unsupported and untested patch" developed by SSH.com. The problem is that the arguments to "kill" are in the wrong order. In other words, to obtain the effect that was apparently intended, the line of code