Your message dated Thu, 29 Dec 2011 17:09:17 +0100
with message-id <[email protected]>
and subject line Re: Bug#506184: Please make --num-callers easier to find in
the manpage.
has caused the Debian Bug report #506184,
regarding Please make --num-callers easier to find in the manpage.
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.)
--
506184: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506184
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: valgrind
Version: 1:3.3.1-2
Severity: wishlist
When I'm tracking a problem down with valgrind and need more than
12 stack frames of context, I always seem to go through the same little
dance (which I never remember until it's too late because it's so
infrequent that I need to do this):
(a) I need a longer backtrace. I know there's an option for this,
so I'll search for "backtrace" in the manpage.
(b) Darn, that wasn't it. Maybe something about the stack? *searches
for stack*.
(c) Nope. Ummmm, maybe I need to increase the number of stack frames?
Ah, --max-stackframe! ... no, that's not it either.
(d) Perhaps "context"?
(e) Ok, I'll just try searching for "max" and pray. Whoa, the first
hit tells me about "num-callers". That's what I want!
.... which is all a long-winded way of saying that for stupid people
like me, it would help if you mentioned the words "backtrace", "stack",
or "frame" in the documentation of --num-callers. Maybe something like
"By default, Valgrind shows the first twelve frames of each backtrace to
help you ... (etc)".
Daniel
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages valgrind depends on:
ii libc6 2.7-16 GNU C Library: Shared libraries
Versions of packages valgrind recommends:
ii gdb 6.8-3 The GNU Debugger
Versions of packages valgrind suggests:
pn alleyoop <none> (no description available)
pn kcachegrind <none> (no description available)
pn libc6-dbg <none> (no description available)
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1:3.7.0-1
On Tue, Nov 18, 2008 at 09:26:33PM -0800, Daniel Burrows wrote:
> .... which is all a long-winded way of saying that for stupid people
> like me, it would help if you mentioned the words "backtrace", "stack",
> or "frame" in the documentation of --num-callers. Maybe something like
> "By default, Valgrind shows the first twelve frames of each backtrace to
> help you ... (etc)".
--num-callers now speaks about *stack* traces, which qualifies I think
:)
--
·O· Pierre Habouzit
··O [email protected]
OOO http://www.madism.org
--- End Message ---
