Re: [ECOS] MIPS TX-39 and Debug Information ---

Re: [ECOS] MIPS TX-39 and Debug Information ---

[Rosimildo daSilva]

>From: Jonathan Larmour <jlarmour@redhat.co.uk>
>To: Rosimildo daSilva <rosimildo@hotmail.com>
>CC: ecos-discuss@sourceware.cygnus.com
>Subject: Re: [ECOS] MIPS TX-39 and Debug Information ---
>Date: Fri, 07 Apr 2000 16:35:39 +0100
>
>Yeah, use -g ;-). Seriously, you could try -gdwarf-2. But this really
>*should* work without that. I've used it happily before with gcc 2.95.2!
>

Ok, I have tried -dwarf-2 and GCC did not compile the code
saying that it was not configured for it. I have no idea how
I got here. Yes, I was *messing around* with the GCC code
a few days before, trying to compile a mips-any-elf
toolset. That might be the case.

I decided to start from *scratch* again. Recompiled
eveything binutils, gcc, gdb. Hey, now everything
works fine.

Thanks for your help on this matter.

Rosimildo.





______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com

Re: [ECOS] MIPS TX-39 and Debug Information ---

[Rosimildo daSilva]

>From: Jonathan Larmour <jlarmour@redhat.co.uk>
>To: Rosimildo daSilva <rosimildo@hotmail.com>
>CC: ecos-discuss@sourceware.cygnus.com
>Subject: Re: [ECOS] MIPS TX-39 and Debug Information ---
>Date: Fri, 07 Apr 2000 16:25:47 +0100
>
>Rosimildo daSilva wrote:
> >
> > BTW, if I check the hello.o, I can see that the debug info it is
> > there. So, it seems to be something related with the link phase.
> > The '-g' flag is included with the flags passed to the linker.
>
>When you say the debug info is there, do you mean a .mdebug section, or are
>there also sections beginning ".debug"? The latter indicates DWARF
>debugging info, which is what is *meant* to be there.
>

It has a section ".mdebug".
I do not have access to the machine with the files right now, so i
can not attach it to the list. I did not see any ".debug" section. So my 
conclusion, from what you said, is that there is no deubg info at all.

One more thing, if I use:

'mips-tx39-objdump --sources hello.o

I can see the C source and its assembly code.

I'll repost a message later today with the information of the
sections in hello.o.

thanks, Rosimildo.








______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com

Re: [ECOS] MIPS TX-39 and Debug Information ---

[Jonathan Larmour]

Rosimildo daSilva wrote:
> How do I know which debugging information it is being used ?.
> I'd like to check if dwarf-2 it is being used.

Use mips-tx39-elf-objdump --section-headers and look for section names
starting with ".debug", e.g. .debug_line
 
> Is it possible to select it at compilation/configutation time of the
> toolset ?

Yeah, use -g ;-). Seriously, you could try -gdwarf-2. But this really
*should* work without that. I've used it happily before with gcc 2.95.2!

Jifl
-- 
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS  Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow."  ||  These opinions are all my own fault

Re: [ECOS] MIPS TX-39 and Debug Information ---

[Rosimildo daSilva]

>From: Jonathan Larmour <jlarmour@redhat.co.uk>
>To: Rosimildo daSilva <rosimildo@hotmail.com>
>CC: ecos-discuss@sourceware.cygnus.com
>Subject: Re: [ECOS] MIPS TX-39 and Debug Information ---
>Date: Fri, 07 Apr 2000 04:53:20 +0100
>
>Rosimildo daSilva wrote:
> >
> > Hi,
> >
> > I am trying to check the TX-39 toolset. I have built everything.
> > Compiled eCOS 1.3.1 and built the "hello" example. Now I am
> > trying to debug it, and GDB reports that there is no debug info.
> >
> > Using objdump, I see no .mdebug section, or something like that.
> > I can see by the size of hello.exe that there is no debug info
> > in it.
>[snip]
>
>The tx39 tools output dwarf-2 debugging information by default, not stabs
>(which would be when the mdebug section is used). There should be no
>.mdebug section - in fact we explicitly remove it for the tx39 because we
>found sometimes GDB got confused when both stabs and dwarf-2 debug
>information was in the same executable.
>

Jonathan,

How do I know which debugging information it is being used ?.
I'd like to check if dwarf-2 it is being used.

Is it possible to select it at compilation/configutation time of the
toolset ?

Thanks, Rosimildo.


______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com

Re: [ECOS] MIPS TX-39 and Debug Information ---

[Jonathan Larmour]

Rosimildo daSilva wrote:
> 
> BTW, if I check the hello.o, I can see that the debug info it is
> there. So, it seems to be something related with the link phase.
> The '-g' flag is included with the flags passed to the linker.

When you say the debug info is there, do you mean a .mdebug section, or are
there also sections beginning ".debug"? The latter indicates DWARF
debugging info, which is what is *meant* to be there.

Jifl
-- 
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS  Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow."  ||  These opinions are all my own fault

Re: [ECOS] MIPS TX-39 and Debug Information ---

[Rosimildo daSilva]

