Skip to Content.
Sympa Menu

sm-sorcery-bugs - [SM-Sorcery-Bugs] [Bug 7903] Super Debug Borked

sm-sorcery-bugs AT lists.ibiblio.org

Subject: Bugs for Sorcery are reported here

List archive

Chronological Thread  
  • From: bugzilla-daemon AT bugs.sourcemage.org
  • To: sm-sorcery-bugs AT lists.ibiblio.org
  • Subject: [SM-Sorcery-Bugs] [Bug 7903] Super Debug Borked
  • Date: Wed, 2 Feb 2005 13:57:18 -0800 (PST)

http://bugs.sourcemage.org/show_bug.cgi?id=7903





------- Additional Comments From acedit AT armory.com 2005-02-02 13:57 -------
I think I figured this out, our favorite process substitution appears to be
the
culprit, in build_api/api1 and build_api/api2 are these things

) 2> >(tee -a $C_LOG 1>&2 > $VOYEUR_STDERR) \
> >(tee -a $C_LOG > $VOYEUR_STDOUT) # see bug 7201

Notice, the redirection to $VOYEUR_STDERR, since theres a > it's truncating
$VOYEUR_STDERR, which for super-debug purposes happens to be a file.
if you change that to tee -a $C_LOG 1>&2 >> $VOYEUR_STDERR it seems to work,
at
least with my preliminary tests i think i get super-debug stuff from all
phases
of cast, or at least multiple spells.

Theres one other less important but still valid problem with super-debug, in
cast we have this
summon_spells "$SPELL" &> $download_log
from change 40200, which was put there because wget logs to stderr, by
redirecting both streams some of the super-debug stuff goes to the
download_log
instead of staying in the super-debug log as its supposed to.

--
Configure bugmail: http://bugs.sourcemage.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.




Archive powered by MHonArc 2.6.24.

Top of Page