printing backtrace

From: alex goldman (hello_at_spamm.er)
Date: 05/27/05

  • Next message: Loic Domaigne: "Re: How to check if the other application exists using UDP sockets" 
    Date: Fri, 27 May 2005 13:02:11 -0700

    I wonder if the assert macro can be modified in any way that would make the
    program (assuming any necessary compile flags for GCC/G++) print the
    backtrace whenever the error occurs.

    Assert prints the location in the code, where the error took place, but not
    what called the code that called the code that called the code that called
    the code that had this assert.

  • Next message: Loic Domaigne: "Re: How to check if the other application exists using UDP sockets"

    Relevant Pages

    • Re: printing backtrace
      ... > I wonder if the assert macro can be modified in any way that would make the ... > backtrace whenever the error occurs. ... Logic errors (assert() etc)? ... register your own signal handler for ...
      (comp.os.linux.development.apps)
    • Re: printing backtrace
      ... >> I wonder if the assert macro can be modified in any way that would make ... >> backtrace whenever the error occurs. ... >> Assert prints the location in the code, where the error took place, but ... However, I tried the example program from `info backtrace`, compiling with ...
      (comp.os.linux.development.apps)
    • printing backtrace
      ... I wonder if the assert macro can be modified in any way that would make the ... program (assuming any necessary compile flags for GCC/G++) print the ... backtrace whenever the error occurs. ...
      (comp.os.linux.development.apps)