[U-Boot] Uboot Remote gdb gives segmentation fault and hangs

[U-Boot] Uboot Remote gdb gives segmentation fault and hangs

[alfred steele]

Hi,
I am trying to debug u-boot using arm-elf-gdb on the PDK board. I have been
succesfully using this gdb to a great extent. However, when i try my
vanilla u-boot image with debug, i get a "segfault".

$ arm-elf-gdb  u-boot
GNU gdb 5.3 (eCosCentric)
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "--host=i686-pc-linux-gnu --target=arm-elf"...

(gdb) symbol-file u-boot
Load new symbol table from "u-boot"? (y or n) y
Reading symbols from u-boot...done.
(gdb) target remote 206.44.17.238:2001
Remote debugging using 206.44.17.238:2001
Segmentation fault

AT this point, even the running u-boot on the console hangs/crashes.

Could it  be something wrong with the uboot binary itslef. If so, any
hints as to what
could be wrong?
I have been using theis arm-elf-gdb sucessfully with Redboot in the past.


Thanks,
Alfred.

[U-Boot] Uboot Remote gdb gives segmentation fault and hangs

[Jean-Christophe PLAGNIOL-VILLARD]

On 11:07 Fri 24 Apr     , alfred steele wrote:
> Hi,
> I am trying to debug u-boot using arm-elf-gdb on the PDK board. I have been
> succesfully using this gdb to a great extent. However, when i try my
> vanilla u-boot image with debug, i get a "segfault".
which ICE do you use?
> 
> $ arm-elf-gdb  u-boot
> GNU gdb 5.3 (eCosCentric)
> Copyright 2002 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for details.
> This GDB was configured as "--host=i686-pc-linux-gnu --target=arm-elf"...
> 
> (gdb) symbol-file u-boot
> Load new symbol table from "u-boot"? (y or n) y
> Reading symbols from u-boot...done.
normally no need
> (gdb) target remote 206.44.17.238:2001
> Remote debugging using 206.44.17.238:2001
> Segmentation fault
> 
> AT this point, even the running u-boot on the console hangs/crashes.
> 
> Could it  be something wrong with the uboot binary itslef. If so, any
> hints as to what
> could be wrong?
> I have been using theis arm-elf-gdb sucessfully with Redboot in the past.
I use arm-elf-gdb for years on u-boot and the kernel without any problem

I use the PEEDI or the BDI2000

Best Regards,
J.

[U-Boot] Uboot Remote gdb gives segmentation fault and hangs

[alfred steele]

Thanks !

> which ICE do you use?
 I use the  the BDI3000. Could there be something wrong with the
U-boot image or the way u-boot doing a partial u-boot initialization.
The fact is that it does not even show the entry point/reset vector
address in startup. Could it be that my uboot elf image isn't laid out
correctly in the memory becuase of an incorrect linker script. How do
i go about debugging this.

This is one of my private uboot builds for the PDK(MX31)  board.

 Best Regards,
 Alfred.

[U-Boot] Uboot Remote gdb gives segmentation fault and hangs

[Wolfgang Denk]

Dear alfred steele,

In message <528f13590904240907v16449286t30b8c1b238da9b57@mail.gmail.com> you wrote:
>
> I am trying to debug u-boot using arm-elf-gdb on the PDK board. I have been
> succesfully using this gdb to a great extent. However, when i try my
> vanilla u-boot image with debug, i get a "segfault".

Then your GDB is obviously broken.

> Could it  be something wrong with the uboot binary itslef. If so, any
> hints as to what
> could be wrong?

NHo. No matter what could be wrong in the debugged proragm - this must
never cause the debugger to crash. You may see all kinds of more or
less friendly error messages, but never a crash.

> I have been using theis arm-elf-gdb sucessfully with Redboot in the past.

If this GDB crahes, then it's obviously broken.

Did you try the GDB that comes with ELDK for comparison?

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
And now remains  That we find out the cause of this effect, Or rather
say, the cause of this defect...           -- Hamlet, Act II, Scene 2

[U-Boot] Uboot Remote gdb gives segmentation fault and hangs

[Jean-Christophe PLAGNIOL-VILLARD]

On 11:48 Fri 24 Apr     , alfred steele wrote:
> Thanks !
> 
> > which ICE do you use?
>  I use the  the BDI3000. Could there be something wrong with the
> U-boot image or the way u-boot doing a partial u-boot initialization.
> The fact is that it does not even show the entry point/reset vector
> address in startup. Could it be that my uboot elf image isn't laid out
> correctly in the memory becuase of an incorrect linker script. How do
> i go about debugging this.
I do not known your schematics but I've seen on some boards a ICE crash due to
a reset signal generated by the board. Normally the ICE is supposed to inform
you and the continue to work. But it"s not always the case.

As ask you Wolfgang do you try other toolchains. If you want I can share you
mines

Best Regards,
J.