public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: chrubis@suse.cz
To: Ajoymon Joseph <AJOY.JOSEPH@LNTTECHSERVICES.COM>
Cc: "ltp-list@lists.sourceforge.net" <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] fstatfs02 issue on mips64
Date: Mon, 23 Jun 2014 17:02:11 +0200	[thread overview]
Message-ID: <20140623150210.GE6050@rei.Home> (raw)
In-Reply-To: <20140623145815.GA982@rei.suse.cz>

Hi!
> > statfs  is not there in strace output. Can you please tell me what can be the reason for strace not showing those functions?
> 
> No idea :(
> 
> Without carefull analysis this can range from missing implementation in
> strace to bugs in strace implementation.

Or could even mean that your libc fails to call the syscall and returns
bogus return value instead...

-- 
Cyril Hrubis
chrubis@suse.cz

------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2014-06-23 15:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-20 13:41 [LTP] fstatfs02 issue on mips64 Ajoymon Joseph
2014-06-23 11:43 ` Jan Stancek
2014-06-23 13:26   ` Ajoymon Joseph
2014-06-23 14:09     ` chrubis
     [not found]       ` <7CF842D49929104A9E5360C8FA9370998CF26D@POCITMSEXMB03.LntUniverse.com>
2014-06-23 14:58         ` chrubis
2014-06-23 15:02           ` chrubis [this message]
2014-06-23 14:47     ` Jan Stancek
2014-06-24  6:35       ` Ajoymon Joseph
2014-06-24  8:40         ` Jan Stancek
2014-06-23 11:51 ` chrubis

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=20140623150210.GE6050@rei.Home \
    --to=chrubis@suse.cz \
    --cc=AJOY.JOSEPH@LNTTECHSERVICES.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox