mc crashes while browsing deb package.

0 views
Skip to first unread message

d.sastr...@gmail.com

unread,
Apr 24, 2010, 8:58:56 AM4/24/10
to mc-...@googlegroups.com
Hello,

This is to report that mc crashes when browsing deb packages.

This box is a:

Linux ghost 2.6.26-2-686-bigmem #1 SMP Tue Mar 9 18:01:52 UTC 2010
i686 GNU/Linux

I've build a copy of mc-4.7.1 with this specs:

$ ./src/mc -V
GNU Midnight Commander 4.7.1
Virtual File System: tarfs, extfs, cpiofs, ftpfs, fish, mcfs, undelfs
With builtin Editor
Using system-installed S-Lang library with terminfo database
With subshell support as default
With support for background operations
With mouse support on xterm and Linux console
With support for X11 events
With internationalization support
With multiple codepages support
Data types: char 8 int 32 long 32 void * 32 off_t 64 ecs_char 32

using this conf line:

$ export CHOST="i686-pc-linux-gnu"; export CFLAGS="-g -march=prescott
-O2 -pipe -fomit-frame-pointer"; export CXXFLAGS="${CFLAGS}";
./configure --enable-extcharset --enable-vfs-cpio --enable-vfs-tar
--enable-vfs-ftp --enable-vfs-fish --enable-vfs-extfs --enable-vfs-sfs
--enable-vfs-undelfs --enable-vfs-mcfs --enable-netcode
--enable-mcserver --enable-background --enable-charset --enable-werror
--with-gnu-ld --with-x --with-gpm-mouse --with-search-engine=pcre
--with-subshell --with-ssl --enable-debug

So I assume debugging symbols to be present in the binary.
I've attached an output log from a gdb session. Hopefully it's useful.
However, I've noticed many "No symbol table info available."
statements in the debugging log. Are any specifical steps needed to
compile mc with debug enabled (other than --enable-debug and -g flag)?

Please CC me in your answers, I'm not subscribed to the list.

Best regards.

--
Huella de clave primaria: 0FDA C36F F110 54F4 D42B D0EB 617D 396C 448B 31EB

gdb.txt

andrew_b

unread,
Apr 28, 2010, 7:36:59 AM4/28/10
to d.sastr...@gmail.com, mc-...@googlegroups.com

On 24 апр, 16:58, d.sastre.med...@gmail.com wrote:
> So I assume debugging symbols to be present in the binary.
> I've attached an output log from a gdb session. Hopefully it's useful.

Unfortunately, there is no debug info in your gdb output.

> However, I've noticed many "No symbol table info available."
> statements in the debugging log. Are any specifical steps needed to
> compile mc with debug enabled (other than --enable-debug and -g flag)?

I believe http://www.midnight-commander.org/wiki/doc/tracingCrash will
help you.

Also there is a bug report in MC Track: http://www.midnight-commander.org/ticket/2065.

--
Regards,
Andrew

David Sastre

unread,
Apr 28, 2010, 9:58:31 AM4/28/10
to andrew_b, mc-...@googlegroups.com
Hello,

Thanks for the feedback. I'll build a debug-enabled copy of mc ASAP.
Hopefully I'll be able to confirm the bug and produce useful backtraces.
Next time I'll use the bug tracking system on Trac.

Regards.
Reply all
Reply to author
Forward
0 new messages