From: "J. Dow" <jdow@earthlink.net>
To: <dank@alumni.caltech.edu>, <atmproj@yahoo.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: malloc(1/0) ??
Date: Mon, 6 Nov 2000 23:13:31 -0800 [thread overview]
Message-ID: <04c301c0488a$694d6360$0a25a8c0@wizardess.wiz> (raw)
In-Reply-To: <3A07A522.3D1914D2@alumni.caltech.edu>
From: "Dan Kegel" <dank@alumni.caltech.edu>
> atmproj@yahoo.com asked:
> > [Why does this program not crash?]
> >
> > main()
> > {
> > char *s;
> > s = (char*)malloc(0);
> > strcpy(s,"fffff");
> > printf("%s\n",s);
> > }
>
> It doesn't crash because the standard malloc is
> optimized for speed, not for finding bugs.
>
> Try linking it with a debugging malloc, e.g.
> cc bug.c -lefence
> and watch it dump core.
I'm not sure that is fully responsive, Dan. Why doesn't the
strcpy throw a hissyfit and coredump?
{^_^}
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-07 7:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-07 6:45 Dan Kegel
2000-11-07 7:13 ` J. Dow [this message]
2000-11-07 7:52 ` David Schwartz
2000-11-08 0:47 ` Igmar Palsenberg
-- strict thread matches above, loose matches on Subject: below --
2000-11-07 16:12 Jesse Pollard
2000-11-07 16:38 ` lost
2000-11-07 9:26 malloc (1/0) ?? David Feuer
2000-11-07 3:59 malloc(1/0) ?? RAJESH BALAN
2000-11-07 7:54 ` David Schwartz
2000-11-07 7:59 ` Andrej Hosna
2000-11-07 8:50 ` David Schwartz
2000-11-07 8:09 ` Lyle Coder
2000-11-07 8:46 ` Matti Aarnio
2000-11-08 0:29 ` Rogier Wolff
2000-11-08 0:36 ` David Schwartz
2000-11-08 0:54 ` Igmar Palsenberg
2000-11-08 0:50 ` Igmar Palsenberg
2000-11-08 22:11 ` H. Peter Anvin
2000-11-08 22:11 ` Rasmus Andersen
2000-11-09 16:03 ` Igmar Palsenberg
2000-11-08 0:41 ` Igmar Palsenberg
2000-11-07 23:58 ` Tim Waugh
2000-11-08 12:38 ` Igmar Palsenberg
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='04c301c0488a$694d6360$0a25a8c0@wizardess.wiz' \
--to=jdow@earthlink.net \
--cc=atmproj@yahoo.com \
--cc=dank@alumni.caltech.edu \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®