On 19/02/2012 12:41 AM, Christopher Faylor wrote:
On Sat, Feb 18, 2012 at 01:42:20PM -0500, Ryan Johnson wrote:
On 18/02/2012 12:58 PM, Christopher Faylor wrote:
On Sat, Feb 18, 2012 at 04:47:48PM +, Jon TURNEY wrote:
On 21/08/2009 00:40, Yaakov (Cygwin/X) wrote:
On 04/08/2009 13:58, Rein
On Sat, Feb 18, 2012 at 01:42:20PM -0500, Ryan Johnson wrote:
>On 18/02/2012 12:58 PM, Christopher Faylor wrote:
>> On Sat, Feb 18, 2012 at 04:47:48PM +, Jon TURNEY wrote:
>>> On 21/08/2009 00:40, Yaakov (Cygwin/X) wrote:
On 04/08/2009 13:58, Reini Urban wrote:
> Rather than stripping
On Sat, Feb 18, 2012 at 11:58 AM, Christopher Faylor wrote:
> On Sat, Feb 18, 2012 at 04:47:48PM +, Jon TURNEY wrote:
>>On 21/08/2009 00:40, Yaakov (Cygwin/X) wrote:
>>> 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
On 18/02/2012 12:58 PM, Christopher Faylor wrote:
On Sat, Feb 18, 2012 at 04:47:48PM +, Jon TURNEY wrote:
On 21/08/2009 00:40, Yaakov (Cygwin/X) wrote:
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
On 18/02/2012 11:47 AM, Jon TURNEY wrote:
On 21/08/2009 00:40, Yaakov (Cygwin/X) wrote:
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
packag
On Sat, Feb 18, 2012 at 04:47:48PM +, Jon TURNEY wrote:
>On 21/08/2009 00:40, Yaakov (Cygwin/X) wrote:
>> 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 s
On 21/08/2009 00:40, Yaakov (Cygwin/X) wrote:
> 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.
FWI
On Fri, 21 Aug 2009, Christopher Faylor wrote:
> On Fri, Aug 21, 2009 at 10:28:13AM -0500, Brian Ford wrote:
> >On Thu, 20 Aug 2009, Christopher Faylor wrote:
> >>How many people here are capable of firing up a debugger to decode
> >>problems?
> >
> >A lot more if they don't have to go through the
On Fri, Aug 21, 2009 at 10:28:13AM -0500, Brian Ford wrote:
>On Thu, 20 Aug 2009, Christopher Faylor wrote:
>>How many people here are capable of firing up a debugger to decode
>>problems?
>
>A lot more if they don't have to go through the pain of downloading
>source code and figuring out how to co
On Thu, 20 Aug 2009, Christopher Faylor wrote:
> How many people here are capable of firing up a debugger to decode
> problems?
A lot more if they don't have to go through the pain of downloading source
code and figuring out how to correctly build the package. You'd get
better bug reports faster
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
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 r
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
13 matches
Mail list logo