What version are you running?
Review Board 1.0 RC2
Apache/2.2.11 (Debian) mod_python/3.3.1 Python/2.5.4
Bazaar (bzr) 1.15rc1
What's the URL of the page containing the problem?
http://<OUR SERVER>/reviewboard/r/8/diff/#index_header
What steps will reproduce the problem?
1. Create a repository using a file:// url pointing to the repo (the
directory the .bzr directory is in) we also tried pointing at the branch -
same effect
2.Checkout the branch separately and do a diff (I used bzr diff -r -2).
3.Create a new review with that diff, / as the base, and the repo created
earlier
4.Try to view the diff in the resulting review
What is the expected output? What do you see instead?
I expect to see the diff. I only see a blank screen.
What operating system are you using? What browser?
Linux - Debian Sid, Iceweasel (Firefox 3.0.6)
Please provide any additional information below.
Apache error log:
2009-06-01 13:03:40,854 - INFO - Logging to /tmp/rb.log/reviewboard.log
with a minimum level of DEBUG
2009-06-01 13:03:40,854 - INFO - Log file for Review Board v1.0rc2
2009-06-01 13:03:41,074 - DEBUG - Generating diff viewer page for filediff id 9
2009-06-01 13:03:41,075 - DEBUG - Begin: Generating diff file info for
diffset id 9
2009-06-01 13:03:41,081 - DEBUG - End: Generating diff file info for
diffset id 9
2009-06-01 13:03:41,081 - DEBUG - Generating diff file info for diffset id
9 took 0.5474 seconds
2009-06-01 13:03:41,083 - DEBUG - Begin: Generating diff file info for
diffset id 9, filediff 17
[NOTICE@1243883021.084428] mcm_server_connect():2302: Software caused
connection abort
[NOTICE@1243883021.084453] mcm_server_connect_next_avail():2333: Software
caused connection abort
[WARN@1243883021.084456] mcm_server_connect_next_avail():2338
2009-06-01 13:03:41,084 - INFO - Cache miss for key <OUR
SERVER>:diff-sidebyside-hl-17.
[Mon Jun 01 19:03:41 2009] [notice] child pid 4055 exit signal Segmentation
fault (11)
Please let me know what other details I can provide. I am new to Review
Board, so I might be missing something, but I can't seem to get over this -
seemingly simple - hurdle. Also, a signal 11 can't be the correct result in
any case, right?
