Trouble getting gdb-gui to work

Trouble getting gdb-gui to work

[Paul_Heijman]

Hi,

first of all i was really impressed about your GDB Debugging System.
I am planning on implementing a new stub for a certain M68k-type
microcontroller, but before i'm going to do that I want the GUI of GDB to work.

I'm working with Windows NT and downloaded from the cygnus website the
following:
- insight-20000105
- cygwin-b20

The commandline-version of GDB works by the way.
After downloading the insight-20000105 archive, I extracted it to a directory
called c:\cygnus\insight-20000105 .
According to the readme file that is included, I entered the commands:

- sh configure (this seemed to work, allthough it takes a while)
- make (this seemed to work also, however several warnings came by).

Afterwards i tried to configure the gdb-directory seperately (as in the readme
file):

-[log
start]------------------------------------------------------------------------------------
bash-2.02$ sh configure
loading cache ./config.cache
checking for gcc... gcc
checking whether the C compiler (gcc  ) works... yes
checking whether the C compiler (gcc  ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking how to run the C preprocessor... gcc -E
checking for AIX... no
checking for POSIXized ISC... no
checking for gcc option to accept ANSI C... none needed
configure: error: can not run /cygnus/insight-20000105/gdb/../config.sub
-[log
end]------------------------------------------------------------------------------------

I noticed that GDB was not 'maked' succesfully (at least I think so):
When making just the /gdb/ directory , the following was reported by gcc:

-[log
start]------------------------------------------------------------------------------------
bash-2.02$ mAKE
gcc -c -g    -I. -I. -I./config -DHAVE_CONFIG_H -I./../include/opcode
-I./../readline/.. -I../bfd -I./../bfd  -I./../inc
lude -I../intl -I./../intl -I./tui -DGDBTK   win32-nat.c
win32-nat.c:43: imagehlp.h: No such file or directory
win32-nat.c:338: psapi.h: No such file or directory
mAKE: *** [win32-nat.o] Error 1
-[log
end]------------------------------------------------------------------------------------

The two missing header files where not anywhere to be found on my harddisk
(while the insight-20000105-directory consists of 7197 files in 286
directories).
When I deleted the 'include' statements regarding the missing headerfiles, it
only got worse (that wasn't the solution to my problem):

-[log
start]------------------------------------------------------------------------------------
bash-2.02$ mAKE
gcc -c -g    -I. -I. -I./config -DHAVE_CONFIG_H -I./../include/opcode
-I./../readline/.. -I../bfd -I./../bfd  -I./../inc
lude -I../intl -I./../intl -I./tui -DGDBTK   win32-nat.c
win32-nat.c:93: parse error before `STACKFRAME'
win32-nat.c:93: warning: no semicolon at end of struct or union
win32-nat.c:94: warning: data definition has no type or storage class
win32-nat.c:96: parse error before `thread_head'
win32-nat.c:96: warning: initialization makes integer from pointer without a
cast
win32-nat.c:96: warning: data definition has no type or storage class
win32-nat.c:106: parse error before `*'
win32-nat.c:106: warning: data definition has no type or storage class
win32-nat.c:195: parse error before `*'
win32-nat.c: In function `thread_rec':
win32-nat.c:198: `th' undeclared (first use in this function)
win32-nat.c:198: (Each undeclared identifier is reported only once
win32-nat.c:198: for each function it appears in.)
win32-nat.c: At top level:
win32-nat.c:220: parse error before `*'
win32-nat.c: In function `child_add_thread':
win32-nat.c:223: `th' undeclared (first use in this function)
win32-nat.c:228: parse error before `)'
win32-nat.c:232: request for member `next' in something not a structure or union
win32-nat.c:233: request for member `next' in something not a structure or union
win32-nat.c: In function `child_init_thread_list':
win32-nat.c:243: `th' undeclared (first use in this function)
win32-nat.c:249: `here' undeclared (first use in this function)
win32-nat.c: In function `child_delete_thread':
win32-nat.c:260: `th' undeclared (first use in this function)
win32-nat.c:273: `here' undeclared (first use in this function)
win32-nat.c: In function `do_child_fetch_inferior_registers':
win32-nat.c:290: request for member `context' in something not a structure or
union
win32-nat.c: In function `do_child_store_inferior_registers':
win32-nat.c:322: request for member `context' in something not a structure or
union
win32-nat.c: At top level:
win32-nat.c:342: parse error before `LPMODULEINFO'
win32-nat.c: In function `psapi_get_dll_name':
win32-nat.c:348: `MODULEINFO' undeclared (first use in this function)
win32-nat.c:348: parse error before `mi'
win32-nat.c:402: `mi' undeclared (first use in this function)
win32-nat.c: In function `handle_exception':
win32-nat.c:559: `th' undeclared (first use in this function)
win32-nat.c: In function `child_continue':
win32-nat.c:622: `th' undeclared (first use in this function)
win32-nat.c:623: parse error before `res'
win32-nat.c:627: `res' undeclared (first use in this function)
win32-nat.c: In function `child_create_inferior':
win32-nat.c:1026: `SYMOPT_DEFERRED_LOADS' undeclared (first use in this
function)
win32-nat.c: In function `child_kill_inferior':
win32-nat.c:1094: request for member `h' in something not a structure or union
win32-nat.c: In function `child_resume':
win32-nat.c:1102: `th' undeclared (first use in this function)
win32-nat.c: In function `win32_child_thread_alive':
win32-nat.c:1253: request for member `h' in something not a structure or union
win32-nat.c: In function `child_frame_chain':
win32-nat.c:1288: `STACKFRAME' undeclared (first use in this function)
win32-nat.c:1288: `sf' undeclared (first use in this function)
win32-nat.c:1288: parse error before `)'
win32-nat.c:1289: `IMAGE_FILE_MACHINE_I386' undeclared (first use in this
function)
win32-nat.c:1290: request for member `h' in something not a structure or union
win32-nat.c:1290: `SymFunctionTableAccess' undeclared (first use in this
function)
win32-nat.c: In function `child_frame_saved_pc':
win32-nat.c:1299: `STACKFRAME' undeclared (first use in this function)
win32-nat.c:1299: `sf' undeclared (first use in this function)
win32-nat.c:1299: parse error before `)'
win32-nat.c: In function `child_init_frame':
win32-nat.c:1306: `STACKFRAME' undeclared (first use in this function)
win32-nat.c:1306: `sf' undeclared (first use in this function)
win32-nat.c:1314: parse error before `)'
win32-nat.c:1318: `AddrModeFlat' undeclared (first use in this function)
win32-nat.c:1319: request for member `context' in something not a structure or
union
mAKE: *** [win32-nat.o] Error 1
---[log
end]----------------------------------------------------------------------------------

