This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: How to debug what I am doing wrong?
- From: Masami Hiramatsu <mhiramat at redhat dot com>
- To: "Theodore Ts'o" <tytso at mit dot edu>
- Cc: systemtap at sourceware dot org
- Date: Thu, 17 Jul 2008 17:29:33 -0400
- Subject: Re: How to debug what I am doing wrong?
- References: <E1KJacT-0007Ft-UY@closure.thunk.org>
Theodore Ts'o wrote:
> <tytso@closure> {/usr/projects/systemtap/examples}
> 8% stap -vvv ext4-check-desk.stp
> SystemTap translator/driver (version 0.7.1/0.131 git branch master, commit 82737bef)
> Copyright (C) 2005-2008 Red Hat, Inc. and others
> This is free software; see the source for copying conditions.
> Session arch: i686 release: 2.6.26-03033-g97438cf
> Created temporary directory "/tmp/stapfX7KWk"
> Searched '/usr/local/share/systemtap/tapset/i686/*.stp', found 2
> Searched '/usr/local/share/systemtap/tapset/*.stp', found 41
> Pass 1: parsed user script and 43 library script(s) in 360usr/10sys/725real ms.
> control symbols: kts: 0xc02f6e60 kte: 0xc02f9f02 stext: 0xc01010e8
> parsed 'ext4_check_descriptors' -> func 'ext4_check_descriptors'
> blacklist regexps:
> blfn: ^(atomic_notifier_call_chain|default_do_nmi|__die|die_nmi|do_debug|do_general_protection|do_int3|do_IRQ|do_page_fault|do_sparc64_fault|do_trap|dummy_nmi_callback|flush_icache_range|ia64_bad_break|ia64_do_page_fault|ia64_fault|io_check_error|mem_parity_error|nmi_watchdog_tick|notifier_call_chain|oops_begin|oops_end|program_check_exception|single_step_exception|sync_regs|unhandled_fault|unknown_nmi_error|.*raw_.*lock.*|.*read_.*lock.*|.*write_.*lock.*|.*spin_.*lock.*|.*rwlock_.*lock.*|.*rwsem_.*lock.*|.*mutex_.*lock.*|raw_.*|.*seq_.*lock.*|atomic_.*|atomic64_.*|get_bh|put_bh|.*apic.*|.*APIC.*|.*softirq.*|.*IRQ.*|.*_intr.*|__delay|.*kernel_text.*|get_current|current_.*|.*exception_tables.*|.*setup_rt_frame.*|.*preempt_count.*|preempt_schedule)$
> blfn_ret: ^(do_exit|sys_exit|sys_exit_group|__switch_to)$
> blfile: ^(kernel/kprobes.c|arch/.*/kernel/kprobes.c)$
> focused on module 'ext4dev = [0x9aa300-0x9d9888, bias 0x0] file /lib/modules/2.6.26-03033-g97438cf/kernel/fs/ext4/ext4dev.ko ELF machine i?86 (code 3)
> WARNING: cannot find module ext4dev debuginfo: No such file or directory
> semantic error: no match while resolving probe point module("ext4dev").function("ext4_check_descriptors")
> semantic error: no probes found
> Pass 2: analyzed script: 0 probe(s), 0 function(s), 0 embed(s), 0 global(s) in 1970usr/170sys/5974real ms.
> Pass 2: analysis failed. Try again with more '-v' (verbose) options.
> Running rm -rf /tmp/stapfX7KWk
> <tytso@closure> {/usr/projects/systemtap/examples}
> 9% grep DEBUG_KERNEL /boot/config-2.6.26-03033-g97438cf
> CONFIG_DEBUG_KERNEL=y
Hi,
Could you check CONFIG_DEBUG_INFO=y instead of DEBUG_KERNEL?
--
Masami Hiramatsu
Software Engineer
Hitachi Computer Products (America) Inc.
Software Solutions Division
e-mail: mhiramat@redhat.com