public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Xavier Wielemans <willy@alterface.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: abort() and exit(1) make RHEL freeze when core size limit is higher than 2 MB
Date: Wed, 28 Apr 2004 20:28:47 -0300	[thread overview]
Message-ID: <20040428232847.GE16387@logos.cnet> (raw)
In-Reply-To: <5.1.0.14.2.20040421141000.02798b80@mail.fluxtopia.net>

On Wed, Apr 21, 2004 at 02:11:19PM +0200, Xavier Wielemans wrote:
> [ I hope this is a relevant linux-kernel bug - I think so, all apologies if 
> not... ]
> [ Please CC me personally if replying, I'm not subscribed to the list - 
> thank you ! ]
> 
> Hi all,
> 
> I encountered the following problem - when my C++ application executes the 
> abort() or exit(1) system instructions, if the core size limit was 
> previously set to more than ~2MB (ulimit -c 2000), my PC freezes totally 
> and must be power-cycled...
> 
> If the core limit is left untouched to 0 (default), the abort or exit 
> instructions are executed without problems, but of course no core file is 
> dumped !
> 
> If core limit is set to 2000 or less, a core file is dumped but it is 
> unreadable (certainly because it is trimmed to less than its actual size).
> 
> If core limit is set to 4000 or higher (including 'ulimit -c unlimited') 
> the machine freezes as soon as abort() or exit() are executed.
> 
> Here are my configuration details :
> 
> [wielemans@electro:wielemans] cat /etc/redhat-release
> Red Hat Enterprise Linux WS release 3 (Taroon Update 1)
> 
> [wielemans@electro:wielemans] uname -a
> Linux electro 2.4.21-9.0.1.EL #2 Fri Apr 16 13:51:32 CEST 2004 i686 i686 
> i386 GNU/Linux
> 
> [wielemans@electro:wielemans] gcc -v
> Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs
> Configured with: ../configure --prefix=/usr --mandir=/usr/share/man 
> --infodir=/usr/share/info --enable-shared --enable-threads=posix 
> --disable-checking --with-system-zlib --enable-__cxa_atexit 
> --host=i386-redhat-linux
> Thread model: posix
> gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-24)
> 
> If you need more details, please ask !  Any help or idea welcome, thanks in 
> advance...

Xavier,

Odd. Is this the latest RH update? Maybe you can try a mainline kernel?

      reply	other threads:[~2004-04-28 23:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-21 12:11 abort() and exit(1) make RHEL freeze when core size limit is higher than 2 MB Xavier Wielemans
2004-04-28 23:28 ` Marcelo Tosatti [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=20040428232847.GE16387@logos.cnet \
    --to=marcelo.tosatti@cyclades.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=willy@alterface.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