From: Will Wagner <will_wagner@carallon.com>
To: buildroot@busybox.net
Subject: [Buildroot] google-breakpad experiences?
Date: Wed, 15 Oct 2014 17:02:37 +0100 [thread overview]
Message-ID: <543E9A9D.2010104@carallon.com> (raw)
In-Reply-To: <CAAXf6LWEBuVmnXosLpkjw0O9aVvGCBE2s=9e1PN6W5S7pK98+g@mail.gmail.com>
On 15/10/2014 15:53, Thomas De Schampheleire wrote:
> Hi,
<snip>
>
> Did any of you succeed in using google-breakpad on embedded targets?
Hi Thomas,
We have successfully been using google-breakpad for a few years. However
it is only on x86 and arm targets and we have our own internal package
(it pre-dates the one now upstream but is broadly similar, we have a
number of custom patches as well).
Are you trying to generate dumps within the crashed process or are you
running the crash server? We have found the latter to be much more reliable.
Regards
Will
--
------------------------------------------------------------------------
Will Wagner will_wagner at carallon.com
Development Manager Office Tel: +44 (0)20 7371 2032
Carallon Ltd, Studio G20, Shepherds Building, Rockley Rd, London W14 0DA
------------------------------------------------------------------------
--
------------------------------------------------------------------------
Will Wagner will_wagner at carallon.com
Development Manager Office Tel: +44 (0)20 7371 2032
Carallon Ltd, Studio G20, Shepherds Building, Rockley Rd, London W14 0DA
------------------------------------------------------------------------
next prev parent reply other threads:[~2014-10-15 16:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 14:53 [Buildroot] google-breakpad experiences? Thomas De Schampheleire
2014-10-15 16:02 ` Will Wagner [this message]
[not found] ` <543E8D2E.70404@carallon.com>
2014-10-15 18:44 ` Thomas De Schampheleire
2014-10-21 7:15 ` Will Wagner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=543E9A9D.2010104@carallon.com \
--to=will_wagner@carallon.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox