Bug#255495: acknowledged by developer (Re: Bug#255495: gcc-snapshot: Keep debugging symbols)

2004-06-27 Thread Daniel Bonniot
In my case, I don't really want to debug gcc, but I want to make an upstream bug report as precise as possible. So including a stack trace would be a bonus. It should help narrowing the nature of the bug, so that the appriopriate upstream author can start investigating, thus saving them time.

Bug#255495: acknowledged by developer (Re: Bug#255495: gcc-snapshot: Keep debugging symbols)

2004-06-27 Thread Roman Zippel
Hi, Daniel Bonniot wrote: In my case, I don't really want to debug gcc, but I want to make an upstream bug report as precise as possible. So including a stack trace would be a bonus. It should help narrowing the nature of the bug, so that the appriopriate upstream author can start investigating,

Bug#255495: acknowledged by developer (Re: Bug#255495: gcc-snapshot: Keep debugging symbols)

2004-06-26 Thread Daniel Jacobowitz
On Sat, Jun 26, 2004 at 07:42:19AM +0200, Matthias Klose wrote: > Daniel Jacobowitz writes: > > On Tue, Jun 22, 2004 at 12:51:41PM +0200, Daniel Bonniot wrote: > > > > > > Thanks for your prompt answer. > > > > > > >yes, space & bandwidth. the packages get 100%-200% bigger. and if you > > > >real

Bug#255495: acknowledged by developer (Re: Bug#255495: gcc-snapshot: Keep debugging symbols)

2004-06-26 Thread Matthias Klose
Daniel Jacobowitz writes: > On Tue, Jun 22, 2004 at 12:51:41PM +0200, Daniel Bonniot wrote: > > > > Thanks for your prompt answer. > > > > >yes, space & bandwidth. the packages get 100%-200% bigger. and if you > > >really want to debug gcc, you need the source and you build it > > >yourself. gcc-

Bug#255495: acknowledged by developer (Re: Bug#255495: gcc-snapshot: Keep debugging symbols)

2004-06-25 Thread Daniel Jacobowitz
On Tue, Jun 22, 2004 at 12:51:41PM +0200, Daniel Bonniot wrote: > > Thanks for your prompt answer. > > >yes, space & bandwidth. the packages get 100%-200% bigger. and if you > >really want to debug gcc, you need the source and you build it > >yourself. gcc-snapshot is intended to check for bugs i

Bug#255495: acknowledged by developer (Re: Bug#255495: gcc-snapshot: Keep debugging symbols)

2004-06-22 Thread Daniel Bonniot
Thanks for your prompt answer. yes, space & bandwidth. the packages get 100%-200% bigger. and if you really want to debug gcc, you need the source and you build it yourself. gcc-snapshot is intended to check for bugs in development versions of gcc, such that package maintainers can have it installe

Bug#255495: gcc-snapshot: Keep debugging symbols

2004-06-21 Thread daniel
Package: gcc-snapshot Version: 20040613-1 Severity: wishlist Since this snapshot is especially usefull for debugging recent versions of gcc, it would seem to me a good idea not to strip the executables, but to keep as much debugging symbols as possible. Is there a compelling reason not to do t