On 07/06/11 09:09, nathan binkert wrote:
>>> mmap: Cannot allocate memory
>>> fatal: Could not mmap!
>> Any arguments with changing this fatal to something more descriptive like?
>> Any suggestions on what it should be?
> Not from me. Could just add something like this: "The most common
> cause of this error is that your system does not have enough virtual
> memory available to allocate the total simulated memory that you are
> trying to create." Honstly though, for this instance, we should
> probably have a wiki page for this error that goes into the various
> issues (32-bit limitation, virtual memory (i.e. RAM+swap) limitation.
> Maybe we should add back the web page thing for error messages, but
> instead create a version of fatal (fatalw? fatalweb?) that sticks in
> that automatic thing for us (or we could create error codes). By
> having the separate version, we'd be explicit about having the URLs be
> valid and not point to some non-exsting web page.
>
> Finally, for this specific error, the perror("mmap") should possibly
> be part of the fatal like this:
>
> fatal("could not mmap (%s)!", strerror(errno));
>
> Then maybe people would read it more closely. Alternatively, we can
> check if errno == ENOMEM and print a special message for that.
>
> Nate
> _______________________________________________
> gem5-dev mailing list
> [email protected]
> http://m5sim.org/mailman/listinfo/gem5-dev
I doesn't have to be automatic. It could just say something like "See
gem5.org/MMap_error_thing".
Gabe
_______________________________________________
gem5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/gem5-dev
