This is the mail archive of the
insight@sources.redhat.com
mailing list for the Insight project.
Re: Insight Bug?
- From: Keith Seitz <keiths at redhat dot com>
- To: Kip Warner <Kip at thevertigo dot com>
- Cc: "insight at sources dot redhat dot com" <insight at sources dot redhat dot com>
- Date: Sun, 10 Oct 2004 12:45:12 -0700
- Subject: Re: Insight Bug?
- References: <opsfi9s0h3e8k94p@mail.thevertigo.com> <1097246057.2765.4.camel@lindt.uglyboxes.com> <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