Lars Richter wrote:
I try to produce a minidump and a log file with Dr. Watson.
A minidump in this case is not going to be useful because the relevant information is the panic data plus a description of how to reproduce the problem.
A public test case isn't possible, because we don't have a public cell.
Then you have to provide enough details to permit me to reconstruct the test environment so that the problem can be reproduced.
I agree with you, that it make no sense to create such links. But our software developer use scripts for creating links with absolute paths to include and library directories. The results of some scripts are such links with "../.." and "..". I also think, that when such links are possible under Linux, it could also happen by other users.
I ask only so I can determine what priority to associate with the bug.If this is a minor inconvenience I am not going to rush out a new general release.
The limit of 100 characters is really strange, but I did some test with shorter links without problems.
/afs/athena.mit.edu/user/j/a/jaltman/Public/test/link1 /afs/athena.mit.edu/user/j/a/jaltman/Public/test/link2 are symlinks that include relative directories and are longer than 100 characters. I can not reproduce a panic on either 32-bit or 64-bit oafw.When you file your bug report indicate whether these paths are sufficient to reproduce your bug and if not, how they differ from the links you are creating.
Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
