diff options
author | Joel Brobecker <brobecker@gnat.com> | 2010-03-16 18:47:15 +0000 |
---|---|---|
committer | Joel Brobecker <brobecker@gnat.com> | 2010-03-16 18:47:15 +0000 |
commit | b8d088acc8f9fe81d5ecbcbbecc694ac0091cb5e (patch) | |
tree | 08e4cf44e8f347db300990cdec5bad720087d78d /gdb/valarith.c | |
parent | d9097b0b398d34090f9cae92c051edf2edba73ac (diff) | |
download | gdb-b8d088acc8f9fe81d5ecbcbbecc694ac0091cb5e.zip gdb-b8d088acc8f9fe81d5ecbcbbecc694ac0091cb5e.tar.gz gdb-b8d088acc8f9fe81d5ecbcbbecc694ac0091cb5e.tar.bz2 |
Avoid switch to invalid ptid during Ada task switch.
This is to prevent an internal error during an Ada task switch. A task
switch is simply a thread switch under the hood. What we do is collect
the info from the Ada Task Control Block, deduce the associated thread
ptid, and then switch to that thread. If the thread ptid computation
routine has not been implemented for the target, of if there is a bug,
then we end up computing a bogus ptid which GDB does not know about,
which eventually leads to an assertion failure:
(gdb) task 1
[New Thread 5715]
/[...]/gdb/thread.c:595: internal-error: is_thread_state:
Assertion `tp' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n)
When this happens, it's just nicer for the user to print an error
message, and cancel the task switch. After this patch is applied,
this is what we get:
(gdb) task 1
[New Thread 10250]
Unable to compute thread ID for task 1.
Cannot switch to this task.
gdb/ChangeLog:
* ada-tasks.c (task_command_1): Check that the task ptid is valid
before doing the associated thread switch.
Diffstat (limited to 'gdb/valarith.c')
0 files changed, 0 insertions, 0 deletions