Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Commits on Aug 31, 2012
  1. @psyeugenic

    Update copyright years

    psyeugenic authored
Commits on Jun 8, 2012
  1. @garazdawi

    Merge branch 'lukas/otp/install_with_whitespace/OTP-10107' into maint

    garazdawi authored
    * lukas/otp/install_with_whitespace/OTP-10107:
      Update to work with space in include path
      Update to work with whitespace in exec path
Commits on Jun 5, 2012
  1. @garazdawi

    Update to work with whitespace in exec path

    garazdawi authored
    OTP-10106
    OTP-10107
Commits on May 10, 2012
  1. @bjorng
Commits on Apr 1, 2012
  1. Prepare release

    Erlang/OTP authored
Commits on Mar 30, 2012
  1. @psyeugenic

    Update copyright years

    psyeugenic authored
Commits on Feb 29, 2012
  1. @dgud

    [debugger] Fixed disappearing breakpoints

    dgud authored
    Reported by Ricardo Catalinas Jiménez
Commits on Feb 9, 2012
  1. @bjorng

    Merge branch 'bjorn/deprecations/OTP-9907' into maint

    bjorng authored
    * bjorn/deprecations/OTP-9907:
      Deprecate the Toolbar application
      Deprecate applications that have been superseded by observer
      Suppress deprecated warnings in all modules that call 'gs'
      Deprecate the gs application
      Mark doc_builder as removed (and not merely deprecated)
Commits on Feb 8, 2012
  1. @bjorng
Commits on Feb 6, 2012
  1. @bjorng

    debugger tests: Increase time trap timeout

    bjorng authored
    Some bit syntax test cases take much longer time to complete when
    libraries are in native code, probably because of context switches
    between the eval_bits module and the debugger modules.
Commits on Dec 12, 2011
  1. Prepare release

    Erlang/OTP authored
Commits on Dec 10, 2011
  1. @dgud

    Merge branch 'dgud/wx/behaviour-spec'

    dgud authored
    * dgud/wx/behaviour-spec:
      [wx] Add handle_cast to avoid behaviour warning
      [wx] Avoid missing wx_object behaviour warning
      [wx] Remove warnings Add an additional cast when casting buffer offsets, to remove warnings "cast to pointer from integer of different size"
      [wx] Add callback specs to wx_object
Commits on Dec 9, 2011
  1. @psyeugenic

    Update copyright years

    psyeugenic authored
  2. @dgud
Commits on Nov 22, 2011
  1. @psyeugenic
  2. @bjorng @psyeugenic

    Update version numbers for pre-release of R15

    bjorng authored psyeugenic committed
Commits on Nov 10, 2011
  1. @proxyles

    Merge branch 'rj/fix-debugger-msgs'

    proxyles authored
    * rj/fix-debugger-msgs:
      Fix "OK" spelling in debugger messages and variables
      Fix debugger message with wx
    
    OTP-9699
  2. @jimenezrick @proxyles
Commits on Nov 9, 2011
  1. @jimenezrick @proxyles

    Fix "OK" spelling in debugger messages and variables

    jimenezrick authored proxyles committed
    Simple code refactor in the debugger: renames all the occurrences of
    "Ok" to "OK" in the code, variable names and strings. This improves the
    consistency of the code and follows the GTK UI where "OK" is always
    used.
  2. @jimenezrick @proxyles

    Fix debugger message with wx

    jimenezrick authored proxyles committed
    Add missing spaces when using wx UI. The gs UI didn't need them.
    Change the exclamation of the message by a dot, more formal style for a
    UI message.
Commits on Nov 7, 2011
  1. @bjorng

    EEP-23: Allow variables in fun M:F/A

    bjorng authored
    Currently, the external fun syntax "fun M:F/A" only supports
    literals. That is, "fun lists:reverse/1" is allowed but not
    "fun M:F/A".
    
    In many real-life situations, some or all of M, F, A are
    not known until run-time, and one is forced to either use
    the undocumented erlang:make_fun/3 BIF or to use a
    "tuple fun" (which is deprecated).
    
    EEP-23 suggests that the parser (erl_parse) should immediately
    transform "fun M:F/A" to "erlang:make_fun(M, F, A)". We have
    not followed that approach in this implementation, because we
    want the abstract code to mirror the source code as closely
    as possible, and we also consider erlang:make_fun/3 to
    be an implementation detail that we might want to remove in
    the future.
    
    Instead, we will change the abstract format for "fun M:F/A" (in a way
    that is not backwards compatible), and while we are at it, we will
    move the translation from "fun M:F/A" to "erlang:make_fun(M, F, A)"
    from sys_pre_expand down to the v3_core pass. We will also update
    the debugger and xref to use the new format.
    
    We did consider making the abstract format backward compatible if
    no variables were used in the fun, but decided against it. Keeping
    it backward compatible would mean that there would be different
    abstract formats for the no-variable and variable case, and tools
    would have to handle both formats, probably forever.
    
    Reference: http://www.erlang.org/eeps/eep-0023.html
