Are you using the latest release, GDB 5.2? If not, please try that
out.
If the problem still occurs there, you'll need to give us a specific
example of what's going wrong. That is:
- a complete test program that we can build and try to debug ourselves,
- a transcript showing the GDB behavior you're seeing, and
- an (brief) explanation of why the behavior is wrong, if it's not
obvious.
"Stu Rae" <[EMAIL PROTECTED]> writes:
> I am unable to debug a shared object file using GDB on a Solaris machine
> using
> gcc-2.95.2 and the default Solaris 'ld' utility ( Solaris-ELF 4.0) as well
> as GDB 5.0.
>
> I have two shared object files; one is 'C', the other is 'C++' (with extern
> 'C')
>
> I am able to see into the 'C' .so file, but I am not able to see into the
> 'C++' .so file.
>
> I compile both with the '-g' debug option. I load both with the '-Wl,-G'
> load options.
> The 'C' code works. The 'C++' does not.
>
> Can someone please give me some insight into this problem. I am will to try
> most
> anything to get this resolved, I just don't know enough to figure out what
> to do next.
>
> - Thanx Stu
>
>
>
>
> ___
> Bug-gdb mailing list
> [EMAIL PROTECTED]
> http://mail.gnu.org/mailman/listinfo/bug-gdb
___
Bug-gdb mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-gdb
