From: Jon TURNEY <jon.turney@dronecode.org.uk>
To: cygwin-apps@cygwin.com
Subject: [ITP] google-breakpad
Date: Tue, 18 Feb 2014 13:28:00 -0000 [thread overview]
Message-ID: <53036001.7060304@dronecode.org.uk> (raw)
These packages contain the minidump analysis part of breakpad, a
multi-platform crash reporting and analysis system using minidumps.
It doesn't make much sense to package the libbreakpad_client crash handling
library, as this conflicts with cygwin's error_start facility. It might make
some sense to make MinGW cross-compiled packages of libbreakpad_client in the
future.
I can't find this in any major linux distribution, so votes are required.
* google-breakpad-tools
This package contains the minidump_dump and minidump_stackwalk tools
The breakpad_dump_syms tool for generating breakpad symbol files has been
patched to read DWARF debug sections from a PE/COFF file (but see [1]).
The core2md and md2core tools to convert between minidump and core files have
not been ported.
The symsrv_convert tool, which reads PDB debug info from a MS symbol server
and converts it to a breakpad symbol file is very hard to port, as it uses the
MS DIA SDK and ATL.
setup.hint:
category: Devel
requires: libcurl4 libstdc++6
sdesc: "google-breakpad (tools)"
ldesc: "google-breakpad (tools)"
external-source: google-breakpad
* google-breakpad-devel
This package contains libbreakpad, a library for minidump processing.
setup.hint:
category: Devel
requires:
sdesc: "google-breakpad (minidump processing library)"
ldesc: "google-breakpad (minidump processing library)"
external-source: google-breakpad
files:
http://www.dronecode.org.uk/cygwin/x86/release/google-breakpad/google-breakpad-1279-1-src.tar.xz
http://www.dronecode.org.uk/cygwin/x86/release/google-breakpad/google-breakpad-tools/google-breakpad-tools-1279-1.tar.xz
http://www.dronecode.org.uk/cygwin/x86/release/google-breakpad/google-breakpad-devel/google-breakpad-devel-1279-1.tar.xz
license:
BSD 3-Clause License
[1] But this is currently not much use with modules produced by the GNU
toolchain. breakpad locates the corresponding symbol files using a unique
build-id recorded for each module in the minidump. For the Windows minidump
writer, this takes the form of a 'CodeView record'. Modules produced by the
GNU toolchain do not have CodeView records, although I have written an example
patch to add this [2].
[2] https://sourceware.org/ml/binutils/2014-01/msg00296.html
next reply other threads:[~2014-02-18 13:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 13:28 Jon TURNEY [this message]
2014-02-20 19:55 ` Corinna Vinschen
2014-02-23 15:48 ` Jon TURNEY
2014-02-21 2:23 ` Yaakov (Cygwin/X)
2014-02-21 2:43 ` Christopher Faylor
2014-02-21 6:09 ` [ITP] google-breakpad (VOTE) Jari Aalto
2014-02-28 13:00 ` Jon TURNEY
2014-02-28 15:47 ` Dr. Volker Zell
2014-02-28 17:09 ` Marco Atzeri
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=53036001.7060304@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@cygwin.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).