| Summary: | ASTERISK-07627: Attempt to set a read-only variable error message should say which variable. | ||
| Reporter: | sedwards (sedwards) | Labels: | |
| Date Opened: | 2006-08-29 19:51:34 | Date Closed: | 2006-08-30 10:15:45 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | Aug 29 17:45:44 dt-ext asterisk[9029]: ERROR[9578]: cdr.c:289 in ast_cdr_setvar: Attempt to set a read-only variable!. It would be nice to say which variable caused the error. | ||
| Comments: | By: Clod Patry (junky) 2006-08-29 21:42:01 its a feature, but logic says if u tried to set a ro var, u know which var. By: sedwards (sedwards) 2006-08-30 09:17:43 Mostly true. If I set several variables, I can "bi-section search" my way to find the culprit, it would just be nice since Asterisk already knows the variable name to tell me. Why should Asterisk keep it a secret? By: Joshua C. Colp (jcolp) 2006-08-30 10:15:44 I've put this into trunk so it'll be in 1.4, but not into 1.2 as I do consider it a new feature... | ||