This is the mail archive of the
insight@sourceware.cygnus.com
mailing list for the Insight project.
Re: Problem in gdbtk-cmds.c
- To: "Staggs, Kevin P (AZ75)" <Staggs_Kevin at htc dot honeywell dot com>
- Subject: Re: Problem in gdbtk-cmds.c
- From: Andrew Cagney <ac131313 at cygnus dot com>
- Date: Sun, 07 Nov 1999 17:48:50 +1100
- CC: "'insight at sourceware dot cygnus dot com'" <insight at sourceware dot cygnus dot com>
- Organization: Cygnus Solutions
- References: <7D2706D329C7D1118EC200805F15C5E44DAF74@htc-az75.htc.honeywell.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