From: Daniel Jacobowitz <drow@false.org>
To: gdb@sources.redhat.com
Subject: Re: cvs build problem with 2.95
Date: Sun, 18 Apr 2004 22:56:00 -0000 [thread overview]
Message-ID: <20040418161340.GA23509@nevyn.them.org> (raw)
In-Reply-To: <20040418152206.GC10611@ata.cs.hun.edu.tr>
On Sun, Apr 18, 2004 at 05:22:06PM +0200, Baurjan Ismagulov wrote:
> On Sun, Apr 18, 2004 at 10:16:43AM -0400, Daniel Jacobowitz wrote:
> > > gcc 3.3.3 gives the same message at the same file. This was actually why
> > > I wanted to try 2.95. I've updated gcc, cpp and g++ packages, and can
> > > still stably reproduce this. I suspect that I should file a bug against
> > > gcc, but before that I wish to have this working. Any ideas?
> >
> > Nope.
>
> Which revisions of gcc, g++ and cpp are you using (I suppose you don't
> experience these problems)?
I've never seen the problem you describe.
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.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-04-18 16:13 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 [this message]
2004-04-19 2:45 ` Baurjan Ismagulov
2004-04-19 13:24 ` Jim Blandy
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=20040418161340.GA23509@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
/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).