RE: How to get software recording to work?
"Metzger, Markus T via Gdb" <[email protected]>
| Newsgroups | gmane.comp.gdb.devel |
|---|---|
| Message-ID | <DM8PR11MB57490806BED63E931C95F44CDE5E9@DM8PR11MB5749.namprd11.prod.outlook.com> |
Hello Simon, >Thanks Markus for your answers (just in case: they weren't CC'ed to the >mailing list, not sure if this was by intent). It was not. My email client sometimes removes mailing lists when I 'reply all' and I forgot to re-add it. Thanks for pointing it out. >> The issue is lack of AVX support in the record full instruction decoder. >> >>> Can this recording be done reliably? Which places would need to be fixed >>> / adjusted to get this working? >> >> AFAIK record full also has issues with multi-threaded processes. To fix the >instruction decode issue, the best approach IMHO would be to extend the >instruction decoder that is used for disassembly and use that for record full. > >Is this something Intel may have a look at? > >I guess Instruction/Processor specific instructions are possibly best >implemented by the vendors, aren't them? Intel is maintaining the binutils disassembler. It is a bit unfortunate that record full uses a separate instruction decoder. Given the issues with multi-threaded debuggee processes, I'm not sure how usable record full would be. Or how much it would be used if we were to enable AVX. I remember it adding significant recording overhead. Regards, Markus. Intel Deutschland GmbH Registered Address: Am Campeon 10, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de> Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928