Mirror of the gdb mailing list
 help / color / mirror / Atom feed
* Shared library call problems on PowerPC with gdb 7.2
@ 2013-04-15 14:21 Klaus Zeitler
  2013-04-15 14:39 ` Pedro Alves
  0 siblings, 1 reply; 4+ messages in thread
From: Klaus Zeitler @ 2013-04-15 14:21 UTC (permalink / raw)
  To: gdb

Hello,
I'm trying to debug a shared library on PowerPC (P3041).
Unfortunately it is nearly impossible to step through
functions in the shared library, cause neither "next" nor "step"
work as expected. e.g. I set a breakpoint at a function in the shared
lib and when I try now to step through the code (with "next" or "step")
I get:
"Single stepping until exit from function call___do_global_ctors_aux,
 which has no line number information."

I can return with "finish" to my function, but the same thing happens
for every "next" or "step".

I found a few reports about this problem from 2007 and 2008 (but it
seems as if they were solved long ago), e.g. from Ulrich Weigand:
http://sourceware.org/ml/gdb-patches/2008-04/msg00639.html

I'm using gdb 7.2, the exact version is:
GNU gdb (Wind River Linux Sourcery G++ 4.4a-341) 7.2.50.20100908-cvs
Maybe the gcc/binutils version is also relevant:
powerpc-wrs-linux-gnu-gcc (Wind River Linux Sourcery G++ 4.4a-341) 4.4.1

Thanks

Klaus

-- 
 -------------------------------------------------------------------
|  Klaus Zeitler              Alcatel-Lucent                        |
|  Lorenzstrasse 10           70435 Stuttgart, Germany              |
|  Department:                Building: 005  Office: 3/171          |
|  Telefon:                   +49 711821 43898                      |
|  Email:                     klaus.zeitler@alcatel-lucent.com      |
|                                                                   |
| Alcatel-Lucent Deutschland AG                                     |
| Sitz der Gesellschaft: Stuttgart · Amtsgericht Stuttgart HRB 4026 |
| Vorsitzender des Aufsichtsrates: Michael Oppenhoff                |
| Vorstand:                                                         |
|   Alf Henryk Wulf (Vorsitzender) · Dr. Rainer Fechner             |
 -------------------------------------------------------------------
---
Nothing is like it seems, but everything is exactly like it is. -- Yogi Berra


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Shared library call problems on PowerPC with gdb 7.2
  2013-04-15 14:21 Shared library call problems on PowerPC with gdb 7.2 Klaus Zeitler
@ 2013-04-15 14:39 ` Pedro Alves
  2013-04-17  7:55   ` Klaus Zeitler
  0 siblings, 1 reply; 4+ messages in thread
From: Pedro Alves @ 2013-04-15 14:39 UTC (permalink / raw)
  To: Klaus.Zeitler; +Cc: gdb

On 04/15/2013 03:20 PM, Klaus Zeitler wrote:

> I'm using gdb 7.2, the exact version is:
> GNU gdb (Wind River Linux Sourcery G++ 4.4a-341) 7.2.50.20100908-cvs
> Maybe the gcc/binutils version is also relevant:
> powerpc-wrs-linux-gnu-gcc (Wind River Linux Sourcery G++ 4.4a-341) 4.4.1

You should request support from Wind River.  You could also
try a current/recent pristine FSF/GNU GDB.  We're about to release 7.6.

-- 
Pedro Alves


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Shared library call problems on PowerPC with gdb 7.2
  2013-04-15 14:39 ` Pedro Alves
@ 2013-04-17  7:55   ` Klaus Zeitler
  2013-04-17  9:48     ` Pedro Alves
  0 siblings, 1 reply; 4+ messages in thread
From: Klaus Zeitler @ 2013-04-17  7:55 UTC (permalink / raw)
  To: Pedro Alves; +Cc: gdb

>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
    Pedro> 
    Pedro> On 04/15/2013 03:20 PM, Klaus Zeitler wrote:
    >> I'm using gdb 7.2, the exact version is:
    >> GNU gdb (Wind River Linux Sourcery G++ 4.4a-341) 7.2.50.20100908-cvs
    >> Maybe the gcc/binutils version is also relevant:
    >> powerpc-wrs-linux-gnu-gcc (Wind River Linux Sourcery G++ 4.4a-341) 4.4.1
    Pedro> 
    Pedro> You should request support from Wind River.

