After some tries of uninstalling pygments now the version 1.3.1 is successfully
uninstalled. I have used cave uninstall --all-versions pygments
--perform-program 'gdb --args cave perform' -x

After compiling paludis using the CXXFLAGS -ggdb3 the pygments version 0.9 left
in the system. Look at this:

amd64x2 / # cave uninstall --all-versions pygments --perform-program 'gdb --args
cave perform' -x
Done: 1056 steps

These are the actions I will take, in order:

<   dev-python/pygments 0.9::installed
    Reasons: target

Total: 1 uninstalls


1 of 1: Starting remove for dev-python/pygments-0.9::installed...

GNU gdb (Gentoo 7.2 p1) 7.2
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
For bug reporting instructions, please see:
<http://bugs.gentoo.org/>...
Reading symbols from /usr/bin/cave...Reading symbols from
/usr/lib64/debug/usr/bin/cave.debug...done.
done.
(gdb) run
Starting program: /usr/bin/cave perform uninstall --hooks --managed-output
--output-exclusivity with-others =dev-python/pygments-0.9::installed --x-of-y 1\
of\ 1
[Thread debugging using libthread_db enabled]
[New Thread 0x7ffff5638710 (LWP 24719)]
[New Thread 0x7fffeffff710 (LWP 24723)]
[Thread 0x7fffeffff710 (LWP 24723) exited]
[New Thread 0x7fffeffff710 (LWP 24726)]
[Thread 0x7fffeffff710 (LWP 24726) exited]

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff772a20a in paludis::VDBRepository::perform_uninstall (this=0xbffb90,
id=..., a=<value optimized out>)
    at vdb_repository.cc:432
432     vdb_repository.cc: No such file or directory.
        in vdb_repository.cc
(gdb) thread apply all bt

Thread 2 (Thread 0x7ffff5638710 (LWP 24719)):
#0  0x00007ffff676d59c in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/libpthread.so.0
#1  0x00007ffff69d49d4 in paludis::Imp<paludis::ActionQueue>::thread_func
(this=0xb65be0) at action_queue.cc:63
#2  0x00007ffff6a51b61 in paludis::Thread::thread_func (r=<value optimized out>)
at thread.cc:51
#3  0x00007ffff6768c1a in start_thread () from /lib/libpthread.so.0
#4  0x00007ffff5b1ea6d in clone () from /lib/libc.so.6

Thread 1 (Thread 0x7ffff7fc5720 (LWP 24716)):
#0  0x00007ffff772a20a in paludis::VDBRepository::perform_uninstall
(this=0xbffb90, id=..., a=<value optimized out>)
    at vdb_repository.cc:432
#1  0x00007ffff757cc9c in visit (this=<value optimized out>, n=...) at
e_installed_repository_id.cc:986
#2  perform_visit<paludis::UninstallAction> (this=<value optimized out>, n=...)
at ../../../paludis/util/simple_visitor.hh:90
#3
paludis::ImplementVisitMethods<paludis::WrappedVoidResultVisitor<paludis::TypeListEntry<paludis::InstallAction,
paludis::TypeListEntry<paludis::UninstallAction,
paludis::TypeListEntry<paludis::PretendAction,
paludis::TypeListEntry<paludis::ConfigAction,
paludis::TypeListEntry<paludis::FetchAction,
paludis::TypeListEntry<paludis::InfoAction,
paludis::TypeListEntry<paludis::PretendFetchAction, paludis::TypeListTail> > > >
> > >, <unnamed>::PerformAction>,
paludis::TypeListEntry<paludis::UninstallAction,
paludis::TypeListEntry<paludis::PretendAction,
paludis::TypeListEntry<paludis::ConfigAction,
paludis::TypeListEntry<paludis::FetchAction,
paludis::TypeListEntry<paludis::InfoAction,
paludis::TypeListEntry<paludis::PretendFetchAction, paludis::TypeListTail> > > >
> > >::forward_visit(paludis::UninstallAction &) (this=<value optimized out>,
n=...) at ../../../paludis/util/simple_visitor.hh:69
#4  0x00007ffff756cbf2 in accept<<unnamed>::PerformAction> (this=<value
optimized out>, a=...)
    at ../../../paludis/util/simple_visitor.hh:134
#5  paludis::erepository::EInstalledRepositoryID::perform_action (this=<value
optimized out>, a=...)
    at e_installed_repository_id.cc:1030
#6  0x0000000000557fb3 in (anonymous namespace)::execute (env=..., cmdline=...,
id=..., action_name=..., action=...,
    output_manager_holder=...) at cmd_perform.cc:257
#7  0x000000000055c04d in paludis::cave::PerformCommand::run (this=<value
optimized out>, env=<value optimized out>,
    args=<value optimized out>) at cmd_perform.cc:594
#8  0x00000000004614f5 in main (argc=<value optimized out>, argv=<value
optimized out>) at cave.cc:109
(gdb) quit
A debugging session is active.

        Inferior 1 [process 24716] will be killed.

Quit anyway? (y or n) y

Done remove for dev-python/pygments-0.9::installed


 * Checking whether the GNU info directory needs updating...
 * No updates needed

Updating world

* Nothing to remove for 'dev-python/pygments'
elog>

 * No unread news items found

 * Searching for configuration files requiring action...
 * No configuration file updates required
amd64x2 / #

Ciao,
aleX!

On 06.01.2011 11:40, Ciaran McCreesh wrote:
> On Thu, 06 Jan 2011 11:32:11 +0100
> Alexander SCHMID <[email protected]> wrote:
>> When I try to use paludis instead of cave I get a Segmentation fault.
> 
> Ah, now we're getting somewhere. I'll need a gdb backtrace rather than
> strace for that (which means you'll need to build Paludis with -ggdb3 in
> CXXFLAGS, and with build_options set appropriately, if you haven't
> already).
> 
> The easiest way to get a backtrace is probably to do:
> 
>     $ cave uninstall blah --perform-program 'gdb --args cave perform' -x
>     (gdb) run
>     (gdb) thread apply all bt
> 
> since it sounds like it's the perform process that's barfing rather
> than the main program.
> 
> 
> 
> 
> _______________________________________________
> paludis-user mailing list
> [email protected]
> http://lists.pioto.org/mailman/listinfo/paludis-user

_______________________________________________
paludis-user mailing list
[email protected]
http://lists.pioto.org/mailman/listinfo/paludis-user

Reply via email to