Hello, On Tue, Sep 16, 2014 at 05:49:04PM -0500, Russell Urquhart wrote: > I got the +DEBUG when i ran that command.
So you get +DEBUG in the `mutt -v|grep BUG'
output, not -DEBUG?
If you cannot find ~/.muttdebug0 (in your home
directory), then maybe installation paths for the
build have been screwed up so that the home
directory is being looked up at some /foo/bar
prefix.
You can always check what's going on by running
mutt via strace:
strace -f -o /tmp/mutt.strace mutt -d4
After entering mutt immediately press `q' to exit
to cmdline, then you can check the strace logfile
for .muttdebug:
xrgtn@x505:~$ strace -f -o /tmp/mutt.strace mutt -d4
Debugging at level 4.
xrgtn@x505:~$ grep muttdebug /tmp/mutt.strace | tail -n2
26573 open("/home/xrgtn/.muttdebug0",
O_WRONLY|O_CREAT|O_LARGEFILE|O_NOFOLLOW, 0600) = 3
26573 lstat64("/home/xrgtn/.muttdebug0", {st_mode=S_IFREG|0600, st_size=0,
...}) = 0
xrgtn@x505:~$
I'm assuming you have GNU/Linux system. For HP-UX
you should use `tusc' and for Tru64/OSF you should
use `truss' instead IIRC.
For Windows, well, I thought there were some
vaguely similar utilities by Mark Russinovich and
regarding MacOS X I'm like ... I just don't
remember.
--
With best regards,
xrgtn
signature.asc
Description: Digital signature
