gnu-arch-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnu-arch-users] Re: tla on aix


From: tow21
Subject: Re: [Gnu-arch-users] Re: tla on aix
Date: Tue, 10 Feb 2004 20:49:39 +0000
User-agent: Mutt/1.5.5.1+cvs20040105i

> > For the test-mv-explicit problem:  if you would, please preface the
> > suspicious 'tla commit' with lines like:
> > 
> >     echo BUG HERE: `pwd` 1>&2
> >         exit 2
> > 
> > Run the tests and then try running the commit command in the indicated
> > directory under a debugger.
> 
> If I have time tomorrow I might try playing around with running it 
> under a debugger.

As promised, some results from the debugger. The hang seems to occur
when trying to format and print the record of which "symlinks point at
nonexistent files". The actual line the execution of which seems to
cause the hang is vu-sys.c:635. Here is the stack trace immediately
before the hang.

[7] stopped in vu_sys_write at line 635 in file
"/users/tow21/dl/arch/tla-1.2pre2/src/hackerlab/vu/vu-sys.c"
  635     rv = write (fd, buf, count);
(dbx) where
vu_sys_write(errn = (nil), fd = 0, buf = (nil), count = 0, closure =
(nil)), lin
e 635 in "vu-sys.c"
vu_write(??, ??, ??, ??), line 1216 in "vu.c"
unnamed block $b970, line 1239 in "vu.c"
vu_write_retry(??, ??, ??, ??), line 1239 in "vu.c"
unnamed block $b941, line 391 in "printfmt-va.c"
printfmt_va_list(??, ??, ??, ??), line 391 in "printfmt-va.c"
safe_printfmt(fd = 2, fmt = "%s%s", ... = 0x20058558, 0x20350738, 0x0,
0x600c801
9, 0x60039767, 0x0), line 32 in "safe-printfmt.c"
rel_print_record(fd = 536931272, rec = (nil)), line 1201 in
"relational.c"
rel_print_table(fd = 2, table = 0x2002b374), line 1160 in "relational.c"
arch_print_tree_lint_report(??, ??), line 82 in "proj-tree-lint.c"
unnamed block $b253, line 355 in "cmd-commit.c"
unnamed block $b249, line 355 in "cmd-commit.c"
arch_cmd_commit(0x2007b498, 0x1, 0x2ff2290c), line 355 in "cmd-commit.c"
unnamed block $b1, line 85 in "tla.c"
main(argc = 0, argv = (nil)), line 85 in "tla.c"
(dbx) up
vu_write(errn = 0x0fba6600, fd = 0, buf = "\200A", count = 572663938),
line 1216 in "vu.c"
(dbx) up
unnamed block $b970, line 1239 in "vu.c"
(dbx) up
vu_write_retry(errn = (nil), fd = 0, buf = (nil), count = 0), line 1239
in "vu.c"
(dbx) up
unnamed block $b941, line 391 in "printfmt-va.c"
(dbx) up
printfmt_va_list(errn = 0xd01e85fc, fd = 537096620, fmt = "", ap =
"archive a changeset-based revision\nArchive a revision of the project
tree containing DIR (or the current\ndirectory)\n\nIf there are any
automated ChangeLog files, update them before\ncomputing the patch
set.\n\nIf --log-message is specified without --summary, then TEXT is
used both\nas the summary and the first line of the log body.\n"), line
391 in "printfmt-va.c"
(dbx) up
safe_printfmt(fd = 2, fmt = "%s%s", ... = 0x20058558, 0x20350738, 0x0,
0x600c8019, 0x60039767, 0x0), line 32 in "safe-printfmt.c"
(dbx) up
rel_print_record(fd = 536931272, rec = (nil)), line 1201 in
"relational.c"
(dbx) up
rel_print_table(fd = 2, table = 0x2002b374), line 1160 in "relational.c"
(dbx) up
arch_print_tree_lint_report(fd = 0, lint = (nil)), line 82 in
"proj-tree-lint.c"
(dbx) up
unnamed block $b253, line 355 in "cmd-commit.c"
(dbx) up
unnamed block $b249, line 355 in "cmd-commit.c"
(dbx) up
arch_cmd_commit(program_name = "tla commit", argc = 1, argv =
0x2ff2290c), line 355 in "cmd-commit.c"
(dbx) up
unnamed block $b1, line 85 in "tla.c"
(dbx) up
main(argc = 0, argv = (nil)), line 85 in "tla.c"
(dbx) 

I should note that I'm not entirely convinced that dbx is doing entirely
the right thing everywhere with respect to printing out arguments.

Toby

-- 
Dr. Toby White, Dept. of Earth Sciences, Downing Street, Cambridge CB2 3EQ. UK
Email: <address@hidden>




reply via email to

[Prev in Thread] Current Thread [Next in Thread]