This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Fri, Feb 8, 2013 at 10:05 AM, Doug Evans <dje@google.com> wrote: > On Tue, Feb 5, 2013 at 5:53 PM, Siva Chandra <sivachandra@google.com> wrote: >> The only useful entry point currently available is gdb_disassembly and >> I do not think it is a bad entry point. Other disassembly functions in >> disasm.c are static. > > Well, it begs the question what entrypoint into libopcodes does > gdb_disassembly use? :-) > Anyways, my point is gdb_disassembly is a bit high level for the > Python API for me. Thanks for your detailed reply. I now have a patch which does not use ui_out. Instead of calling gdb_disassembly, it essentially re-implements disasm.c:dump_insns. The patch is attached. 2013-02-12 Siva Chandra Reddy <sivachandra@google.com> Add a new method 'disassemble' to gdb.Architecture class. * python/py-arch.c (archpy_disassmble): Implementation of the new method gdb.Architecture.disassemble. (arch_object_methods): Add entry for the new method.
Attachment:
arch_disassemble_patch_v3.txt
Description: Text document
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |