public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: umut aymakoglu <umutaymak@yahoo.com>
To: linux-ia64@vger.kernel.org
Subject: RE: segv at strcmp
Date: Mon, 05 Jan 2004 19:52:38 +0000	[thread overview]
Message-ID: <20040105195238.80473.qmail@web60006.mail.yahoo.com> (raw)
In-Reply-To: <20040105190848.66033.qmail@web60006.mail.yahoo.com>

Probably the location of "x" is not at the end of the
shared memory segment. In /usr/include/bits/string2.h
strcmp is defined as memcmp which must be getting
picked up.

thanks,
Umut
--- "Luck, Tony" <tony.luck@intel.com> wrote:
> > Hi -
> >   The gcc version is gcc-3.2-29 and the flags we
> pass
> > to gcc are : -O -ansi -fwritable-strings
> -fsigned-char
> > -D_GNU_SOURCE -D_REENTRANT
> 
> I have gcc 3.2.3 ... but it appears to not do
> anything
> strange to my test program with those options.
> 
> main()
> {
>         char *x = "7chars!";
> 
>         strcmp(x, "This is 24 chars long!!!");
> }
> 
> with those options.  Do you have any include files
> that
> might be redefining strcmp as memcmp?
> 
> -Tony


__________________________________
Do you Yahoo!?
New Yahoo! Photos - easier uploading and sharing.
http://photos.yahoo.com/

  parent reply	other threads:[~2004-01-05 19:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-05 19:08 segv at strcmp umut aymakoglu
2004-01-05 19:19 ` Luck, Tony
2004-01-05 19:52 ` umut aymakoglu [this message]
2004-01-05 20:10 ` Luck, Tony
2004-01-05 22:06 ` David Mosberger
2004-01-06  0:04 ` umut aymakoglu
2004-01-06  1:14 ` Luck, Tony
2004-01-06  1:38 ` umut aymakoglu
2004-01-06  2:01 ` Chen, Kenneth W
2004-01-06 19:58 ` umut aymakoglu
  -- strict thread matches above, loose matches on Subject: below --
2003-12-24 23:13 umut aymakoglu
2003-12-24 23:44 ` Jeff Woods
2003-12-25  0:25 ` Luck, Tony
2003-12-25  1:11 ` Zhu, Yi

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=20040105195238.80473.qmail@web60006.mail.yahoo.com \
    --to=umutaymak@yahoo.com \
    --cc=linux-ia64@vger.kernel.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