public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: "Kirk Hagberg" <kirk.hagberg@qlogic.com>
To: <gdb@sources.redhat.com>
Subject: FW: fatal: libstdc++.so.6: open failed
Date: Thu, 13 Oct 2005 16:04:00 -0000	[thread overview]
Message-ID: <E19D2D286A3784409DD574031C30D727BDB1A2@EPEXCH01.qlogic.org> (raw)

I'm running:

GCC 3.4.3         (Solaris, compiled in 64-bit)
GDB 6.3            (Solaris, compiled in 64-bit)

I compile a simple C program:

#include <stdio.h>

int main(void)
{
        int a=77;
        printf("long size=%d, a=%d\n",sizeof(long),a);
        return 0;
}

In both 32-bit and 64-bit, with gcc and g++.  They execute fine on the command line.  Although when the g++ compiled files are run in GDB, I get the following message:

$ g++ -g -m32 longsize.c -olongsize32cpp
$ gdb longsize32cpp
GNU gdb 6.3
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "sparc-sun-solaris2.8"...
(gdb) r
Starting program: /tmp/longsize32cpp 
ld.so.1: /tmp/longsize32cpp: fatal: libstdc++.so.6: open failed: No such file or directory

Program terminated with signal SIGKILL, Killed.
The program no longer exists.

libstdc++.so.6 is in the LD_LIBRARY_PATH.


Any assistance would be great!  Thanks!


             reply	other threads:[~2005-10-13 16:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-13 16:04 Kirk Hagberg [this message]
2005-10-14 15:28 ` Daniel Jacobowitz

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=E19D2D286A3784409DD574031C30D727BDB1A2@EPEXCH01.qlogic.org \
    --to=kirk.hagberg@qlogic.com \
    --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).