EmbeddedRelated.com
Forums
The 2026 Embedded Online Conference

I can't set a breakpoint ?

Started by learn June 19, 2015
I'm running Renesas e2 studio version 3.1.0.24.  I used to be able to set
breakpoints without any problem.


Today, I can't set a breakpoint.  I double click on a line and nothing
happens.

FYI, when e2 studio is closed, there is a process running e2studio.exe
*32.


---------------------------------------
Posted through http://www.EmbeddedRelated.com
On Fri, 19 Jun 2015 13:45:16 -0500, learn wrote:

> I'm running Renesas e2 studio version 3.1.0.24. I used to be able to > set breakpoints without any problem. > > > Today, I can't set a breakpoint. I double click on a line and nothing > happens. > > FYI, when e2 studio is closed, there is a process running e2studio.exe > *32.
I know nothing specific about your setup, but trying some combination of rebooting everything may help. Is your software still talking to the chip? Most ARM Cortex parts that I've used come with the ability to disable the debug port in software; usually this means having to replace the chip (unless you build in an escape hatch into your software -- which I routinely do). I use the OpenOCD tool along with the STLink probe for ARM-core products; every once in a while I need to unplug the STLink from USB and the board, power down the board, and then reconnect and power everything up. -- Tim Wescott Wescott Design Services http://www.wescottdesign.com
>On Fri, 19 Jun 2015 13:45:16 -0500, learn wrote: > >> I'm running Renesas e2 studio version 3.1.0.24. I used to be able to >> set breakpoints without any problem. >> >> >> Today, I can't set a breakpoint. I double click on a line and nothing >> happens. >> >> FYI, when e2 studio is closed, there is a process running e2studio.exe >> *32. > >I know nothing specific about your setup, but trying some combination of
>rebooting everything may help. > >Is your software still talking to the chip? Most ARM Cortex parts that >I've used come with the ability to disable the debug port in software; >usually this means having to replace the chip (unless you build in an >escape hatch into your software -- which I routinely do). > >I use the OpenOCD tool along with the STLink probe for ARM-core products;
>every once in a while I need to unplug the STLink from USB and the board,
>power down the board, and then reconnect and power everything up. > >-- > >Tim Wescott >Wescott Design Services >http://www.wescottdesign.com
I shut down my computer. Now, I can set breakpoint in at least one file but I cannot set breakpoint in at least one other file. The breakpoint menu is enabled in file where I can set breakpoints. The breakpoint menu is disabled in file where I cannot set breakpoints. The code is running fine in the debugger. --------------------------------------- Posted through http://www.EmbeddedRelated.com
learn wrote:
>> On Fri, 19 Jun 2015 13:45:16 -0500, learn wrote: >> >>> I'm running Renesas e2 studio version 3.1.0.24. I used to be able to >>> set breakpoints without any problem. >>> >>> >>> Today, I can't set a breakpoint. I double click on a line and nothing >>> happens. >>> >>> FYI, when e2 studio is closed, there is a process running e2studio.exe >>> *32. >> >> I know nothing specific about your setup, but trying some combination of > >> rebooting everything may help. >> >> Is your software still talking to the chip? Most ARM Cortex parts that >> I've used come with the ability to disable the debug port in software; >> usually this means having to replace the chip (unless you build in an >> escape hatch into your software -- which I routinely do). >> >> I use the OpenOCD tool along with the STLink probe for ARM-core products; > >> every once in a while I need to unplug the STLink from USB and the board, > >> power down the board, and then reconnect and power everything up. >> >> -- >> >> Tim Wescott >> Wescott Design Services >> http://www.wescottdesign.com > > > > I shut down my computer. Now, I can set breakpoint in at least one file > but I cannot set breakpoint in at least one other file. > > The breakpoint menu is enabled in file where I can set breakpoints. > The breakpoint menu is disabled in file where I cannot set breakpoints. >
Was the file you cannot set breakpoints in compiled without debug turned on ? IOW, make sure you're using the "debug" build or whatever the toolchain requires to turn on debug and rebuild everything. On the Gnu toolchain, it's the "-g" option. Many compilers use the GNU options. Capture the output from your build and make sure the right options are set.
> The code is running fine in the debugger. > --------------------------------------- > Posted through http://www.EmbeddedRelated.com >
-- Les Cargill
>learn wrote: >>> On Fri, 19 Jun 2015 13:45:16 -0500, learn wrote: >>> >>>> I'm running Renesas e2 studio version 3.1.0.24. I used to be able
to
>>>> set breakpoints without any problem. >>>> >>>> >>>> Today, I can't set a breakpoint. I double click on a line and
nothing
>>>> happens. >>>> >>>> FYI, when e2 studio is closed, there is a process running
e2studio.exe
>>>> *32. >>> >>> I know nothing specific about your setup, but trying some combination
of
>> >>> rebooting everything may help. >>> >>> Is your software still talking to the chip? Most ARM Cortex parts
that
>>> I've used come with the ability to disable the debug port in
software;
>>> usually this means having to replace the chip (unless you build in an >>> escape hatch into your software -- which I routinely do). >>> >>> I use the OpenOCD tool along with the STLink probe for ARM-core >products; >> >>> every once in a while I need to unplug the STLink from USB and the >board, >> >>> power down the board, and then reconnect and power everything up. >>> >>> -- >>> >>> Tim Wescott >>> Wescott Design Services >>> http://www.wescottdesign.com >> >> >> >> I shut down my computer. Now, I can set breakpoint in at least one
file
>> but I cannot set breakpoint in at least one other file. >> >> The breakpoint menu is enabled in file where I can set breakpoints. >> The breakpoint menu is disabled in file where I cannot set
breakpoints.
>> > >Was the file you cannot set breakpoints in compiled without debug turned >on ? IOW, make sure you're using the "debug" build or whatever >the toolchain requires to turn on debug and rebuild everything. > >On the Gnu toolchain, it's the "-g" option. Many compilers use the GNU >options. Capture the output from your build and make sure the right >options are set. > > >> The code is running fine in the debugger. >> --------------------------------------- >> Posted through http://www.EmbeddedRelated.com >> > >-- >Les Cargill
I used to be able to hover over local variable to see it's value. Now, I cannot hover over local variables in the debugger. However, in eclipse IDE I can hover over local variables and see information. I think something is not setup correctly in my debugger. Do I need to do something with the Indexer ? What is it ? How to use it ? My project is based on Renesas RH850F1L Microcontroller. My language is 'C'. --------------------------------------- Posted through http://www.EmbeddedRelated.com
On Fri, 19 Jun 2015 13:45:16 -0500, "learn" <102059@EmbeddedRelated>
wrote:

