* Problems with gdb on Solaris 8
@ 2003-04-04 2:29 David Frager
2003-04-11 5:23 ` Michael Snyder
0 siblings, 1 reply; 6+ messages in thread
From: David Frager @ 2003-04-04 2:29 UTC (permalink / raw)
To: gdb
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.
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.
--
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: Problems with gdb on Solaris 8
2003-04-04 2:29 Problems with gdb on Solaris 8 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
0 siblings, 2 replies; 6+ messages in thread
From: Michael Snyder @ 2003-04-11 5:23 UTC (permalink / raw)
To: David Frager; +Cc: gdb
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.
>
> --
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: Problems with gdb on Solaris 8
2003-04-11 5:23 ` Michael Snyder
@ 2003-04-11 6:20 ` David Frager
2003-04-11 7:00 ` Frédéric RISS
1 sibling, 0 replies; 6+ messages in thread
From: David Frager @ 2003-04-11 6:20 UTC (permalink / raw)
To: Michael Snyder; +Cc: gdb
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.
> >
> > --
--
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: Problems with gdb on Solaris 8
2003-04-11 5:23 ` Michael Snyder
2003-04-11 6:20 ` David Frager
@ 2003-04-11 7:00 ` Frédéric RISS
2003-04-12 19:47 ` Michael Snyder
1 sibling, 1 reply; 6+ messages in thread
From: Frédéric RISS @ 2003-04-11 7:00 UTC (permalink / raw)
To: gdb
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
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: Problems with gdb on Solaris 8
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
0 siblings, 1 reply; 6+ messages in thread
From: Michael Snyder @ 2003-04-12 19:47 UTC (permalink / raw)
To: Frédéric RISS; +Cc: gdb
Frédéric RISS wrote:
>
> 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
It's not familiar to me, but sounds like a STABS problem.
I'm not really up on my recent version history.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Problems with gdb on Solaris 8
2003-04-12 19:47 ` Michael Snyder
@ 2003-04-15 6:20 ` Frédéric RISS
0 siblings, 0 replies; 6+ messages in thread
From: Frédéric RISS @ 2003-04-15 6:20 UTC (permalink / raw)
To: gdb
On Sat, 2003-04-12 at 21:47, msnyder@redhat.com wrote:
> > 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
>
> It's not familiar to me, but sounds like a STABS problem.
> I'm not really up on my recent version history.
Is nobody else aware of this _very_ annoying issue ? It seems it's
really a GDB problem as gdb 5.0 copes well with the generated binaries,
our should this be reported to GCC ?
Regards,
--
Frédéric RISS <frederic.riss@st.com>
STMicroelectronics - DAIS
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2003-04-15 6:20 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-04-04 2:29 Problems with gdb on Solaris 8 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
2003-04-12 19:47 ` Michael Snyder
2003-04-15 6:20 ` Frédéric RISS
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox