Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Frédéric RISS" <frederic.riss@st.com>
To: gdb@sources.redhat.com
Subject: Re: Problems with gdb on Solaris 8
Date: Fri, 11 Apr 2003 07:00:00 -0000	[thread overview]
Message-ID: <1050044432.1761.7.camel@crx1085> (raw)
In-Reply-To: <3E965161.955869C7@redhat.com>

Hi,

On Fri, 2003-04-11 at 07:23, msnyder@redhat.com wrote:
> David Frager wrote:
> > 
> > I have been experiencing problems with debugging programs on Solaris 8.
> > 
> > The programs are compiled using g++ 3.2, and I am attempting to debug running gdb 5.3
> > Both my modules and the ACE library used by my modules are compiled with optimzation turned off and debug turned on.  Additionally, the module is not striped.
> 
> David, was the module built as a 64-bit app, or 32?
> And likewise, how was gdb  built?
> 
> On Solaris, gdb can only debug 64-bit apps if it is itself one.
> 
> > 
> > I have attempted to set other breakpoints, but I get the same results.
> > 

I'm having some problems with gdb 5.2.1 on Solaris when I compile my
applications with gcc 3.2. The symptoms are not the same as David's
ones, but I think this may be related. Here's a more precise situation :

gcc 3.2 with -g option => I can debug with gdb 5.0 without problem, but
                          gdb5.2 is unusable (breakpoints put at the
                          wrong place for the most)

gcc 3.2 with -gdwarf-2 => I can debug with gdb 5.2 !

Unfortunately, I depend on libs which are compiled with -g, so I'm stuck
debugging with gdb 5.0... Is this a known issue ? Is there any solution
?

PS : We build only 32-bits libs/binaries and our GDBs are 32bits too.

Regards,

-- 
Frédéric RISS <frederic.riss@st.com>
STMicroelectronics - DAIS


  parent reply	other threads:[~2003-04-11  7:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-04  2:29 David Frager
2003-04-11  5:23 ` Michael Snyder
2003-04-11  6:20   ` David Frager
2003-04-11  7:00   ` Frédéric RISS [this message]
2003-04-12 19:47     ` Michael Snyder
2003-04-15  6:20       ` Frédéric RISS

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=1050044432.1761.7.camel@crx1085 \
    --to=frederic.riss@st.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