[Bug gdb/31152] New: Formalise unintened functionality in version 9.1

["chris_douglas_email at yahoo dot com" <sourceware-bugzilla@sourceware.org>]

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

            Bug ID: 31152
           Summary: Formalise unintened functionality in version 9.1
           Product: gdb
           Version: 14.1
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: chris_douglas_email at yahoo dot com
  Target Milestone: ---

Most of the time (approximately 95%) I use a gdb binary provided by the Linux
distribution I am using. The remainder of the time, I cross compile a source
release for an obscure processor, in order to debug on “bare metal”
(re-purposing old tech so all I have to start with is a Linux kernel and a
terminal of some kind).

The first time I did this I used release 9.1 and cross compiling a static
executable gave me what I needed. This time (after cross compiling glib etc) I
tried the same with version 14.1 and the box restarted indicating a kernel
error. I rebuilt 9.1 and started to debug 14.1 and found it was trying to exec
iconv. A quick hack and it compiled with the dummy iconv used for a win32 build
only to have a segment trap because the ifdef path for linux used a pointer set
up through the exec iconv path.

I have a workaround because I can use version 9.1 (possibly others, I have not
checked) until GCC adopts a version of dwarf this version does not understand,
so I believe this is low priority.

I wish to request an enhancement of a configuration option for “bare metal”
which errors at some point (even compile or link) if more than a linux kernel
is required to run the executable.

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