[fpc-devel] MIPS big-endian program starts but does nothing

[Reinier Olislagers]

On 08/09/2014 18:01, Joost van der Sluis wrote:
> On 09/08/2014 10:25 AM, Reinier Olislagers wrote:
>> gdb ./hellomips
>>
>>
>> dlopen failed on 'libthread_db.so.1' - File not found
>> GDB will not be able to debug pthreads.
>>
>> GNU gdb 6.8
>> Copyright (C) 2008 Free Software Foundation, Inc.
>> License GPLv3+: GNU GPL version 3 or later
>> <http://gnu.org/licenses/gpl.html>
>> This is free software: you are free to change and redistribute it.
>> There is NO WARRANTY, to the extent permitted by law.  Type "show
>> copying"
>> and "show warranty" for details.
>> This GDB was configured as "mips-openwrt-linux"...
>> (no debugging symbols found)
>> (gdb) run
>> Starting program: /usbstorage/backup/hellomips
>>
>>
> 
> That's it? Nothing more? You could try to send a sigint (ctrl-c) and
> then ask for a backtrace (bt).
(gdb) run
Starting program: /usbstorage/backup/hellomips
^C
Program received signal SIGINT, Interrupt.
0x00401b20 in ?? ()
(gdb) bt
#0  0x00401b20 in ?? ()
warning: GDB can't find the start of the function at 0x401b20.

    GDB is unable to find the start of the function at 0x401b20
and thus can't determine the size of that function's stack frame.
This means that GDB may be unable to access that stack frame, or
the frames below it.
    This problem is most likely caused by an invalid program counter or
stack pointer.
    However, if you think GDB should simply search farther back
from 0x401b20 for code which looks like the beginning of a
function, you can increase the range of the search using the `set
heuristic-fence-post' command.
#1  0x00401b20 in ?? ()
warning: GDB can't find the start of the function at 0x401b1f.
Backtrace stopped: previous frame identical to this frame (corrupt stack?