[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: AW: problem with gdb-cris
- To: Schachner Thomas <email@example.com>
- Subject: Re: AW: problem with gdb-cris
- From: Orjan Friberg <firstname.lastname@example.org>
- Date: Wed, 04 Jun 2003 14:03:31 +0200
- Cc: email@example.com
- In-reply-to: <4D50D5110555D5119F270800062B4165047FDA90@xxxxxxx.at>
- Organization: Axis Communications
- References: <4D50D5110555D5119F270800062B4165047FDA90@xxxxxxx.at>
- Sender: firstname.lastname@example.org
- User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030312
Schachner Thomas wrote:
> Sorry for that bad explanation of the problem :
> I have a server application which communicates over usb with a dedicated
> system, on the linux enviroment there is no segmentation fault but if i
> the code and execute on the axis device then i get an segmentation fault.
(Please keep dev-etrax on the CC list.)
Just to be sure: the kernel doesn't crash, does it?
> So i want to examine the problem i installed the cris-gdb and all i get
> is "Cannot access memory at address 0x0" so i do not know where the problem
> is, its not a problem with gdb but with this message i can't do anything.
I don't know if this is the cause for your problem, but did you compile
your application with -fno-omit-frame-pointer?
> backtrace brings -> Cannot access memory at address 0x0
> list brings -> rtld.c: no such file or directory in rtld.c
Please try the command 'cris-fpless-backtrace' also (which tries to get
a backtrace without using the frame pointer). Try 'info registers' as
well (it should give you the current pc).
> what is rtld.c ?
It is probably the file where the crash happened, since gdb tries to
read the source code from it. Maybe it belongs to one of your libraries.