From: Arjan van de Ven <arjanv@redhat.com>
To: Norbert Preining <preining@logic.at>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6.7-mm2, mmaps rework, buggy apps, setarch
Date: Fri, 25 Jun 2004 10:31:16 +0200 [thread overview]
Message-ID: <1088152275.2704.8.camel@laptop.fenrus.com> (raw)
In-Reply-To: <20040625082243.GA11515@gamma.logic.tuwien.ac.at>
[-- Attachment #1: Type: text/plain, Size: 481 bytes --]
>
> Can someone please explain me *what* the effects of a `buggy app' would
> be: Segfault I suppose. But what to do with a commerical app where I
> cannot check a stack trace or whatever?
basically the applications that break do:
int ptr;
ptr = malloc(some_size);
if (ptr <= 0)
handle_no_memory();
> Background: I am having problems with current debian/sid on 2.6.7-mm2
> with vuescan.
can you describe these problems in somewhat more detail ?
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-06-25 8:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-25 8:22 2.6.7-mm2, mmaps rework, buggy apps, setarch Norbert Preining
2004-06-25 8:31 ` Arjan van de Ven [this message]
2004-06-25 10:00 ` Norbert Preining
2004-06-25 10:05 ` Arjan van de Ven
2004-06-25 8:35 ` Andrew Morton
2004-06-25 10:33 ` Norbert Preining
[not found] ` <4f.3ff82aed.2e0d624a@aol.com>
[not found] ` <20040625105312.GD20954@devserv.devel.redhat.com>
2004-06-25 10:43 ` Arjan van de Ven
2004-06-25 20:47 ` Norbert Preining
2004-06-30 7:10 ` Norbert Preining
2004-06-30 7:19 ` Ingo Molnar
2004-06-25 8:39 ` Arjan van de Ven
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=1088152275.2704.8.camel@laptop.fenrus.com \
--to=arjanv@redhat.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=preining@logic.at \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.