Re: Problem in gdbtk-cmds.c

[Andrew Cagney <ac131313@cygnus.com>]

"Staggs, Kevin P (AZ75)" wrote:
> 
> Hello,
> I have found a problem in gdbtk-cmds.c in the 19991018 version.  Line 3262
> of gdbtk-cmds.c is as follows:
>   rnum = target_read_memory_partial (addr, mbuf, nbytes, NULL);
> The target_read_memory_partion function is in target.c at line 943 and looks
> like:
> int
> target_read_memory_partial (CORE_ADDR memaddr, char *buf, int len, int *err)
> {
>         return target_xfer_memory_partial (memaddr, buf, len, 0, err);
> }
> Immediately above in target.c is the target_xfer_memory_partial function.
> Most of the successful paths will write a 0 to *err and *err is set to NULL.
> This results in a segmentation violation in insight and a crash.
> 
> Thanks
> Kevin Staggs

Er, yes.  My fault.  I'll check in a change in the next day.

	Andrew