Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Wu Zhou <woodzltc@cn.ibm.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Ivan Popivanov <popivan@gmx.net>, gdb@sources.redhat.com
Subject: Re: AIX support
Date: Mon, 23 May 2005 06:22:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.63.0505230703430.22761@plinuxt18.cn.ibm.com> (raw)
In-Reply-To: <20050523055427.GT12565@adacore.com>


ok. I didn't know that the executable file formats on AIX is COFF.  In 
fact I don't have any experiecne coding on AIX.  But I do have some 
experience with xlC compiler on linux.  That is ppc64 arch however.  
GDB will drop into segmentation fault if there are any virtual classes or 
functions in the debugged code. The reason is that xl c++ compiler will
generate a virtual function table for each virtual classes, and so it 
doesn't depends on DW_AT_containing_type like g++ does.     

I don't know what kind of debuginfo XLC will generate on AIX.  If it is 
other than DWARF, or your code don't use any virutal feature of c++, I 
think GDB will work well with xlc compiler on AIX.  

Cheers
- Wu Zhou

On Mon, 23 May 2005, Joel Brobecker wrote:

> > Aren't the executable file formats different on AIX and Linux? Does GDB 
> > support both?
> 
> Yes, the executable formats are different. One is COFF based, and the
> other is ELF. GDB supports both. (I assume by linux you mean ppc-linux)
> 
> -- 
> Joel
> 
> 


  reply	other threads:[~2005-05-23  6:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-21 21:09 Ivan Popivanov
2005-05-23  0:00 ` Joel Brobecker
2005-05-23  1:26   ` Wu Zhou
2005-05-23  2:19     ` Wu Zhou
2005-05-23  5:32       ` Ivan Popivanov
2005-05-23  5:54         ` Joel Brobecker
2005-05-23  6:22           ` Wu Zhou [this message]
2005-05-23 15:51 ` Manoj Iyer

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=Pine.LNX.4.63.0505230703430.22761@plinuxt18.cn.ibm.com \
    --to=woodzltc@cn.ibm.com \
    --cc=brobecker@adacore.com \
    --cc=gdb@sources.redhat.com \
    --cc=popivan@gmx.net \
    /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