RE: shared objects and device drivers

["Chakrabarti, Suvendra (CTS)" <CSUVENDRA@xxxxxxxxxxxxxxxx>]

    Hi Vimal,

     Thanks for the help. I found that out, (help is better than man ;-)). I
found the error too. I was using a math function
     cos() in the shared object, which itself accesses libm.so, another
shared object. What I said about a runaway program,
     was wrong. It was actually giving seg. fault with a vary large core
image. (I always Ctrl-C'ed) that before the core was
     generated (sip). Well, I used the same funcs. to open and access this
file (/usr/lib/libm.so), and now it is working fine.
     Btw, it was gdb which helped me find out this error. o:-)

     Suvendra

> -----Original Message-----
> From:	Vimal Mathew [SMTP:m_vimal@xxxxxxxxxxx]
> Sent:	Friday, July 23, 1999 3:58 PM
> To:	linux-india@xxxxxxxxx
> Subject:	Re: shared objects and device drivers
> 
> Hi,
>   The best help I found for "gdb" was by typing "help" at the gdb prompt.
> Some other useful commands are
> info functions
> break <function-name>
> [ If you noticed, it was break followed by function-name or line-number,
> you
> dont give an "at" in between. If you try giving line-numbers, you
> should have specified the source-file. ]
>   You type "run" to start execution. You could also use "next","nexti",
> "step", "stepi" instructions with gdb. Type "help" followed by a
> command to get help on that command.
> -
> Bye,
> Vimal
> 
> 
> ______________________________________________________
> Get Your Private, Free Email at http://www.hotmail.com
> 
> 
> --------------------------------------------------------------------
> For more information on Linux in India visit http://www.linux-india.org/
> The Linux India mailing list does not accept postings in HTML format.

- --------------------------------------------------------------------
For more information on Linux in India visit http://www.linux-india.org/
The Linux India mailing list does not accept postings in HTML format.

------------------------------