Debugger issues with NTFS Volume
Original Reporter info from Mantis: Hansaplast
-
Reporter name: Hans Luijten
Original Reporter info from Mantis: Hansaplast
- Reporter name: Hans Luijten
Description:
When a project is stored on a NTFS volume (I'm using "Paragon NTFS for Mac v8" - which works perfectly fine for other applications) the following things happen:
You will need to click the "Run" button (or menu option) twice.
The first click the application is being compiled but never runs.
The second click it compiles again and runs just fine.
(see attached log files)
However the second run starts with the debugger window opening with a notification of an error state ("oops, the debugger entered the error state").
After closing the window, the compiled application runs just fine (incl. reporting crashes, breakpoints, etc).
The debug output shows that the gdb does not seem to recognize the volume:
<-environment-cd "/Volumes/Shared Data/Projects/Lazarus/test/">
^error,msg="/Volumes/Shared: No such file or directory"
(gdb)
(the volume obviously does exist)
Steps to reproduce:
-
Install Lazarus/FPC as usual
-
Create a project on a NTFS volume
(might require "Paragon NTFS for Mac v8" for that) -
Click run.
-
Click run again.
Additional information:
Work around:
Save your project on a MacOS volume instead.
Mantis conversion info:
- Mantis ID: 18457
- OS: MacOS X
- OS Build: 10.6.5/10.6.6
- Build: 2011-01-08
- Version: 0.9.31 (SVN)
- Fixed in version: 0.9.31 (SVN)
- Fixed in revision: 31831 (#53cbfeeb)
- Monitored by: » Hansaplast (Hans Luijten)
- Target version: 0.99.0
- LazTarget: 1.0