Hi, Paugam Luc
Your excutable might be on flash, then you could not set break point.
(code address show that program is in flash)
And when you try debugging on program on ram,
setting break point at line 1 could be OK, but before stepping,
try run command first and then enter into stepping.
first 'run' command after break on line 1 will stop the program
at the very first instruction.
Linker will complain about library. Please read my notes about this.
you could find my notes at this mailing list archive or bellow.
I'm currently tring to improve RT for uClinux. Jeff said that
current RT has time drift about 300 usec. I know that there
are something to improve on rt_time.c code. I'll try to extract
best timing result from 68EZ328 but may be about 50 usec
(or above) could be a maximum response time (my guess,
think about ~2Mips speed).
>I tried to use gdbserver from Kwonsk on my uCsimm module, and i am unable
>step (from GDB) into a simple test program.
>However, I successfully compiled all the stuff: m68k-unknown-gdb + uCsimm
>gdbserver + add uC-libc ptrace + patch trap #1 on linux kernel.
>The host's GDB talk perfectly at initialization with the uCsimm's
>I can view the C code of my test program, i can set breakpoint.
>But when i step 1, i can't stop at the breakpoint. Each time, the test
>program completes its execution.
>Does anyone know why this is happening ?
>PS: while compiling gdbserver, i needed to add low-linux.o into OBJS part
>the associated Makefile.
> And i also removed the _cleanup fonction from gdbserver/server.c
>because it is already defined into crt0.S (uC-libc).
>Thanks in advance for any help.
>Here are the dumps (gdb & gdbserver) of my try :
>----------------------------gdb-4.18 on my
>paugaml@p5ak6450:~/uCsimm/src/test > m68k-unknown-coff-gdb ./test.coff
>GNU gdb 4.18
>Copyright 1998 Free Software Foundation, Inc.
>GDB is free software, covered by the GNU General Public License, and you
>welcome to change it and/or distribute copies of it under certain
>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=i586-pc-linux-gnu
>(gdb) target remote 192.168.0.12:1024
>Remote debugging using 192.168.0.12:1024
>0x10ce36a0 in text_start ()
>1 #include <unistd.h>
>2 #include <string.h>
>5 main (argc, argv)
>6 int argc;
>7 char **argv;
>9 unsigned char *p = "BONJOUR !!!";
>10 unsigned short k;
>(gdb) b 1
>Breakpoint 1 at 0x10ce36e8: file test.c, line 1.
>Single stepping until exit from function text_start,
>which has no line number information.
>Program exited with code 013.
># gdbserver :1024 test
>Process test created; pid = 19
>code at 10ce36a0, data at 75e018
>Remote debugging using :1024
>Child exited with retcode = b
>Child exited with status 0
>This message resent by the email@example.com list server
This message resent by the firstname.lastname@example.org list server http://www.uClinux.com/
This archive was generated by hypermail 2b30 : Sun Apr 07 2002 - 00:01:35 EST