public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jim Wilson <wilson@cygnus.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] ia64 gcc implementation of alloca
Date: Wed, 07 Jun 2000 01:29:03 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590678205123@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205122@msgid-missing>

	Has anyone had any problem using alloca, or knows where in the gcc code it
	is implemented?

There is a lot of GNU code that uses alloca.  I haven't seen any alloca bug
reports.

There are a number of places in gcc that deal with alloca.  The main one
is allocate_dynamic_stack_space in explow.c.

It is probably easier to debug your failing code before trying to debug gcc.
Look at the instruction that failed, disassemble the loose routine, and figure
out why you get the segmentation fault.  It could be a problem with the code
rather than a gcc problem.  Is the stack pointer valid?  Is it aligned
properly, does it point to a valid stack address?

It looks like the program is dying in the dynamic loader when trying to load a
shared library.  Do you have a reasonably up to date copy of the dynamic
loader?  Are your shared libraries up to date?  There were many reports of
problems with glibc failing when a /etc/nsswitch.conf file was present early
this year, but it seems to work fine now.  The Red Hat May 17, 2000 OS release
has the file and it works fine.  I suspect a glibc bug that was fixed maybe a
month or two ago.

Jim



      reply	other threads:[~2000-06-07  1:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-06 22:34 [Linux-ia64] ia64 gcc implementation of alloca roneng
2000-06-07  1:29 ` Jim Wilson [this message]

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=marc-linux-ia64-105590678205123@msgid-missing \
    --to=wilson@cygnus.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