www.delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
X-Spam-Check-By: | sourceware.org |
Date: | Thu, 20 Aug 2009 20:17:02 -0400 |
From: | Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com> |
To: | cygwin AT cygwin DOT com |
Subject: | Re: add -debuginfo packages |
Message-ID: | <20090821001702.GA15308@ednor.casa.cgf.cx> |
Reply-To: | cygwin AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
References: | <6910a60908041158p10fa632cvc2f21524e33b74ce AT mail DOT gmail DOT com> <4A8DDEE8 DOT 2050606 AT users DOT sourceforge DOT net> |
MIME-Version: | 1.0 |
In-Reply-To: | <4A8DDEE8.2050606@users.sourceforge.net> |
User-Agent: | Mutt/1.5.20 (2009-06-14) |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.com> |
List-Unsubscribe: | <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com> |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
On Thu, Aug 20, 2009 at 06:40:24PM -0500, Yaakov (Cygwin/X) wrote: >Sorry for not getting back to this earlier. > >On 04/08/2009 13:58, Reini Urban wrote: >> Rather than stripping our exe's and dll's I suggest to strip the debug >> info into >> seperate /usr/lib/debug/path/file.dbg and package them seperately in -debuginfo >> packages such as with fedora. >> >> On any error which requires user-side debugging these symbols can be used >> by gdb (--symbols=SYMFILE) easily. >> >> dumper should use them too. >> Is this a good idea? > >At least in theory, certainly. As for implementation: I don't see why dumper would need this. AFAIK, the linux kernel doesn't need debugging information to dump core. >This would require changes in cygport, upset, and setup.exe but would >save maintainers from having to change each one of their packages. > >Thoughts? This seems like a not-inconsiderable amount of work for something that would only rarely be used. How many people here are capable of firing up a debugger to decode problems? cgf -- 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
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |