public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org To: ecos-bugs@ecos.sourceware.org Subject: [Bug 1002024] New: configtool segfault at libc6 Date: Thu, 06 Nov 2014 14:01:00 -0000 [thread overview] Message-ID: <bug-1002024-13@http.bugs.ecos.sourceware.org/> (raw) Please do not reply to this email, use the link below. http://bugs.ecos.sourceware.org/show_bug.cgi?id=1002024 Bug ID: 1002024 Summary: configtool segfault at libc6 Product: eCos Version: 3.0 Target: Other (please specify) Architecture/Host HostOS: Linux OS: Status: UNCONFIRMED Severity: major Priority: low Component: ConfigTool Assignee: unassigned@bugs.ecos.sourceware.org Reporter: marek.matej@gmail.com CC: ecos-bugs@ecos.sourceware.org Created attachment 2549 --> http://bugs.ecos.sourceware.org/attachment.cgi?id=2549&action=edit configtool running with emul-linux packages on 64bit gentoo linux system Hi folks, I'm using on Gentoo Linux system. Using configtool downloaded from ecoscentric $ configtool -v eCos Configuration Tool (C) Free Software Foundation, Inc., 1998-2009 (C) eCosCentric Limited 2005-2009 Version 3.0.12, Mar 5 2010 This 32b binary works on pure gentoo system, however several components are not displayed (checkboxes, radio-buttons, images) and can not be used to alter the configuration. The binary is using precompiled emul-linux* packages (no multilib). The binary segfaults immediately on the Calculate Linux (AMD64) The binary segfaults when clicking on File menu (and several others) on Linux Mint (IA32), but works in terms of saving current configuration and rebuilding the target library. This makes it partialy usable. I've made attempts to build configtool on my own (on Gentoo amd64) using the step by step description from ecoscentric configtool page. I can build my own binary which runs and contains previously missing widgets (checkboxes, radiobuttons...), but it segfault in situations when I'm altering theese settings, however. This can be reproduced allways: (gdb) bt full #0 0x00000000004baa8b in ?? () No symbol table info available. #1 0x000000000046ac3a in ?? () No symbol table info available. #2 0x00000000006045f0 in ?? () No symbol table info available. #3 0x000000000046d84f in ?? () No symbol table info available. #4 0x00000000006e6ec3 in ?? () No symbol table info available. #5 0x00000000006e7034 in ?? () No symbol table info available. #6 0x00000000006e7357 in ?? () No symbol table info available. #7 0x00000000006e72e0 in ?? () No symbol table info available. #8 0x0000000000652e05 in ?? () No symbol table info available. #9 0x0000000000659ade in ?? () No symbol table info available. #10 0x000000000065c894 in ?? () No symbol table info available. #11 0x00000000006e6ec3 in ?? () No symbol table info available. #12 0x00000000006e7034 in ?? () No symbol table info available. #13 0x00000000006e7357 in ?? () No symbol table info available. #14 0x00000000006e72e0 in ?? () No symbol table info available. #15 0x0000000000652e05 in ?? () No symbol table info available. #16 0x00000000005b7bd9 in ?? () No symbol table info available. #17 0x00007ffff72838c9 in ?? () from /usr/lib64/libgtk-x11-2.0.so.0 No symbol table info available. #18 0x00007ffff6039210 in g_closure_invoke () from /usr/lib64/libgobject-2.0.so.0 Any help, even hint what should be checked would be apprecciated. I see that official ecos develpment is not very active right now, but we believe that ecos is powerfull and one of the best RTOS solutions on the market and we are willing to continue its development. Thanks, Mark PS: attachment with the working configtool without the widgets follows. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2014-11-06 14:01 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-11-06 14:01 bugzilla-daemon [this message] 2014-11-07 17:18 ` [Bug 1002024] " bugzilla-daemon 2014-12-12 14:37 ` bugzilla-daemon 2014-12-12 14:39 ` bugzilla-daemon 2015-04-24 11:13 ` bugzilla-daemon 2014-11-06 14:01 [Bug 1002024] New: " bugzilla-daemon
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-1002024-13@http.bugs.ecos.sourceware.org/ \ --to=bugzilla-daemon@bugs.ecos.sourceware.org \ --cc=ecos-bugs@ecos.sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).