TED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: Getting c/assembler listings
On Tue, 29 Oct 2002, pa3gcu wrote:
> On Tuesday 29 October 2002 12:03, Kevin Curtis wrote:
> > Hi,
> > I hope this question is not too technical. When an oops message is
> > generated and de
On Tue, 29 Oct 2002, pa3gcu wrote:
> On Tuesday 29 October 2002 12:03, Kevin Curtis wrote:
> > Hi,
> > I hope this question is not too technical. When an oops message is
> > generated and decoded with ksymoops, how do I get an assembler listing of
> > the module that caused the problem so I c
On Tuesday 29 October 2002 12:03, Kevin Curtis wrote:
> Hi,
> I hope this question is not too technical. When an oops message is
> generated and decoded with ksymoops, how do I get an assembler listing of
> the module that caused the problem so I can see where in my program the
> error occur
Hi,
I hope this question is not too technical. When an oops message is
generated and decoded with ksymoops, how do I get an assembler listing of
the module that caused the problem so I can see where in my program the
error occurred. The ksymoops output seems to be bytes of code offset fro
