RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 601536 - execute extend trace.so unsuccessfully
Summary: execute extend trace.so unsuccessfully
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: crash-trace-command
Version: 6.0
Hardware: All
OS: Linux
low
urgent
Target Milestone: rc
: ---
Assignee: Dave Anderson
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
: 601538 601539 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-08 07:12 UTC by Caspar Zhang
Modified: 2010-11-10 20:04 UTC (History)
3 users (show)

Fixed In Version: crash-trace-command-1.0-3.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-10 20:04:34 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
current RHEL6 crash-trace-command package (30.35 KB, application/x-rpm)
2010-06-08 14:34 UTC, Dave Anderson 		no flags Details
View All

Description Caspar Zhang 2010-06-08 07:12:24 UTC 
Description of problem:

When I tried to load trace.so module in crash by using `extend /path/to/trace.so', it returns error:

extend: /usr/lib64/crash/extensions/trace.so: no commands registered: shared object unloaded

in older version (1.2.el6) this command works, I regard it as a regression.

Version-Release number of selected component (if applicable):
crash-5.0.0-14.el6
crash-trace-command-1.0-1.2.el6

How reproducible:
100%

Steps to Reproduce:
1. install crash-trace-command and run crash
2. run extend /path/to/trace.so
  
Actual results:
error occur: extend: /usr/lib64/crash/extensions/trace.so: no commands registered: shared object unloaded

Expected results:
module loaded: /usr/lib64/crash/extensions/trace.so: shared object loaded

Additional info:
Comment 1 Caspar Zhang 2010-06-08 07:14:47 UTC 
*** Bug 601538 has been marked as a duplicate of this bug. ***
Comment 2 Caspar Zhang 2010-06-08 07:14:50 UTC 
*** Bug 601539 has been marked as a duplicate of this bug. ***
Comment 3 Caspar Zhang 2010-06-08 07:16:07 UTC 
due to network issues, sorry for submitted two duplicated bugzillas,
Comment 6 Dave Anderson 2010-06-08 14:34:12 UTC 
Created attachment 422224 [details]
current RHEL6 crash-trace-command package
Comment 7 Dave Anderson 2010-06-08 14:51:22 UTC 
Hello Lai,

The current crash-trace-command package does not work with RHEL6
kernels (2.6.32 + patches) because of the addition of the
"generate trace.dat from core-file" in BZ #592887:

 https://bugzilla.redhat.com/show_bug.cgi?id=592887#c6

It fails to load because the ftrace_init_event_types() function
depends upon a "print_fmt" member in the ftrace_event_call structure,
which doesn't exist in RHEL6.  Here's what the structure looks like
in 2.6.32-30.el6:

crash> ftrace_event_call
struct ftrace_event_call {
    struct list_head list;
    char *name;
    char *system;
    struct dentry *dir;
    struct trace_event *event;
    int enabled;
    int (*regfunc)(struct ftrace_event_call *);
    void (*unregfunc)(struct ftrace_event_call *);
    int id;
    int (*raw_init)(struct ftrace_event_call *);
    int (*show_format)(struct ftrace_event_call *, struct trace_seq *);
    int (*define_fields)(struct ftrace_event_call *);
    struct list_head fields;
    int filter_active;
    struct event_filter *filter;
    void *mod;
    void *data;
    atomic_t profile_count;
    int (*profile_enable)(struct ftrace_event_call *);
    void (*profile_disable)(struct ftrace_event_call *);
}
SIZE: 176
crash>

That patch is called "trace_dump.patch" in the attached src.rpm file.
If I remove that patch and rebuild the package, the module loads OK.

So the question is: 

 (1) do you want to remove that patch from RHEL6, or 
 (2) would you like to "fix" it for RHEL6?

Doing (1) would certainly be the easiest thing to do, but doing (2)
would possibly keep the RHEL6 version of trace.c closer to the
upstream version.

What should be done?

Thanks,
  Dave
Comment 8 Lai Jiangshan 2010-06-09 02:13:42 UTC 
Hi, Dave,

In the newest kernel, the ftrace_event_call structure has the "print_fmt" member.

I forgot RHEL6 uses the kernel 2.6.32 which is a little older than I expected.
The work of "trace_dump.patch" requires the "print_fmt" member, so I
can't fix it for RHEL6 and I choice (1).

Thanks a lot.
Lai
Comment 11 Caspar Zhang 2010-07-02 07:53:58 UTC 
Verified that this bug has been fixed in version -1.0-3.el6
Comment 12 releng-rhel@redhat.com 2010-11-10 20:04:34 UTC 
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.
Note You need to log in before you can comment on or make changes to this bug.