Furthermore, TCL/TK has been installed (and working). I just can't get any of
the GDB-TCL's to work.
I assume 'interface.tcl' should be the startup file for the GUI ?

Does anything sound familiar to you folks?
I sure hope you can help me, because I've been working on this for two days and
haven't gotten any further than this.


Wit kind regards,

Paul Heijmann
OMRON E.T.C.
The Netherlands

Trouble getting gdb-gui to work

[Elena Zannoni]

Paul_Heijman@eu.omron.com writes:
 > 
 > 
 > Hi,
 > 
 > first of all i was really impressed about your GDB Debugging System.
 > I am planning on implementing a new stub for a certain M68k-type
 > microcontroller, but before i'm going to do that I want the GUI of GDB to work.
 > 
 > I'm working with Windows NT and downloaded from the cygnus website the
 > following:
 > - insight-20000105
 > - cygwin-b20

Try to download a recent development snapshot of Cygwin from the
sourceware site. That should include the missing files.

 > bash-2.02$ mAKE
 > gcc -c -g    -I. -I. -I./config -DHAVE_CONFIG_H -I./../include/opcode
 > -I./../readline/.. -I../bfd -I./../bfd  -I./../inc
 > lude -I../intl -I./../intl -I./tui -DGDBTK   win32-nat.c
 > win32-nat.c:43: imagehlp.h: No such file or directory
 > win32-nat.c:338: psapi.h: No such file or directory
 > mAKE: *** [win32-nat.o] Error 1
 > -[log
 > end]------------------------------------------------------------------------------------
[...]
 > 
 > Furthermore, TCL/TK has been installed (and working). I just can't get any of
 > the GDB-TCL's to work.
 > I assume 'interface.tcl' should be the startup file for the GUI ?
 > 

Don't know about this one. Sorry.


 > Does anything sound familiar to you folks?
 > I sure hope you can help me, because I've been working on this for two days and
 > haven't gotten any further than this.
 > 
 > 
 > Wit kind regards,
 > 
 > Paul Heijmann
 > OMRON E.T.C.
 > The Netherlands
 > 
 > 
 > 

Elena Zannoni

Re: Trouble getting gdb-gui to work

[James Ingham]

Paul,

Elena's answer about the Cygwin is correct.

 > 
 > Furthermore, TCL/TK has been installed (and working). I just can't get any of
 > the GDB-TCL's to work.
 > I assume 'interface.tcl' should be the startup file for the GUI ?

Which Tcl/Tk are you referring to here?  Did you install one from
Scriptics?  Insight uses its own version of Tcl, which is installed as 
part of the whole Insight package.  You don't need to remove the
Scriptics version, they will happily coexist.  But trying to get gdb
to use the Scriptics version is unlikely to work.

Anyway, "main.tcl" is actually the startup file, but you can't use
that in a plain Tcl interpreter.  It uses a bunch of C implemented
commands that are in the gdb executable.  So you need to run gdb to
get Insight to work.

If you still can't get this to work, send me more details, and I will
try to figure out what is going wrong.

Jim

 > 
 > Does anything sound familiar to you folks?
 > I sure hope you can help me, because I've been working on this for two days and
 > haven't gotten any further than this.
 > 
 > 
 > Wit kind regards,
 > 
 > Paul Heijmann
 > OMRON E.T.C.
 > The Netherlands
 > 
 > 
 > 

-- 
++==++==++==++==++==++==++==++==++==++==++==++==++==++==++==++==++==++==++
Jim Ingham                                              jingham@redhat.com
Red Hat, Inc.                      

Problem with registers display for MPC860

[Dr. Leon Pollak]

Hello all,
	I am trying to use this great GUI for the cross debugging of my MPC860
embedded application from my Linux host. Most of the things look working and
this is great!!!
	The small problem I have is a s following:
After I set "set processor 860" in gdb console window, the "Registers" window
shows all registers that my MPC860 has and even more. But their values are
shifted for 2. Schematically this looks so:
SPR001 SPR002 SPR003 SPR004........
VAL003 VAL004 VAL005 VAL006...........
	Where SPR00X are the names of the registers and VAL00X are their
corresponding values.
	Still, when I read registers values via gdb console window (like p/x
$immr) I receive correct value and this value is generated from inside of gdb
(no packets are sent to my target).
	This leads me to the conclusion that the problem is in registers
presentation only, while all the rest of the environment works fine.
	Am I right?
	Thanks ahead.

Leon Pollak
leonp@plris.com