Mailing-List: contact dev-help@trafficserver.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@trafficserver.apache.org
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
Subject: Re: backtrace
From: James Peach <jpeach@apache.org>
In-Reply-To: 
 <CAGATen6M5bxYggTZVSf-eA_sNVuGrV7foS9y3KMjsUEsZP1j+w@mail.gmail.com>
Date: Thu, 21 Jan 2016 19:27:54 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <523F2DAD-4879-40EC-83FD-E204A722BD6C@apache.org>
References: 
 <CAGATen6M5bxYggTZVSf-eA_sNVuGrV7foS9y3KMjsUEsZP1j+w@mail.gmail.com>
To: dev@trafficserver.apache.org


> On Jan 21, 2016, at 6:37 PM, Dk Jack <dnj0496@gmail.com> wrote:
>=20
> Hi,
> I am a newbie to ATS and I am trying to write a plugin. My plugin is
> crashing... and the crashlog
> has this message
>=20
> "Unable to retrieve backtrace: [6] Error reading from socket."

This means that traffic_crashlog was unable to make an API call into =
traffic_manager. Maybe traffic_manager was hosed or not available?

> I have installed libunwind8 and libunwind8-dev on my build machine and =
the
> target machine.
>=20
> I see the following lines when I run my configure script...
>=20
> =
--------------------------------------------------------------------------=
---------------------
> checking execinfo.h usability... yes
> checking execinfo.h presence... yes
> checking for execinfo.h... yes
> checking for library containing backtrace... none required    =
<<<<<<<<<
> checking pkg-config is at least version 0.9.0... yes
> checking for LIBUNWIND... yes
> configure: Using epoll event interface
> =
--------------------------------------------------------------------------=
---------------------
>=20
> When I run 'ldd' against the traffic_server binary, I see that it's =
not
> linking against libunwind.

traffic_manager is the one using libunwind to do the backtrace

> How do I enable backtrace so that I can see where my plugin is =
crashing.

Independently of the crash logging mechanism, you ought to get a =
backtrace in the traffic_server log, which would probably be traffic.out =
or diags.log depending on your configuration.

> Thanks in advance
> for any help.
>=20
> -Dk