Home » Language IDEs » C / C++ IDE (CDT) » Debugger terminates unexpectantly
| Debugger terminates unexpectantly [message #70780] |
Mon, 19 May 2003 22:08  |
Eclipse User |
|
|
|
Originally posted by: jmiller.incon.com
Hi folks,
Been working today on getting my cross development environment going on my
Power PC. Except for a little pesky snag where I had to modify the
mi.core plugin.xml, setting cpp to "ppc" .... the IDE is very slick!!! As
I step through code with the debugger, I get the following message:
../../insight-5.3/ui-out.c:130: gdb-internal-error: push_level: Assertion
`uiout->level >= 0 && uiout->level < MAX_UI_OUT_LEVELS' failed.
I found that they had this problem in the hurd user group and recommneded
cranking up MAX_UI_OUT_LEVELS. Originally set to 5, I raised it to 12,
which got me farther along debugging the "HelloWorld" demo, now I've
cranked it up to 32. At this point I'm able to completely step through
the entire program, but am sure that this not the best solution.
OS is Redhat8.0
Eclipse is latest and greatest as is cdt (2.1 and 1.1 respective, I think)
gdb is version5.3
Any suggestions on a more appropriate solution to the MAX_UI_OUT_LEVELS
issue?
cheers
|
|
|
| Re: Debugger terminates unexpectantly [message #70860 is a reply to message #70780] |
Tue, 20 May 2003 15:12  |
| Eclipse User |
|
|
|
Originally posted by: mikhailk.qnx.com
CDT uses legitimate gdb commands to communicate with gdb. What you are
getting is an internal gdb error and has to be fixed in gdb.
BTW, are there messages in the gdb console? Check the "Show Debugger Console
On Target Selection" button of the "Debug" view's toolbar to switch between
the inferrior and gdb outputs.
"John Miller" <jmiller@incon.com> wrote in message
news:babklb$bv$1@rogue.oti.com...
> Hi folks,
>
> Been working today on getting my cross development environment going on my
> Power PC. Except for a little pesky snag where I had to modify the
> mi.core plugin.xml, setting cpp to "ppc" .... the IDE is very slick!!! As
> I step through code with the debugger, I get the following message:
>
> ./../insight-5.3/ui-out.c:130: gdb-internal-error: push_level: Assertion
> `uiout->level >= 0 && uiout->level < MAX_UI_OUT_LEVELS' failed.
>
> I found that they had this problem in the hurd user group and recommneded
> cranking up MAX_UI_OUT_LEVELS. Originally set to 5, I raised it to 12,
> which got me farther along debugging the "HelloWorld" demo, now I've
> cranked it up to 32. At this point I'm able to completely step through
> the entire program, but am sure that this not the best solution.
>
> OS is Redhat8.0
> Eclipse is latest and greatest as is cdt (2.1 and 1.1 respective, I think)
> gdb is version5.3
>
> Any suggestions on a more appropriate solution to the MAX_UI_OUT_LEVELS
> issue?
>
>
> cheers
>
>
>
>
|
|
|
| Re: Debugger terminates unexpectantly [message #71022 is a reply to message #70860] |
Wed, 21 May 2003 13:20 |
| Eclipse User |
|
|
|
Originally posted by: jmiller.incon.com
Hi Mikhail,
Yes, I did check the output, that is where the error message below comes
from, clueing me into the fact that maybe I should crank up
MAX_UI_OUT_LEVELS. I will post this on a GDB newsgroup to see if they
have any ideas. Regards
Mikhail Khodjaiants wrote:
> CDT uses legitimate gdb commands to communicate with gdb. What you are
> getting is an internal gdb error and has to be fixed in gdb.
> BTW, are there messages in the gdb console? Check the "Show Debugger Console
> On Target Selection" button of the "Debug" view's toolbar to switch between
> the inferrior and gdb outputs.
> "John Miller" <jmiller@incon.com> wrote in message
> news:babklb$bv$1@rogue.oti.com...
> > Hi folks,
> >
> > Been working today on getting my cross development environment going on my
> > Power PC. Except for a little pesky snag where I had to modify the
> > mi.core plugin.xml, setting cpp to "ppc" .... the IDE is very slick!!! As
> > I step through code with the debugger, I get the following message:
> >
> > ./../insight-5.3/ui-out.c:130: gdb-internal-error: push_level: Assertion
> > `uiout->level >= 0 && uiout->level < MAX_UI_OUT_LEVELS' failed.
> >
> > I found that they had this problem in the hurd user group and recommneded
> > cranking up MAX_UI_OUT_LEVELS. Originally set to 5, I raised it to 12,
> > which got me farther along debugging the "HelloWorld" demo, now I've
> > cranked it up to 32. At this point I'm able to completely step through
> > the entire program, but am sure that this not the best solution.
> >
> > OS is Redhat8.0
> > Eclipse is latest and greatest as is cdt (2.1 and 1.1 respective, I think)
> > gdb is version5.3
> >
> > Any suggestions on a more appropriate solution to the MAX_UI_OUT_LEVELS
> > issue?
> >
> >
> > cheers
> >
> >
> >
> >
|
|
|
| Re: Debugger terminates unexpectantly [message #71041 is a reply to message #71022] |
Wed, 21 May 2003 14:55 |
| Eclipse User |
|
|
|
Originally posted by: mikhailk.qnx.com
You can run Eclipse with tracing to find out which of gdb commands causes
the problem.
To run with tracing:
1. Create a file (for example, .options)
2. Add the following line to it:
org.eclipse.cdt.debug.mi.core/debug=true
3. Start Eclipse with
-debug "file:<full path>/.options"
You will see all gdb commands that CDT sends to gdb.
"John Miller" <jmiller@incon.com> wrote in message
news:bafufh$ff8$1@rogue.oti.com...
> Hi Mikhail,
>
> Yes, I did check the output, that is where the error message below comes
> from, clueing me into the fact that maybe I should crank up
> MAX_UI_OUT_LEVELS. I will post this on a GDB newsgroup to see if they
> have any ideas. Regards
>
> Mikhail Khodjaiants wrote:
>
> > CDT uses legitimate gdb commands to communicate with gdb. What you are
> > getting is an internal gdb error and has to be fixed in gdb.
> > BTW, are there messages in the gdb console? Check the "Show Debugger
Console
> > On Target Selection" button of the "Debug" view's toolbar to switch
between
> > the inferrior and gdb outputs.
>
> > "John Miller" <jmiller@incon.com> wrote in message
> > news:babklb$bv$1@rogue.oti.com...
> > > Hi folks,
> > >
> > > Been working today on getting my cross development environment going
on my
> > > Power PC. Except for a little pesky snag where I had to modify the
> > > mi.core plugin.xml, setting cpp to "ppc" .... the IDE is very slick!!!
As
> > > I step through code with the debugger, I get the following message:
> > >
> > > ./../insight-5.3/ui-out.c:130: gdb-internal-error: push_level:
Assertion
> > > `uiout->level >= 0 && uiout->level < MAX_UI_OUT_LEVELS' failed.
> > >
> > > I found that they had this problem in the hurd user group and
recommneded
> > > cranking up MAX_UI_OUT_LEVELS. Originally set to 5, I raised it to
12,
> > > which got me farther along debugging the "HelloWorld" demo, now I've
> > > cranked it up to 32. At this point I'm able to completely step
through
> > > the entire program, but am sure that this not the best solution.
> > >
> > > OS is Redhat8.0
> > > Eclipse is latest and greatest as is cdt (2.1 and 1.1 respective, I
think)
> > > gdb is version5.3
> > >
> > > Any suggestions on a more appropriate solution to the
MAX_UI_OUT_LEVELS
> > > issue?
> > >
> > >
> > > cheers
> > >
> > >
> > >
> > >
>
>
>
>
>
|
|
|
| Re: Debugger terminates unexpectantly [message #71140 is a reply to message #71041] |
Thu, 22 May 2003 16:26 |
| Eclipse User |
|
|
|
Originally posted by: jmiller.incon.com
Thanks,
The gdb news groups seem to be dead so I searched on the Problem Reports
and found that a colleauge of yours was running into the same types of
problems, alain@qnx.com. S/He submitted PR\'s 1045 and 796, neither
which has been resolved yet. I also created a PR, #1223. The trace
information should be very useful, Thanks again.
Mikhail Khodjaiants wrote:
> You can run Eclipse with tracing to find out which of gdb commands causes
> the problem.
> To run with tracing:
> 1. Create a file (for example, .options)
> 2. Add the following line to it:
> org.eclipse.cdt.debug.mi.core/debug=true
> 3. Start Eclipse with
> -debug \"file:<full path>/.options\"
> You will see all gdb commands that CDT sends to gdb.
> \"John Miller\" <jmiller@incon.com> wrote in message
> news:bafufh$ff8$1@rogue.oti.com...
> > Hi Mikhail,
> >
> > Yes, I did check the output, that is where the error message below comes
> > from, clueing me into the fact that maybe I should crank up
> > MAX_UI_OUT_LEVELS. I will post this on a GDB newsgroup to see if they
> > have any ideas. Regards
> >
> > Mikhail Khodjaiants wrote:
> >
> > > CDT uses legitimate gdb commands to communicate with gdb. What you are
> > > getting is an internal gdb error and has to be fixed in gdb.
> > > BTW, are there messages in the gdb console? Check the \"Show Debugger
> Console
> > > On Target Selection\" button of the \"Debug\" view\'s toolbar to switch
> between
> > > the inferrior and gdb outputs.
> >
> > > \"John Miller\" <jmiller@incon.com> wrote in message
> > > news:babklb$bv$1@rogue.oti.com...
> > > > Hi folks,
> > > >
> > > > Been working today on getting my cross development environment going
> on my
> > > > Power PC. Except for a little pesky snag where I had to modify the
> > > > mi.core plugin.xml, setting cpp to \"ppc\" .... the IDE is very
slick!!!
> As
> > > > I step through code with the debugger, I get the following message:
> > > >
> > > > ./../insight-5.3/ui-out.c:130: gdb-internal-error: push_level:
> Assertion
> > > > `uiout->level >= 0 && uiout->level < MAX_UI_OUT_LEVELS\' failed.
> > > >
> > > > I found that they had this problem in the hurd user group and
> recommneded
> > > > cranking up MAX_UI_OUT_LEVELS. Originally set to 5, I raised it to
> 12,
> > > > which got me farther along debugging the \"HelloWorld\" demo, now I\'ve
> > > > cranked it up to 32. At this point I\'m able to completely step
> through
> > > > the entire program, but am sure that this not the best solution.
> > > >
> > > > OS is Redhat8.0
> > > > Eclipse is latest and greatest as is cdt (2.1 and 1.1 respective, I
> think)
> > > > gdb is version5.3
> > > >
> > > > Any suggestions on a more appropriate solution to the
> MAX_UI_OUT_LEVELS
> > > > issue?
> > > >
> > > >
> > > > cheers
> > > >
> > > >
> > > >
> > > >
> >
> >
> >
> >
> >
|
|
|
| Re: Debugger terminates unexpectantly [message #71199 is a reply to message #70780] |
Thu, 22 May 2003 21:09 |
| Eclipse User |
|
|
|
Originally posted by: jmiller.incon.com
Hi folks,
I solved this issue (with some help!). fetch the latest version of gdb
from the "Mainline" and the problem does not occur. the version I used is
insight+dejagnu-weekly-CVS-20030520.tar.bz2 from
ftp://sources.redhat.com/pub/gdb/snapshots/current/
thanks to those involved.
John
John Miller wrote:
> Hi folks,
> Been working today on getting my cross development environment going on my
> Power PC. Except for a little pesky snag where I had to modify the
> mi.core plugin.xml, setting cpp to "ppc" .... the IDE is very slick!!! As
> I step through code with the debugger, I get the following message:
> ../../insight-5.3/ui-out.c:130: gdb-internal-error: push_level: Assertion
> `uiout->level >= 0 && uiout->level < MAX_UI_OUT_LEVELS' failed.
> I found that they had this problem in the hurd user group and recommneded
> cranking up MAX_UI_OUT_LEVELS. Originally set to 5, I raised it to 12,
> which got me farther along debugging the "HelloWorld" demo, now I've
> cranked it up to 32. At this point I'm able to completely step through
> the entire program, but am sure that this not the best solution.
> OS is Redhat8.0
> Eclipse is latest and greatest as is cdt (2.1 and 1.1 respective, I think)
> gdb is version5.3
> Any suggestions on a more appropriate solution to the MAX_UI_OUT_LEVELS
> issue?
> cheers
|
|
|
| Re: Debugger terminates unexpectantly [message #71219 is a reply to message #71140] |
Thu, 22 May 2003 21:11 |
| Eclipse User |
|
|
|
Originally posted by: jmiller.incon.com
Hi folks,
I solved this issue (with some help!). fetch the latest version of gdb
from the "Mainline" and the problem does not occur. the version I used is
insight+dejagnu-weekly-CVS-20030520.tar.bz2 from
ftp://sources.redhat.com/pub/gdb/snapshots/current/
thanks to those involved.
John
John Miller wrote:
> Thanks,
> The gdb news groups seem to be dead so I searched on the Problem Reports
> and found that a colleauge of yours was running into the same types of
> problems, alain@qnx.com. S/He submitted PR\'s 1045 and 796, neither
> which has been resolved yet. I also created a PR, #1223. The trace
> information should be very useful, Thanks again.
> Mikhail Khodjaiants wrote:
> > You can run Eclipse with tracing to find out which of gdb commands causes
> > the problem.
> > To run with tracing:
> > 1. Create a file (for example, .options)
> > 2. Add the following line to it:
> > org.eclipse.cdt.debug.mi.core/debug=true
> > 3. Start Eclipse with
> > -debug \"file:<full path>/.options\"
> > You will see all gdb commands that CDT sends to gdb.
> > \"John Miller\" <jmiller@incon.com> wrote in message
> > news:bafufh$ff8$1@rogue.oti.com...
> > > Hi Mikhail,
> > >
> > > Yes, I did check the output, that is where the error message below comes
> > > from, clueing me into the fact that maybe I should crank up
> > > MAX_UI_OUT_LEVELS. I will post this on a GDB newsgroup to see if they
> > > have any ideas. Regards
> > >
> > > Mikhail Khodjaiants wrote:
> > >
> > > > CDT uses legitimate gdb commands to communicate with gdb. What you are
> > > > getting is an internal gdb error and has to be fixed in gdb.
> > > > BTW, are there messages in the gdb console? Check the \"Show Debugger
> > Console
> > > > On Target Selection\" button of the \"Debug\" view\'s toolbar to switch
> > between
> > > > the inferrior and gdb outputs.
> > >
> > > > \"John Miller\" <jmiller@incon.com> wrote in message
> > > > news:babklb$bv$1@rogue.oti.com...
> > > > > Hi folks,
> > > > >
> > > > > Been working today on getting my cross development environment going
> > on my
> > > > > Power PC. Except for a little pesky snag where I had to modify the
> > > > > mi.core plugin.xml, setting cpp to \"ppc\" .... the IDE is very
> slick!!!
> > As
> > > > > I step through code with the debugger, I get the following message:
> > > > >
> > > > > ./../insight-5.3/ui-out.c:130: gdb-internal-error: push_level:
> > Assertion
> > > > > `uiout->level >= 0 && uiout->level < MAX_UI_OUT_LEVELS\' failed.
> > > > >
> > > > > I found that they had this problem in the hurd user group and
> > recommneded
> > > > > cranking up MAX_UI_OUT_LEVELS. Originally set to 5, I raised it to
> > 12,
> > > > > which got me farther along debugging the \"HelloWorld\" demo, now
I\'ve
> > > > > cranked it up to 32. At this point I\'m able to completely step
> > through
> > > > > the entire program, but am sure that this not the best solution.
> > > > >
> > > > > OS is Redhat8.0
> > > > > Eclipse is latest and greatest as is cdt (2.1 and 1.1 respective, I
> > think)
> > > > > gdb is version5.3
> > > > >
> > > > > Any suggestions on a more appropriate solution to the
> > MAX_UI_OUT_LEVELS
> > > > > issue?
> > > > >
> > > > >
> > > > > cheers
> > > > >
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >
> > >
> > >
|
|
|
Goto Forum:
Current Time: Sat Aug 10 07:32:47 GMT 2024
Powered by FUDForum. Page generated in 0.03791 seconds |
] 
Search
Help
Register
Login
Home
