On Dec 10, 11:36 pm, Tom Tromey wrote:
> >>>>> "Stone" == Stone writes:
>
> Stone> However, when I debugged the code in gdb, all the ptr*'s turned to
> Stone> void*.
>
> Stone> Is there anyone knows the reason for this please?
>
>
>>>>> "Stone" == Stone writes:
Stone> However, when I debugged the code in gdb, all the ptr*'s turned to
Stone> void*.
Stone> Is there anyone knows the reason for this please?
Maybe http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45088
Tom
_
,sht);
}
}shthead[11], comp[21], tree[21];
However, when I debugged the code in gdb, all the ptr*'s turned to
void*.
There is no compile error though I didn't ever know this problem when
coding, and I have to convert the void* to ptr* to view the data in it
in gdb.
I w
Hello experts,
I am working on a new architecture. Can anyone help me regarding how to
port gdb for a new architecture?
Thank you.
--
View this message in context:
http://old.nabble.com/gdb-porting-tp27125890p27125890.html
Sent from the gcc - Gnu Help List mailing list archive at
Andre Poenitz <[EMAIL PROTECTED]> writes:
> It pretty much the behaviour one gets from g++ by default without doing
> anything fancy:
>
> #include
> int main() { throw std::logic_error("empty rule"); }
>
> produces exactly the same output.
For some (but not all) versions of gcc.
It didn't p
Paul Pluzhnikov <[EMAIL PROTECTED]> wrote:
> moongeegee <[EMAIL PROTECTED]> writes:
>
>> I am learning gdb to debug the program. As soon as I run the program,
>> it prompt me an error and terminated.
>> How to step into it or set breakpoint and find the prob
On 18 Mar, 20:47, moongeegee <[EMAIL PROTECTED]> wrote:
> I am learning gdb to debug the program. As soon as I run the program,
> it prompt me an error and terminated.
> How to step into it or set breakpoint and find the problem. Thanks.
>
> (gdb) run
> Starting program
moongeegee <[EMAIL PROTECTED]> writes:
> I am learning gdb to debug the program. As soon as I run the program,
> it prompt me an error and terminated.
> How to step into it or set breakpoint and find the problem. Thanks.
You may get better answers if you specify which platfor
I am learning gdb to debug the program. As soon as I run the program,
it prompt me an error and terminated.
How to step into it or set breakpoint and find the problem. Thanks.
(gdb) run
Starting program: /usr/home/grp/gramtest < inputdata
terminate called after throwing an instance of &
On Feb 27, 12:21 pm, Paul Pluzhnikov <[EMAIL PROTECTED]>
wrote:
> Did you compile the OTL and ospace libraries yourself, and with
> the same version of g++ you used for the rest of the application?
>
> If you are using pre-compiled binaries, chances are there is a g++
> version mis-match, which ca
[EMAIL PROTECTED] writes:
> On Feb 25, 4:07 am, Paul Pluzhnikov <[EMAIL PROTECTED]> wrote:
>> You should at least post the gdb backtrace -- it may not give you any
>> clues, but may give someone else a good idea of what you are seeing.
>
> Here is the (big) backtra
On Feb 25, 4:07 am, Paul Pluzhnikov <[EMAIL PROTECTED]> wrote:
> You should at least post the gdb backtrace -- it may not give you any
> clues, but may give someone else a good idea of what you are seeing.
Here is the (big) backtrace (with some names changed):
#0 0x0837e037
h
'export LD_LIBRARY_PATH=/usr/lib/debug'
2. You may have installed libstdc++.N.debug debug-info file into
/usr/lib/debug/usr/lib/...
In that case, all you should need is a version of gdb that
understands debuginfo files.
Since you referred to RH-7.2 errata, it sounds like you are
On Feb 24, 10:40 pm, Paul Pluzhnikov <[EMAIL PROTECTED]>
wrote:
> Naam Nahin <[EMAIL PROTECTED]> writes:
> > To get the debug version of libstdc++,
> > I installed the debug library and passed in -D_GLIBCXX_DEBUG as
> > a command line parameter.
>
> Installed where?
The debug versions are installe
Naam Nahin <[EMAIL PROTECTED]> writes:
> To get the debug version of libstdc++,
> I installed the debug library and passed in -D_GLIBCXX_DEBUG as
> a command line parameter.
Installed where?
Also, '-D_GLIBCXX_DEBUG' has nothing to do with your problem --
it's a flag that enables various STL asse
Paul Pluzhnikov wrote:
"naam nahin" <[EMAIL PROTECTED]> writes
I am trying to debug a C++ program on Linux. g++ version is 4.1.3.
While debugging the program under gdb, I get a SIGABRT with the following
backtrace:
#4 0xb7ef0f65 in ?? () from /usr/lib/libstdc++.so.6
Paul Pluzhnikov wrote:
Jeff Schwab <[EMAIL PROTECTED]> writes:
Why can't gdb show me the function name for that function?
Because it can't find the debug symbols for the file.
Gdb doen't need any debug symbols to deduce function name:
$ cat t.c && gcc t.c &am
Jeff Schwab <[EMAIL PROTECTED]> writes:
>> Why can't gdb show me the function name for that function?
>
> Because it can't find the debug symbols for the file.
Gdb doen't need any debug symbols to deduce function name:
$ cat t.c && gcc t.c && gd
Paul Pluzhnikov <[EMAIL PROTECTED]> writes:
> "naam nahin" <[EMAIL PROTECTED]> writes:
>> It is expected because I am not catching the exception I am throwing.
> It may be expected, but it is *not* happening.
Oops. I misread Naam's statement; please ignore the 'not happening'
part of my post.
Ch
"naam nahin" <[EMAIL PROTECTED]> writes:
> I am trying to debug a C++ program on Linux. g++ version is 4.1.3.
> While debugging the program under gdb, I get a SIGABRT with the following
> backtrace:
> #0 0xe410 in __kernel_vsyscall ()
> #1 0xb7ce7875 in r
naam nahin wrote:
Hi,
I am trying to debug a C++ program on Linux. g++ version is 4.1.3.
While debugging the program under gdb, I get a SIGABRT with the
following backtrace:
#0 0xe410 in __kernel_vsyscall ()
#1 0xb7ce7875 in raise () from /lib/tls/i686/cmov/libc.so.6
#2 0xb7ce9201 in
Hi,
I am trying to debug a C++ program on Linux. g++ version is 4.1.3.
While debugging the program under gdb, I get a SIGABRT with the following
backtrace:
#0 0xe410 in __kernel_vsyscall ()
#1 0xb7ce7875 in raise () from /lib/tls/i686/cmov/libc.so.6
#2 0xb7ce9201 in abort () from /lib
Or simply I have a.hh and .cc file.How can I break in it.
I tried
break readelement.cc:20
Then I got the error "No source file named readelement.cc."
Even though the file is in the same folder as where I ran the command
___
help-gplusplus mailing list
he
I am using trying to run the click modular router in debug mode.
So I had complied it.
And then I had stated gdb using
gdb click
then I had set the break point
b elementname:line_num
then I get the above error.
Does it make sense?.
Do you want to see the make file
On Feb 19, 8:20 am, Jeff Schwab <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
> > Hi all,
> > I am used to following command to compile
> > g++ -W -Wall -g -O2 -o
>
> > But when I start setting the breakpoint with gdb I get the error
> > No symbo
"Neo" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Hi,
> I am trying to debug a piece of code which is giving the error as
> 'illegal instruction' when executed. But I am having trouble while
> using GDB or DD because of this error-
>
Hi,
I am trying to debug a piece of code which is giving the error as
'illegal instruction' when executed. But I am having trouble while
using GDB or DD because of this error-
"loading shared libraries: libstdc++.so.6: cannot open shared object
file: No such file or directory"
with gdb 6.3 i am able to attach process and debug them, but not with
6.6
Is there some known issue.,
i can recreate it with gdb 6.6 with our internal code.
I will try to do it with some other file, if it not a known issue
-Parag
___
help-gplusplus
On Thu, 2007-11-15 at 14:32 -0800, [EMAIL PROTECTED] wrote:
> I want to step 3 times and then set a=1 in the function stack then
>
> Can it be done. I think expect scripts will do fine, but is there any
> gdb thing
Use the "commands" command to input a set of commands that
hi All,
Can there be stop points, where we can change a value after some
steps,
LIke stop func1()
I want to step 3 times and then set a=1 in the function stack then
Can it be done. I think expect scripts will do fine, but is there any
gdb thing
-Parag
I am using gdb. 6.6 for the last few months,
The load time is pretty high for it,
How are the bugs in the GDB maintained, What about the performance
data, Is there anyway to track it,
Some Benchmarks on them , so that we can take a look at it and may be
forgo some latest features but use a
I did not find a /usr/lib/debug
But the following in gdb prompt for gdb-6.6 does show about /usr/lib/
debug,
show debug-file-directory
The directory where separate debug symbols are searched for is "/usr/
lib/debug".show debug-file-directory
__
Thanks a lot Paul
That helps
-Parag
___
help-gplusplus mailing list
help-gplusplus@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gplusplus
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes:
> Is there any GDB variable that will stop this from coming so that I
> see these output continuously
RTFM:
`set height LPP'
`show height'
`set width CPL'
`show width'
These `set' comm
I have for loop in GDb that should show the pointer to an object
Now my output is waiting for an user "Enter" to go ahead. See below.
Is there any GDB variable that will stop this from coming so that I
see these output continuously
mdaNet = 0,
refVar = 0,
co
GDB is not stepping into some function.
I think it is a C++ function call from a C routine.
Are there issues
I am using gdb -6.6
___
help-gplusplus mailing list
help-gplusplus@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gplusplus
For a huge design,
when I am trying some thing like
b '::(
it starts giving a huge list which cannot be interrupted. For huge
code base this can be painful till it alpahbetially or some other
predefined order shows all possible functions
I had to kill one gdb sessio after 2 hou
I am using the following GDB
GNU gdb Red Hat Linux (6.3.0.0-0.30.1rh)
But all my gdb commands end up giving me the following sequence of
infrun messages
infrun: resume (step=0, signal=0)
infrun: wait_for_inferior
infrun: infwait_normal_state
infrun: TARGET_WAITKIND_STOPPED
infrun: stop_pc
On Sep 26, 9:54 pm, Paul Pluzhnikov <[EMAIL PROTECTED]>
wrote:
> mathieu <[EMAIL PROTECTED]> writes:
> > I think I misunderstood how to set hardware breakpoint in gdb. I
> > would usually do:
>
> > gdb> hb *((int*)0x0123456)
>
> This is exactly the
hi All,
I am using GDB GNU gdb Red Hat Linux (6.3.0.0-0.30.1rh)
Is this haivng some compatibility issues with RH4 machines.
Can anybody point me out to a better version of GDB,
With ddd, I am not able to do proper up and down and the frame in DDD
remains stuck and does not refresh,
Whereas a
mathieu <[EMAIL PROTECTED]> writes:
> I think I misunderstood how to set hardware breakpoint in gdb. I
> would usually do:
>
> gdb> hb *((int*)0x0123456)
This is exactly the same as 'break *0x0123456' on platforms that
have hardware breakpoint instruction (wh
Hello,
I think I misunderstood how to set hardware breakpoint in gdb. I
would usually do:
gdb> hb *((int*)0x0123456)
For some reason this is not working anymore:
(gdb) p output.MTime.ModifiedTime
$14 = 1339
(gdb) p &output.MTime.ModifiedTime
$15 = (long unsigned int *) 0x80da27c
(
> sorry for bothering here, but can anyone tell me *the* current newsgroups
> or forums for questions/bugs concerning gdb?
You can try http://lists.gnu.org/mailman/listinfo/gdb. Always check the
GNU mailing lists at http://lists.gnu.org/mailman/listinfo, which has a
complete list of m
Hi,
sorry for bothering here, but can anyone tell me *the* current newsgroups
or forums for questions/bugs concerning gdb?
gmane.comp.gdb.general seems to be rather low traffic, and
gmane.comp.gdb.bugs.general to contain barely more than spam...
Thanks,
Ulrich
uot; but if I include the FOO,
whatis bar = foo ** and print *(foo *) bar works.
And
Class A {};
Class B : public A{};
A *ptr = new B();
print *(B*) ptr give a syntax error at 'B*) ptr'.
If they aren't bugs in g++ and/or gdb, how do I work around them.
Both examples are valid
ing problems with
> the GDB.
> The application has a 'runtime error' or in other words, it has a
> segmentation
> fault, to find out which method call caused the segmentation fault
> [sf], I typed gdb Jaime.exe -> run [the sf occurs] -> bt... then
> the words &quo
Sorry, but I don't know where else to find C++ programmers who, without
a doubt, will be able to help me with this problem.
I am developing a GUI [GTKMM] under MS Window XP, and since I am not
familiar with the development aspect of MSW I am having problems with
the GDB.
The application
Since using the G++ 4.0.3, my GDB 6.4 is unable to use the "catch
throw" or "catch catch" commands - telling me "__cxa_throw" /
"__cxa_begin_catch" not found.
With G++ 3.3.6 this works fine, so I think this is an compiler issue,
not an issue of GDB.
When u
Ulrich Lauther wrote:
> I use g++ 4.1.0 and gdb 6.4.0, compile with -g and no optimization
> flags. Often, I get
> No symbol "foo" in current context.
> when foo is definitely in the scope.
>
> Is this a common problem? Any workaround?
Perhaps a name mangling probl
Maurizio Loreti wrote:
Ulrich Lauther <[EMAIL PROTECTED]> writes:
Is this a common problem?
no
When I used g++ I used to see that all the time. Never did figure out
what was wrong, and most people I asked said what you heard: "it doesn't
happen to me". It was unpredictable. I b
Ulrich Lauther <[EMAIL PROTECTED]> writes:
> Is this a common problem?
no
--
Maurizio Loreti http://www.pd.infn.it/~loreti/mlo.html
Dept. of Physics, Univ. of Padova, Italy ROT13: [EMAIL PROTECTED]
___
help-gpluspl
I use g++ 4.1.0 and gdb 6.4.0, compile with -g and no optimization flags.
Often, I get
No symbol "foo" in current context.
when foo is definitely in the scope.
Is this a common problem? Any workaround?
Cheers
--
-lauthe
Paul Pluzhnikov wrote:
> "swagat" <[EMAIL PROTECTED]> writes:
>
> > I don't know if it is the right forum to ask for gdb problems. IF it is
> > not, please do let me know.
>
> Asking in OS-specific group (and indicating what OS you are on)
> may yi
"swagat" <[EMAIL PROTECTED]> writes:
> I don't know if it is the right forum to ask for gdb problems. IF it is
> not, please do let me know.
Asking in OS-specific group (and indicating what OS you are on)
may yield better results.
> In my c++ program, a particular
Hi all!
I don't know if it is the right forum to ask for gdb problems. IF it is
not, please do let me know.
In my c++ program, a particular variable takes up "nan" value after
sometime. I want my program to stop executing at a line where it takes
up a NAN value.
How can I use
THANKS
___
Help-gplusplus mailing list
Help-gplusplus@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gplusplus
"Linda" <[EMAIL PROTECTED]> writes:
> So I cannot debug normally. But if I change CCC to g++, gdb can work
> normally. So is the version of the compiler is crucial for gdb?
No, it's not. However you should read "man CC", and pay extra
attention to the
) -o $@ $?
clean:
rm -f *.o
rm main
After I type "make" on the screen, I got its executable file named
main.
But when I type "gdb main", I got:
GNU gdb 5.0
Copyright 2000 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public
Paul Pluzhnikov <[EMAIL PROTECTED]> writes:
> Maurizio Loreti <[EMAIL PROTECTED]> writes:
>
> > Paul Pluzhnikov <[EMAIL PROTECTED]> writes:
> >
> >> current gdb is 6.3
> >
> > 6.4
>
> According to what source?
ftp://ftp.gnu.
[EMAIL PROTECTED] writes:
> Can anyone confim if this problem is fixed in 6.3.
Not without you telling us what OS you are on (appears to be some
version of Solaris) and which compiler (version) you used to compile
the test case with (appears to be g++ 2.9x).
Cheers,
--
In order to understand r
Maurizio Loreti <[EMAIL PROTECTED]> writes:
> Paul Pluzhnikov <[EMAIL PROTECTED]> writes:
>
>> current gdb is 6.3
>
> 6.4
According to what source?
http://www.gnu.org/software/gdb/ still says 6.3.
Apparently "real" gdb home is somewhere else ...
Aha http
Paul Pluzhnikov <[EMAIL PROTECTED]> writes:
> current gdb is 6.3
6.4
--
Maurizio Loreti http://www.pd.infn.it/~loreti/mlo.html
Dept. of Physics, Univ. of Padova, Italy ROT13: [EMAIL PROTECTED]
___
Help-
Ok, I should have said I am calling the function d.foo(). I think it is
perfectly valid in gdb to call a function that does not return
anything.
Even if I change void to int and have proper return values. and gdb
crashes with Segmentation fault
Program received signal SIGSEGV, Segmentation
[EMAIL PROTECTED] writes:
> GDB crashes when I'm trying to print a function.
You are not trying to "print a function".
You are trying to print return value from a void function, which
itself is not very meaningful (but should not cause debugger
to crash).
> Here is the c
GDB crashes when I'm trying to print a function.
Here is the code snippet. When I'm trying to print "d.foo()" in main
function from GDB, it crashes. I'm using GNU gdb 4.18. Is there anyway
to prevent this crash (without making changes to the code)?
#include
using na
it?
You don't write what OS you're using, but if you happen to run something
Unix-ish, and if you are really really desperate, you could try to force
a core dump. Using this core dump, and the exact binary that produced it,
gdb can perform a post-mortem analysis. Sometimes. If you'
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes:
> Suppose it takes me a lot of time to reach the bug code. I don't want
> to run the program again and again.
If you have a good idea where the bug is, you can make your program
skip steps and get to the problem faster.
> Is there any way to dump t
Hi,
Suppose it takes me a lot of time to reach the bug code. I don't want
to run the program again and again. Is there any way to dump the
internal information to the disk? And then load it when I need it?
I heard it is possible. Would you help me?
Best wishes,
Peng
cout<<"not digit ,once more"<>i;
(gdb) s //here ,no chance to input anything.
(gdb) s
(gdb) s
not digit ,once more
(gdb) s
i=4
(gdb) s
(gdb) s
bad boy
(gdb) s //no chance to input anything,there is no prompt for input.
(gdb) s
(gdb) s
not digit ,once more
(gdb) s
i=4
(gdb)
Hello!
I'm compiling a project using g++ 3.3.2.
GDB (v6.3) gives me a message like:
warning: RTTI symbol not found for class 'xx:yy'
Where xx is the namespace and yy the class name.
The whole project is being compiled with the
same flags and other classes have the RTTI inform
"Hansen" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Hi everybody
>
> I know that this isn't the gdb group, but since that one, seemed kind of
> dead, I'll try in here.
>
> I'm using the arm-elf-gdb to debug a program for a LPC21
Hi everybody
I know that this isn't the gdb group, but since that one, seemed kind of
dead, I'll try in here.
I'm using the arm-elf-gdb to debug a program for a LPC2138, but when I start
debugging and tell gdb to set a breakpoint at main, it sets the breakpoint
at line 13
72 matches
Mail list logo
