search for: counter2

Friends, Last week, Hans Petter Selansky alerted us of a potential security issue in all releases of Asterisk. In fact, it doesn't involve the code, but the most common way to construct dialplans. If you have something like this in your Asterisk, you need to update your dialplans: [incoming-from-voip] exten => _X., 1, dial(SIP/${EXTEN}) Many VoIP protocols support a large character set,

...se debug info as is or add some > extra (valid) debug info to support this, or (b) add an extra > debug-info-like section to instrumented binaries with the information we > need. > I'd try this data format (binary equivalent): /path/to/binary/or/dso1 num_counters1 pc1 counter1 pc2 counter2 pc3 counter3 ... /path/to/binary/or/dso2 num_counters2 pc1 counter1 pc2 counter2 pc3 counter3 ... I don't see a straightforward way to produce such data today because individual Instructions do not work as labels. But I think this can be supported in LLVM codegen. Here is a *raw* patch with co...

...lt;<- so that it works back up through the environment stack and carries out the assigment on the first variable it finds with the right name. mk.counter <- function(count=0) function() { count <<- count + 1 count } counter1 <- mk.counter() # each has its own count counter2 <- mk.counter() counter1() # -> returns 1 counter1() # -> returns 2 counter2() # -> returns 1 ... This gives functions what is called "mutable state" and could be used to create a real object system (the instance variables would really be private). We haven't really...

I've built chromium with " -fprofile-instr-generate -fsanitize=address" -- the performance looks good! The file format from r198638 is indeed rudimentary. Do you already know how the real output format will look like? Just to summarize what I think is important: - minimal size on disk, minimal amount of files - minimal i/o while writing to disk, no lockf or some such -