I'm having a similar problem. However in the process of tracking that
one down I found a bug in kernel/ptrace.c.
there is a line:
#define TRACE_BITS 0x8000
then this is used later like:
TRACE_BITS << 16
I guessed the define should be:
#define TRACE_BITS 0x0080
This seems to make the gdb "step" command work. Previously the step
command crashed my ucsimm.
My original problem: (which I still haven't figured out)
I can "continue" only if it is the very first command I try. Every
other time I continue the ucsimm crashes with different errors each
However, I can use the "go" command multiple times without a problem.
Another interesting problem. The "print" command doesn't print the
correct values for my variables.
> Hi .
> Sorry to bother you again.
> I have follow thw "kwonsk"'s explianation to patch my gdbserver and
> uClinux-2.0.38 kernel.
> I have no problem to set break points.
> But, when I put continue command on client command ...
> My uClinux-kernel alway is go into bad_super_trap() function.
> What problem I have got ??
> Can someone tell me ??
> For some reasons, I have build my owm trap system calls. I use trap 10, trap 13,
> and trap 14.
> Do those traps influence uClinux for gdbserver ??
> The second question is,
> On gdb-4.18 version, I set remote debug 3 to show packets message between
> gdbserver and gdb-client.
> The basic packets is showed on gdb manul.
> But, when I command break 10, for example, gdb-client sent a serial of basic
> My question is, where can I find document that explain the gdb commands
> correspond to a serial of basic packets.
> Or, does someway I can know the basic packets sequence to gdb commands ??
> Thank you in advance.
> Bobby Lai.
> This message resent by the email@example.com list server http://www.uClinux.com/
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:37 EST