Fossil SCM
Crash on "fossil info 1234"
Fixed
aa8ba0fffadbba9…
· opened 16 years, 3 months ago
- Type
- Code_Defect
- Priority
- —
- Severity
- Minor
- Resolution
- Fixed
- Subsystem
- —
- Created
- Dec. 27, 2009 4:39 p.m.
I recently stumped across Fossil and got really interested by its concepts. In order to play with it, I installed Debian unstable's fossil ([dcf7bf4455] 2009-12-23 20:27:15 UTC), cloned the fossil repository, opened a working directory, cd'ed into that and issued "fossil info 1234" which resulted in the following crash:
$ fossil info 1234
uuid: e7ff366ee10efd6005d3eadf64d42a9d1dafb194
*** glibc detected *** fossil: free(): invalid pointer: 0x080b7363 ***
======= Backtrace: =========
/lib/i686/cmov/libc.so.6[0x40133824]
/lib/i686/cmov/libc.so.6[0x401350b3]
/lib/i686/cmov/libc.so.6(cfree+0x6d)[0x401380ad]
fossil[0x806275f]
fossil[0x8062917]
fossil[0x80652b4]
/lib/i686/cmov/libc.so.6(__libc_start_main+0xe5)[0x400deb55]
fossil[0x804a471]
======= Memory map: ========
...
More can be supplied on request.
I built a local version [06b964a0cf] which shows the same problem.
Note: The problem only occurs when trying to (invalidly) specifying an artefact id with 2 to 4 digits.
Greetings, Stefan
drh added on 2009-12-27 18:20:41:
Fixed in check-in [9d3fe01ae333adcea94acb637f8a8a5f40acb280].