public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
* [Bug default/19103] New: make abidw --abidiff output on stdout rather than stderr
@ 2015-01-01  0:00 woodard at redhat dot com
  2016-01-01  0:00 ` [Bug default/19103] " woodard at redhat dot com
  2020-11-11 15:50 ` maennich at android dot com
  0 siblings, 2 replies; 3+ messages in thread
From: woodard at redhat dot com @ 2015-01-01  0:00 UTC (permalink / raw)
  To: libabigail

https://sourceware.org/bugzilla/show_bug.cgi?id=19103

            Bug ID: 19103
           Summary: make abidw --abidiff output on stdout rather than
                    stderr
           Product: libabigail
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: default
          Assignee: dodji at redhat dot com
          Reporter: woodard at redhat dot com
                CC: libabigail at sourceware dot org
  Target Milestone: ---

in the case where abidw is run with the --abidiff it would be helpful if it
emitted its output on stdout rather than stderr. It makes scripting harder, it
splitting off the aborts vs. the abixml correctness issues more difficult and
it forces me to use a command like:

~/bin/abidw --abidiff
/collab/usr/global/tools/order/spack/opt/chaos_5_x86_64_ib/gcc@4.4.7/dyninst@8.2.1-a77e6bbb/lib/libpcontrol.so.8.2.1
2>&1 | less

rather than the normal piping. Since nothing is being printed when you are
doing an abidw --abidiff unless it is a change that must be what you are
looking for when you use the --abidiff option.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug default/19103] make abidw --abidiff output on stdout rather than stderr
  2015-01-01  0:00 [Bug default/19103] New: make abidw --abidiff output on stdout rather than stderr woodard at redhat dot com
@ 2016-01-01  0:00 ` woodard at redhat dot com
  2020-11-11 15:50 ` maennich at android dot com
  1 sibling, 0 replies; 3+ messages in thread
From: woodard at redhat dot com @ 2016-01-01  0:00 UTC (permalink / raw)
  To: libabigail

https://sourceware.org/bugzilla/show_bug.cgi?id=19103

--- Comment #1 from Ben Woodard <woodard at redhat dot com> ---
The file in the report now doesn't report any areas. However, I would still
love to have this feature.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug default/19103] make abidw --abidiff output on stdout rather than stderr
  2015-01-01  0:00 [Bug default/19103] New: make abidw --abidiff output on stdout rather than stderr woodard at redhat dot com
  2016-01-01  0:00 ` [Bug default/19103] " woodard at redhat dot com
@ 2020-11-11 15:50 ` maennich at android dot com
  1 sibling, 0 replies; 3+ messages in thread
From: maennich at android dot com @ 2020-11-11 15:50 UTC (permalink / raw)
  To: libabigail

https://sourceware.org/bugzilla/show_bug.cgi?id=19103

Matthias Maennich <maennich at android dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |enhancement
                 CC|                            |maennich at android dot com

-- 
You are receiving this mail because:
You are on the CC list for the bug.

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2020-11-11 15:50 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-01-01  0:00 [Bug default/19103] New: make abidw --abidiff output on stdout rather than stderr woodard at redhat dot com
2016-01-01  0:00 ` [Bug default/19103] " woodard at redhat dot com
2020-11-11 15:50 ` maennich at android dot com

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).