Nieuws:

Welkom, Gast. Alsjeblieft inloggen of registreren.
Heb je de activerings-mail niet ontvangen?

Auteur Topic: sigabrt  (gelezen 425 keer)

snipke

  • Gast
sigabrt
« Gepost op: 2008/04/17, 22:29:49 »
Hoi mensen, ik ben een volkomen leek op het gebied van linux, heb effe onder ubuntu gewerkt maar heb nu de kubuntu erop gezet, en moet zeggen dat deze simpelder is en meer naar windows neigt dan de ubuntu, maar telkens ik programma's wil toevoegen en dus mijn adept installer wil gebruiken krijg ik de mededeling dat er ergens iets mis gelopen is en de code 6 sigabrt komt er dan op, wat wil dit zeggen, en hoe kan ik dit probleem weg krijgen

Alvast bedankt

Grtz

Offline Gijsbert

  • Lid
  • Steunpunt: Ja
sigabrt
« Reactie #1 Gepost op: 2008/04/17, 23:25:22 »
3.4.6.   

Why do I get a SIGABRT after a STAF process has completed on HP-UX?
If you see the following error on an HP-UX machine after a STAF process has completed:
Received signal 6 (SIGABRT)
/usr/lib/dld.sl: Call to __sigenable() failed
/usr/lib/dld.sl: Not owner
Received signal 6 (SIGABRT)
/usr/lib/dld.sl: Unresolved symbol: __h_errno__Fv (code)  from
/usr/local/staf/l
ib/libSTAF.sl
Received signal 6 (SIGABRT)
/usr/lib/dld.sl: Call to __sigenable() failed
/usr/lib/dld.sl: Not owner
Received signal 6 (SIGABRT)
/usr/lib/dld.sl: Unresolved symbol: __h_errno__Fv (code)  from
/usr/local/staf/l
This is likely due to an incorrect hostname. Verify that the DNS is setup correctly an all machines (Refer to "Why can't my STAF machines communicate?").
Van deze site http://staf.sourceforge.net/current2x/STAFFAQ.htm#d0e17 als je er meer over wilt lezen. Verder kwam ik niet met de SIGABRT genoeg hits maar geen oplossing. Dus ik hoop dat je er wat aan hebt.

Met vriendelijke groet,

Gijs
In der Beschränkung zeigt sich der Meister.

snipke

  • Gast
sigabrt
« Reactie #2 Gepost op: 2008/04/18, 13:03:07 »
ik krijg de melding alleen als ik iets wil installeren met adept installer, deze mededeling komt er dan ook nog bij Another process is using the packaging system database (probably some other Adept application or apt-get or aptitude).
Would you like to attempt to resolve this problem? No will enter read-only mode and Cancel to quit and resolve this issue yourself.
Als ik op ja druk dan krijg ik te zien wat het is maar kan er niet aan uit
(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47308903056240 (LWP 6380)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#5  0x00002b06f0756765 in raise () from /lib/libc.so.6
#6  0x00002b06f07581c0 in abort () from /lib/libc.so.6
#7  0x00002b06f00507b4 in __gnu_cxx::__verbose_terminate_handler ()
   from /usr/lib/libstdc++.so.6
#8  0x00002b06f004e746 in ?? () from /usr/lib/libstdc++.so.6
#9  0x00002b06f004e773 in std::terminate () from /usr/lib/libstdc++.so.6
#10 0x00002b06f004e85a in __cxa_throw () from /usr/lib/libstdc++.so.6
#11 0x00000000004fae31 in ?? ()
#12 0x00000000004fb4a4 in ?? ()
#13 0x00000000004fba1d in ?? ()
#14 0x00000000004e6df6 in ?? ()
#15 0x000000000045aa4c in ?? ()
#16 0x000000000043524a in ?? ()
#17 0x0000000000437285 in ?? ()
#18 0x00002b06f195cd76 in QObject::activate_signal ()
   from /usr/lib/libqt-mt.so.3
#19 0x00002b06f1ccae51 in QSignal::signal () from /usr/lib/libqt-mt.so.3
#20 0x00002b06f197beeb in QSignal::activate () from /usr/lib/libqt-mt.so.3
#21 0x00002b06f1982f1e in QSingleShotTimer::event ()
   from /usr/lib/libqt-mt.so.3
#22 0x00002b06f18f82a2 in QApplication::internalNotify ()
   from /usr/lib/libqt-mt.so.3
#23 0x00002b06f18fa031 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#24 0x00002b06f1237308 in KApplication::notify ()
   from /usr/lib/libkdecore.so.4
#25 0x00002b06f188ad12 in QApplication::sendEvent ()
   from /usr/lib/libqt-mt.so.3
#26 0x00002b06f18eb55c in QEventLoop::activateTimers ()
   from /usr/lib/libqt-mt.so.3
#27 0x00002b06f189f443 in QEventLoop::processEvents ()
   from /usr/lib/libqt-mt.so.3
#28 0x00002b06f19117e7 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#29 0x00002b06f19115ef in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#30 0x00002b06f18f9d68 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#31 0x00000000004324ec in ?? ()
#32 0x00002b06f0742b44 in __libc_start_main () from /lib/libc.so.6
#33 0x0000000000432279 in ?? ()
#34 0x00007fffbc025758 in ?? ()
#35 0x0000000000000000 in ?? ()

Grtz