[asterisk-bugs] [JIRA] (ASTERISK-22351) Segfault in LIBEDIT_INTERNAL after tgetstr()

[Matt Jordan (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-22351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209519#comment-209519 ] 

Matt Jordan edited comment on ASTERISK-22351 at 8/23/13 8:42 AM:
-----------------------------------------------------------------

Optimization was activated again because I was doing some tests. Removed again...

You're right, I was using t outside the for itineration where it's declared. Sorry if I'm not to fast, but it's been a long time since my c programming, and I'm trying to remember while I'm studyng the code, so sometimes is not clear to me what you're asking for.

About the cap...

{noformat}
(gdb) print cap
$1 = 0xffffffffffffad20 <Address 0xffffffffffffad20 out of bounds>

(gdb) print &cap
$2 = (const char **) 0x7fffffff3398

(gdb) up
#1  0x0000000000571089 in term_set (el=0x8417f0, term=0x7fffffffeea1 "xterm") at term.c:963
963                             term_alloc(el, t, tgetstr((char *)t->name, &area));

(gdb) print buf
$3 = '\000' <repeats 10240 times>, "\033[L", '\000' <repeats 10236 times>

(gdb) print &buf
$4 = (char (*)[20480]) 0x7fffffff8520
{noformat}

So it seems cap (0x7fffffff3398) < buf (0x7fffffff8520)  ... right?
                
      was (Author: arcanos):
    Optimization was activated again because I was doing some tests. Removed again...

You're right, I was using t outside the for itineration where it's declared. Sorry if I'm not to fast, but it's been a long time since my c programming, and I'm trying to remember while I'm studyng the code, so sometimes is not clear to me what you're asking for.

About the cap...

(gdb) print cap
$1 = 0xffffffffffffad20 <Address 0xffffffffffffad20 out of bounds>

(gdb) print &cap
$2 = (const char **) 0x7fffffff3398

(gdb) up
#1  0x0000000000571089 in term_set (el=0x8417f0, term=0x7fffffffeea1 "xterm") at term.c:963
963                             term_alloc(el, t, tgetstr((char *)t->name, &area));

(gdb) print buf
$3 = '\000' <repeats 10240 times>, "\033[L", '\000' <repeats 10236 times>

(gdb) print &buf
$4 = (char (*)[20480]) 0x7fffffff8520


So it seems cap (0x7fffffff3398) < buf (0x7fffffff8520)  ... right?
                  
> Segfault in LIBEDIT_INTERNAL after tgetstr()
> --------------------------------------------
>
>                 Key: ASTERISK-22351
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22351
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 1.8.23.0, 11.5.0
>         Environment: HP Proliant DL320e G8
> Debian Wheezy (kernel 3.2.0-4-amd64)
> DAHDI 2.7.0 (no cards installed)
> Libpri 1.4.14
>            Reporter: A. Iglesias
>         Attachments: issueA22351_larger_buf_and_offset.patch, issueA22351_larger_buf.patch
>
>
> New installation in this server. After everything is installed and asterisk started, anytime a try to open an asterisk console with asterisk -vvvvvvvvvr I get a "Segmentation fault" and console doesn't open, but asterisk keeps running. If I stop asterisk and try to start it with asterisk -vvvvvvc, it fails in the same way.
> I've been doing some research, and found a guy with the same problem in the past, related whit the value of the TERM system variable. In my case is "xterm", but if I change it for a non existent value ('lalalala' for example) then console starts.
> Digging deeper, I've found that the problem is in main/editline/term.c , in line 960 when executing this:
> term_alloc(el, t, tgetstr((char *)t->name, &area));
> If I change this line with the one executed when TERM has an unknown value...
> term_alloc(el, t, NULL);
> ... and recompile, then console starts.
>  the problem seems to be in the tgetstr function, because if I add a line just with this...
> tgetstr((char *)t->name, &area);
> ... I get the same error.
> I'll try to get core dump stuff, but maybe with this info is enough at the moment to find a solution. I've been trying to find the problem/solution studying the code, but no luck yet.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira