This is the mail archive of the gdb-prs@sourceware.org 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]

[Bug tdep/19731] New: errant warnings regenerating target feature files


https://sourceware.org/bugzilla/show_bug.cgi?id=19731

            Bug ID: 19731
           Summary: errant warnings regenerating target feature files
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: tdep
          Assignee: unassigned at sourceware dot org
          Reporter: dje at google dot com
  Target Milestone: ---

@ruffy:gdb$ cd features
@ruffy:features$ make GDB=/build/main/all-targets/rel64/usr/bin/gdb
clean-cfiles cfiles

causes several warnings, e.g.,

/build/main/all-targets/rel64/usr/bin/gdb -nx -q -batch \
          -ex "set tdesc filename microblaze-with-stack-protect.xml" -ex 'maint
print c-tdesc' > microblaze-with-stack-protect.c.tmp
warning: Architecture rejected target-supplied description

The problem is that the xml file doesn't specify an architecture so gdb then
uses the default which is i386.

I'm not sure what the best solution is.
I think it's a clear bug to default to i386 for a microblaze xml file.
That suggests these xml files must specify an architecture.
At the least we should be printing a warning if the architecture isn't
specified to alert the user as to potential issues (like the fact that the
"rejected" warning is annoying, useless, and can cause someone to waste time
digging into why it's happening).

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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