From: Keith Seitz <keiths@redhat.com>
To: Pierre Muller <muller@ics.u-strasbg.fr>
Cc: insight@sourceware.org
Subject: Re: cygwin runtime woes (was Re: [RFA] ARI fixes for gdbtk directories)
Date: Mon, 06 Apr 2009 23:52:00 -0000 [thread overview]
Message-ID: <49DA95C4.2070007@redhat.com> (raw)
In-Reply-To: <002d01c9b70f$db0cc750$912655f0$@u-strasbg.fr>
Pierre Muller wrote:
> I finally managed to get one:
> Can you do something with this??
This is kind of odd...
> (gdb) bt
> #0 error (string=0x62915c "Argument required (%s).")
> at ../../purecvs/gdb/utils.c:812
[snip]
> #8 0x0041318b in catch_errors (func=0x4a15b0 <wrapped_call>,
> func_args=0x22a5b0, errstring=0x653e13 "", mask=6)
> at ../../purecvs/gdb/exceptions.c:510
Frame 8, catch_errors, should have caught any the call to frame 0.
However, the question is, why is gdb_loc calling decode_line_1 with no
arguments?
My memory is a little fuzzy about this, but I fired up insight on my
linux box under gdb and set a breakpoint in gdb_loc. As I recall, this
happens at start-up to find "main", but for some reason, it appears that
the argument which should contain "main" instead contains an empty string.
Can you set a breakpoint in gdb_loc, run insight, and tell me what objc
is? It should be 2, and objv[0]->bytes should be "gdb_loc" and
objv[1]->bytes should be "main".
Is this not the case?
Keith
next prev parent reply other threads:[~2009-04-06 23:52 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 [this message]
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
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=49DA95C4.2070007@redhat.com \
--to=keiths@redhat.com \
--cc=insight@sourceware.org \
--cc=muller@ics.u-strasbg.fr \
/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).