From: Keith Seitz <keiths@redhat.com>
To: Kip Warner <Kip@thevertigo.com>
Cc: "insight@sources.redhat.com" <insight@sources.redhat.com>
Subject: Re: Insight Bug?
Date: Sun, 10 Oct 2004 19:40:00 -0000 [thread overview]
Message-ID: <1097437511.3306.3.camel@lindt.uglyboxes.com> (raw)
In-Reply-To: <opsfn5rmzge8k94p@mail.thevertigo.com>
On Sun, 2004-10-10 at 12:29, Kip Warner wrote:
> > On Thu, 2004-10-07 at 21:08, Kip Warner wrote:
> >> >> (gdb) info func main
> >> >> All functions matching regular expression "main":
> >> >>Non-debugging symbols:
> >> >> 0x00401000 mainCRTStartup
> >> >>(gdb) list main
> >> >> Error: No line number known for main.
> >>
> >> Hey Keith,
> >>
> >> objdump gives me a ton of output when I pass it the -g switch and the
> >> path
> >> to my win32 executable. Any ideas? I think it may be a bug in Insights
> >> as
> >> I have heard of many others having this problem.
> >
> > Okay, I believe your problem is in gdb, but to be sure, I need to ask
> > another question. MinGW doesn't use a "main" function, so that was a
> > silly test. Can you list the contents of a function for which you know
> > you have debug info? Open a console and enter "list MYFUNC" or "info
> > func MYFUNC".
> >
> > Keith
> >
> >
>
> Hey Keith,
>
> I added...
>
> void foo(void)
> {
> puts("foo");
> return;
> }
>
> ...to my source and called it in WinMain to ensure that was compiled in
> there and invoked. I compile with -g3 and no optimizations or strips. I
> open Insight (--version gives: GNU gdb 2003-09-20-cvs (cygwin-special))
> and select function "foo." It gives only assembly listing still, even when
> I select "source" feature in listbox.
>
> I then opened the gdb console from the menu and performed the following:
>
> (gdb) list foo
> 9 in WinMain.cpp
>
> (gdb) info func foo
> All functions matching regular expression "foo":
>
> File WinMain.cpp:
> void foo();
>
> (gdb)
>
> I hope this is helping. There are many people having the same problem. You
> are a major help. The entire MinGW community that uses a GUI debugger
> depends on you =)
Okay, before I ask for a pre-compiled testcase, let me bark down a
hunch. First, let me ask if we've tried the whole debug window thing?
("tk ManagedWin::open DebugWin" in console window; then switch to
function by typing it into function combobox; any errors show up in
debug window?)
After that, try this: open a console window and type "maint print
psymbols OUTFILE". Look for the function "foo" in OUTFILE. What does it
say? Win32 paths, I'll bet?m
Keith
next prev parent reply other threads:[~2004-10-10 19:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <opsfi9s0h3e8k94p@mail.thevertigo.com>
2004-10-08 14:29 ` Keith Seitz
[not found] ` <opsfn5rmzge8k94p@mail.thevertigo.com>
2004-10-10 19:40 ` Keith Seitz [this message]
2004-10-03 3:12 Kip Warner
2004-10-03 3:43 ` Keith Seitz
-- strict thread matches above, loose matches on Subject: below --
2000-05-29 6:32 Paul_Heijman
2000-05-29 8:12 ` Fernando Nasser
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=1097437511.3306.3.camel@lindt.uglyboxes.com \
--to=keiths@redhat.com \
--cc=Kip@thevertigo.com \
--cc=insight@sources.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).