From: Marco Gerards <metgerards@student.han.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: network support : memory management problem
Date: Wed, 08 Jun 2005 21:38:20 +0200 [thread overview]
Message-ID: <87acm0prkj.fsf@student.han.nl> (raw)
In-Reply-To: <42A41F7E.6040403@inma.ucl.ac.be> (Vincent Guffens's message of "Mon, 06 Jun 2005 12:03:42 +0200")
Vincent Guffens <guffens@inma.ucl.ac.be> writes:
> I have tested three different card: Tulip, e1000, nforce2 as well as
> three compilers: gcc-2.95, gcc-3.0, gcc-3.3 However, the memory
> problem is still there, and I have no idea where it comes from. It
> varies depending on the compiler, the optimization flag, and some very
> small changes in the code. But it is always possible to find one
> combination of these for which the problem appears after loading a
> linux kernel or after the command boot or after a cat of a text file
> in the loopback device.
It can even be in some other code you did not write... If you can
reproduce this problem easily, it would be very nice.
--
Marco
next prev parent reply other threads:[~2005-06-08 19:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-31 13:48 network support : memory management problem Vincent Guffens
2005-05-31 16:45 ` Vincent Guffens
2005-05-31 17:08 ` Marco Gerards
2005-06-06 10:03 ` Vincent Guffens
2005-06-08 19:38 ` Marco Gerards [this message]
2005-06-09 23:09 ` Vincent Guffens
2005-06-12 8:54 ` Scripting and keystrokes Serbinenko Vladimir
2005-06-13 18:09 ` Serbinenko Vladimir
2005-06-13 18:52 ` Yoshinori K. Okuji
2005-06-13 19:39 ` Serbinenko Vladimir
2005-06-13 18:50 ` Yoshinori K. Okuji
2005-06-13 19:47 ` Serbinenko Vladimir
2005-05-31 22:56 ` network support : memory management problem Yoshinori K. Okuji
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=87acm0prkj.fsf@student.han.nl \
--to=metgerards@student.han.nl \
--cc=grub-devel@gnu.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 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.