[Bug: 21.4.20] Network Drives

[Steve Higham]

Hi Benson,

 

This looks fine. The problem is that the code is calling the function with a
mode value of 1. Under a debug build this is causing an assertion to fail.

 

I have tried looking into this. However there's some complicated code
involved (function pointers etc.) and I haven't been able to determine where
this invalid mode value is originating from. I'm not familiar with the
xemacs architecture.

 

Any help appreciated.

 

Kind Regards,

 

Steve

 

  _____  

From: Benson Margulies [mailto:bim2007 at basistech.com] 
Sent: 12 March 2007 12:02
To: Steve Higham; Vin Shelton; Stephen J. Turnbull
Cc: xemacs-beta at xemacs.org
Subject: RE: [Bug: 21.4.20] Network Drives

 

The theme of my recent changes was to remove the use of 'pseudo-Unix' APIs
like access() and replace them with use of actual Win32. MSDN says:

 

When used with files, the _access function determines whether the specified
file exists and can be accessed as specified by the value of mode. When used
with directories, _access determines only whether the specified directory
exists; in Windows NT and Windows 2000, all directories have read and write
access.


mode value

Checks file for


00

Existence only


02 

Write permission


04

Read permission


06

Read and write permission

 

-----Original Message-----
From: Steve Higham [mailto:steve at sjlt.co.uk] 
Sent: Sunday, March 11, 2007 4:56 PM
To: 'Vin Shelton'; 'Stephen J. Turnbull'; Benson Margulies
Cc: xemacs-beta at xemacs.org
Subject: RE: [Bug: 21.4.20] Network Drives

 

Vin, Stephen, Benson,

 

I have been trying to build xemacs on my machine to investigate this bug. I

have been building on Windows using MS VS 2005.

 

An exception (debug assertion) is being thrown during the build. This is

coming from the Microsoft file access.c line 81 (fn _access_s). The

expression failing is ((amode &(~6)) == 0). This is failing due to an

"amode" value of 1. I have traced this call back to a call into fn

locate_file in xemacs file lread.c with a mode value of 1.

 

The executable being run at the time was temacs.exe.

 

The makefile had fired this off with the following command: -

 

"C:\Temp\XEmacs\xemacs-21.4.20\lib-src\i"

"C:\Temp\XEmacs\xemacs-21.4.20\src\temacs.exe" -batch -l

C:\Temp\XEmacs\xemacs-21.4.20\lisp\make-docfile.el -- -o

C:\Temp\XEmacs\xemacs-21.4.20\lib-src\DOC -i

 

I would like any help with the following points: -

Is this a known issue - if so how do I workaround it to build xemacs

successfully?

Where are these enumerations for the file access mode coming from?

Is it possible that this issue is also causing the problems I have been

experiencing with networked drives?

 

Any help really appreciated. This is the first time I have tried to build

xemacs.

 

Kind Regards,

 

Steve

 

-----Original Message-----

From: Steve Higham [mailto:steve at sjlt.co.uk] 

Sent: 28 February 2007 12:22

To: 'Vin Shelton'

Cc: 'xemacs-beta at xemacs.org'; 'Benson Margulies'

Subject: RE: [Bug: 21.4.20] Network Drives

 

Hi Vin,

 

The shared drive is hosted on a Windows 2000 Pro box.

 

I have just created a new file (S:\test.txt) on the server. This worked fine

and is editable on the server. However I cannot edit it when connecting over

the network. I can edit it (and save it) over the network using GNU Emacs so

this is not a permissions issue.

 

According to explorer the attributes are "AC". Both server and network

client have "Full control" permissions.

 

This problem is affecting all my files on my network drive. Everything was

working fine until I upgraded from previous version (21.4.13).

 

My network client is running XP Pro 64. This shared drive is accessed by a

number of other applications which are not experiencing this problem.

 

Please let me know if I can help further.

 

Kind Regards,

 

Steve

 

 

-----Original Message-----

From: ethersoft at gmail.com [mailto:ethersoft at gmail.com] On Behalf Of Vin

Shelton

Sent: 28 February 2007 11:32

To: Steve Higham

Cc: xemacs-beta at xemacs.org; Benson Margulies

Subject: Re: [Bug: 21.4.20] Network Drives

 

On 2/27/07, Steve Higham <steve at sjlt.co.uk> wrote:

> I have just reinstalled latest stable version of Xemacs. However any file

> opened on a network drive (e.g. S:\Misc\ToDo.txt) opens as a read-only

> buffer regardless of whether the file has the read only attribute set.

 

Thanks for the bug report.  As Stephen mentioned, this is an area that

has been undergoing active work in the last couple of releases.  In

any case, a few more details would help.  Is s: a samba share?  Also,

please send us the permissions on s:\Misc\Todo.txt as well as the

s:\Misc directory.

 

Thanks,

  Vin

-- 

The Journey by Mary Oliver

http://www.poemhunter.com/p/m/poem.asp?poet=6771&poem=30506

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.xemacs.org/pipermail/xemacs-beta/attachments/20070312/109fd471/attachment.htm