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: Tue, 31 May 2005 19:08:37 +0200 [thread overview]
Message-ID: <871x7ncoh6.fsf@student.han.nl> (raw)
In-Reply-To: <429C949E.1080700@inma.ucl.ac.be> (Vincent Guffens's message of "Tue, 31 May 2005 18:45:18 +0200")
Vincent Guffens <guffens@inma.ucl.ac.be> writes:
> it looks like the problem is gone. I changed the way I allocate the
> memory to hold a block. I changed from:
>
> int load_block ()
> char * p = (char *) grub_malloc(len*sizeof(char));
>
> to
>
> int load_block ()
> char * p;
> [...]
> p = (char *) grub_malloc(len*sizeof(char));
This code is just the same. I think the problem is still there but
just does not show up anymore. I have seen a similar error before,
but I did not have the time to debug it.
> but still, I would be interested in documentation about the memory
> layout and the memory management of grub2, if available.
AFAIK there is none. But you can ask specific questions of course.
--
Marco
next prev parent reply other threads:[~2005-05-31 17:11 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 [this message]
2005-06-06 10:03 ` Vincent Guffens
2005-06-08 19:38 ` Marco Gerards
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=871x7ncoh6.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.