public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Paul_Heijman@eu.omron.com
To: insight@sourceware.cygnus.com
Subject: Trouble getting gdb-gui to work
Date: Wed, 02 Feb 2000 08:16:00 -0000	[thread overview]
Message-ID: <41256879.00590C61.00@eu.omron.com> (raw)

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


             reply	other threads:[~2000-02-02  8:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-02  8:16 Paul_Heijman [this message]
2000-02-02  8:24 ` Elena Zannoni
2000-02-02  9:36 ` James Ingham
2000-02-02 10:07   ` Problem with registers display for MPC860 Dr. Leon Pollak

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=41256879.00590C61.00@eu.omron.com \
    --to=paul_heijman@eu.omron.com \
    --cc=insight@sourceware.cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).