[Bug 674320] New: Various improvements for logging on W32

GStreamer (bugzilla.gnome.org) bugzilla at gnome.org
Wed Apr 18 04:54:47 PDT 2012


https://bugzilla.gnome.org/show_bug.cgi?id=674320
  GStreamer | gstreamer (core) | git

           Summary: Various improvements for logging on W32
    Classification: Platform
           Product: GStreamer
           Version: git
        OS/Version: Windows
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: Normal
         Component: gstreamer (core)
        AssignedTo: gstreamer-bugs at lists.freedesktop.org
        ReportedBy: lrn1986 at gmail.com
         QAContact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---


1) Log coloring on W32 uses W32 console API. Which is fine when you're logging
into console, but NOT fine when you need to log colored output into a file for
later viewing. On W32 such file can be viewed in MSys (cat, less, vim etc). Or
it can be sent to someone running an OS with a terminal that understands these
codes. W32 console API affects only the console; when logging into a file it
produces colorless log.

2) On Windows (at least) __FILE__ is the absolute source filename. It might be
a bug in the buildsystem, i wouldn't know. However, there's a workaround for it
(calling basename()), but it's only enabled for MSVC.

3) I've noticed that after fixing (2) i've got black sources and filenames in
colored logs. Black text doesn't work well on W32 when printed over black
background. The code that is responsible for not printing black over black*
checks that color definition is 0 as a way to detect black color. However, when
color definition contains formatting (bold, underline) it becomes != 0, but its
lower byte is still 0 (black), but the code doesn't catch that.
Also, that code ignores underline format.



*Actually, it's not true that W32 console can only have black background, black
is just the default.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.


More information about the gstreamer-bugs mailing list