From: Wanlong Gao <gaowanlong@cn.fujitsu.com>
To: file@mx.gw.com
Cc: LTP List <ltp-list@lists.sourceforge.net>
Subject: [LTP] [BUG] I'm reporting a bug about file
Date: Thu, 26 Apr 2012 11:52:46 +0800 [thread overview]
Message-ID: <4F98C68E.9050809@cn.fujitsu.com> (raw)
Hi folks,
Here, I'm reporting a bug, maybe it is solved upstream,
but it's already on Fedora 16. Below shows the bug,
It appears when testing https://github.com/linux-test-project/ltp/blob/master/testcases/commands/ade/file/file_test.sh#L292
the file command can't recognize below file as a "C program" file but just a ASSCII text.
> cat > $LTPTMP/cprog.c <<EOF
> #include <stdio.h>
>
> main()
> {
> printf("Hello Hell\n");
> exit(0);
> }
> EOF
But when I add a line like "#include <stdlib.h>", it can recognize to a "C program" file,
this problem doesn't appear on RHEL6 but appears recently.
And just test use the files under the source of "file" command like,
> $ file src/file.c
> src/file.c: ASCII English text
Do you think this is a bug, or I missed something?
Can you file command guys give me some idea about this?
Thanks in advance,
Wanlong Gao
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next reply other threads:[~2012-04-26 4:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 3:52 Wanlong Gao [this message]
2012-04-26 5:19 ` [LTP] [BUG] I'm reporting a bug about file Wanlong Gao
2012-04-28 5:50 ` Zhouping Liu
2012-04-28 11:12 ` Wanlong Gao
2012-04-28 21:23 ` Christos Zoulas
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=4F98C68E.9050809@cn.fujitsu.com \
--to=gaowanlong@cn.fujitsu.com \
--cc=file@mx.gw.com \
--cc=ltp-list@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.