On Tue, 28 Apr 2020 at 17:50, ISHIKAWA,chiaki <ishik...@yk.rim.or.jp> wrote:
>
> 0:28.98 GECKO(727384) #01: ???
> (/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so + 0x5ab5921)
> 0:28.99 GECKO(727384) #02: ???
> (/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so + 0x5ab7f34)
> 0:28.99 GECKO(727384) #03: ???
> (/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so + 0x590de76)
> 0:28.99 GECKO(727384) #04: ???
> (/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so + 0x5a94c2f)
> 0:28.99 GECKO(727384) #05: ???
> (/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so + 0x5ab1589)
>
> [...]
> The file is mozilla/tools/rb/fix_stacks.py.:
>
> # Matches lines produced by MozFormatCodeAddress(), e.g.
> # `#01: ???[tests/example +0x43a0]`.
> line_re = re.compile("#\d+: .+\[.+ \+0x[0-9A-Fa-f]+\]")
>
> You see the re (Regular Expression) does not match the line in mochitest
> log produced by NS_ASSERTION().
>
> What gives?
>
The example at the top of https://github.com/mozilla/fix-stacks/ explains
this.
```
For example, a line like this in the input:
#01: ???[tests/example +0x43a0]
is changed to something like this in the output:
#01: main (/home/njn/moz/fix-stacks/tests/example.c:24)
```
So the output has definitely gone through `fix-stacks`, which is what I
would expect for mochitest output, because all mochitest output is fed
through `fix-stacks`.
I don't know why it was unable to find the function name, filename and line
number. If something was wrong with the files I would expect `fix-stacks`
to emit an error message. Are the files built with debug info?
Nick
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
