** Description changed:

  Binary package hint: imagemagick
  
  no idea
  
  ProblemType: Crash
  Architecture: i386
  CrashCounter: 1
  Date: Tue Oct  2 00:27:58 2007
  DistroRelease: Ubuntu 7.10
  ExecutablePath: /usr/bin/identify
  NonfreeKernelModules: cdrom
  Package: imagemagick 7:6.2.4.5.dfsg1-1ubuntu1 [modified: usr/bin/animate 
usr/bin/compare usr/bin/composite usr/bin/conjure usr/bin/convert 
usr/bin/display usr/bin/identify usr/bin/import usr/bin/mogrify usr/bin/montage]
  PackageArchitecture: i386
  ProcCmdline: identify -format %w;\\n%h;\\n%c;\\n -ping 
/usr/share/inkscape/screens/keys.svg
  ProcCwd: /home/mike
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 24
  SourcePackage: imagemagick
  Stacktrace:
   #0  0xffffe410 in __kernel_vsyscall ()
   #1  0x4bf9e590 in raise () from /lib/tls/i686/cmov/libpthread.so.0
   #2  0x4cb0b6cf in ?? () from /usr/lib/libMagick.so.9
   #3  0x00000018 in ?? ()
   #4  0x00000000 in ?? ()
  StacktraceTop:
   __kernel_vsyscall ()
   raise () from /lib/tls/i686/cmov/libpthread.so.0
   ?? () from /usr/lib/libMagick.so.9
   ?? ()
   ?? ()
  Title: identify crashed with signal 24 in __kernel_vsyscall()
  Uname: Linux ubuntu 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 
i686 GNU/Linux
  UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin netdev 
plugdev powerdev scanner video
+ SegvAnalysis:
+  Segfault happened at: 0xffffe410 <__kernel_vsyscall+16>:     pop    %ebp
+  PC (0xffffe410) ok
+  source "%ebp" ok
+  destination "(%esp)" (0xbfd838c0) ok
+  Reason could not be automatically determined.
+ SegvReason: Reason could not be automatically determined.

-- 
identify crashed with signal 24 in __kernel_vsyscall()
https://bugs.launchpad.net/bugs/147877
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to