Re: "buffer overrun detected" message from Visual C++ Runtime Library

OK, I installed the debug version.  How do I get the stack information?

Now when it crashes, I get a dialog that says this:

----------------
(title)  Microsoft Visual C++ Debug Library

Program:  C:\Program Files\OpenAFS\Client\Program\afsd_service.exe
Module:  C:\Program Files\OpenAFS\Client\Program\afsd_service.exe
File:

Run-Time Check Failure #2 - Stack around the variable 's' was corrupted.

(Press Retry to debug the application)

[Abort] [Retry] [Ignore]
----------------

If I hit Retry, I get the standard your-app-crashed dialog box where it 
says "for more information about this error, click here".  A bunch of 
files were created:

afsd_service.exe.hdmp
afsd_service.exe.mdmp
appcompat.txt
manifest.txt

Should I e-mail those files to [email protected]?

Thanks,
Richard


Jeffrey Altman wrote:

> Richard Hansen wrote:
>
>> I just installed OpenAFS for Windows version 1.3.6400 on a fresh 
>> Windows XP install on a Pentium M laptop.  I mapped drive Z: to \afs 
>> and typed "afs-root" as its description.  I then obtained tokens and 
>> went to drive Z: in Windows Explorer.  As soon as I clicked on the 
>> one and only folder named "rcf" contained in Z:, I got this message:
>>
>> ---------------
>> (title) Microsoft Visual C++ Runtime Library
>>
>> Buffer overrun detected!
>>
>> Program: ... Files\OpenAFS\Client\Program\afsd_service.exe
>>
>> A buffer overrun has been detected which has corrupted the program's 
>> internal state.  The program cannot safely continue execution and 
>> must now be terminated.
>>
>> [OK]
>> ---------------
>>
>> It happens reliably whenever I click on that folder.  I mapped 
>> \afs\rcf to drive R: and I have no problems accessing everything 
>> inside R: (that I'm allowed to access anyway).
>>
>> Perhaps there's a bug lurking?
>>
>> Richard Hansen
>>
> Please install the debug build from 
> //afs/athena.mit.edu/user/j/a/jaltman/Public/OpenAFS/
> and if possible file a report to [email protected] which 
> contains the stack information
> for the location of the buffer overrun as reported by Windows.
>
>