https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71951
--- Comment #7 from Timo Teräs ---
(In reply to Andrew Pinski from comment #6)
> (In reply to Timo Teräs from comment #5)
> > Not easily. It's musl, and using iterate phdr. Same build script works on
> > x86, x86_64 and armhf. It's only aarch64 m
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71951
--- Comment #6 from Andrew Pinski ---
(In reply to Timo Teräs from comment #5)
> Not easily. It's musl, and using iterate phdr. Same build script works on
> x86, x86_64 and armhf. It's only aarch64 misbehaving like this with omit
> frame pointer.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71951
--- Comment #5 from Timo Teräs ---
Not easily. It's musl, and using iterate phdr. Same build script works on x86,
x86_64 and armhf. It's only aarch64 misbehaving like this with omit frame
pointer. Any other suggestions what to try/how to debug fu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71951
--- Comment #4 from Andrew Pinski ---
Can you try this on a glibc instead musl?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71951
--- Comment #3 from Timo Teräs ---
$ cat a.cpp <
int foo()
{
throw "Foo!";
}
int main ()
{
try {
foo();
}catch (const char* msg) {
std::cerr << msg << std::endl;
}
return 0;
}
EOF
$ gdb a
GNU gdb (GDB) 7.11.1
Copyrig
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71951
--- Comment #2 from Andrew Pinski ---
Do you have an example? Because I ran with omit frame pointer all the time.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71951
--- Comment #1 from Andrew Pinski ---
Unwind code in lib gcc does uses the dwarf2 unwinding tables. So omit frame
pointer should not change anything.
