[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Any more ideas? -- RE: How to debug binary-only modules and binaries
- From: "Guolin Cheng" <guolin alexa com>
- To: "For users of Fedora Core releases" <fedora-list redhat com>
- Subject: Any more ideas? -- RE: How to debug binary-only modules and binaries
- Date: Tue, 24 Aug 2004 18:42:11 -0700
Fred,
Thanks for your reply, but I've tried strings, objdump, gdb and several
commands but little help to my binary-only debug.
Any more ideas? Thanks.
--Guolin Cheng
-----Original Message-----
From: fedora-list-bounces redhat com
[mailto:fedora-list-bounces redhat com] On Behalf Of fred vachon
Sent: Tuesday, August 24, 2004 5:47 PM
To: fedora-list redhat com
Subject: RE: How to debug binary-only modules and binaries
Good question. I don't have an answer but am also interested if there
is a way to do this. I just wanted to mention the strings command
in case you are not already familiar with it. I have found it very
useful to show text inside a binary.
There is a man page for strings.
Fred
In response to:
Title: *How to debug binary-only modules and binaries*
Hi,
Nowadays it is not rare that we Linux FC1 users have to use binary-only
modules or user-space binaries, and even worse, those binaries are
reporting problems from time to time.
Are there any tools can we use to debug these binary-only user-space
programs and kernel-space modules at first hand?
Gdb seems mostly used for debugging binaries with sources.
Any suggestions are greatly appreciated. Thanks a lot.
--Guolin Cheng
--
fedora-list mailing list
fedora-list redhat com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]