Re: Need advice debugging SIGSEV in memcpy()

"Miguel A.L. Paraz" <map@iphil.net> writes:
> When I run it under gdb (this is Red Hat Linux 4.0, kernel 2.0.29),
> I get a SIGSEGV in memcpy(), and a stack backtrace ("bt") loses
> the context. In contrast, this works for SIGPIPE, making it easy to
> show what exactly triggered the signal.

I would try with any of the memory debuggers avilable: gcc-bounds,
memchecker, ElectricFence, ... I'm not familiar with the tools
available for Linux but have been using purify and sentinel to find
memory bugs in my code.

/assar
Received on Tue Jul 29 2003 - 13:15:40 MDT