Re: [dmo-discussion] mpd on mipsel fails to reconfigure (ins…

Página superior

Responder a este mensaje
Autor: Javier Vasquez
Fecha:  
A: dmo-discussion
Asunto: Re: [dmo-discussion] mpd on mipsel fails to reconfigure (install) and to restart
On Wed, Jul 3, 2013 at 11:26 PM, Christian Marillat <marillat@???> wrote:
> ...
> Otherwise install the mpd-dbg under gdb and send the backtrace. Enter bt
> in gdb after the crash.
> ...


As suspected, mpd-dbg doesn't install cleanly:

-------------------
dpkg: error processing mpd (--configure):
subprocess installed post-installation script returned error exit status 132
dpkg: dependency problems prevent configuration of mpd-dbg:
mpd-dbg depends on mpd (= 1:0.17.4-dmo1); however:
Package mpd is not configured yet.

dpkg: error processing mpd-dbg (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
mpd
mpd-dbg
E: Sub-process /usr/bin/dpkg returned an error code (1)
-------------------

But I attempted gdb, and it appears the symbols were found, so here it
goes the gdb output:

-------------------
# gdb /usr/bin/mpd |& tee mpd_gdb.log
GNU gdb (GDB) 7.6 (Debian 7.6-4)
...
This GDB was configured as "mipsel-linux-gnu".
...
Reading symbols from /usr/bin/mpd...Reading symbols from
/usr/lib/debug/.build-id/e1/7ae727e30ac52994447ae735a7acdcffdc7ef7.debug...done.
done.
(gdb) run
Starting program: /usr/bin/mpd
[Thread debugging using libthread_db enabled]
Using host libthread_db library
"/lib/mipsel-linux-gnu/loongson2f/libthread_db.so.1".

Program received signal SIGILL, Illegal instruction.
0x76876948 in ?? () from /usr/lib/mipsel-linux-gnu/libavcodec.so.54
(gdb) bt
#0 0x76876948 in ?? () from /usr/lib/mipsel-linux-gnu/libavcodec.so.54
warning: GDB can't find the start of the function at 0x76876948.

    GDB is unable to find the start of the function at 0x76876948
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 0x76876948 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.
-------------------


Thanks,

--
Javier.