This behavior of linker caused by a protection suit with sandbox
or similiar technology. Affected systems are win xp, win 7. With
a standard antivirus is all ok.
Is it really a bug, or is it this feature (NTFS tunneling)?
http://blogs.msdn.com/b/oldnewthing/archive/2005/07/15/439261.aspx
Walter Bright wrote in message news:jkmceb$r5f$1...@digitalmars.com...
On 3/24/2012 2:55 PM, Andrej Mitrovic wrote:
I can't reproduce this on Win7 x86. I've tried
On 3/28/2012 12:10 AM, Don wrote:
On 27.03.2012 00:42, Andrej Mitrovic wrote:
On 3/26/12, Walter Brightnewshou...@digitalmars.com wrote:
On 3/25/2012 2:50 PM, Kagamin wrote:
Microsoft has antivirus bundled with windows. Go to security center and
see
whether Windows Defender is working.
The names involved were short, so it should not have triggered that.
On 3/29/2012 1:01 AM, Mehrdad wrote:
Is it really a bug, or is it this feature (NTFS tunneling)?
http://blogs.msdn.com/b/oldnewthing/archive/2005/07/15/439261.aspx
Walter Bright wrote in message
On 27.03.2012 00:42, Andrej Mitrovic wrote:
On 3/26/12, Walter Brightnewshou...@digitalmars.com wrote:
On 3/25/2012 2:50 PM, Kagamin wrote:
Microsoft has antivirus bundled with windows. Go to security center and
see
whether Windows Defender is working.
Well, I'll be hornswoggled. That did
try
handle:
http://technet.microsoft.com/de-de/sysinternals/bb896655
or
process explorer:
http://technet.microsoft.com/de-de/sysinternals/bb896653
to find the blocking process
Am 24.03.2012 19:55, schrieb Walter Bright:
Note the failure to write out test.exe. I instrumented Optlink to
Seems like you got your answer (anti-virus).
I've been struggling with this for creating a temp file, then
deleting. Disabling AV isn't a solution so I have it run delete
when the program exits :P
Also, I've been using system(pause) to do waiting ha, if the
user closes the console with the X,
On 3/26/12, Walter Bright newshou...@digitalmars.com wrote:
On 3/25/2012 2:50 PM, Kagamin wrote:
Microsoft has antivirus bundled with windows. Go to security center and
see
whether Windows Defender is working.
Well, I'll be hornswoggled. That did the trick!
I really don't think that's the
On 3/24/2012 2:55 PM, Andrej Mitrovic wrote:
I can't reproduce this on Win7 x86. I've tried numerous times but it
never failed. It seems it's x64-related (or just a Win7 x64 bug).
I submitted a bug report to Microsoft.
On 24.03.2012 19:55, Walter Bright wrote:
I've been upgrading to a Windows 64 bit box. Running the D test suite, I
ran into a very strange problem. Here's the program:
---
extern(C) int printf(const char*, ...);
int main()
{
byte[3] a;
byte[3] b;
byte[3] c;
a[] = b[] +
On Saturday, 24 March 2012 at 19:22:03 UTC, Walter Bright wrote:
On 3/24/2012 12:18 PM, Xinok wrote:
If you have an antivirus, try disabling it before compiling.
I have a brand new vanilla install of Windows 7 home premium.
Microsoft has antivirus bundled with windows. Go to security
On 3/25/2012 2:50 PM, Kagamin wrote:
Microsoft has antivirus bundled with windows. Go to security center and see
whether Windows Defender is working.
Well, I'll be hornswoggled. That did the trick! Defender has a feature where it
will to real time scanning of new executables. Apparently, it
I've been upgrading to a Windows 64 bit box. Running the D test suite, I ran
into a very strange problem. Here's the program:
---
extern(C) int printf(const char*, ...);
int main()
{
byte[3] a;
byte[3] b;
byte[3] c;
a[] = b[] + c[];
On 3/24/2012 11:55 AM, Walter Bright wrote:
I'm mystified. Does anyone have any ideas?
If I add a del test.exe to the cc.bat file:
..\dmd test
test
del test.exe
..\dmd test
---
It now fails with GetLastError() of 5, meaning Access is denied.
The cc.bat
On Saturday, 24 March 2012 at 19:08:00 UTC, Walter Bright wrote:
On 3/24/2012 11:55 AM, Walter Bright wrote:
I'm mystified. Does anyone have any ideas?
If I add a del test.exe to the cc.bat file:
..\dmd test
test
del test.exe
..\dmd test
---
It now fails
On 3/24/2012 12:07 PM, Walter Bright wrote:
On 3/24/2012 11:55 AM, Walter Bright wrote:
I'm mystified. Does anyone have any ideas?
If I add a del test.exe to the cc.bat file:
..\dmd test
test
del test.exe
..\dmd test
---
It now fails with
On 3/24/2012 12:18 PM, Xinok wrote:
If you have an antivirus, try disabling it before compiling.
I have a brand new vanilla install of Windows 7 home premium.
On 3/24/2012 12:19 PM, Brad Roberts wrote:
I saw this sort of behavior in the auto-tester (was win7 at the time,
At least I'm not losing my mind :-)
now it's running on a windows server 2008 box)
during the various combinations of compilation options until I switched to
adding a counter and
Walter Bright newshou...@digitalmars.com wrote in message
news:jkl5ab$1ocp$1...@digitalmars.com...
I've been upgrading to a Windows 64 bit box. Running the D test suite, I
ran into a very strange problem. Here's the program:
---
extern(C) int printf(const char*,
On 3/24/2012 12:31 PM, Nick Sabalausky wrote:
Windows is known to enjoy holding locks on files just for the fuck of it.
See if the behavior changes if you add some delay just before the last line.
Or, if you adjust it so that compiling test.d takes longer.
I tried those. No dice.
Nick Sabalausky a@a.a wrote in message
news:jkl7fd$1rqs$1...@digitalmars.com...
Windows is known to enjoy holding locks on files just for the fuck of it.
See if the behavior changes if you add some delay just before the last
line. Or, if you adjust it so that compiling test.d takes longer.
Nick Sabalausky a@a.a wrote in message
news:jkl816$1t08$1...@digitalmars.com...
Nick Sabalausky a@a.a wrote in message
news:jkl7fd$1rqs$1...@digitalmars.com...
Windows is known to enjoy holding locks on files just for the fuck of it.
See if the behavior changes if you add some delay just
On 3/24/2012 12:36 PM, Walter Bright wrote:
On 3/24/2012 12:31 PM, Nick Sabalausky wrote:
Windows is known to enjoy holding locks on files just for the fuck of it.
See if the behavior changes if you add some delay just before the last line.
Or, if you adjust it so that compiling test.d takes
On 3/24/2012 12:48 PM, Walter Bright wrote:
On 3/24/2012 12:36 PM, Walter Bright wrote:
On 3/24/2012 12:31 PM, Nick Sabalausky wrote:
Windows is known to enjoy holding locks on files just for the fuck of it.
See if the behavior changes if you add some delay just before the last line.
Or, if
On Sat, 24 Mar 2012 20:48:47 +0100, Walter Bright
newshou...@digitalmars.com wrote:
On 3/24/2012 12:36 PM, Walter Bright wrote:
On 3/24/2012 12:31 PM, Nick Sabalausky wrote:
Windows is known to enjoy holding locks on files just for the fuck of
it.
See if the behavior changes if you add
On 3/24/2012 12:40 PM, Nick Sabalausky wrote:
If it still fails with the delay, you can probably find out (for whatever
help it might be) what process is holding the file open by adding a pause
right after running test. Then before Press[ing] a key as it suggests,
run SysInternal's Process
On 3/24/12, Walter Bright newshou...@digitalmars.com wrote:
Running the D test suite, I ran into a very strange problem.
I can reproduce the problem on Win7 x64. It doesn't seem to have
anything to do with DMD. This is my cc.bat:
dmd -c test.obj
link test.obj
test
link test.obj
But it's not
Walter Bright newshou...@digitalmars.com wrote in message
news:jklc1h$25l6$1...@digitalmars.com...
Also, looking at the process list when doing a PAUSE shows no new
processes, but it still fails.
No, no, first download this, it's like Task Manager on steriods:
On 3/24/2012 2:08 PM, Andrej Mitrovic wrote:
But it's not Optlink's fault either. Unilink has the same issue:
I did initially suspect Optlink. It's good to know that that is not the problem.
On 3/24/12, Walter Bright newshou...@digitalmars.com wrote:
On 3/24/2012 2:08 PM, Andrej Mitrovic wrote:
But it's not Optlink's fault either. Unilink has the same issue:
I did initially suspect Optlink. It's good to know that that is not the
problem.
In the meantime if you're just building
On 3/24/2012 2:39 PM, Andrej Mitrovic wrote:
On 3/24/12, Walter Brightnewshou...@digitalmars.com wrote:
On 3/24/2012 2:08 PM, Andrej Mitrovic wrote:
But it's not Optlink's fault either. Unilink has the same issue:
I did initially suspect Optlink. It's good to know that that is not the
On 3/24/12, Andrej Mitrovic andrej.mitrov...@gmail.com wrote:
It could be a Win7 x64 bug. If you'll give me 20 minutes I'll get a
hold of an x86 Win7 installation and see if I can reproduce the bug
there.
I can't reproduce this on Win7 x86. I've tried numerous times but it
never failed. It
On 3/24/2012 2:55 PM, Andrej Mitrovic wrote:
On 3/24/12, Andrej Mitrovicandrej.mitrov...@gmail.com wrote:
It could be a Win7 x64 bug. If you'll give me 20 minutes I'll get a
hold of an x86 Win7 installation and see if I can reproduce the bug
there.
I can't reproduce this on Win7 x86. I've
33 matches
Mail list logo