Commits on Oct 27, 2011
  1. @bjorng

    Remove unused */doc/src/make.dep files

    bjorng authored
    These dependency files was once used when building the documentation,
    but are no longer needed.
Commits on Aug 18, 2011
  1. @bjorng

    debugger: By default, only save non-tail-recursive calls

    bjorng authored
    By default, the debugger use to save all calls on its simulated
    stack. That could facilitate finding errors, but it could also
    mean that the Debugger could become very slow while executing
    tail-recursive code.
  2. @bjorng
  3. @bjorng
  4. @bjorng
Commits on Aug 16, 2011
  1. @bjorng

    emulator: Add a fourth element in exception stacktraces

    bjorng authored
    This commit is a preparation for introducing location information
    (filename/line number) in stacktraces in exceptions. Currently
    a stack trace looks like:
    
      [{Mod1,Function1,Arity1},
       .
       .
       .
       {ModN,FunctionN,ArityN}]
    
    Add a forth element to each tuple that can be used indication
    the filename and line number of the source file:
    
      [{Mod1,Function1,Arity1,Location1},
       .
       .
       .
       {ModN,FunctionN,ArityN,LocationN}]
    
    In this commit, the fourth element will just be an empty list,
    and we will change all code that look at or manipulate stacktraces.
  2. @bjorng

    Remove support for very old BEAM files

    bjorng authored
    Since the run-time system cannot load those BEAM files, it was
    not possible to debug them anyway.
  3. @bjorng

    Don't include tail-recursive calls in stacktraces

    bjorng authored
    The stacktrace in debugger-generated exceptions should be
    as similar to stacktraces in BEAM-generated exceptions as
    possible.
  4. @bjorng

    Fix the no_tail option

    bjorng authored
    The 'no_tail' option was broken and would work almost as the
    'all' option, because it would use #ieval.top (formerly
    known as #ieval.last_call) as the basis for its decision
    to push or not.
    
    Fix it by including a boolean in each call/apply instruction
    indicating whether the call is tail-recursive and pass
    that boolean to the dbg_istk:push() function.
  5. @bjorng

    dbg_ieval: Properly handle exceptions when binary construction fails

    bjorng authored
    An exception from eval_bits:expr_grp/5 (for constructing binaries)
    was not caught and handled by exception/4; thus exit_info and
    and stacktrace for the process was not set.
  6. @bjorng

    Fix binary matching in the debugger

    bjorng authored
    'eval_bits' is a common utility module used for evaluting binary
    construction and matching. The functions that do matching
    (match_bits/{6,7} and bin_gen/6) are supposed to treat the bindings as
    an abstract data type, but they assume that the bindings have the same
    representation as in the erl_eval module.  That may cause binary
    matching to fail in the debugger, because the debugger represents the
    bindings as an unordered list of two-tuples, while the erl_eval
    modules uses an ordered list of two-tuple (an ordset).
    
    One way to fix the problem would be to let the debugger to use ordered
    lists to represent the bindings. Unfortunately, that would also change
    how the bindings are presented in the user interface. Currently, the
    variable have most been recently assigned is shown first, which is
    convenient.
    
    Fix the matching problem by mending the leaky abstraction in
    eval_bits.  The matching functions needs to be passed two additional
    operations: one for looking up a variable in the bindings and one for
    adding a binding. Those operations could be passed as two more funs
    (in addition to the evaluation and match fun already passed), but the
    functions already have too many arguments. Therefore, change the
    meaning of the match fun, so that the first argument is the operation
    to perform ('match', 'binding', or 'add_binding') and second argument
    is a tuple with arguments for the operation.
  7. @bjorng

    Delay saving of the stack in exit_info when an exception occurs

    bjorng authored
    When an exception occurs, the entire stack will be converted to
    the external term format and kept in the exit_info variable in
    the process dictionary. But the exit_info variable will only be
    needed if the exception causes the process to terminate (not if
    it is caught).
    
    Delay the conversion of the stack to external format. That can
    save significant amounts of time (e.g. in bs_construct:mem_leak/1).
  8. @bjorng
  9. @bjorng

    Update test suites that have been copied from other applications

    bjorng authored
    A long time ago, test suites were copied from other applications.
    Copy the tests again to get more test cases.
Something went wrong with that request. Please try again.