Dear all,
this discussion thread was about my problem with debugging a large
module put together from several source files. The sources were
compiled separately then linked together using "partial linking"
(ld -r).
Yesterday things started to work and actually I don't know what
was wrong. The
Hello Pavel,
I only tried this on a very simple module (split the hello example,
sources attached), and stepping between files does work, as do
breakpoints. GNU gdb 19990928, RTL 3.0pre6e. Please try this example
and let me know if it works.
Michael.
Pavel Andris ([EMAIL PROTECTED]) wrote:
> De
Wei Ren ([EMAIL PROTECTED]) wrote:
> hi,
>I get some problem like that. I want to trace into some other modules use "s",
>but I failed.
>I write some module A, and module B . The task created by module B called some
>function in module A.
>I compile both modules with -g flag.
> D
Hi RTers,
The debuggers available (zentropix/fsmlabs) are both based on gdbstubs
(maintained by David Grothe, ftp.gcom.com). To work with modules,
gdbstubs was enhanced by zentropix over a year ago to reply to the
qOffsets with the correct sections for the modules (text, data and
bss), the fsml
On Wed, Aug 02, 2000 at 09:29:57AM +0800, Wei Ren wrote:
> hi,
>I get some problem like that. I want to trace into some other modules use "s",
>but I failed.
>I write some module A, and module B . The task created by module B called some
>function in module A.
>I compile both modu
lti-module debug?
- Original Message -
From: Pavel Andris <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, July 31, 2000 8:26 PM
Subject: [rtl] debugging a module
> Dear all,
>
> I've tried to debug a large module put together from several source
Dear all,
I've tried to debug a large module put together from several source
files. The sources were compiled separately then linked together
using "partial linking" (ld -r).
gdb commands work well on the basic source file (i.e. one where the
debugged RT thread starts, it contains also init_mo
