Your message dated Mon, 4 Jan 2010 13:03:52 +0100
with message-id <[email protected]>
and subject line Re: Bug#162638: reportbug: -f should read a core file (a dump
file) to extract a stack trace
has caused the Debian Bug report #162638,
regarding reportbug: -f should read a core file (a dump file) to extract a
stack trace
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
162638: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=162638
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: reportbug
Version: 1.99.60
Severity: wishlist
I've been looking to see what features bug has that reportbug lacks. The
consistency is overall very good, even using the same option names for
nearly everything. One missing little feature is bug allows use of -f
core and will get a stack trace from the core file and include it in the
bug report. I would not use this feature, but you might want to
consider including it to move toward implementing all of bug's features.
-- Package-specific info:
** Environment settings:
EDITOR="vim"
VISUAL="vim"
DEBEMAIL="[email protected]"
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux dragon 2.4.19 #1 Thu Sep 5 18:51:06 EDT 2002 i586
Locale: LANG=C, LC_CTYPE=C
Versions of packages reportbug depends on:
ii python2.2 2.2.1-12 An interactive object-oriented scr
ii python2.2-optik 1.3-6 advanced command-line parsing libr
-- no debconf information
--- End Message ---
--- Begin Message ---
Hello Joey,
a year has passed (quite precisely ;) ) and no reply come, so I'm
closing this report.
On Sat, Jan 3, 2009 at 01:09, Sandro Tosi <[email protected]> wrote:
> Hi Joey and happy new year.
>
> I'm wondering to close this bug, because we cannot find a correct way
> to implement this: for core files, we need debug symbols, etc. The
> people that generates a core, and want to report that to the
> maintainer, can say so in the report and the maint can guide them (for
> example, for some binaries there is no -dbg package) or we can add
> some sort of documentation.
maybe that could be part of the auto-debugging symbols architecture
we've heard will be available anytime soon.
Cheers,
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
--- End Message ---
