Skip to content
Snippets Groups Projects
  1. Nov 08, 2013
    • Kevin Harwell's avatar
      app_dahdiras: Use waitpid instead of wait4. · 2564ed26
      Kevin Harwell authored
      Several places in the code were using wait4 while other places were using
      waitpid.  This change makes all places use waitpid in order to make things
      more consistent and since the 'rusage' object passed in/out of wait4 was
      never used.
      
      (closes issue ASTERISK-22557)
      Reported by: YvesGael
      Patches:
           asterisk-11.5.1-wait4.patch uploaded by hurdman (license 6537)
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@402546 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      2564ed26
  2. Oct 25, 2013
  3. Oct 24, 2013
  4. Sep 10, 2013
  5. Aug 06, 2013
  6. Aug 05, 2013
  7. Aug 02, 2013
  8. Aug 01, 2013
  9. Jun 13, 2013
  10. Jun 08, 2013
    • Matthew Jordan's avatar
      Add backtrace generation to MALLOC_DEBUG memory corruption reports · c43f380d
      Matthew Jordan authored
      This patch allows astmm to access the backtrace generation code in Asterisk.
      When memory is allocated, a backtrace is created and stored with the memory
      region that tracks the allocation. If a memory corruption is detected, the
      backtrace is printed to the astmm log. The backtrace will make use of the
      BETTER_BACKTRACES build option if available.
      
      As a result, this patch moves the backtrace generation code into its own file
      and uses the non-wrapped versions of the C library memory allocation routines.
      This allows the memory allocation code to safely use the backtrace generation
      routines without infinitely recursing.
      
      Review: https://reviewboard.asterisk.org/r/2567
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@391012 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      c43f380d
  11. May 02, 2013
  12. Nov 16, 2012
  13. Oct 14, 2012
  14. Oct 02, 2012
  15. Sep 22, 2012
    • Andrew Latham's avatar
      Doxygen Updates Janitor Work · fd98835f
      Andrew Latham authored
      * Whitespace, doc-blocks, spelling, case, missing and incorrect tags.
      * Add cleanup to Makefile for the Doxygen configuration update
      * Start updating Doxygen configuration for cleaner output
      * Enable inclusion of configuration files into documentation
      * remove mantisworkflow...
      * update documentation README
      * Add markup to Tilghman's email and talk with him about updating his email, he knows...
      * no code changes on this commit other than the mentioned Makefile change
      
      (issue ASTERISK-20259)
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@373384 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      fd98835f
  16. Aug 18, 2012
  17. Aug 01, 2012
  18. Jul 31, 2012
  19. Jun 15, 2012
    • Kevin P. Fleming's avatar
      Multiple revisions 369001-369002 · 166b4e2b
      Kevin P. Fleming authored
      ........
        r369001 | kpfleming | 2012-06-15 10:56:08 -0500 (Fri, 15 Jun 2012) | 11 lines
        
        Add support-level indications to many more source files.
        
        Since we now have tools that scan through the source tree looking for files
        with specific support levels, we need to ensure that every file that is
        a component of a 'core' or 'extended' module (or the main Asterisk binary)
        is explicitly marked with its support level. This patch adds support-level
        indications to many more source files in tree, but avoids adding them to
        third-party libraries that are included in the tree and to source files
        that don't end up involved in Asterisk itself.
      ........
        r369002 | kpfleming | 2012-06-15 10:57:14 -0500 (Fri, 15 Jun 2012) | 3 lines
        
        Add a script to enable finding source files without support-levels defined.
      ........
      
      Merged revisions 369001-369002 from http://svn.asterisk.org/svn/asterisk/branches/1.8
      ........
      
      Merged revisions 369005 from http://svn.asterisk.org/svn/asterisk/branches/10
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@369013 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      166b4e2b
  20. Apr 19, 2012
    • Matthew Jordan's avatar
      Fix a variety of potential buffer overflows · f7829006
      Matthew Jordan authored
      * chan_mobile: Fixed an overrun where the cind_state buffer (an integer array
        of size 16) would be overrun due to improper bounds checking. At worst, the
        buffer can be overrun by a total of 48 bytes (assuming 4-byte integers),
        which would still leave it within the allocated memory of struct hfp.  This
        would corrupt other elements in that struct but not necessarily cause any
        further issues.
      
      * app_sms: The array imsg is of size 250, while the array (ud) that the data
        is copied into is of size 160.  If the size of the inbound message is 
        greater then 160, up to 90 bytes could be overrun in ud.  This would corrupt
        the user data header (array udh) adjacent to ud.
      
      * chan_unistim: A number of invalid memmoves are corrected.  These would move
        data (which may or may not be valid) into the ends of these buffers.
      
      * asterisk: ast_console_toggle_loglevel does not check that the console log
        level being set is less then or equal to the allowed log levels of 32.
      
      * format_pref: In ast_codec_pref_prepend, if any occurrence of the specified
        codec is not found, the value used to index into the array pref->order
        would be one greater then the maximum size of the array.
      
      * jitterbuf: If the element being placed into the jitter buffer lands in the
        last available slot in the jitter history buffer, the insertion sort attempts
        to move the last entry in the buffer into one slot past the maximum length
        of the buffer.  Note that this occurred for both the min and max jitter
        history buffers.
      
      * tdd: If a read from fsk_serial returns a character that is greater then 32,
        an attempt to read past one of the statically defined arrays containing the
        values that character maps to would occur.
      
      * localtime: struct ast_time and tm are not the same size - ast_time is larger,
        although it contains the elements of tm within it in the same layout.  Hence,
        when using memcpy to copy the contents of tm into ast_time, the size of tm
        should be used, as opposed to the size of ast_time.
      
      * extconf: this treats ast_timing's minmask array as if it had a length of 48,
        when it has defined the size of the array as 24.  pbx.h defines minmask as
        having a size of 48.
      
      (issue ASTERISK-19668)
      Reported by: Matt Jordan
      ........
      
      Merged revisions 362485 from http://svn.asterisk.org/svn/asterisk/branches/1.8
      ........
      
      Merged revisions 362496 from http://svn.asterisk.org/svn/asterisk/branches/10
      
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@362497 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      f7829006
  21. Mar 14, 2012
  22. Mar 13, 2012
    • Tilghman Lesher's avatar
      Enable macros in 1.8 to find the next highest "h" extension in a context, like in 1.4. · 9af5c769
      Tilghman Lesher authored
      This change restores functionality that was present in 1.4, when AEL macros
      were implemented with the Macro dialplan application.  Macros are fraught with
      functionality issues, because they consume a large portion of the underlying
      application stack.  This limits the ability of AEL users to call many layers
      of subroutines, an issue which Gosub does not have (originally tested to
      100,000 levels deep).  Therefore, starting in 1.6.0, AEL macros were
      implemented with Gosub.
      
      However, there were some implicit behaviors of Macro, which were not replicated
      at the same time as with the transition to Gosub, one of which is documented in
      the related issue.  In particular, the "h" extension is designed to execute not
      in the Macro context, but in the topmost calling context.  Due to legacy issues
      with a misapplied bugfix many years ago, when a macro exited in 1.4, it looks
      in all calling contexts, bubbling up from the deepest level until it finds an
      "h" extension.
      
      Since AEL hides the complexity of the underlying dialplan logic from the AEL
      programmer, it's reasonable to assume that this behavior should not change in
      the transition from Asterisk 1.4 LTS to Asterisk 1.8 LTS, lest we break
      working AEL configurations in the transition to Asterisk 1.8 LTS.  This fix
      is the result, which implements a search for the "h" extension in all calling
      Gosub contexts.
      
      Fixes ASTERISK-19336
      
      Patch: 20120308__ael_bugfix_for_trunk__2.diff (License #5003) by Tilghman Lesher
      	(with slight modifications for 1.8)
      
      Tested by: Johan Wilfer
      
      Review: https://reviewboard.asterisk.org/r/1776/
      ........
      
      Merged revisions 358810 from http://svn.asterisk.org/svn/asterisk/branches/1.8
      ........
      
      Merged revisions 358811 from http://svn.asterisk.org/svn/asterisk/branches/10
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@358812 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      9af5c769
  23. Feb 14, 2012
  24. Feb 08, 2012
  25. Jan 15, 2012
  26. Dec 12, 2011
    • Matthew Jordan's avatar
      Backed out core changes from r346391 · 9057aa20
      Matthew Jordan authored
      During testing, it was discovered that there were a number of side effects
      introduced by r346391 and subsequent check-ins related to it (r346429,
      r346617, and r346655).  This included the /main/stdtime/ test 'hanging',
      as well as the remote console option failing to receive the appropriate output
      after a period of time.
      
      I only backed out the changes to main/ and utils/, as this was adequate
      to reverse the behavior experienced.
      
      (issue ASTERISK-18974)
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@347997 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      9057aa20
  27. Nov 29, 2011
  28. Oct 14, 2011
  29. Oct 10, 2011
  30. Sep 28, 2011
  31. Aug 17, 2011
  32. Jul 14, 2011
  33. Jul 07, 2011
  34. Jul 06, 2011
    • Terry Wilson's avatar
      Replace Berkeley DB with SQLite 3 · efd040cd
      Terry Wilson authored
      There were some bugs in the very ancient version of Berkeley DB that Asterisk
      used. Instead of spending the time tracking down the bugs in the Berkeley code
      we move to the much better documented SQLite 3.
      
      Conversion of the old astdb happens at runtime by running the included
      astdb2sqlite3 utility. The ast_db API with SQLite 3 backend should behave
      identically to the old Berkeley backend, but in the future we could offer a
      much more robust interface.
      
      We do not include the SQLite 3 library in the source tree, but instead rely
      upon the distribution-provided libraries. SQLite is so ubiquitous that this
      should not place undue burden on administrators.
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@326589 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      efd040cd
  35. Feb 04, 2011
Loading