On Tue, Dec 23, 2008 at 9:12 AM, Ryan Graham <[email protected]> wrote: > On Tue, Dec 23, 2008 at 8:48 AM, Chris Miller > <[email protected]> wrote: >> On Dec 23, 2008, at 6:41 AM, Ryan Graham wrote: >>> And in the case of strcpy(), strlcpy(), memcpy(), memset(), and >>> similar functions, they probably don't exist as functions in the >>> compiled code. These small standard functions tend to be built into >>> the compiler and injected in-line when a program is compiled. This >>> allows them to be written in optimized assembly without having to be >>> called as functions, which could negate the optimizations. >>> >>> If you are getting a segfault in strcpy(), you are passing it bad >>> data, so pick a breakpoint in your code just before you call it. >> >> >> Most of stdlib is implemented in the kernel itself. >> > > Ya, that's another spot where a debugger will likely choke. Anything > involving system calls such as file or network access.
You can build a debug version of your kernel. It's not hard. -- Registered Linux Addict #431495 http://profile.xfire.com/mrstalinman | John 3:16! http://www.fsdev.net/ | http://lordsauron.wordpress.com/ Parents, Take Responsibility For Your Kids! http://www.whattheyplay.com/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Linux Users Group. To post a message, send email to [email protected] To unsubscribe, send email to [email protected] For more options, visit our group at http://groups.google.com/group/linuxusersgroup -~----------~----~----~----~------~----~------~--~---
