public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bkorb at gnu dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/12232] setrlimit interferes with malloc
Date: Mon, 10 Jan 2011 01:25:00 -0000	[thread overview]
Message-ID: <bug-12232-131-hG0CYqrKqd@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12232-131@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=12232

Bruce Korb <bkorb at gnu dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |

--- Comment #18 from Bruce Korb <bkorb at gnu dot org> 2011-01-10 01:25:05 UTC ---
RE: core image -- I've uploaded both the core and the binary
here:  http://autogen.sourceforge.net/data

$ ldd test-dprintf-posix2 
        linux-vdso.so.1 =>  (0x00007fff34aeb000)
        librt.so.1 => /lib64/librt.so.1 (0x00007f4783c6d000)
        libm.so.6 => /lib64/libm.so.6 (0x00007f4783a16000)
        libc.so.6 => /lib64/libc.so.6 (0x00007f47836b6000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f4783499000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f4783e76000)

The failing scenario is to run it with one argument: the digit "1".

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  parent reply	other threads:[~2011-01-10  1:25 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-18 16:47 [Bug libc/12232] New: " bkorb at gnu dot org
2010-11-18 19:02 ` [Bug libc/12232] " drepper.fsp at gmail dot com
2010-11-18 20:14 ` bkorb at gnu dot org
2010-11-18 20:27 ` jakub at redhat dot com
2010-11-18 20:39 ` drepper.fsp at gmail dot com
2010-11-18 20:56 ` bkorb at gnu dot org
2010-11-18 21:00 ` bkorb at gnu dot org
2010-11-22 12:38 ` roucaries.bastien+bugs at gmail dot com
2010-11-23 16:00 ` bkorb at gnu dot org
2011-01-07 22:26 ` bkorb at gnu dot org
2011-01-07 23:24 ` bkorb at gnu dot org
2011-01-07 23:31 ` bkorb at gnu dot org
2011-01-08 14:32 ` drepper.fsp at gmail dot com
2011-01-08 21:32 ` roucaries.bastien+bugs at gmail dot com
2011-01-09 17:52 ` bkorb at gnu dot org
2011-01-09 17:53 ` bkorb at gnu dot org
2011-01-09 17:54 ` bkorb at gnu dot org
2011-01-09 18:59 ` bkorb at gnu dot org
2011-01-10  1:25 ` bkorb at gnu dot org [this message]
2011-01-10  3:19 ` drepper.fsp at gmail dot com
2011-01-10 16:00 ` bkorb at gnu dot org
2014-06-30  6:27 ` fweimer at redhat dot com

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=bug-12232-131-hG0CYqrKqd@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).