This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
mi/1761: Two output records generated in response to -data-disassemble
- From: set at users dot sf dot net
- To: gdb-gnats at sources dot redhat dot com
- Date: 25 Aug 2004 20:29:31 -0000
- Subject: mi/1761: Two output records generated in response to -data-disassemble
- Reply-to: set at users dot sf dot net
>Number: 1761
>Category: mi
>Synopsis: Two output records generated in response to -data-disassemble
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Wed Aug 25 20:38:00 UTC 2004
>Closed-Date:
>Last-Modified:
>Originator: set@users.sf.net
>Release: CVS code for 2004-08-25
>Organization:
>Environment:
Debian GNU/Linux Woody
>Description:
When -data-disassemble includes a region of memory that gdb can´t access it sends to responses. One indicating the error (^error,....) and another indicating successful completion (^done,....).
I think the problem is that gdb_disassembly doesn´t return error states. IMHO this function should return error and mi_cmd_disassemble should discard the partial result.
Another, better, option is to just supress the error like -data-read-memory does.
Another option id to check the range before disassembling it.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: