Get location info from function indexes in addr2line script

[eloparco]

Updating the addr2line script so that:

• line info is printed in a more convenient format, e.g.

0: c
        at wasm-micro-runtime/test-tools/addr2line/trap.c:5:1
1: b
        at wasm-micro-runtime/test-tools/addr2line/trap.c:11:12
2: a
        at wasm-micro-runtime/test-tools/addr2line/trap.c:17:12

similar to how Rust prints stack traces when there's a panic. In an IDE, the user can conveniently click on the printed path and be redirected to the file line.

• a new --no-addr argument can be provided to the script

It can be used in fast interpreter mode (that is not supported by the script otherwise) or with older wamr versions (where the stack trace only had the function index info and not the function address). In that case, wasm-objdump is used to get the function name from the index and llvm-dwarfdump to obtain the location info (where the line refers to the start of the function).

[eloparco]

Tested with a few simple examples:

int
c(int n)
{
    __builtin_trap();
}

int
b(int n)
{
    n += 3;
    return c(n);
}

int
a(int n)
{
    return b(n);
}

int
main(int argc, char **argv)
{
    int i = 5;
    a(i);

    return 0;
}

fn c(_: i32) -> i32 {
    panic!("this is a panic!");
}

fn b(mut n: i32) -> i32 {
    n += 3;
    c(n)
}

fn a(n: i32) -> i32 {
    b(n)
}

fn main() {
    let i = 5;
    a(i);
}

If I want to run it in CI, should I add a new folder in samples with a program that crashes (as above)? Or should I use test-tools/addr2line?

[lum1n0us]

wondering what kind of case it is?

[eloparco]

That happens with _start

#00: 0x0159 - $f5
#01: 0x01b2 - $f6
#02: 0x0200 - $f7
#03: 0x026b - $f8
#04: 0x236b - $f15
#05: 0x011f - _start

I added a comment in the code.

[lum1n0us]

duplicated with L154 and L155 ?

[eloparco]

What do you mean? L154-155 are for the file, L157-158 for the line

[wenyongh]

Tested with a few simple examples:

int
c(int n)
{
    __builtin_trap();
}

int
b(int n)
{
    n += 3;
    return c(n);
}

int
a(int n)
{
    return b(n);
}

int
main(int argc, char **argv)
{
    int i = 5;
    a(i);

    return 0;
}

fn c(_: i32) -> i32 {
    panic!("this is a panic!");
}

fn b(mut n: i32) -> i32 {
    n += 3;
    c(n)
}

fn a(n: i32) -> i32 {
    b(n)
}

fn main() {
    let i = 5;
    a(i);
}

If I want to run it in CI, should I add a new folder in samples with a program that crashes (as above)? Or should I use test-tools/addr2line?

@eloparco how about creating a new folder under samples, so it not only tests the tool but also shows the usage for the developers.

[eloparco]

@eloparco how about creating a new folder under samples, so it not only tests the tool but also shows the usage for the developers.

That's what I had in mind as well, added it.

When I use AOT, the first stack frame address seems to be incorrect:

#00: 0x0000 - $f5
#01: 0x01ac - $f6
#02: 0x01fa - $f7
#03: 0x0265 - $f8
#04: 0x2365 - $f15
#05: 0x0119 - _start

I'm compiling with --enable-dump-call-stack. And added --size-level=0 as well to avoid problems on mac M1 (that I'm using for testing).

[wenyongh]

LGTM

[lum1n0us]

LGTM

[eloparco]

When I use AOT, the first stack frame address seems to be incorrect:

@wenyongh @lum1n0us any ideas about this one? Opened an issue #3212

[wenyongh]

@eloparco please try #3213.