>From: Jonathan Larmour <jlarmour@redhat.co.uk>
>To: Rosimildo daSilva <rosimildo@hotmail.com>
>CC: ecos-discuss@sourceware.cygnus.com
>Subject: Re: [ECOS] MIPS TX-39 and Debug Information ---
>Date: Fri, 07 Apr 2000 04:53:20 +0100
>
>Rosimildo daSilva wrote:
> >
> > Hi,
> >
> > I am trying to check the TX-39 toolset. I have built everything.
> > Compiled eCOS 1.3.1 and built the "hello" example. Now I am
> > trying to debug it, and GDB reports that there is no debug info.
> >
> > Using objdump, I see no .mdebug section, or something like that.
> > I can see by the size of hello.exe that there is no debug info
> > in it.
>[snip]
>
>The tx39 tools output dwarf-2 debugging information by default, not stabs
>(which would be when the mdebug section is used). There should be no
>.mdebug section - in fact we explicitly remove it for the tx39 because we
>found sometimes GDB got confused when both stabs and dwarf-2 debug
>information was in the same executable.
>
>Which gcc and gdb versions are you using? And did you compile hello.exe
>(and your app) with -g and not -ggdb or -gstabs or anything? If you just
>used the makefile, then that would mean just -g.


I followed the instructions from the eCos documentation to
generate the toolset for TX39. I used GCC 2.95.2.

For gdb, I have used the tarball from ( 2000, Mar 13 ).
I have tried with GDB and Insight. Both fail. I am almost
cartain that it is the "flags" passed to the link. I just
cannot see what it is wrong. :-).

yes, I used the makefile for hello. I have tried -g, -ggdb. It did not work.

BTW, if I check the hello.o, I can see that the debug info it is
there. So, it seems to be something related with the link phase.
The '-g' flag is included with the flags passed to the linker.

I have tried this under Linux, and CygWin 20.1. Same results.

Thanks for your help.

Regards, Rosimildo.

















______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com

Re: [ECOS] MIPS TX-39 and Debug Information ---

[Jonathan Larmour]

Rosimildo daSilva wrote:
> 
> Hi,
> 
> I am trying to check the TX-39 toolset. I have built everything.
> Compiled eCOS 1.3.1 and built the "hello" example. Now I am
> trying to debug it, and GDB reports that there is no debug info.
> 
> Using objdump, I see no .mdebug section, or something like that.
> I can see by the size of hello.exe that there is no debug info
> in it.
[snip]

The tx39 tools output dwarf-2 debugging information by default, not stabs
(which would be when the mdebug section is used). There should be no
.mdebug section - in fact we explicitly remove it for the tx39 because we
found sometimes GDB got confused when both stabs and dwarf-2 debug
information was in the same executable.

Which gcc and gdb versions are you using? And did you compile hello.exe
(and your app) with -g and not -ggdb or -gstabs or anything? If you just
used the makefile, then that would mean just -g.

Jifl
-- 
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS  Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow."  ||  These opinions are all my own fault

[ECOS] MIPS TX-39 and Debug Information ---

[Rosimildo daSilva]

Hi,

I am trying to check the TX-39 toolset. I have built everything.
Compiled eCOS 1.3.1 and built the "hello" example. Now I am
trying to debug it, and GDB reports that there is no debug info.

Using objdump, I see no .mdebug section, or something like that.
I can see by the size of hello.exe that there is no debug info
in it.

is there any special setting to get GDB aware executables ?


--------------------------------------------------------------
hello.exe:     file format elf32-bigmips

Sections:
Idx Name          Size      VMA               LMA               File off  
Algn
  0 .rom_vectors  000000cc  ffffffff80000000  ffffffff80000000  00001000  
2**0
                  CONTENTS, ALLOC, LOAD, READONLY, CODE
  1 .text         00008294  ffffffff800000cc  ffffffff800000cc  000010cc  
2**2
                  CONTENTS, ALLOC, LOAD, READONLY, CODE
  2 .fini         00000000  ffffffff80008360  ffffffff80008360  0000a420  
2**0
                  CONTENTS
  3 .ctors        00000030  ffffffff80008360  ffffffff80008360  00009360  
2**2
                  CONTENTS, ALLOC, LOAD, DATA
  4 .dtors        00000020  ffffffff80008390  ffffffff80008390  00009390  
2**2
                  CONTENTS, ALLOC, LOAD, DATA
  5 .rodata       00000724  ffffffff800083b0  ffffffff800083b0  000093b0  
2**3
                  CONTENTS, ALLOC, LOAD, DATA
  6 .vsr_table    00000000  ffffffff80008ad4  ffffffff80008ad4  0000a420  
2**0
                  CONTENTS
  7 .rodata1      00000000  ffffffff80008ad4  ffffffff80008ad4  0000a420  
2**0
                  CONTENTS
  8 .fixup        00000000  ffffffff80008ad4  ffffffff80008ad4  0000a420  
2**0
                  CONTENTS
  9 .gcc_except_table 00000000  ffffffff80008ae0  ffffffff80008ae0  0000a420 
  2*
*0
                  CONTENTS
10 .data         00000940  ffffffff80008ae0  ffffffff80008ae0  00009ae0  
2**3
                  CONTENTS, ALLOC, LOAD, DATA
11 .bss          000038d0  ffffffff80009420  ffffffff80009420  0000a420  
2**4
                  ALLOC
bash-2.02$
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com