5282 gdb Eclipse MI support, was remote connection crash

NZG
2006-01-30T17:02:48Z

> > For reference, I added Dwarf CFI for the _start function in crt0.s for
> > the m32c libgloss port:
Interesting, but it may be beyond what I have a timeline for at this point.
I have had some luck simply by enabling the section of code below, which
appears to have been designed specifically for this purpose.

Everything appears to be working now, although a little bit slower than I
like.
Anyway progress is being made.

thank you for all your help,
Nathan

/* If we're inside the entry file, it isn't valid. Don't apply this
test to a dummy frame - dummy frame PC's typically land in the
entry file. Don't apply this test to the sentinel frame.
Sentinel frames should always be allowed to unwind. */
/* NOTE: drow/2002-12-25: should there be a way to disable this
check? It assumes a single small entry file, and the way some
debug readers (e.g. dbxread) figure out which object is the
entry file is somewhat hokey. */
/* NOTE: cagney/2003-01-10: If there is a way of disabling this test
then it should probably be moved to before the ->prev_p test,
above. */
/* NOTE: vinschen/2003-04-01: Disabled. It turns out that the call
to deprecated_inside_entry_file destroys a meaningful backtrace
under some conditions. E. g. the backtrace tests in the
asm-source testcase are broken for some targets. In this test
the functions are all implemented as part of one file and the
testcase is not necessarily linked with a start file (depending
on the target). What happens is, that the first frame is printed
normaly and following frames are treated as being inside the
enttry file then. This way, only the #0 frame is printed in the
backtrace output. */
/**NZG enabled for expermentation**/

if (1
&& this_frame->type != DUMMY_FRAME && this_frame->level >= 0
&& deprecated_inside_entry_file (get_frame_pc (this_frame)))
{
if (frame_debug)
{
fprintf_unfiltered (gdb_stdlog, "-> ");
fprint_frame (gdb_stdlog, NULL);
fprintf_unfiltered (gdb_stdlog, " // inside entry file }\n");
}
return NULL;
}

On Thursday 26 January 2006 6:03 pm, NZG wrote:
> > For reference, I added Dwarf CFI for the _start function in crt0.s for
> > the m32c libgloss port:
> >
> > http://sourceware.org/cgi-bin/cvsweb.cgi/src/libgloss/m32c/crt0.S?rev=1.2
> >&c ontent-type=text/x-cvsweb-markup&cvsroot=src
> >
> > You'll need to look at the CFI section of the Dwarf spec to adapt this
> > to your processor. (Fortunately, Dwarf CFI is pretty independent of
> > the rest of Dwarf, so don't be discouraged by the overall size of the
> > spec.)
>
> Thanks Jim, I'll take a look at her tomorrow.
> I'm goin home.
>
> thx for all you help today,
> Gnight.