| Summary: | ASTERISK-05356: segfault (in atxfer ??) | ||
| Reporter: | Wallace Wadge (wwadge) | Labels: | |
| Date Opened: | 2005-10-24 04:05:06 | Date Closed: | 2011-06-07 14:00:28 |
| Priority: | Critical | Regression? | No |
| Status: | Closed/Complete | Components: | Resources/res_adsi |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) asterisk_crash_bt_full | |
| Description: | Triggered another segfault running on CVS (not bleeding-edge - how do I find out the revision I'm running)? Stack traces attached In case you're wondering re : /tmp/asterisk_is_alive I have a cron job which calls a local channel every 1 minute to test if asterisk is still alive (and restarts asterisk if it's dead) | ||
| Comments: | By: Serge Vecher (serge-v) 2005-10-24 10:52:20 type "show version" at CLI prompt to find out the version. By: Wallace Wadge (wwadge) 2005-10-25 02:43:48 not much info I'm afraid: asterisk*CLI> show version Asterisk CVS HEAD built by root@asterisk on a i686 running Linux on 2005-10-10 13:19:55 UTC Also note that the system has been up for several days without problems so it's not very reproducible :-( By: Mark Spencer (markster) 2005-10-28 13:14:43 Please confirm this is fixed in latest CVS head. Thanks. By: Mark Spencer (markster) 2005-11-02 21:47:18.000-0600 Should be fixed in head, closing unless we get feedback to the contrary. | ||