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]

gdb/381: Regression: src_and_asm_line line attribute "line" for file gdb.mi/basics.c changed from 31 to 0 in several places.



>Number:         381
>Category:       gdb
>Synopsis:       Regression: src_and_asm_line line attribute "line" for file gdb.mi/basics.c changed from 31 to 0 in several places.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Feb 23 23:38:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     mec@shout.net
>Release:        gdb HEAD%20020222
>Organization:
>Environment:
[target=native, host=i686-pc-linux-gnu%rh-7.2, gdb=HEAD%20020222, gcc=HEAD%20020222, glibc=vendor, goption=-gstabs+]
>Description:
This is a regression bug versus gdb=HEAD%20020216, gcc=HEAD%20020216.

This bug is likely to be related to pr gdb/380.

The mi interface returns "0" for a line number attribute in several places.  This causes failures in:

  gdb.mi/mi-disassemble.exp: data-disassemble file, line, number (zero lines) assembly mixed
  gdb.mi/mi0-disassemble.exp: data-disassemble file, line, number (zero lines) assembly mixed

This bug is sensitive to gcc version and goption.  It's possible that a change in gcc HEAD is responsible, but more likely that a change in gdb HEAD is responsible.
>How-To-Repeat:
download the versions indicated.
run gdb.mi/midisassemble.exp and gdb.mi/mi0-disassemble.exp.
look carefully at the outputs for all src_and_asm_line attribute "line".

>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]