allow ASSERT_ALWAYS_ABORT for debug builds on windows to be true or false

Bjoern Michaelsen bjoern.michaelsen at
Tue Oct 14 03:12:15 PDT 2014

Hi Miklos,

On Tue, Oct 14, 2014 at 11:49:24AM +0200, Miklos Vajna wrote:
> So it's the same as yours, just you need to do 'git show
> $sha1:build-info.txt', not 'git show $sha1' if you want to get core.git
> hashes.

Not quite (unless Im missing something). Compare e.g.:


Because the bisect log shows the tag names in the latter
(source-hash-d6cde02dbce8c28c6af836e2dc1120f8a6ef9932 etc.), I can see from the
bugzilla commit what the bisect range is, while I cannot do that with the
former (I think) without downloading the whole dbgutil bibisect repo.

Since you have the source hash in the build-info.txt file, it might be helpful
to have some script tagging the commit accordingly so that 'git bisect log'
shows the source hashes too.



More information about the LibreOffice mailing list