| CDT RC2 Debug/Launch Bugs [message #149868] |
Sat, 23 July 2005 05:35  |
Eclipse User |
|
|
|
Originally posted by: dev.jonw.f2s.com
Hi,
For a while I have been using Eclipse 3.0 / CDT2.x to drive gcc/gdb for my
remote m68k target with the following setup:
Win2000 Pro SP4
Cygwin 1.5.12
GNU toolchain crossed for m68k-elf
binutils 2.15
m68k-elf-gcc 3.4.1
m68k-elf-gdb 6.2.1
....using slightly modified m68k gdb-stub for debugging.
I have moved from CDT 2.1 to 3.0 and Eclipse3.1, and although there are some
excellent improvements (particularly in the source parser) I have come
across the following problems (most serious first).
(Have tested with 3.0.M7 and 3.0.RC2 - all a present in both - 2.1.1 had
none).
* Breakpoints not cleared at target:
When I clear breakpoint in the editor it is not cleared in the target (in
every case).
i.e. the target still breaks despite the breakpoint being clear in eclipse.
I have to reload the code to remove them.
All the other stuff that issues breakpoints to the target (e.g. Run to Line)
is OK.
* Lengthy source lookup warnings on Launch
When launching, the source search seems to get confused (but it still works
OK once going).
If there are a number of search paths the launch time is considerably
increased.
E.g.: I get this lot in the console when launching:
Warning: /cygdrive/d/Dev/M68C-elf/bios5/5v00/D: No such file or directory.
Warning: \cygwin\usr\src\gcc-3.4.1\gcc\config\m68k: No such file or
directory.
Warning: /cygdrive/d/Dev/M68C-elf/bios5/5v00/D: No such file or directory.
Warning: \cygwin\usr\src\newlib-1.13.0\newlib\libc\unix: No such file or
directory.
Warning: /cygdrive/d/Dev/M68C-elf/bios5/5v00/D: No such file or directory.
Warning: \cygwin\usr\src\newlib-1.13.0\newlib\libc\time: No such file or
directory.
Warning: /cygdrive/d/Dev/M68C-elf/bios5/5v00/D: No such file or directory.
Warning: \cygwin\usr\src\newlib-1.13.0\newlib\libc\syscalls: No such file or
directory.
Warning: /cygdrive/d/Dev/M68C-elf/bios5/5v00/D: No such file or directory.
....loads more...
....and finally
Warning: \Dev\M68C-elf\bios5\5v00\.settings: No such file or directory.
Warning: /cygdrive/d/Dev/M68C-elf/bios5/5v00/D: No such file or directory.
Warning: \Dev\M68C-elf\bios5\5v00: No such file or directory.
Warning: /cygdrive/d/Dev/M68C-elf/bios5/5v00/-r: No such file or directory.
Source lookup is set for:
Default: - D:\Dev\M68C-elf\bios5\5v00
m68k - D:\cygwin\usr\src\gcc-3.4.1\gcc\config
libc - D:\cygwin\usr\src\newlib-1.13.0\newlib
It looks as though the launcher is confusing cygwin paths and Windows
paths - is this just a setup issue??
* 'Internal Error: Failed to fetch children from target'
Get the above message spuriously during debugging... I get no details and
the debugger seems to continue working after the message box is dismissed.
* Double click to change register values.
Double clicking on a register no longer brings up the 'Change Value' dialog.
I just seem to get flicker - fine if selected from the context menu.
Has anybody else come across these?
If nobody recognizes them I'll slap them in bugzilla.
Thanks,
John.
|
|
|
| Re: CDT RC2 Debug/Launch Bugs [message #149900 is a reply to message #149868] |
Sun, 24 July 2005 15:39  |
| Eclipse User |
|
|
|
Originally posted by: mikhailkhod.rogers.com
Please, see my comments inline.
"John Wilson" <dev@jonw.f2s.com> wrote in message
news:dbt31u$n6f$1@news.eclipse.org...
> Hi,
>
> For a while I have been using Eclipse 3.0 / CDT2.x to drive gcc/gdb for my
> remote m68k target with the following setup:
>
> Win2000 Pro SP4
> Cygwin 1.5.12
> GNU toolchain crossed for m68k-elf
> binutils 2.15
> m68k-elf-gcc 3.4.1
> m68k-elf-gdb 6.2.1
> ...using slightly modified m68k gdb-stub for debugging.
>
> I have moved from CDT 2.1 to 3.0 and Eclipse3.1, and although there are
some
> excellent improvements (particularly in the source parser) I have come
> across the following problems (most serious first).
>
> (Have tested with 3.0.M7 and 3.0.RC2 - all a present in both - 2.1.1 had
> none).
>
> * Breakpoints not cleared at target:
> When I clear breakpoint in the editor it is not cleared in the target (in
> every case).
> i.e. the target still breaks despite the breakpoint being clear in
eclipse.
> I have to reload the code to remove them.
> All the other stuff that issues breakpoints to the target (e.g. Run to
Line)
> is OK.
>
I can't reproduce it, but there are other complains about breakpoints not
being cleared in the target. See
https://bugs.eclipse.org/bugs/show_bug.cgi?id=103567
> * Lengthy source lookup warnings on Launch
> When launching, the source search seems to get confused (but it still
works
> OK once going).
> If there are a number of search paths the launch time is considerably
> increased.
>
> E.g.: I get this lot in the console when launching:
>
> Warning: /cygdrive/d/Dev/M68C-elf/bios5/5v00/D: No such file or directory.
> Warning: \cygwin\usr\src\gcc-3.4.1\gcc\config\m68k: No such file or
> directory.
> Warning: /cygdrive/d/Dev/M68C-elf/bios5/5v00/D: No such file or directory.
> Warning: \cygwin\usr\src\newlib-1.13.0\newlib\libc\unix: No such file or
> directory.
> Warning: /cygdrive/d/Dev/M68C-elf/bios5/5v00/D: No such file or directory.
> Warning: \cygwin\usr\src\newlib-1.13.0\newlib\libc\time: No such file or
> directory.
> Warning: /cygdrive/d/Dev/M68C-elf/bios5/5v00/D: No such file or directory.
> Warning: \cygwin\usr\src\newlib-1.13.0\newlib\libc\syscalls: No such file
or
> directory.
> Warning: /cygdrive/d/Dev/M68C-elf/bios5/5v00/D: No such file or directory.
>
> ...loads more...
> ...and finally
>
> Warning: \Dev\M68C-elf\bios5\5v00\.settings: No such file or directory.
> Warning: /cygdrive/d/Dev/M68C-elf/bios5/5v00/D: No such file or directory.
> Warning: \Dev\M68C-elf\bios5\5v00: No such file or directory.
> Warning: /cygdrive/d/Dev/M68C-elf/bios5/5v00/-r: No such file or
directory.
>
> Source lookup is set for:
>
> Default: - D:\Dev\M68C-elf\bios5\5v00
> m68k - D:\cygwin\usr\src\gcc-3.4.1\gcc\config
> libc - D:\cygwin\usr\src\newlib-1.13.0\newlib
>
> It looks as though the launcher is confusing cygwin paths and Windows
> paths - is this just a setup issue??
>
Set the mi protocol level to 1. To do this, go to the "Debugger" page of the
launch configuration dialog and open the "Advanced" dialog. This should fix
the problem.
> * 'Internal Error: Failed to fetch children from target'
> Get the above message spuriously during debugging... I get no details and
> the debugger seems to continue working after the message box is dismissed.
>
There are changes in the Eclipse Debug platform implementation comparing to
Eclipse 3.0. I suspect this type of errors are caused by race conditions,
but unfortunately I don't have a reproducable case.
> * Double click to change register values.
> Double clicking on a register no longer brings up the 'Change Value'
dialog.
> I just seem to get flicker - fine if selected from the context menu.
>
I wasn't aware this feature existed in Eclipse 3.0. If you feel that it is
important, file a bug against Platform Debug.
> Has anybody else come across these?
>
> If nobody recognizes them I'll slap them in bugzilla.
>
> Thanks,
>
> John.
>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.26103 seconds
Home