Re: [cdt-debug-dev] arm-elf-gcc simulator debugging

["Alain Magloire" <alain@xxxxxxx>]

> 
> > The crash is gdb related, you should probably send the PR to=20
> > the gdb mailing list with the backtrace.
> 
> I have, though who knows when, if ever, this would get fixed.=20
> 
> It is not the same pleasure reporting bugs to the GCC team as=20
> the Eclipse team(generally I get feedback from the Eclipse guys,
> they are very welcoming towards bug reporting noviceses).=20
> I'm not too familiar with the GCC development process and how
> to best present things. For one thing I see from the mailing lists
> that everybody seems to hate the bug reporting tool they are using,
> and I've heard they are planning to replace it with Bugzilla.
> 
> Aren't you guys firing of PRs to them left and right? :-)

Yes.  It will take a little time, the priorities are not the same,
we are more interested in getting the GDB/MI side of things rolling.
And like any free software projects it takes volunteers to
dig in the code and come up with a sensible patch.

> > Glad to see things work out.
> >=20
> > Can I close the PR 8-)
> 
> I would suggest no.
> 
> It isn't entirely unreasonable to add a modification to Eclipse such=20
> that it does not issue commands to query the machine configuration
> until the program is running.
> 

Fair enough.

> This is the only thing that stops Eclipse from working out of the
> box with the GDB emulator and from a "marketing point of view", it
> is important that new users to CDT get a basic hello world development
> cycle up and running on the first attempt.
> 

We are looking at ways to make this more configurable.
But to do this we need a good understanding of the problem
and the requirements.  This is why feedback like this is *very* good.