Hi Jörg,
> Could you also provide the call stack here? Obviously, it must be the
> caller of mem2hex already calling it with a NULL pointer.
#2 0x000000000040dc65 in main (argc=4, argv=0x7fffffffd468) at main.cc:735
// Now do the actual processing of GDB messages
// We stay here until exiting because of error of EOF on the
// gdb connection
for (;;)
-> talkToGdb();
}
#1 0x000000000040f303 in talkToGdb () at remote.cc:709
case 'm': // mAA..AA,LLLL Read LLLL bytes at address AA..AA
{
uchar *jtagBuffer;
if((hexToInt(&ptr, &addr)) &&
(*(ptr++) == ',') &&
(hexToInt(&ptr, &length)))
{
debugOut("\nGDB: Read %d bytes from 0x%X\n", length, addr);
try
{
jtagBuffer = theJtagICE->jtagRead(addr, length);
-> mem2hex(jtagBuffer, remcomOutBuffer, length);
delete [] jtagBuffer;
}
catch (jtag_exception&)
{
error(1);
}
}
break;
}
#0 0x000000000040e578 in mem2hex (mem=0x0, buf=0x738220
<remcomOutBuffer> "", count=2) at remote.cc:230
Hm, the variable jtagBuffer is 0 after jtagRead, which explains the
crash. "addr" has the value 140 and "length" the value 2 (but I don't
know whether this is of any help here).
> Did you already do anything in GDB, or is this during the initial
> startup (after the "target remote" command)?
I called GDB from Eclipse so it is difficult to say, which commands were
already issued. What do I have to do during compilation to switch on the
output from "debugOut"?
Best regards,
Frank
------------------------------------------------------------------------------
Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS
and more. Get SQL Server skills now (including 2012) with LearnDevNow -
200+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
SALE $99.99 this month only - learn more at:
http://p.sf.net/sfu/learnmore_122512
_______________________________________________
avarice-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/avarice-user
