From: James Ingham <jingham@cygnus.com>
To: Joseph Nicholas Yarbrough <pimpsmurf@sostech.net>
Cc: insight@sourceware.cygnus.com
Subject: Re: insight gdb all messed up...
Date: Fri, 03 Mar 2000 18:39:00 -0000 [thread overview]
Message-ID: <14528.30710.395028.178466@leda.cygnus.com> (raw)
In-Reply-To: <00030321330000.02405@pimpsmurf>
Joseph,
Sorry, there is not enough in your message to go on, so I can't help
that much... If you actually want help, you have to send a recipe that
I can follow that leads to bad behavior, and then describe the
behavior. Just saying it is broken is useless... You also have to
tell me what your host & targets are, etc...
> ok. first calling the main executable gdb is messed up..
Messed up how?
> I had to change all of
> my other debuggin scripts to add --nw... but I can get past that 1-1/2 minute
> tcl programming job. but opening a source file with the 20000204 version just
> doesn't work.
>
> (gdb) source main.c
> main.c:1: Error in sourced command file:
> Undefined command: "". Try "help".
What are you trying to do here? The gdb "source" command treats the
file you give it as a list of gdb commands:
(gdb) help source
Read commands from a file named FILE.
Note that the file ".gdbinit" is read automatically in this way
when gdb is started.
I doubt that main.c is a valid list of gdb commands... If it is, you
write mighty strange C code...
To see source code in gdb, use the "list" command.
>
> that is the error... to be precise. I love asm as much as the next guy, but
> being able to see the C code can be helpfull. seeing as I debug c code. ;]
> it seems to look for init.c as the code. I renamed main.c to init.c, and list
> worked. But, when I tried to set a breakpoint with break. it broke.
>
> any ideas on something I might be doing wrong?
>
> thanks for this nice looking (although currently unusable) debugger.
> I cant wait to get it running.
>
> PimpSmurf
> a.k.a. Joseph Nicholas Yarbrough
>
> also... thought about adding a button to rebuild packages with make?
>
This is handled from the CodeFusion IDE, so we don't add it to
Insight.
Jim
--
++==++==++==++==++==++==++==++==++==++==++==++==++==++==++==++==++==++==++
Jim Ingham jingham@cygnus.com
Cygnus Solutions, a Red Hat Company
prev parent reply other threads:[~2000-03-03 18:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-03 18:28 Joseph Nicholas Yarbrough
2000-03-03 18:38 ` Keith Seitz
2000-03-03 18:39 ` James Ingham [this message]
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=14528.30710.395028.178466@leda.cygnus.com \
--to=jingham@cygnus.com \
--cc=insight@sourceware.cygnus.com \
--cc=pimpsmurf@sostech.net \
/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).