Summary: | sys-devel/gdb-7.8 - findvar.c:773: internal-error: address_from_register: Assertion `!gdbarch_convert_register_p (gdbarch, regnum, type)' failed. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Tom Li <biergaizi2009> |
Component: | [OLD] Core system | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | mips |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | MIPS | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | emerge --info |
Description
Tom Li
2014-08-14 05:07:22 UTC
And it is my first time to use -g3 -ggdb on this platform. I just use -g before. I'll recompile and test to confirm whether -ggdb is buggy or not. Created attachment 382870 [details]
emerge --info
-g3 -ggdb isn't the problem. Downgrading to gdb-7.7 and the issue not longer represents. A git bisect is needed. my guess is the mips part is what makes this a bit flakier. i'm not sure i have suggestions other than doing a bisect as you noted. upstream repo: git://sourceware.org/git/binutils-gdb.git upstream bug tracker if you want to try that too: https://sourceware.org/bugzilla/enter_bug.cgi?product=gdb Mild curiosity, is -g3 -ggdb equivalent to -ggdb3? (In reply to Joshua Kinard from comment #5) the upstream documentation seems to indicate that is the case: https://gcc.gnu.org/onlinedocs/gcc-4.9.1/gcc/Debugging-Options.html This one corresponds to upstream bug https://sourceware.org/bugzilla/show_bug.cgi?id=17316 which has been fixed meanwhile. While I don't know the exact release in which it is fixed, I can confirm that I saw this problem (outside of gentoo context; on an embedded target) on MIPS64/n32 with gdb 7.8.2 and that the problem disappeared with gdb 7.9. According to me, this bug should be closed. thanks for the heads up |