This is the mail archive of the libc-alpha@sources.redhat.com mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: glibc debugging


It isn't - the assembly is generated at build time.  This is true of
most basic syscalls.

On Mon, Feb 24, 2003 at 05:09:54PM -0500, Chris Gniady wrote:
> Thank you Andreas. It worked. I have additional question.
> I am able to step into fread() function, but I cannot step into read. I 
> get following error from gdb.
> 
> 0x400c9df0 in __libc_read () at __libc_read:-1
> -1    __libc_read: No such file or directory.
>    in __libc_read
> 
> Can you please tell me what I am doing wrong or in what file  
> __libc_read() is located.
> 
> Thanks again,
> Chris
> 
> 
> Andreas Schwab wrote:
> 
> >Chris Gniady <gniady at ecn dot purdue dot edu> writes:
> >
> >|> Hello,
> >|> I am new to glib debugging and I have spent most of the day looking for
> >|> some faq. Can someone point me to a faq that explains how to setup glibc
> >|> so I can step into the library using a debugger when debugging a 
> >program.
> >
> >There's not much you have to do, just make sure you have compiled it with
> >debugging information.
> >
> >Andreas.
> >
> > 
> >
> 
> 
> 

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]