Re: Help: Remote debugging using gdb

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

zubair khalil wrote:

> kgdb in Linux 2.4.32 kernel ported for my MIPS r4k processor. 
>  
> Well the problem is when I try to back trace then gdb is unable to show me the 
> arguments passed to it. Instead of showing the actual arguments it just shows 
> garbage.

For specific questions concerning MIPS, you can also try to ask on the
Linux-MIPS mailing list [1].

(Pure supposition.) However, if I remember correctly, on MIPS, function
arguments are passed in registers, not on the stack. This could explain
why gdb is not able to show the arguments in backtraces.

The http://linux.junsun.net/porting-howto/porting-howto.html webpage
also says:

« Sometimes if you break on a function, you cannot see the correct value
in variables and cannot do back-tracing. This is probably because
certain registers are still not initialized [HELP: because kernel is
compiled with -O2 flag?]. Step into the function a couple of lines, and
you should see the variable and back-tracing fine. »

Anyway, you'd better asking on the Linux-MIPS mailing-list rather than
relying on my early-in-the-morning suppositions.

Sincerly,

Thomas

[1] http://www.linux-mips.org/wiki/Net_Resources#Mailing_lists
-- 
Thomas Petazzoni
thomas.petazzoni@xxxxxxxx


--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/kernelnewbies/
FAQ:           http://kernelnewbies.org/faq/



[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux