This is the mail archive of the
xconq7@sources.redhat.com
mailing list for the Xconq project.
Re: "Open file" bug?
- From: Eric McDonald <mcdonald at phy dot cmich dot edu>
- To: Hans Ronne <hronne at comhem dot se>
- Cc: Lincoln Peters <sampln at sbcglobal dot net>, <xconq7 at sources dot redhat dot com>
- Date: Sat, 6 Mar 2004 16:48:54 -0500 (EST)
- Subject: Re: "Open file" bug?
Hi Hans, others,
On Sat, 6 Mar 2004, Hans Ronne wrote:
> Yes. It is a consequence of how the new network-adapted save/load code
> works. I have noticed that you cannot load files from non-standard
> locations any longer and planned to do something about it. Not sure exactly
> what, though.
Another symptom that I have seen, at least since the network
support of load/save was added, is NULL filenames being reported
during the addition of modules to the module list. For example:
Reading module "ww2-pac-41" from library file "(null)" ...
Reading module "ww2-div-pac" from library file "(null)" ...
Reading module "ww2s-42" from library file "(null)" ...
Reading module "standard" from library file "(null)" ...
Reading module "ww2s-eur-42" from library file "(null)" ...
Reading module "standard" from library file "(null)" ...
Reading module "ww2s-pac-41" from library file "(null)" ...
Reading module "standard" from library file "(null)" ...
I think I may have known why that bug was occurring at one
point,
around the time when I was hardening Xconq against buffer
overflows and the network save/restore stuff was being added, but
now I would have to track it down again....
Eric