| Summary: | ASTERISK-06191: asterisk -rx fails to return to command line | ||
| Reporter: | edgreenberg (edgreenberg) | Labels: | |
| Date Opened: | 2006-01-25 11:44:29.000-0600 | Date Closed: | 2011-06-07 14:10:17 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | Executing asterisk -rx followed by a command (I tried reload and show channels) results in the command being executed, and the process continuing to run and sending console output to the terminal until process externally terminated by ^C or similar action. ****** ADDITIONAL INFORMATION ****** Sorry I don't know how to categorize this. | ||
| Comments: | By: Russell Bryant (russell) 2006-01-25 12:01:44.000-0600 I can't reproduce this. Is this Linux or something else? Can you get a backtrace of when this is happening? See doc/README.backtrace for more details. By: edgreenberg (edgreenberg) 2006-01-25 12:27:40.000-0600 This is Fedora Core 4. Asterisk doesn't crash, so I'm not sure how to get a backtrace for you. By: edgreenberg (edgreenberg) 2006-01-25 14:10:36.000-0600 My bad. Please close. Excuse me for using up oxygen. (Embarrassed.) By: Russell Bryant (russell) 2006-01-25 14:55:31.000-0600 For future reference, you can actually take a backtrace from a running process as well as from a core dump after Asterisk crashes. We even have a script that does this for you: contrib/scripts/ast_grab_core. This script attaches gdb to the running process, takes the necessary backtraces, and detatches. | ||