aboutsummaryrefslogtreecommitdiff
path: root/gdb/symfile.c
diff options
context:
space:
mode:
authorJoel Brobecker <brobecker@gnat.com>2010-04-27 21:01:57 +0000
committerJoel Brobecker <brobecker@gnat.com>2010-04-27 21:01:57 +0000
commitdde59185267c8f3df6c3aa19d132277f45143c79 (patch)
tree4222e02cf8c2240200826721695063a97ca4c040 /gdb/symfile.c
parentd09ce91e4f69a3cd451e35fc7a6476561c4d68c8 (diff)
downloadfsf-binutils-gdb-dde59185267c8f3df6c3aa19d132277f45143c79.zip
fsf-binutils-gdb-dde59185267c8f3df6c3aa19d132277f45143c79.tar.gz
fsf-binutils-gdb-dde59185267c8f3df6c3aa19d132277f45143c79.tar.bz2
Associate .dg files to Ada
The .dg files are files containing the user's code, after the GNAT expander was applied. The expansion replaces some of the complex features by simpler pseudo-Ada code and the user can ask to see and debug that code using the -gnatDG option... For instance, given the following code where Circle is a tagged type (aka as a class type in C++): procedure Foo is My_Shape : Circle := (X => 1, Y => 2, R => 3); X : Integer; begin X := Position_X (My_Shape); end Foo; The expansion results in: procedure foo is my_shape : pck__circle := ( _parent => ( _tag => pck__circleP, x => 1, y => 2), r => 3); x : integer; begin x := pck__position_x (my_shape); return; end foo; 2010-04-27 Joel Brobecker <brobecker@adacore.com> * symfile.c (init_filename_language_table): Register .dg files with language_ada.
Diffstat (limited to 'gdb/symfile.c')
-rw-r--r--gdb/symfile.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/gdb/symfile.c b/gdb/symfile.c
index 0528488..a02b2d2 100644
--- a/gdb/symfile.c
+++ b/gdb/symfile.c
@@ -2637,6 +2637,7 @@ init_filename_language_table (void)
add_filename_language (".ads", language_ada);
add_filename_language (".a", language_ada);
add_filename_language (".ada", language_ada);
+ add_filename_language (".dg", language_ada);
}
}