Bug 11135 - errors in gdb.execute run in MI abort the whole command instead of throwing a python exception
Summary: errors in gdb.execute run in MI abort the whole command instead of throwing a...
Status: RESOLVED INVALID
Alias: None
Product: gdb
Classification: Unclassified
Component: python (show other bugs)
Version: 7.0
: P2 normal
Target Milestone: 7.1
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-05 09:33 UTC by Andre'
Modified: 2010-01-08 10:07 UTC (History)
1 user (show)

See Also:
Host: i486-linux-gnu
Target: i486-linux-gnu
Build: i486-linux-gnu
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andre' 2010-01-05 09:33:54 UTC 
Running python gdb.execute("print something_that_does_not_exist") in MI mode in
7.0 and 7.0.1 immediately aborts the whole command with ^error,msg="Error while
executing Python code." without throwing a python exception as documented in
http://sourceware.org/gdb/current/onlinedocs/gdb/Exception-Handling.html#Exception-Handling.

It works as documented in archer-tromey-python.
Comment 1 Andre' 2010-01-08 10:07:10 UTC 
Can't reproduce it myself anymore.