search for: regx

Hello, I'm trying to cut off the "+" sign if part of a telephone number, but not succeeding : exten => test,n,Set(cid=+99999600) exten => test,n,Set(regx="([0-9])") exten => test,n,Set(cid2=$["${cid}" : ${regx}]) exten => test,n,NoOp(cid2=${cid2}) cid2 is empty afterwards... What I want is to make sure there are only numbers and no other characters. So +99999600 needs to become 99999600 (without + ) So 99999#600 needs t...

Hello, ctags(1) uses external application sort(1) for sorting the tags file. It calls it via system(3) function. Look at the /usr/src/usr.bin/ctags/ctags.c file, there are such lines here: if (uflag) { (void)asprintf(&cmd, "sort -o %s %s", outfile, outfile); if (cmd == NULL) err(1, "out of space"); system(cmd); free(cmd); cmd = NULL; } This code will be

Hi R Users, I have produced a simulated scatter plot of y versus x tightly clustered around the 45 degree line through the origin with the following code: x <- seq(1,100) y <- x+rnorm(100,0,10) plot(x,y,col="blue") abline(0,1) Is there some way to generate a 3-dimensional analogue of this? Can I get a similar simulated scatter plot of points in 3 dimensions where the points

...expression" in DWARF. A DWARF expression computes a value; if the available value is a pointer, you add DW_OP_deref to express the pointed-to value. A DWARF location expression computes a location, and adds various operators to express locations that a (value) expression cannot, such as DW_OP_regx. You also have DW_OP_stack_value to say "just kidding, this location expression is a value expression." So, whether we want to start throwing around deref or stack_value or regx (implicit or explicit) really depends on whether we are going to be using value expressions or location expres...

Here's a weird problem that I'm not quite sure how to resolve. Zaptel 1.2.10 compiles just fine with "make", but when "make install" is run, this happens: [ `id -u` = 0 ] && /sbin/depmod -a 2.6.17-10-generic || : [ -f /etc/zaptel.conf ] || install -D -m 644 zaptel.conf.sample /etc/zaptel.conf build_tools/genmodconf linux26 "" "tor2 torisa wcusb

Sorry, this is the attachment. 2014-02-19 15:08 GMT+08:00 杨勇勇 <triple.yang at gmail.com>: > Thank you. > > Here is an example and the attchment contains extra files including object > file and executable file. > I want to print for example the value of "a", but lldb command "frame > variable a" displays "0" and so does "b", and

...l_line( 2 ) > DW_AT_prototyped( true ) > DW_AT_type( {0x0000007f} ( int ) ) > DW_AT_external( true ) > DW_AT_low_pc( 0x00000028 ) > DW_AT_high_pc( 0x00000084 ) > DW_AT_frame_base( regx 0x0000003c ) > > So it says the frame base register is DWARF register 0x3c. In your target > definition you will need to have told us which register has the DWARF > register number 0x3c, otherwise we will fail to evaluate the expression. > > Greg > > > On Feb 18, 2014, at...

...debug info generator. > > Here is my questions: > > 1. How can we specify which register should be DW_AT_frame_base? > > You don't need to, there is a DWARF location expression in the > DW_AT_frame_base attribute attached to the function: > > DW_AT_frame_base( regx 0x0000003c ) > > This means: > > DW_OP_regx(0x0000003c) > > Or that the frame base is in register 0x3c. Now qRegisterInfo packets you > send back to LLDB must include "DWARF" register numbers. Sometimes the > register numbers the compiler uses for EH frame...

Debug info today handles two cases reasonably well: 1. At -O0, dbg.declare does a good job describing variables that live at some known stack offset 2. With optimizations, variables promoted to SSA can be described with dbg.value This leaves behind a large hole in our optimized debug info: variables that cannot be promoted, typically because they are address-taken. This is