mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tim Bird <tim.bird@am.sony.com>
To: naresh kamboju <naresh.kernel@gmail.com>
Cc: Mike Frysinger <vapier@gentoo.org>,
	ltp-list@lists.sourceforge.net, linux-kernel@vger.kernel.org,
	maxin john <maxinbjohn@gmail.com>,
	brinda_mn@yahoo.co.in, Oleg Nesterov <oleg@redhat.com>,
	rohit.170309@gmail.com
Subject: Re: [LTP] Char Limit issue on 2.6.29 kernels
Date: Fri, 24 Jul 2009 11:26:27 -0700	[thread overview]
Message-ID: <4A69FCD3.9070707@am.sony.com> (raw)
In-Reply-To: <f5a7b3810907241104g498b00a6i60c8858b8805091a@mail.gmail.com>

naresh kamboju wrote:
> Hi Mike,
> 
> On Fri, Jul 24, 2009 at 11:19 PM, Mike Frysinger<vapier@gentoo.org> wrote:
>> On Friday 24 July 2009 11:31:59 naresh kamboju wrote:
>>> I have come across with char Limit issue on 2.6.29 kernels.
>>>
>>>
>>> SIGFAULT:
>>>
>>> #define SIZE � � � � � �8053759
>>> char buf1[SIZE] ;
>>>
>>> NO SIGFAULT:
>>>
>>> #define SIZE � � � � � �8053758
>>> char buf1[SIZE] ;
>>>
>>> This SIGFAULT not observed on 2.6.23 kernels.
>> -ENOINFO
>>
>> post some actual code rather than saying "i declared a large buffer and things
>> crashed".
> 
> currently i am debugging this issue.
> i'll come up with more details.

Some more feedback...

It's SEGFAULT - short for "Segmentation Fault", not SIGFAULT.

Please include in your details at least the following:
 * what software this is in (is this declaration in the kernel?, a library, a
 user space program, etc.)
 * what operation is being performed when the SEGFAULT occurs.
 * what compiler you are using.
 * the code surrounding the operation when the fault occurs

If you can, make the smallest possible program that reproduces this error,
and send the complete source for that.
 -- Tim

=============================
Tim Bird
Architecture Group Chair, CE Linux Forum
Senior Staff Engineer, Sony Corporation of America
=============================


  reply	other threads:[~2009-07-24 18:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-24 15:31 naresh kamboju
2009-07-24 17:49 ` [LTP] " Mike Frysinger
2009-07-24 18:04   ` naresh kamboju
2009-07-24 18:26     ` Tim Bird [this message]
2009-07-24 19:16 ` Ray Lee

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=4A69FCD3.9070707@am.sony.com \
    --to=tim.bird@am.sony.com \
    --cc=brinda_mn@yahoo.co.in \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=maxinbjohn@gmail.com \
    --cc=naresh.kernel@gmail.com \
    --cc=oleg@redhat.com \
    --cc=rohit.170309@gmail.com \
    --cc=vapier@gentoo.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

Powered by JetHome