Opened 17 years ago
Last modified 17 years ago
#1963 closed bug
BFS Finds Spurious File — at Initial Version
| Reported by: | bonefish | Owned by: | axeld |
|---|---|---|---|
| Priority: | critical | Milestone: | R1/alpha1 |
| Component: | System/libroot.so | Version: | R1/pre-alpha1 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
hrev24582, VMware
While configuring/building gcc, a spurious "cp" entry appeared in the current output directory (.../gcc-obj/gcc/). According to the kernel tracing access() returned OK for the entry and it could even be opened. Reading from it failed with B_BAD_VALUE, though. There's also a respective "bfs_read()..." line in the serial debug output. I suspended and uploaded the virtual machine state (512 MB RAM, 1 GB disk):
http://tfs.cs.tu-berlin.de/~bonefish/private/haiku/CrashOMatic-non-existent-cp.zip
BFS tracing was enabled, but I forgot to enable block cache tracing. :-/
Note:
See TracTickets
for help on using tickets.
