public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: setup-x86.exe v2.893 has stopped working
Date: Wed, 03 Oct 2018 16:54:00 -0000	[thread overview]
Message-ID: <bb8b6370-59f2-c52d-8e0e-8185d9604f43@dronecode.org.uk> (raw)
In-Reply-To: <CAFWoy7HqmDSEDt0FxeTyJ4y4qU53_60bLiBR=Jcg5-VNFteAYA@mail.gmail.com>

On 03/10/2018 14:55, Keith Christian wrote:
> Ken and Jon,
> 
> I've downloaded setup-2.893.x86.dbg referenced above.  I haven't used
> gdb in a while but I am confident I can use it.  I''ve read the page
> referenced at sourceware.org/git.
> 
> I'm willing to build a setup-x86.exe to work with setup-2.893.x86.dbg

The whole point of preserving the symbols is that you don't need to 
rebuild setup in order to debug it.

Something like the following should work:

upx -d setup-x86.exe
gdb setup-x86.exe
symbol-file setup-2.893.x86.dbg
run
[reproduce crash]
bt full


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  parent reply	other threads:[~2018-10-03 16:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-02 16:12 Keith Christian
2018-10-02 17:32 ` Marco Atzeri
2018-10-02 18:48   ` Keith Christian
2018-10-02 19:24     ` cyg Simple
2018-10-03 13:49       ` Keith Christian
2018-10-02 19:36     ` Ken Brown
2018-10-02 20:30       ` Jon Turney
2018-10-03 13:55         ` Keith Christian
2018-10-03 14:03           ` Marco Atzeri
2018-10-03 15:40             ` Keith Christian
2018-10-03 16:53               ` Jon Turney
2018-10-03 16:54           ` Jon Turney [this message]
2018-10-03 22:32             ` Keith Christian
2018-10-04 18:43               ` Jon Turney
2018-10-05  3:07                 ` Keith Christian
2018-10-13 18:19                   ` Jon Turney

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=bb8b6370-59f2-c52d-8e0e-8185d9604f43@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin@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).