On 07/21/13 09:36, Timo Juhani Lindfors wrote:
> 
> Unfortunately not but I'm quite sure that the errors related to valgrind
> are related, do you see them too?

When running under valgrind I can see that crash is realizing on the
same uninitialised variables that you are showing but that does not
manifest in the same issue that you are seeing:

  root@sid:/var/crash/201307181438$ valgrind crash 
/home/troyhebe/this_is_going_to_be_a_really_long_path/and_this_is_going_to_make_it_even_longer/plus_now_I_am_adding_this/lib/debug/boot/vmlinux-3.10.1
 vmcore.201307181438 
  ==4991== Memcheck, a memory error detector
  ==4991== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al.
  ==4991== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright info
  ==4991== Command: crash 
/home/troyhebe/this_is_going_to_be_a_really_long_path/and_this_is_going_to_make_it_even_longer/plus_now_I_am_adding_this/lib/debug/boot/vmlinux-3.10.1
 vmcore.201307181438
  ==4991== 

  crash 7.0.1
  Copyright (C) 2002-2013  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation

  ...

  ==4991== Conditional jump or move depends on uninitialised value(s)
  ==4991==    at 0x4E077D: kernel_init (in /usr/bin/crash)
  ==4991==    by 0x46797E: main_loop (in /usr/bin/crash)
  ==4991==    by 0x696795: ??? (in /usr/bin/crash)
  ==4991==    by 0x695339: catch_errors (in /usr/bin/crash)
  ==4991==    by 0x697899: ??? (in /usr/bin/crash)
  ==4991==    by 0x695339: catch_errors (in /usr/bin/crash)
  ==4991==    by 0x697C60: gdb_main_entry (in /usr/bin/crash)
  ==4991==    by 0x465FB4: main (in /usr/bin/crash)
  ==4991== 
  please wait... (gathering kmem slab cache data)
  crash: invalid kernel virtual address: 7373656363615f69  type: "array cache 
limit"

  crash: unable to initialize kmem slab cache subsystem

        KERNEL: 
/home/troyhebe/this_is_going_to_be_a_really_long_path/and_this_is_going_to_make_it_even_longer/plus_now_I_am_adding_this/lib/debug/boot/vmlinux-3.10.1
      DUMPFILE: vmcore.201307181438
          CPUS: 8

I have tried both a very long path and a long filename and simply can not
duplicate the issue with a clean sid environment.

Troy

Attachment: signature.asc
Description: Digital signature

Reply via email to