public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: Baurjan Ismagulov <ibr@ata.cs.hun.edu.tr>
Cc: gdb@sources.redhat.com
Subject: Re: cvs build problem with 2.95
Date: Mon, 19 Apr 2004 13:24:00 -0000	[thread overview]
Message-ID: <vt2brloxyev.fsf@zenia.home> (raw)
In-Reply-To: <20040418225743.GA14873@ata.cs.hun.edu.tr>


Baurjan Ismagulov <ibr@ata.cs.hun.edu.tr> writes:
> On Sun, Apr 18, 2004 at 12:13:41PM -0400, Daniel Jacobowitz wrote:
> > 9 is SIGKILL.  That suggests the problem has nothing to do with your
> > compiler, and everything to do with your system resource limits, or
> > kernel.
> 
> Ah, yes, this was OOM; thank you! 256MB RAM + 128MB swap had worked for
> gdb 6.0 compilation, that is why I didn't think about this. Adding 256MB
> swap fixed the problem, albeit with intensive thrashing. What in this
> file makes gcc consume 350MB of virtual memory 8) , according to top? Is
> it an essential part of gdb? In other words, can I build a "minimal" gdb
> without it? I'm going to compile various versions for testing, and I
> wanted to apply patches on clean trees.

The file you're compiling is part of SID, the simulator, not GDB.  SID
contains a lot of really huge machine-generated files, of which
asm-semsw.cxx is one.  I think that's the file that actually
implements the instruction set of the ARM.

From what you've posted, it doesn't seem that you actually want the
simulator; why not just drop it?


  reply	other threads:[~2004-04-19 12:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-17 14:35 Baurjan Ismagulov
2004-04-18  0:16 ` Daniel Jacobowitz
2004-04-18 14:16   ` Baurjan Ismagulov
2004-04-18 15:20     ` Daniel Jacobowitz
2004-04-18 16:13       ` Baurjan Ismagulov
2004-04-18 22:56         ` Daniel Jacobowitz
2004-04-19  2:45           ` Baurjan Ismagulov
2004-04-19 13:24             ` Jim Blandy [this message]
2004-04-19 12:43               ` Baurjan Ismagulov
2004-04-19 18:32                 ` Daniel Jacobowitz
2004-04-20 16:34                   ` Baurjan Ismagulov
2004-04-20 16:42 ` Andrew Cagney
2004-04-21  0:44   ` Baurjan Ismagulov

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=vt2brloxyev.fsf@zenia.home \
    --to=jimb@redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=ibr@ata.cs.hun.edu.tr \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).