Summary: | ASTERISK-12314: Asterisk cli filename completion (completion_fn_2&3). Crash when asterisk could not open a directory. | ||
Reporter: | Nickolay Kharchevin (mykola) | Labels: | |
Date Opened: | 2008-07-04 07:29:20 | Date Closed: | 2011-06-07 14:00:21 |
Priority: | Critical | Regression? | No |
Status: | Closed/Complete | Components: | Core/General |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ||
Description: | Steps to reproduce: Asterisk Ready. Asterisk Malloc Debugger Started (see /var/log/asterisk/mmlog)) *CLI> *CLI> *CLI> unload app app_amd.so app_followme.so app_playback.so app_queue.so app_timetable.so app_voicemail.so *CLI> unload app_followme.so == Unregistered application 'FollowMe' The 'unload' command is deprecated and will be removed in a future release. Please use 'module unload' instead. *CLI> load app_follow<PRESS TAB> WARNING: Freeing unused memory at (nil), in complete_fn_2 of cli.c, line 1268 ****** ADDITIONAL INFORMATION ****** Reason: cli.c +1268: c = d = filename_completion_function(....) ... free(d) But filename_completion_function can return NULL in some cases (see code) [Patch removed] | ||
Comments: | By: Sean Bright (seanbright) 2008-07-04 07:45:56 Patches need to be submitted as separate attachments to the issue in mantis in order for us to look at them. By: Sean Bright (seanbright) 2008-07-04 09:41:54 What does "when asterisk could not open a directory" mean? In what situations would asterisk be unable to open a directory? By: Tilghman Lesher (tilghman) 2008-07-04 11:08:15 If you're reporting a crash, we need to be able to actually see a stack backtrace from a generated core file. By: Tilghman Lesher (tilghman) 2008-07-14 16:42:11 Closed, due to lack of response. If you're able to provide the requested information, please reopen this issue. For assistance, please contact a bug marshal in #asterisk-bugs on Freenode. |