This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
gdb 5.2.1-4, gcc 3.2-7 and lyx thread problem
- From: Ben Stanley <bds02 at uow dot edu dot au>
- To: gdb at sources dot redhat dot com
- Date: 20 Nov 2002 08:39:30 +1100
- Subject: gdb 5.2.1-4, gcc 3.2-7 and lyx thread problem
- Organization: University of Wollongong
Hi,
I was trying to use gdb on lyx-1.3.0cvs. I would place a breakpoint in
the lyx code (Counter::reset) and run until the program hit the
breakpoint. When that happened, gdb went crazy:
(gdb) run
[New Thread 8192 (LWP 26110)]
Unknown token, keepLyXAspectRatio, skipping.
Unknown token, keepLyXAspectRatio, skipping.
[New Cannot find thread 16385: invalid thread handle
This LyX was built with the Qt front end, and I'm told by the LyX
developers that only a single thread is used.
I then tried to find out what's going on with the threads:
(gdb) info threads
* 1 Thread 8192 (LWP 26128) [No stack.]
lyx: SIGHUP signal caught
Segmentation fault
The segmentation fault was actually gdb, not lyx (reported by ddd).
Thus gdb is becoming internally corrupted when I use it on LyX.
I'm wondering if upgrading gdb to the latest cvs version might help
here. I'm currently using the version that comes with RH-8.0.
LyX uses lots of advanced C++.
I also have a problem with the following:
(gdb) list Counters::reset
[0] cancel
[1] all
[2] Counters::reset(std::string const&) at counters.C:174
[3] Counters::reset() at counters.C:164
That output is correct. However, trying to set a breakpoint is wrong:
(gdb) break 'Counters::reset'
[0] cancel
[1] all
[2] Counters::reset(std::string const&) at
/usr/include/c++/3.2/bits/basic_string.h:229
[3] Counters::reset() at /usr/include/c++/3.2/bits/stl_tree.h:651
This gives incorrect information on the source location of these
functions.
Quoted and unquoted versions of each command give the same answers.
Thanks for any help.
Ben.
--
Ben Stanley, PhD candidate
School of Information Technology and Computer Science
University of Wollongong