Hi,
I am encountering problems with debugging a multi threaded
application:
when I try to do

gdb applnName

I get the following error:
DW_FORM_strp pointing outside of .debug_str section

it is able to read around 4 shared object files, but not able to
read 5th one. It is throwing up the above error.

I have gone through various mailing lists but still unable to
get a clue about the problem.


OS: Red Hat Linux 9
gcc: gcc-3.2.2-2
gdb: GNU gdb 6.0
binutils binutils-2.14.90.0.6-4

Please Help!!
thanks in advance,
mallikarjuna

[ Post a follow-up to this message ]

mallik1@rediffmail.com (mallik) writes:
quote:

>  I am encountering problems with debugging a multi threaded
> application: when I try to do
>
> gdb applnName
>
> I get the following error:
> DW_FORM_strp pointing outside of .debug_str section


Mutithreading probably has nothing to do with the problem.
It is either a bug in gdb, in gcc, or in binutils.
quote:

> it is able to read around 4 shared object files, but not able to
> read 5th one. It is throwing up the above error.


First try to 'readelf -w 5th.so > /dev/null' (it should print some
warning or error similar to the gdb one).

Then you can try to reduce the amount of code linked into 5th.so
until the error is no longer reported. After you know what code
produces the "bad debug info", you could submit a proper bug report
to gcc maintainers (see "info gcc" Bugs).

Cheers,
--
In order to understand recursion you must first understand recursion.
Remove /-nsp/ for email.

[ Post a follow-up to this message ]

Hi,
I have made progress regarding this issue.
Our application consists of assembly code which if included
would result in following error.
DW_FORM_strp pointing outside of .debug_str section.

When I replace the assembly code with c++ code, I am able to read
all the .so files from gdb.

I have tried   'readelf -w 5th.so > /dev/null' I did not get
warnings of any sort ( with the assembly code put in!!).
thanks,
mallikarjuna
Paul Pluzhnikov <ppluzhnikov-nsp@charter.net> wrote in message news:<m3oeu2rml7.fsf@salmon.parasof
t.com>...
quote:

> mallik1@rediffmail.com (mallik) writes:
>
> Mutithreading probably has nothing to do with the problem.
> It is either a bug in gdb, in gcc, or in binutils.

quote:
 
[QUOTE]
> First try to 'readelf -w 5th.so > /dev/null' (it should print some
> warning or error similar to the gdb one).

[ Post a follow-up to this message ]

mallik1@rediffmail.com (mallik) writes:
quote:

>   Our application consists of assembly code which if included
> would result in following error.
>   DW_FORM_strp pointing outside of .debug_str section.
>
>   When I replace the assembly code with c++ code, I am able to read
> all the .so files from gdb.


Sounds like the assembly code has invalid debug directives. This
could easily be the result of compiling some C++ code with
'g++ -g -S ...', then hand-tuning the resulting assembly without
corresponding changes to the debug directives in it.

If that is the history of your assembly source, remove the debug
directives from it (code that follows ".section debug_str",
".section debug_pubnames", etc).

Cheers,
--
In order to understand recursion you must first understand recursion.
Remove /-nsp/ for email.

[ Post a follow-up to this message ]