RE: [microblaze-uclinux] Microblaze GDB problems

["Brettschneider Falk" <fbrettschneider@xxxxxxxxxxxxxxx>]

Hi,

Otto Blomqvist wrote:
> I read somewhere that the "(old)" version should not be used. 
> For me the new 
> version compiles just fine using the v0.30 rc1. Very strange. 
> Did you try 
> rebuilding everything after enabling it ?
thanks for your hint, now it was clear to that it only works with just "gdbserver" rather than "gdbserver (old)". I found my compile problem and have been able to get it work here.
Otto, I don't have problems with stepping through the source code, there's no reboot behaviour here.

> What platform are 
> you using ..?
> I am using Xilinx / Spartan 3E Rev D reference design.
> Linux 2.6.
I use a custom platform based on Spartan 3, and also Linux 2.6 (v0.30 rc1)

Although I'm one step further than you, I ran into next problems with my multi-threaded user app. Firstly, every start of a new thread let the debugger interrupt with a messagebox "Program received signal SIG32, Real-time event 32" and this callstack:
 sigsuspend
 __rt_sigsuspend
Secondly, after successfully starting about 5 threads via pthread_create() gdbserver exits back to command line shell when executing another call to pthread_create() in my user app:
on target device:
 Child exited with retcode = 0
 Child exited with status 0
I get just "NO_STACK" in the callstack window of microblaze-uclinux-gdb on my PC.

What does it mean? Could this problably be just an 'out of memory' unhandled in gdbserver?

Cheers, Falk


___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/