This is the mail archive of the gdb-prs@sources.redhat.com 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]

pending/1128: [RFC/DWARF2] Fallback unknown language to C?


>Number:         1128
>Category:       pending
>Synopsis:       [RFC/DWARF2] Fallback unknown language to C?
>Confidential:   yes
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          change-request
>Submitter-Id:   unknown
>Arrival-Date:   Fri Mar 07 17:18:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     
>Release:        
>Organization:
>Environment:
>Description:
 This is a followup on a concern reported by Stephane Carrez on the
 GDB mailing list:
 
     http://sources.redhat.com/ml/gdb/2003-02/msg00533.html
 
 > In the past, a gdb without Ada support could be used to, at least, see the
 > source.  However, we are now in this sad situation where this is no longer
 > possible because now gdb complains at unknown languages and... stops.
 
 I think we shouldn't fail like this because we have some symbols for an
 unsupported language. Could we for instance fallback to C for unknown
 language symbols.
 
 I looked at set_cu_language in dwarf2read.c. What would be the
 consequences of setting cu_language to language_c in these cases:
 
     case DW_LANG_Ada83:
     case DW_LANG_Ada95:
     case DW_LANG_Cobol74:
     case DW_LANG_Cobol85:
     case DW_LANG_Pascal83:
     case DW_LANG_Modula2:
     default:
       cu_language = language_unknown;
       break;
 
 -- 
 Joel
 
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]