RE: crossgcc debug with HP emulator

RE: crossgcc debug with HP emulator

[Jepsen Hans Peter]

[-- Attachment #1: Type: text/plain, Size: 437 bytes --]

Hi again

> Looks like this may work for me.  I will give it a try and 
> let you know.
> 
> Which leads me to the next question - how does one install a 
> patch (ok, yes
> I am a newbie....)?

Here is how:
- cd to directory where you untared gcc
- gunzip toplev.c.patch.gz
- patch -p0 < toplev.c.patch

Then you run make again.

The patch I sent last was for egcs-1.1b. 
The attached one is for gcc-2.95.2.

Kind regards

Hans Peter



[-- Attachment #2: toplev.c.patch.gz --]
[-- Type: application/x-gzip, Size: 852 bytes --]

RE: crossgcc debug with HP emulator

[Jepsen Hans Peter]

[-- Attachment #1: Type: text/plain, Size: 437 bytes --]

Hi again

> Looks like this may work for me.  I will give it a try and 
> let you know.
> 
> Which leads me to the next question - how does one install a 
> patch (ok, yes
> I am a newbie....)?

Here is how:
- cd to directory where you untared gcc
- gunzip toplev.c.patch.gz
- patch -p0 < toplev.c.patch

Then you run make again.

The patch I sent last was for egcs-1.1b. 
The attached one is for gcc-2.95.2.

Kind regards

Hans Peter



[-- Attachment #2: toplev.c.patch.gz --]
[-- Type: application/x-gzip, Size: 852 bytes --]

RE: crossgcc debug with HP emulator

[Jepsen Hans Peter]

[-- Attachment #1: Type: text/plain, Size: 2697 bytes --]

Hi 

Steve deRosier wrote:

> I am having problems creating code with my crossgcc that 
> works properly with the HP emulator that we are using.  
...

> Is there a flag that I am missing or another
> permutation of the -g flag that will allow me to display the 
> C/C++ source in my debugger? 

We had the same problem. I ended up in modifying gcc as shown in the
attached small patch.

The effect is to add an option: -fkeep-file-path
that, when applied, does not strip the path from the supplied filename.

For us it works with HP emulator and Lauterbach hostdriver.

Kind regards

Hans Peter

   --
Hans Peter Jepsen          Phone: +45 74 88 50 11
Danfoss Drives A/S,        Fax:   +45 74 65 28 38
DG-133, Ulsnaes 1,         Email: Hans_Peter_Jepsen@danfoss.com
DK-6300 Graasten, Denmark  or:    hpj@computer.org



*** egcs-1.1b/gcc/toplev.c.orig	Sun May  2 20:47:14 1999
--- egcs-1.1b/gcc/toplev.c	Mon Jun 21 09:06:40 1999
***************
*** 721,726 ****
--- 721,731 ----
     if alias analysis (in general) is enabled.  */
  int flag_strict_aliasing = 0;
  
+ /* -fkeep-file-path causes the file directive in the outputfile to be the
name
+    given on the commandline, ie a possible directory path is not removed.
+    Normal/default behavior is to strip the path */
+ int keep_file_path = 0;
+ 
  extern int flag_dump_unnumbered;
  
  
***************
*** 908,913 ****
--- 913,920 ----
     "Generate code to check every memory access" },
    {"prefix-function-name", &flag_prefix_function_name, 1,
     "Add a prefix to all function names" },
+   {"keep-file-path", &keep_file_path,1,
+    "Do not strip path in .file directive"},
    {"dump-unnumbered", &flag_dump_unnumbered, 1}
  };
  
***************
*** 2371,2386 ****
       FILE *asm_file;
       char *input_name;
  {
!   int len = strlen (input_name);
!   char *na = input_name + len;
  
!   /* NA gets INPUT_NAME sans directory names.  */
!   while (na > input_name)
!     {
!       if (na[-1] == '/')
! 	break;
!       na--;
!     }
  
  #ifdef ASM_OUTPUT_MAIN_SOURCE_FILENAME
    ASM_OUTPUT_MAIN_SOURCE_FILENAME (asm_file, na);
--- 2378,2400 ----
       FILE *asm_file;
       char *input_name;
  {
!    char *na;
!    
!    if ( keep_file_path) /* leave the input_name unchanged */
!       na = input_name;
!    else /* strip leadin path from input_name - default behaviour */
!    {      
!       int len = strlen (input_name);
!       na = input_name + len;
  
!       /* NA gets INPUT_NAME sans directory names.  */
!       while (na > input_name)
!       {
! 	 if (na[-1] == '/')
! 	    break;
! 	 na--;
!       }
!    }
  
  #ifdef ASM_OUTPUT_MAIN_SOURCE_FILENAME
    ASM_OUTPUT_MAIN_SOURCE_FILENAME (asm_file, na);


[-- Attachment #2: toplev.c.patch.gz --]
[-- Type: application/x-gzip, Size: 813 bytes --]

crossgcc debug with HP emulator

[Steve deRosier]

I am having problems creating code with my crossgcc that works properly with
the HP emulator that we are using.  We are converting a project from a
Microtec tool chain to the GNU tool chain for a M68x target.  The crossgcc
tools are configured for m68k-coff (hosted on a Sun), and I can successfully
compile, assemble, link and run (not withstanding code bugs) the code on the
emulator plugged into our target system, but can't seem to get the source
code to be displayed in the emulator window when debugging.

Originally we used the
-g    { generate debug info }
-Gf   { generates fully qualified path names for input files }
flags when compiling our code with the MRI compiler.  This allowed us to
automagically display the C and C++ source in the debug window of our
emulator when we were stepping through code.

Now I am using -gstabs flag on the crossgcc (-g would kill our emulator when
loading symbols due to the gdb specific debug info).  I've also tried to use
-gcoff (doesn't help any, and causes a segfault when using objcopy to create
srecords) and other permutations of -g that seem reasonable

While I can get it running on the emulator and even debug (instruction
stepping specifically), trying to step through C/C++ code at the assembly
instruction level is painful.  Is there a flag that I am missing or another
permutation of the -g flag that will allow me to display the C/C++ source in
my debugger? Is there an equivalent flag to the MRI -Gf that we were using
(and I suspect is mostly responsible for our previous ability to display the
C/C++ source)?

I am a relative newbie to using a crossgcc, so I figure that I am missing
something obvious and simple.  I would greatly appreciate any help from
someone who is doing this successfully.

Thanks,
- Steve


--
Steve deRosier
Embedded Software Engineer
Vari-Lite International, Inc.


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

Re: crossgcc debug with HP emulator

[John Breen]

>From: "Steve deRosier" <sderosier@vari-lite.com>

>I am having problems creating code with my crossgcc that works
>properly with the HP emulator that we are using.  [...] [I] can't
>seem to get the source code to be displayed in the emulator window
>when debugging.

Whose emulator software are you using?  I know you said "HP emulator", but 
IIRC, HP isn't doing the front-end software for their emulators anymore (at 
least that's what they told me when I bought my emulator a couple of years 
ago).

I used SingleStep with an HP emulator & m68k-elf for a 68360 system.  
Getting source-level debugging working did take some effort, but 
unfortunately that was at another company, and I don't have my notes 
anymore.  I think I had to use -gdwarf (which, I think, meant I had to 
change some configuration stuff when I built gcc; look through the archives 
(here and egcs) from about 2 years ago and you may see some messages from me 
on the subject).

Hope this helps.
--
John Breen

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

Re: crossgcc debug with HP emulator

[Steve deRosier]

Thanks, 

Looks like this may work for me.  I will give it a try and let you know.

Which leads me to the next question - how does one install a patch (ok, yes
I am a newbie....)?

Thanks,

- Steve


--
Steve deRosier
Embedded Software Engineer
Vari-Lite International, Inc.


----------
>From: Jepsen Hans Peter <hans_peter_jepsen@Danfoss.com>
>To: "'Steve deRosier'" <sderosier@vari-lite.com>, crossgcc
<crossgcc@sources.redhat.com>
>Subject: RE: crossgcc debug with HP emulator
>Date: Tue, Jan 9, 2001, 7:53 AM
>

> Hi
>
> Steve deRosier wrote:
>
>> I am having problems creating code with my crossgcc that
>> works properly with the HP emulator that we are using.
> ...
>
>> Is there a flag that I am missing or another
>> permutation of the -g flag that will allow me to display the
>> C/C++ source in my debugger?
>
> We had the same problem. I ended up in modifying gcc as shown in the
> attached small patch.
>
> The effect is to add an option: -fkeep-file-path
> that, when applied, does not strip the path from the supplied filename.
>
> For us it works with HP emulator and Lauterbach hostdriver.
>
> Kind regards
>
> Hans Peter
>
>    --
> Hans Peter Jepsen          Phone: +45 74 88 50 11
> Danfoss Drives A/S,        Fax:   +45 74 65 28 38
> DG-133, Ulsnaes 1,         Email: Hans_Peter_Jepsen@danfoss.com
> DK-6300 Graasten, Denmark  or:    hpj@computer.org
>
>
>
> *** egcs-1.1b/gcc/toplev.c.orig Sun May  2 20:47:14 1999
> --- egcs-1.1b/gcc/toplev.c Mon Jun 21 09:06:40 1999
> ***************
> *** 721,726 ****
> --- 721,731 ----
>      if alias analysis (in general) is enabled.  */
>   int flag_strict_aliasing = 0;
>
> + /* -fkeep-file-path causes the file directive in the outputfile to be the
> name
> +    given on the commandline, ie a possible directory path is not removed.
> +    Normal/default behavior is to strip the path */
> + int keep_file_path = 0;
> +
>   extern int flag_dump_unnumbered;
>
>
> ***************
> *** 908,913 ****
> --- 913,920 ----
>      "Generate code to check every memory access" },
>     {"prefix-function-name", &flag_prefix_function_name, 1,
>      "Add a prefix to all function names" },
> +   {"keep-file-path", &keep_file_path,1,
> +    "Do not strip path in .file directive"},
>     {"dump-unnumbered", &flag_dump_unnumbered, 1}
>   };
>
> ***************
> *** 2371,2386 ****
>        FILE *asm_file;
>        char *input_name;
>   {
> !   int len = strlen (input_name);
> !   char *na = input_name + len;
>
> !   /* NA gets INPUT_NAME sans directory names.  */
> !   while (na > input_name)
> !     {
> !       if (na[-1] == '/')
> !  break;
> !       na--;
> !     }
>
>   #ifdef ASM_OUTPUT_MAIN_SOURCE_FILENAME
>     ASM_OUTPUT_MAIN_SOURCE_FILENAME (asm_file, na);
> --- 2378,2400 ----
>        FILE *asm_file;
>        char *input_name;
>   {
> !    char *na;
> !
> !    if ( keep_file_path) /* leave the input_name unchanged */
> !       na = input_name;
> !    else /* strip leadin path from input_name - default behaviour */
> !    {
> !       int len = strlen (input_name);
> !       na = input_name + len;
>
> !       /* NA gets INPUT_NAME sans directory names.  */
> !       while (na > input_name)
> !       {
> !   if (na[-1] == '/')
> !      break;
> !   na--;
> !       }
> !    }
>
>   #ifdef ASM_OUTPUT_MAIN_SOURCE_FILENAME
>     ASM_OUTPUT_MAIN_SOURCE_FILENAME (asm_file, na);
>
>
> 

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

Re: crossgcc debug with HP emulator

[Steve deRosier]

Thanks, 

Looks like this may work for me.  I will give it a try and let you know.

Which leads me to the next question - how does one install a patch (ok, yes
I am a newbie....)?

Thanks,

- Steve


--
Steve deRosier
Embedded Software Engineer
Vari-Lite International, Inc.


----------
>From: Jepsen Hans Peter <hans_peter_jepsen@Danfoss.com>
>To: "'Steve deRosier'" <sderosier@vari-lite.com>, crossgcc
<crossgcc@sources.redhat.com>
>Subject: RE: crossgcc debug with HP emulator
>Date: Tue, Jan 9, 2001, 7:53 AM
>

> Hi
>
> Steve deRosier wrote:
>
>> I am having problems creating code with my crossgcc that
>> works properly with the HP emulator that we are using.
> ...
>
>> Is there a flag that I am missing or another
>> permutation of the -g flag that will allow me to display the
>> C/C++ source in my debugger?
>
> We had the same problem. I ended up in modifying gcc as shown in the
> attached small patch.
>
> The effect is to add an option: -fkeep-file-path
> that, when applied, does not strip the path from the supplied filename.
>
> For us it works with HP emulator and Lauterbach hostdriver.
>
> Kind regards
>
> Hans Peter
>
>    --
> Hans Peter Jepsen          Phone: +45 74 88 50 11
> Danfoss Drives A/S,        Fax:   +45 74 65 28 38
> DG-133, Ulsnaes 1,         Email: Hans_Peter_Jepsen@danfoss.com
> DK-6300 Graasten, Denmark  or:    hpj@computer.org
>
>
>
> *** egcs-1.1b/gcc/toplev.c.orig Sun May  2 20:47:14 1999
> --- egcs-1.1b/gcc/toplev.c Mon Jun 21 09:06:40 1999
> ***************
> *** 721,726 ****
> --- 721,731 ----
>      if alias analysis (in general) is enabled.  */
>   int flag_strict_aliasing = 0;
>
> + /* -fkeep-file-path causes the file directive in the outputfile to be the
> name
> +    given on the commandline, ie a possible directory path is not removed.
> +    Normal/default behavior is to strip the path */
> + int keep_file_path = 0;
> +
>   extern int flag_dump_unnumbered;
>
>
> ***************
> *** 908,913 ****
> --- 913,920 ----
>      "Generate code to check every memory access" },
>     {"prefix-function-name", &flag_prefix_function_name, 1,
>      "Add a prefix to all function names" },
> +   {"keep-file-path", &keep_file_path,1,
> +    "Do not strip path in .file directive"},
>     {"dump-unnumbered", &flag_dump_unnumbered, 1}
>   };
>
> ***************
> *** 2371,2386 ****
>        FILE *asm_file;
>        char *input_name;
>   {
> !   int len = strlen (input_name);
> !   char *na = input_name + len;
>
> !   /* NA gets INPUT_NAME sans directory names.  */
> !   while (na > input_name)
> !     {
> !       if (na[-1] == '/')
> !  break;
> !       na--;
> !     }
>
>   #ifdef ASM_OUTPUT_MAIN_SOURCE_FILENAME
>     ASM_OUTPUT_MAIN_SOURCE_FILENAME (asm_file, na);
> --- 2378,2400 ----
>        FILE *asm_file;
>        char *input_name;
>   {
> !    char *na;
> !
> !    if ( keep_file_path) /* leave the input_name unchanged */
> !       na = input_name;
> !    else /* strip leadin path from input_name - default behaviour */
> !    {
> !       int len = strlen (input_name);
> !       na = input_name + len;
>
> !       /* NA gets INPUT_NAME sans directory names.  */
> !       while (na > input_name)
> !       {
> !   if (na[-1] == '/')
> !      break;
> !   na--;
> !       }
> !    }
>
>   #ifdef ASM_OUTPUT_MAIN_SOURCE_FILENAME
>     ASM_OUTPUT_MAIN_SOURCE_FILENAME (asm_file, na);
>
>
> 

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

RE: crossgcc debug with HP emulator

[Jepsen Hans Peter]

[-- Attachment #1: Type: text/plain, Size: 2697 bytes --]

Hi 

Steve deRosier wrote:

> I am having problems creating code with my crossgcc that 
> works properly with the HP emulator that we are using.  
...

> Is there a flag that I am missing or another
> permutation of the -g flag that will allow me to display the 
> C/C++ source in my debugger? 

We had the same problem. I ended up in modifying gcc as shown in the
attached small patch.

The effect is to add an option: -fkeep-file-path
that, when applied, does not strip the path from the supplied filename.

For us it works with HP emulator and Lauterbach hostdriver.

Kind regards

Hans Peter

   --
Hans Peter Jepsen          Phone: +45 74 88 50 11
Danfoss Drives A/S,        Fax:   +45 74 65 28 38
DG-133, Ulsnaes 1,         Email: Hans_Peter_Jepsen@danfoss.com
DK-6300 Graasten, Denmark  or:    hpj@computer.org



*** egcs-1.1b/gcc/toplev.c.orig	Sun May  2 20:47:14 1999
--- egcs-1.1b/gcc/toplev.c	Mon Jun 21 09:06:40 1999
***************
*** 721,726 ****
--- 721,731 ----
     if alias analysis (in general) is enabled.  */
  int flag_strict_aliasing = 0;
  
+ /* -fkeep-file-path causes the file directive in the outputfile to be the
name
+    given on the commandline, ie a possible directory path is not removed.
+    Normal/default behavior is to strip the path */
+ int keep_file_path = 0;
+ 
  extern int flag_dump_unnumbered;
  
  
***************
*** 908,913 ****
--- 913,920 ----
     "Generate code to check every memory access" },
    {"prefix-function-name", &flag_prefix_function_name, 1,
     "Add a prefix to all function names" },
+   {"keep-file-path", &keep_file_path,1,
+    "Do not strip path in .file directive"},
    {"dump-unnumbered", &flag_dump_unnumbered, 1}
  };
  
***************
*** 2371,2386 ****
       FILE *asm_file;
       char *input_name;
  {
!   int len = strlen (input_name);
!   char *na = input_name + len;
  
!   /* NA gets INPUT_NAME sans directory names.  */
!   while (na > input_name)
!     {
!       if (na[-1] == '/')
! 	break;
!       na--;
!     }
  
  #ifdef ASM_OUTPUT_MAIN_SOURCE_FILENAME
    ASM_OUTPUT_MAIN_SOURCE_FILENAME (asm_file, na);
--- 2378,2400 ----
       FILE *asm_file;
       char *input_name;
  {
!    char *na;
!    
!    if ( keep_file_path) /* leave the input_name unchanged */
!       na = input_name;
!    else /* strip leadin path from input_name - default behaviour */
!    {      
!       int len = strlen (input_name);
!       na = input_name + len;
  
!       /* NA gets INPUT_NAME sans directory names.  */
!       while (na > input_name)
!       {
! 	 if (na[-1] == '/')
! 	    break;
! 	 na--;
!       }
!    }
  
  #ifdef ASM_OUTPUT_MAIN_SOURCE_FILENAME
    ASM_OUTPUT_MAIN_SOURCE_FILENAME (asm_file, na);


[-- Attachment #2: toplev.c.patch.gz --]
[-- Type: application/x-gzip, Size: 813 bytes --]

Re: crossgcc debug with HP emulator

[John Breen]

>From: "Steve deRosier" <sderosier@vari-lite.com>

>I am having problems creating code with my crossgcc that works
>properly with the HP emulator that we are using.  [...] [I] can't
>seem to get the source code to be displayed in the emulator window
>when debugging.

Whose emulator software are you using?  I know you said "HP emulator", but 
IIRC, HP isn't doing the front-end software for their emulators anymore (at 
least that's what they told me when I bought my emulator a couple of years 
ago).

I used SingleStep with an HP emulator & m68k-elf for a 68360 system.  
Getting source-level debugging working did take some effort, but 
unfortunately that was at another company, and I don't have my notes 
anymore.  I think I had to use -gdwarf (which, I think, meant I had to 
change some configuration stuff when I built gcc; look through the archives 
(here and egcs) from about 2 years ago and you may see some messages from me 
on the subject).

Hope this helps.
--
John Breen

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

crossgcc debug with HP emulator

[Steve deRosier]

I am having problems creating code with my crossgcc that works properly with
the HP emulator that we are using.  We are converting a project from a
Microtec tool chain to the GNU tool chain for a M68x target.  The crossgcc
tools are configured for m68k-coff (hosted on a Sun), and I can successfully
compile, assemble, link and run (not withstanding code bugs) the code on the
emulator plugged into our target system, but can't seem to get the source
code to be displayed in the emulator window when debugging.

Originally we used the
-g    { generate debug info }
-Gf   { generates fully qualified path names for input files }
flags when compiling our code with the MRI compiler.  This allowed us to
automagically display the C and C++ source in the debug window of our
emulator when we were stepping through code.

Now I am using -gstabs flag on the crossgcc (-g would kill our emulator when
loading symbols due to the gdb specific debug info).  I've also tried to use
-gcoff (doesn't help any, and causes a segfault when using objcopy to create
srecords) and other permutations of -g that seem reasonable

While I can get it running on the emulator and even debug (instruction
stepping specifically), trying to step through C/C++ code at the assembly
instruction level is painful.  Is there a flag that I am missing or another
permutation of the -g flag that will allow me to display the C/C++ source in
my debugger? Is there an equivalent flag to the MRI -Gf that we were using
(and I suspect is mostly responsible for our previous ability to display the
C/C++ source)?

I am a relative newbie to using a crossgcc, so I figure that I am missing
something obvious and simple.  I would greatly appreciate any help from
someone who is doing this successfully.

Thanks,
- Steve


--
Steve deRosier
Embedded Software Engineer
Vari-Lite International, Inc.


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com