Re: [Piklab-users] piklab-0.16.2 crashes on toolchain settings

[Nicolas <aa...@gm...>]

Hi,

It should now be fixed in the svn repository.

Thanks!
Nicolas

On Wed, Nov 7, 2012 at 11:19 AM, bitlord <bit...@gm...> wrote:

> On Wed, 7 Nov 2012 20:10:44 +0100
> bitlord <bit...@gm...> wrote:
>
> > Hello,
> >
> > I built 0.16.2 for testing, and when I try to configure toolchain
> > Settings > Configure Toolchains ...
> > Tried with 'PICC Compiler' and 'PICC Lite Compiler' selecting
> > executable directory (I installed it as user in home directory
> > "/home/<user>/bin/hitech/picc/9.83/bin" ) the program crashes.
> > I don't know how to enable debug and compile it with debugging
> > symbols, tried adding '-ggdb' to C and CXX FLAGS (test machine
> > running gentoo (mostly stable)), but still get this:
> >
> > Reading symbols from /usr/bin/piklab...(no debugging symbols
> > found)...done.
> >
> > Here is a backtrace I get with '-ggdb'
> >
> > piklab: version 0.16.2 (rev. distribution)
> > [New Thread 0x7fffe7c5f700 (LWP 14317)]
> > [New Thread 0x7fffe70c4700 (LWP 14344)]
> > piklab(14314) KSambaSharePrivate::isSambaInstalled: Samba is not
> > installed! piklab(14314) KSambaSharePrivate::findSmbConf: KSambaShare:
> > Could not find smb.conf! piklab(14314)
> > KSambaSharePrivate::isSambaInstalled: Samba is not installed! Qt has
> > caught an exception thrown from an event handler. Throwing exceptions
> > from an event handler is not supported in Qt. You must reimplement
> > QApplication::notify() and catch all exceptions there.
> >
> > Qt has caught an exception thrown from an event handler. Throwing
> > exceptions from an event handler is not supported in Qt. You must
> > reimplement QApplication::notify() and catch all exceptions there.
> >
> > terminate called after throwing an instance of 'std::bad_alloc'
> >   what():  std::bad_alloc
> >
> > Program received signal SIGABRT, Aborted.
> > 0x00007ffff3d9fcc5 in raise () from /lib64/libc.so.6
> > (gdb) bt
> > #0  0x00007ffff3d9fcc5 in raise () from /lib64/libc.so.6
> > #1  0x00007ffff3da0edf in abort () from /lib64/libc.so.6
> > #2  0x00007ffff41bbb45 in __gnu_cxx::__verbose_terminate_handler() ()
> >    from /usr/lib/gcc/x86_64-pc-linux-gnu/4.5.4/libstdc++.so.6
> > #3  0x00007ffff41ba246 in ?? ()
> > from /usr/lib/gcc/x86_64-pc-linux-gnu/4.5.4/libstdc++.so.6 #4
> > 0x00007ffff41ba268 in std::terminate() ()
> > from /usr/lib/gcc/x86_64-pc-linux-gnu/4.5.4/libstdc++.so.6 #5
> > 0x00007ffff41ba391 in __cxa_rethrow ()
> > from /usr/lib/gcc/x86_64-pc-linux-gnu/4.5.4/libstdc++.so.6 #6
> > 0x00007ffff5a5972f in
> > QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) ()
> > from /usr/lib64/qt4/libQtCore.so.4 #7  0x00007ffff5a5d561 in
> > QCoreApplication::exec() () from /usr/lib64/qt4/libQtCore.so.4 #8
> > 0x00007ffff3d8d474 in __libc_start_main () from /lib64/libc.so.6 #9
> > 0x000000000044a839 in _start ()
>
> Oh, little update (I hope it will get to the right thread, I don't know
> how this mailing list works, but it looks strange, don't get my
> messages in inbox). Now I tested it adding a path directly to the
> "textbox" and it works fine, so the problem only exists if I click on
> the little icon and search for a path/location
>
>
> ------------------------------------------------------------------------------
> LogMeIn Central: Instant, anywhere, Remote PC access and management.
> Stay in control, update software, and manage PCs from one command center
> Diagnose problems and improve visibility into emerging IT issues
> Automate, monitor and manage. Do more in less time with Central
> http://p.sf.net/sfu/logmein12331_d2d
> _______________________________________________
> Piklab-users mailing list
> Pik...@li...
> https://lists.sourceforge.net/lists/listinfo/piklab-users
>