[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [MiNT] This must be an gcc / ld error!
- To: ole@monochrom.net
- Subject: Re: [MiNT] This must be an gcc / ld error!
- From: Miro Kropacek <miro.kropacek@gmail.com>
- Date: Thu, 27 May 2010 22:26:53 +0200
- Cc: mint@lists.fishpool.fi
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=6nf1+DFeVakFiGhU0nGxQ637ldxRIkZUgf83VjdsAqA=; b=tr3K6E7y+sV7t5UrtbJKEPDqgf/pgZ4npvJ8o1fIPEj7cBF3kseh8X/M5WZ5is0h5E rtNNYtUgdNfZ8U/SfBCu02K76jhqg5x1JeB8DUA9gP6cBmRV0LR0qUaikiQwWDtRwGe7 PpXVSHhXKI8FRR20WrXzU5yUZME2+Yuuy1NMg=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=YWEbd8+sHtkp/c8oVcBIXHmM1PkjeAKBA64MwsQiOPcBcmspPW3ke7jg5wXgMN6gSv wIYfHlqbK6kYtGa72Mn42x5DrSedDMTKTBD87Am+rCtqUweP3n9ZrWkE5JiNsWDrkfHc oTVrGOLaxtBgbZeiukyR8n26kRBmswf9L3Hs8=
- In-reply-to: <6f058cd2548d6d5f3dd6be1d3e1793ba-EhVcX1lFRQVaRwYcDTpQCEFddQZLVF5dQUBFBDBTXF5bVkYAWEF3AVU6XF1YRUwLXlxYSQ==-webmailer2@server07.webmailer.hosteurope.de>
- List-help: <mailto:ecartis@lists.fishpool.fi?Subject=help>
- List-id: <mint.lists.fishpool.fi>
- List-owner: <mailto:tjhukkan@fishpool.fi>
- List-post: <mailto:mint@lists.fishpool.fi>
- List-subscribe: <mailto:mint-request@lists.fishpool.fi?Subject=subscribe>
- List-unsubscribe: <mailto:mint-request@lists.fishpool.fi?Subject=unsubscribe>
- References: <6f058cd2548d6d5f3dd6be1d3e1793ba-EhVcX1lFRQVaRwYcDTpQCEFddQZLVF5dQUBFBDBTXF5bVkYAWEF3AVU6XF1YRUwLXlxYSQ==-webmailer2@server07.webmailer.hosteurope.de>
- Sender: mint-bounce@lists.fishpool.fi
> OK, I did that. The make file produced some test executables... any of the
> produced executables throws an Illegal Instruction exception. I removed
> the -O2 flag from the compiler options and I also removed the -g option.
Well, it's clear you're new to this, we old mercenaries ;) know the
first thing to try is ... stack tool! :) So try to increase stack
size, something like: stack --size=512k test_file (this increases
stack size from 64K to 512K) and run again. Another things to try:
increase stack size for sh/bash (depends what you use) and as last
resort gcc's cc1 (in case of some huge C files).
--
MiKRO / Mystic Bytes
http://mikro.atari.org