Modify

Opened 9 years ago

Closed 9 years ago

Last modified 4 years ago

#4701 closed task (fixed)

toolchain gdb 6.8 upgrade

Reported by: johnrw Owned by: developers
Priority: normal Milestone:
Component: toolchain Version:
Keywords: gdb Cc:

Description

Here is a patch to upgrade the toolchain's gdb to version 6.8.

The patch I include does not remove the patches from the previous version. Files in this patch are:

Makefile
patches/600-fix-compile-flag-mismatch.patch

I compiled this using uclibc 0.9.29 and gcc 4.1.2,
and uclibc 0.9.30 and gcc 4.3.3.

Attachments (7)

gdb_6.8.MakeFile.patch (2.0 KB) - added by johnrw 9 years ago.
gdb-6.8 update
gdb_6.8.Makefile-with-Insight.patch (4.8 KB) - added by johnrw 9 years ago.
Add gdb's frontend Insight to the buildroot
insight.sh (283 bytes) - added by johnrw 9 years ago.
bash script that I use to start Insight from the build (source) dir.
gdb_6.8-Makefile-with-Insight-a.patch (4.8 KB) - added by johnrw 9 years ago.
gdb_6.8-Makefile-with-Insight-a.2.patch (4.8 KB) - added by johnrw 9 years ago.
Changed from PKG_BUILD_DIR to HOST_BUILD_DIR in buildsystem
Insight.patch (2.7 KB) - added by johnrw 9 years ago.
Separate Insight patch... from trunk rev 14722
insight-02.patch (1.2 KB) - added by johnrw 9 years ago.

Download all attachments as: .zip

Change History (13)

Changed 9 years ago by johnrw

gdb-6.8 update

comment:1 Changed 9 years ago by johnrw

Adding the gdb gui Insight to the mix.
The second patch includes the first patch, so unless you just want gdb cmdline only... take the second patch. gdb_6.8.Makefile-with-Insight.patch

Changed 9 years ago by johnrw

Add gdb's frontend Insight to the buildroot

comment:2 Changed 9 years ago by johnrw

A few notes...
Since Insight needs tcl/tk, it is built with Insight in a subdirectory of Insight's top level directory.

To use the toolchain's Insight debugger... well here is how I did it.
A) cd to the toplevel Insight directory in build_dir.
cd ~/trunk/build_dir/toolchain-armeb_gcc-4.3.3_uClibc-0.9.30/insight-6.8/ 

B) from the top level Insight dir... exec it with the full path to the linux vmlinux file. 
./gdb/insight ~/trunk/build_dir/linux-ixp4xx_generic/linux-2.6.28.6/vmlinux

This was all I needed to do to confirm my build worked. It is not a final setup by any stretch of the imagination. But you can debug your board from there.

http://sourceware.org/insight/faq.php is a must read.

Some screenshots can be seen here.
http://sourceware.org/insight/screenshots.php

nbd, I did not get the m68k support patch... but it is available, so if you want that let me know.

knoppix@gw614ge:~/usr-p54/trunk/build_dir/toolchain-armeb_gcc-4.3.3_uClibc-0.9.30/insight-6.8$ gdb/insight --help
This is the GNU debugger.  Usage:

    gdb [options] [executable-file [core-file or process-id]]
    gdb [options] --args executable-file [inferior-arguments ...]

Options:

  --args             Arguments after executable-file are passed to inferior
  -b BAUDRATE        Set serial port baud rate used for remote debugging.
  --batch            Exit after processing options.
  --batch-silent     As for --batch, but suppress all gdb stdout output.
  --return-child-result
                     GDB exit code will be the child's exit code.
  --cd=DIR           Change current directory to DIR.
  --command=FILE, -x Execute GDB commands from FILE.
  --eval-command=COMMAND, -ex
                     Execute a single GDB command.
                     May be used multiple times and in conjunction
                     with --command.
  --core=COREFILE    Analyze the core dump COREFILE.
  --pid=PID          Attach to running process PID.
  --dbx              DBX compatibility mode.
  --directory=DIR    Search for source files in DIR.
  --epoch            Output information used by epoch emacs-GDB interface.
  --exec=EXECFILE    Use EXECFILE as the executable.
  --fullname         Output information used by emacs-GDB interface.
  --help             Print this message.
  --interpreter=INTERP
                     Select a specific interpreter / user interface
  -l TIMEOUT         Set timeout in seconds for remote debugging.
  --nw               Do not use a window interface.
  --nx               Do not read .gdbinit file.
  --quiet            Do not print version number on startup.
  --readnow          Fully read symbol files on first access.
  --se=FILE          Use FILE as symbol file and executable file.
  --symbols=SYMFILE  Read symbols from SYMFILE.
  --tty=TTY          Use TTY for input/output by the program being debugged.
  --tui              Use a terminal user interface.
  --version          Print version information and then exit.
  -w                 Use a window interface.
  --write            Set writing into executable and core files.
  --xdb              XDB compatibility mode.

For more information, type "help" from within GDB, or consult the
GDB manual (available as on-line info or a printed manual).
Report bugs to "bug-gdb@gnu.org".

comment:3 Changed 9 years ago by johnrw

So, I read the faq page... and gave environment vars a chance to try and set up a moved Insight root. It fails for me on Iwidgets. It seems that the Iwidgets component doesn't check the environment for locations.

So I decided to run it from the build dir which works nicely.
I'm attaching a script I use to invoke the Insight located in the build dir.

Enjoy.

Changed 9 years ago by johnrw

bash script that I use to start Insight from the build (source) dir.

Changed 9 years ago by johnrw

Changed 9 years ago by johnrw

Changed from PKG_BUILD_DIR to HOST_BUILD_DIR in buildsystem

Changed 9 years ago by johnrw

Separate Insight patch... from trunk rev 14722

comment:4 Changed 9 years ago by johnrw

Just put in a separate Insight.patch patch... to make it easier to merge, since the gdb was upgraded... yea!

Changed 9 years ago by johnrw

comment:5 Changed 9 years ago by johnrw

Ok... this 2nd patch is needed to complete the build.
I needed to add it to my local svn copy, before the last patch was generated.
My bad.

comment:6 Changed 9 years ago by florian

  • Resolution set to fixed
  • Status changed from new to closed

Applied in [17019], thanks !

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.