andreas> Program received signal SIGSEGV, Segmentation fault.
andreas> 0x000519ec in interface_jtag_add_dr_out (device_num=0, 
num_fields=0, num_bits=0x2, value=0xf1040, end_state=TAP_RTI) at jtag.c:721
andreas> 721             (*last_cmd)->cmd.scan->ir_scan = 0;

Hmm - Some ideas

1) As rick asks - what SVN version of OpenOCD are you using?

Look at the file: "jtag.c" - function:  "cmd_queue_allocate()' is there 
a *BIG*WARNING* comment that talks about alignment?

2) Can you run openocd under gdb on your uCLinux box?

3) Can you do this again (with newer SVN version) - line numbers do not 
match well.
Then - get a disassembly dump of the relevent section of the code.
There are 3 different pointers going on there., (a) (*last_cmd), (b) the 
-> part, and (c) the value of ".scan"
By looking at the disassembly - and the address (ie: above it iwas 
0x000519ec) one can figure out what pointer is bad

4) you can perhaps configure uClinux to save a core file - and look at 
the register value @ the time of the crash
(other version of uCLinux - have a kernel config to dump/print the cpu 
registers when the above happens)
It would be helpful to determine what they where.

5) A bunch of simplistic "printf()" statements at that point in the code 
would be very helpful.
for example:

    printf( "LAST CMD = %p\n", last_cmd );
    printf(" last command pointer = %p\n", last_command_ptr );
    .... and all the other ones.
    For example - print the return values of the "cmd_queue_allocate()" 
calls.

andreas> So I did an strace with the same configuration. In fact ioctl 
calls are failing.

That might be perfectly valid.

> After taking a deeper look to the code I found that "fopen" calls for 
> the configuration files like this fail:

With out detail and context, it is hard to say what is happening here - 
it most likely is 100% NORMAL.

Example: When GCC is hunting for .H files you are #including, there are 
multiple fails.



-- Duane.

_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to