>I'm running Renesas e2 studio version 3.1.0.24. I used to be able to set >breakpoints without any problem. > > >Today, I can't set a breakpoint. I double click on a line and nothing >happens. > >FYI, when e2 studio is closed, there is a process running e2studio.exe >*32.
Are you absolutely sure that you have compiled exactly the same version of the source code that you try to debug ?
In article <9bydndJQAZoiRhjInZ2dnUU7-VudnZ2d@giganews.com>, 102059
@EmbeddedRelated says...
> > >learn wrote: > >>> On Fri, 19 Jun 2015 13:45:16 -0500, learn wrote: > >>> > >>>> I'm running Renesas e2 studio version 3.1.0.24. I used to be able > to > >>>> set breakpoints without any problem. > >>>> > >>>> > >>>> Today, I can't set a breakpoint. I double click on a line and > nothing > >>>> happens. > >>>> > >>>> FYI, when e2 studio is closed, there is a process running > e2studio.exe > >>>> *32. > >>> > >>> I know nothing specific about your setup, but trying some combination > of
.....
> >> I shut down my computer. Now, I can set breakpoint in at least one > file > >> but I cannot set breakpoint in at least one other file. > >> > >> The breakpoint menu is enabled in file where I can set breakpoints. > >> The breakpoint menu is disabled in file where I cannot set > breakpoints. > >> > > > >Was the file you cannot set breakpoints in compiled without debug turned > >on ? IOW, make sure you're using the "debug" build or whatever > >the toolchain requires to turn on debug and rebuild everything. > > > >On the Gnu toolchain, it's the "-g" option. Many compilers use the GNU > >options. Capture the output from your build and make sure the right > >options are set. > > > > > >> The code is running fine in the debugger.
....
> > I used to be able to hover over local variable to see it's value. Now, I > cannot hover over local variables in the debugger. However, in eclipse > IDE I can hover over local variables and see information. I think > something is not setup correctly in my debugger. Do I need to do > something with the Indexer ? What is it ? How to use it ? > > My project is based on Renesas RH850F1L Microcontroller. My language is > 'C'.
Check the code is not a library module, all modules have NO optimistaion and debug mode set. You may be hovering over variable or code that has been optimised away. -- Paul Carpenter | paul@pcserviceselectronics.co.uk <http://www.pcserviceselectronics.co.uk/> PC Services <http://www.pcserviceselectronics.co.uk/pi/> Raspberry Pi Add-ons <http://www.pcserviceselectronics.co.uk/fonts/> Timing Diagram Font <http://www.badweb.org.uk/> For those web sites you hate
>In article <9bydndJQAZoiRhjInZ2dnUU7-VudnZ2d@giganews.com>, 102059 >@EmbeddedRelated says... >> >> >learn wrote: >> >>> On Fri, 19 Jun 2015 13:45:16 -0500, learn wrote: >> >>> >> >>>> I'm running Renesas e2 studio version 3.1.0.24. I used to be
able
>> to >> >>>> set breakpoints without any problem. >> >>>> >> >>>> >> >>>> Today, I can't set a breakpoint. I double click on a line and >> nothing >> >>>> happens. >> >>>> >> >>>> FYI, when e2 studio is closed, there is a process running >> e2studio.exe >> >>>> *32. >> >>> >> >>> I know nothing specific about your setup, but trying some
combination
>> of >..... >> >> I shut down my computer. Now, I can set breakpoint in at least one >> file >> >> but I cannot set breakpoint in at least one other file. >> >> >> >> The breakpoint menu is enabled in file where I can set breakpoints. >> >> The breakpoint menu is disabled in file where I cannot set >> breakpoints. >> >> >> > >> >Was the file you cannot set breakpoints in compiled without debug
turned
>> >on ? IOW, make sure you're using the "debug" build or whatever >> >the toolchain requires to turn on debug and rebuild everything. >> > >> >On the Gnu toolchain, it's the "-g" option. Many compilers use the
GNU
>> >options. Capture the output from your build and make sure the right >> >options are set. >> > >> > >> >> The code is running fine in the debugger. >.... >> >> I used to be able to hover over local variable to see it's value. Now,
I
>> cannot hover over local variables in the debugger. However, in
eclipse
>> IDE I can hover over local variables and see information. I think >> something is not setup correctly in my debugger. Do I need to do >> something with the Indexer ? What is it ? How to use it ? >> >> My project is based on Renesas RH850F1L Microcontroller. My language
is
>> 'C'. > >Check the code is not a library module, all modules have NO optimistaion
>and debug mode set. > >You may be hovering over variable or code that has been optimised away. > >-- >Paul Carpenter | paul@pcserviceselectronics.co.uk ><http://www.pcserviceselectronics.co.uk></http:> PC Services ><http://www.pcserviceselectronics.co.uk/pi></http:> Raspberry Pi
Add-ons
><http://www.pcserviceselectronics.co.uk/fonts></http:> Timing Diagram
Font
><http://www.badweb.org.uk></http:> For those web sites you hate
Now I can't set breakpoints anywhere but my application runs fine. From main menu, I go to Windows - Show Views - Disassembly. When Disassembly window opens, debugger stops responding. --------------------------------------- Posted through http://www.EmbeddedRelated.com
The 2026 Embedded Online Conference