From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: "'Keith Seitz'" <keiths@redhat.com>
Cc: <insight@sourceware.org>
Subject: RE: cygwin runtime woes
Date: Wed, 06 May 2009 16:41:00 -0000 [thread overview]
Message-ID: <001801c9ce69$6a1ec860$3e5c5920$@u-strasbg.fr> (raw)
In-Reply-To: <4A01B691.7060909@redhat.com>
The -nx made a bigger difference!!!
I had a starting insight !
Thus I removed the gdbtk.ini file
and retried to start insight with gdb.exe
but I got no source window, and when I tried to
load gdb.exe manually after, I got this:
can't set "gdb_loaded": {hook=namespace inscope ::SrcWin {::.srcwin0.srcwin
_set_state} args="gdb_loaded" can't read "twin": no such variable
}
while executing
"set gdb_loaded 0"
(procedure "set_exe" line 24)
invoked from within
"set_exe"
(procedure "_open_file" line 63)
invoked from within
"_open_file"
(menu invoke)errorCode is NONE
> -----Message d'origine-----
> De : insight-owner@sourceware.org [mailto:insight-owner@sourceware.org]
> De la part de Keith Seitz
> Envoyé : Wednesday, May 06, 2009 6:11 PM
> À : Pierre Muller
> Cc : insight@sourceware.org
> Objet : Re: cygwin runtime woes
>
> Pierre Muller wrote:
> > I debugged the problem a bit:
> >
> > gdb_loc is call a few times
> > for 'main' 'MAIN___' 'MAIN__' 'cyg_user_start' 'cyg_start'
> > and then finally with '*' which causes the abort.
>
> That sounds normal. When insight starts up and gdb loads an executable,
> it will attempt to locate the entry point for the executable so that
> the
> source window can display it. These function names are actually from
> the
> preference gdb/main_names, defined in prefs.tcl.
>
> The '*' argument is odd. I don't know where that is coming from.
> Passing
> '*' to gdb_loc will cause gdb_loc to error, though.
>
> Out of curiosity, have you tried inhibiting preferences at startup?
> (insight -nx) Does it make any difference?
>
> > the first calls all fail with
> > "No symbol table loaded. Use "file" command"
> > even though I used ./gdb.exe as arg for run command.
>
> That sounds odd, too. Can you start vanilla gdb this way? I wonder what
> insight might be complaining about. Have you tried running insight in
> debug mode? To enable this, set GDBTK_DEBUG=1 in your environment
> before
> starting insight. It will write out the file "insight.log" (which you
> can change by setting GDBTK_DEBUGFILE).
>
> Keith
prev parent reply other threads:[~2009-05-06 16:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-06 22:32 [RFA] ARI fixes for gdbtk directories Pierre Muller
2009-04-06 22:51 ` Keith Seitz
2009-04-06 23:14 ` Pierre Muller
2009-04-06 23:18 ` cygwin runtime woes (was Re: [RFA] ARI fixes for gdbtk directories) Keith Seitz
2009-04-06 23:32 ` Pierre Muller
2009-04-06 23:52 ` Keith Seitz
2009-04-07 6:54 ` Pierre Muller
2009-05-06 16:11 ` cygwin runtime woes Keith Seitz
2009-05-06 16:24 ` Pierre Muller
2009-05-06 16:31 ` Keith Seitz
2009-05-06 20:45 ` Pierre Muller
2009-05-07 2:06 ` Keith Seitz
2009-05-06 16:41 ` Pierre Muller [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='001801c9ce69$6a1ec860$3e5c5920$@u-strasbg.fr' \
--to=muller@ics.u-strasbg.fr \
--cc=insight@sourceware.org \
--cc=keiths@redhat.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).