public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
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: Fri, 08 Oct 2004 14:29:00 -0000	[thread overview]
Message-ID: <1097246057.2765.4.camel@lindt.uglyboxes.com> (raw)
In-Reply-To: <opsfi9s0h3e8k94p@mail.thevertigo.com>

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

       reply	other threads:[~2004-10-08 14:29 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 [this message]
     [not found]   ` <opsfn5rmzge8k94p@mail.thevertigo.com>
2004-10-10 19:40     ` Keith Seitz
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=1097246057.2765.4.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).