On Wed, Aug 06, 2008 at 12:30:06PM +0200, Pascal Obry wrote: > > The following command fails on my repository: > > $ git commit --file=clog > fatal: could not read log file 'clog': No such file or directory > > $ cat clog > toto > > Using the following command the commit pass without problem: > > $ cat clog | git commit --file=- > > With GDB I get: > > $ gdb --args git ci --file=clog > This GDB was configured as "i686-pc-cygwin"... > (gdb) break strbuf_read_file > Breakpoint 1 at 0x44e64a: file strbuf.c, line 301. > (gdb) run > Starting program: /usr/local/bin/git.exe ci --file=clog > > Breakpoint 1, strbuf_read_file (sb=0x22cac0, path=0x22ccfa "clog", hint=0) > at strbuf.c:301 > 301 fd = open(path, O_RDONLY); > (gdb) print path > $1 = 0x0 > > ???? outch, this is strange, or a gdb artifact? gdb artifact. The breakpoint info shows the correct value. Could you at that point run the following? (gdb) p get_current_dir_name() $1 = ... "..." If the returned value doesn't match the directory you were in, then there's a bug in git. If the function doesn't exist, try: (gdb) p getwd(malloc(2048)) Regards, Luciano Rocha -- Luciano Rocha <luciano@xxxxxxxxxxx> Eurotux Informática, S.A. <http://www.eurotux.com/>
Attachment:
pgpBb3xi2UegD.pgp
Description: PGP signature
