From: "pabs3 at bonedaddy dot net" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/28027] New: abilint: "Unknown file type given in input" error message has no end of line character (LF)
Date: Wed, 30 Jun 2021 07:41:43 +0000 [thread overview]
Message-ID: <bug-28027-9487@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=28027
Bug ID: 28027
Summary: abilint: "Unknown file type given in input" error
message has no end of line character (LF)
Product: libabigail
Version: unspecified
Status: UNCONFIRMED
Severity: minor
Priority: P3
Component: default
Assignee: dodji at redhat dot com
Reporter: pabs3 at bonedaddy dot net
CC: libabigail at sourceware dot org
Target Milestone: ---
I noticed while playing with abilint that the "Unknown file type given in
input" error message has no end of line character (LF or \n), so if you are
passing multiple files to abilint via xargs, you get all the output on one
line. As far as I can tell all the other errors printed by abilint contain and
end of line character (\n).
$ echo foo > foo
$ abilint --noout foo |& hd
00000000 61 62 69 6c 69 6e 74 3a 20 55 6e 6b 6e 6f 77 6e |abilint: Unknown|
00000010 20 66 69 6c 65 20 74 79 70 65 20 67 69 76 65 6e | file type given|
00000020 20 69 6e 20 69 6e 70 75 74 3a 20 66 6f 6f | in input: foo|
0000002e
$ echo foo | hd
00000000 66 6f 6f 0a |foo.|
00000004
$ grep -B2 -A1 'Unknown file type given in input' tools/abilint.cc
case abigail::tools_utils::FILE_TYPE_UNKNOWN:
emit_prefix(argv[0], cerr)
<< "Unknown file type given in input: " << opts.file_path;
return 1;
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-06-30 7:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-30 7:41 pabs3 at bonedaddy dot net [this message]
2021-08-19 6:01 ` [Bug default/28027] " ucelsanicin at yahoo dot com
2021-09-10 19:36 ` mehmetgelisin at aol dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-28027-9487@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libabigail@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).