Did that November last year. I've exchanged many emails with Windriver,
but so far we haven't made any progress. That's why I thought that maybe
asking the real gdb experts here could help. Because from the info I
gathered in the internet, I thought this problem was already solved with
a patch for 6.8.
So of course the question remains, if and when (i.e. which version)
the patch went upstream into the sources.
And I also hoped that maybe there's some workaround for the version 7.2
we are using.

    Pedro> You could also try a current/recent pristine FSF/GNU GDB.
    Pedro> We're about to release 7.6.

Ok, I'll give 7.5.1 a try in the next days.

Thanks

Klaus

-- 
 -------------------------------------------------------------------
|  Klaus Zeitler              Alcatel-Lucent                        |
|  Lorenzstrasse 10           70435 Stuttgart, Germany              |
|  Department:                Building: 005  Office: 3/171          |
|  Telefon:                   +49 711821 43898                      |
|  Email:                     klaus.zeitler@alcatel-lucent.com      |
|                                                                   |
| Alcatel-Lucent Deutschland AG                                     |
| Sitz der Gesellschaft: Stuttgart · Amtsgericht Stuttgart HRB 4026 |
| Vorsitzender des Aufsichtsrates: Michael Oppenhoff                |
| Vorstand:                                                         |
|   Alf Henryk Wulf (Vorsitzender) · Dr. Rainer Fechner             |
 -------------------------------------------------------------------
---
There are two ways to write error-free programs.  Only the third one works.


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Shared library call problems on PowerPC with gdb 7.2
  2013-04-17  7:55   ` Klaus Zeitler
@ 2013-04-17  9:48     ` Pedro Alves
  0 siblings, 0 replies; 4+ messages in thread
From: Pedro Alves @ 2013-04-17  9:48 UTC (permalink / raw)
  To: Klaus.Zeitler; +Cc: gdb

On 04/17/2013 08:54 AM, Klaus Zeitler wrote:
>>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
>     Pedro> 
>     Pedro> On 04/15/2013 03:20 PM, Klaus Zeitler wrote:
>     >> I'm using gdb 7.2, the exact version is:
>     >> GNU gdb (Wind River Linux Sourcery G++ 4.4a-341) 7.2.50.20100908-cvs
>     >> Maybe the gcc/binutils version is also relevant:
>     >> powerpc-wrs-linux-gnu-gcc (Wind River Linux Sourcery G++ 4.4a-341) 4.4.1
>     Pedro> 
>     Pedro> You should request support from Wind River.
> 
> Did that November last year. I've exchanged many emails with Windriver,
> but so far we haven't made any progress. That's why I thought that maybe
> asking the real gdb experts here could help. Because from the info I
> gathered in the internet, I thought this problem was already solved with
> a patch for 6.8.
> So of course the question remains, if and when (i.e. which version)
> the patch went upstream into the sources.
> And I also hoped that maybe there's some workaround for the version 7.2
> we are using.

Maybe you'll find someone here willing to volunteer to do that work
for you, but I wouldn't hold my breath.  The info should be retrievable
from the mailing list archives, from the ChangeLog files in the source
tree, and from CVS/git history.

>     Pedro> You could also try a current/recent pristine FSF/GNU GDB.
>     Pedro> We're about to release 7.6.
> 
> Ok, I'll give 7.5.1 a try in the next days.

Try mainline and 7.6 too.  The later is in the
gdb_7_6-branch branch at git://sourceware.org/git/gdb.git .
The former is "master".  Lots of changes between 7.5 and 7.6.
Even if you don't want to use those versions, they could hold
a fix already, and you could then backport instead of wasting
time fixing it again.

-- 
Pedro Alves


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2013-04-17  9:48 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-04-15 14:21 Shared library call problems on PowerPC with gdb 7.2 Klaus Zeitler
2013-04-15 14:39 ` Pedro Alves
2013-04-17  7:55   ` Klaus Zeitler
2013-04-17  9:48     ` Pedro Alves

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox