From: David Frager <dbfrager@attbi.com>
To: Michael Snyder <msnyder@redhat.com>
Cc: gdb <gdb@sources.redhat.com>
Subject: Re: Problems with gdb on Solaris 8
Date: Fri, 11 Apr 2003 06:20:00 -0000 [thread overview]
Message-ID: <20030411011740.4fbfe824.dbfrager@attbi.com> (raw)
In-Reply-To: <3E965161.955869C7@redhat.com>
Thanks for the response..I will verify this
On Thu, 10 Apr 2003 22:23:45 -0700
Michael Snyder <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.
> >
> > # gdb ./MIBtest
> > GNU gdb 5.3
> > Copyright 2002 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) l 'ACE_SV_Semaphore_Complex::ACE_SV_Semaphore_Complex(int, int, int, unsigned short, int)'
> > 211 ACE_SV_Semaphore_Complex::ACE_SV_Semaphore_Complex (key_t k,
> > 212 int flags,
> > 213 int initial_value,
> > 214 u_short nsems,
> > 215 int perms)
> > 216 {
> > 217 ACE_TRACE ("ACE_SV_Semaphore_Complex::ACE_SV_Semaphore_Complex");
> > 218 if (this->open (k, flags, initial_value, nsems, perms) == -1)
> > 219 ACE_ERROR ((LM_ERROR, ACE_LIB_TEXT ("%p\n"), ACE_LIB_TEXT ("ACE_SV_Semaphore_Complex"))
> > );
> > 220 }
> > (gdb) b 218
> > Breakpoint 1 at 0x133854: file SV_Semaphore_Complex.cpp, line 218.
> > (gdb) run
> > Starting program: /dfrager/MIBtest
> > Warning:
> > Cannot insert breakpoint 1.
> > Error accessing memory address 0x133854: I/O error.
> > The same program may be running in another process.
> >
> > --
--
next prev parent reply other threads:[~2003-04-11 6:20 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 [this message]
2003-04-11 7:00 ` Frédéric RISS
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=20030411011740.4fbfe824.dbfrager@attbi.com \
--to=dbfrager@attbi.com \
--cc=gdb@sources.redhat.com \
--cc=msnyder@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