public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: rob@encodia.biz
To: Daniel Jacobowitz <drow@false.org>
Cc: Dave Korn <dave.korn@artimi.com>,  gdb@sources.redhat.com
Subject: Re: C++, "too few arguments in function call" error?
Date: Fri, 17 Mar 2006 22:02:00 -0000	[thread overview]
Message-ID: <133C1A61-2351-4335-B9B7-F49D663C48F9@encodia.biz> (raw)
In-Reply-To: <20060317174315.GA16517@nevyn.them.org>


On Mar 17, 2006, at 12:43 PM, Daniel Jacobowitz wrote:
>
> That's pretty likely.  Rob, we probably can't help you with problems
> involving C++ and MacOS X; Apple's highly patched GDB uses stabs, not
> DWARF-2, and therefore represents debug information for methods very
> differently.

Ah... I was wondering about the Mac OS effect.  Thanks for the info.   
I'll try asking on an Apple mailing list, or maybe just move back to  
Linux for compiling and debugging.

Rob


  reply	other threads:[~2006-03-17 19:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-17  7:07 rob
2006-03-17 11:37 ` Dave Korn
2006-03-17 18:36   ` Daniel Jacobowitz
2006-03-17 22:02     ` rob [this message]
2006-03-17 19:06   ` rob
2006-03-18 10:18     ` Dave Korn

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=133C1A61-2351-4335-B9B7-F49D663C48F9@encodia.biz \
    --to=rob@encodia.biz \
    --cc=dave.korn@artimi.com \
    --cc=drow@false.org \
    --cc=gdb@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).