From: Arjan van de Ven <arjanv@redhat.com>
To: Norbert Preining <preining@logic.at>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: 2.6.7-mm2, mmaps rework, buggy apps, setarch
Date: Fri, 25 Jun 2004 12:43:17 +0200 [thread overview]
Message-ID: <20040625104317.GB20954@devserv.devel.redhat.com> (raw)
In-Reply-To: <20040625103326.GA21814@gamma.logic.tuwien.ac.at>
[-- Attachment #1: Type: text/plain, Size: 765 bytes --]
On Fri, Jun 25, 2004 at 12:33:26PM +0200, Norbert Preining wrote:
> On Fre, 25 Jun 2004, Andrew Morton wrote:
> > > But what to do with a commerical app where I
> > > cannot check a stack trace or whatever?
> >
> > Use strace -f, look at the last screenful of output. That usually works.
>
> open("/media4/scan/cam-2002.03/001-100/raw/scan0100.tif", O_RDONLY) = 6
> lseek(6, 0, SEEK_END) = 43426634
> lseek(6, 0, SEEK_CUR) = 43426634
> lseek(6, 0, SEEK_SET) = 0
> mmap2(NULL, 43426634, PROT_READ|PROT_WRITE, MAP_PRIVATE, 6, 0) = -1 ENOMEM (Cann
> ot allocate memory)
interesting.
Could you start the binary in gdb, and then when the segfault happens, take
a snapshot of /proc/<pid>/maps of this binary ?
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-06-25 10:43 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
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 [this message]
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=20040625104317.GB20954@devserv.devel.redhat.com \
--to=arjanv@redhat.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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.