From: Guillaume Yziquel <guillaume.yziquel@citycable.ch>
To: gdb@sourceware.org
Subject: watchpoint hangs.
Date: Sat, 02 Jan 2010 20:55:00 -0000 [thread overview]
Message-ID: <4B3FB2BC.9040104@citycable.ch> (raw)
Hi.
I've been experiencing the following problem on amd64, Linux Debian,
with version
> yziquel@seldon:~$ gdb --version
> GNU gdb (GDB) 7.0-debian
Here it goes:
> yziquel@seldon:~/git/ocaml-monetdb5$ make gdb-native
> ocamlfind ocamlopt -g -o test/monetdb_sql.native -I . test/monetdb_sql.ml monetDB5.cmxa
> ocamlfind ocamlc -g -o test/monetdb_sql.byte test/monetdb_sql.ml monetDB5.cma
> gdb -nx -silent test/monetdb_sql.native
> Reading symbols from /home/yziquel/git/ocaml-monetdb5/test/monetdb_sql.native...(no debugging symbols found)...done.
> (gdb) set breakpoint pending on
> (gdb) break mal_init
> Breakpoint 1 at 0x403d70
> (gdb) run
> Starting program: /home/yziquel/git/ocaml-monetdb5/test/monetdb_sql.native
> [Thread debugging using libthread_db enabled]
> [New Thread 0x2aaaaf359910 (LWP 6752)]
> [Switching to Thread 0x2aaaaf359910 (LWP 6752)]
>
> Breakpoint 1, mal_init () at mal.c:52
> 52 MT_lock_init( &mal_contextLock, "mal_contextLock");
> (gdb) continue
> Continuing.
> !MALException:malInclude:could not open file: sql
> Done!
> [Thread 0x2aaaaf359910 (LWP 6752) exited]
>
> Program exited normally.
> (gdb)
OK. Fine. But when I add a watchpoint, it hangs:
> yziquel@seldon:~/git/ocaml-monetdb5$ make gdb-native
> ocamlfind ocamlopt -g -o test/monetdb_sql.native -I . test/monetdb_sql.ml monetDB5.cmxa
> ocamlfind ocamlc -g -o test/monetdb_sql.byte test/monetdb_sql.ml monetDB5.cma
> gdb -nx -silent test/monetdb_sql.native
> Reading symbols from /home/yziquel/git/ocaml-monetdb5/test/monetdb_sql.native...(no debugging symbols found)...done.
> (gdb) set breakpoint pending on
> (gdb) break mal_init
> Breakpoint 1 at 0x403d70
> (gdb) run
> Starting program: /home/yziquel/git/ocaml-monetdb5/test/monetdb_sql.native
> [Thread debugging using libthread_db enabled]
> [New Thread 0x2aaaaf359910 (LWP 7063)]
> [Switching to Thread 0x2aaaaf359910 (LWP 7063)]
>
> Breakpoint 1, mal_init () at mal.c:52
> 52 MT_lock_init( &mal_contextLock, "mal_contextLock");
> (gdb) print box
> $1 = {0x0 <repeats 64 times>}
> (gdb) watch box
> Watchpoint 2: box
> (gdb) continue
> Continuing.
And it eats up 90% of one of my CPU from now on...
All the best,
--
Guillaume Yziquel
http://yziquel.homelinux.org/
next reply other threads:[~2010-01-02 20:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-02 20:55 Guillaume Yziquel [this message]
2010-01-02 20:59 ` Jan Kratochvil
2010-01-03 23:44 ` Guillaume Yziquel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B3FB2BC.9040104@citycable.ch \
--to=guillaume.yziquel@citycable.ch \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox