On Tue, Aug 20, 2002 at 05:43:23PM +0300, Shlomi Fish wrote: > > Hi! > > I'm trying to debug a gtk+ 1.2.10 application (GImageView to be specific). > The problem is that when I type Ctrl+C and then type bt, I get the > following display: > > <<< > #0 0x4049bc74 in poll () from /lib/libc.so.6 > #1 0x402d9734 in g_source_remove_by_funcs_user_data () > from /usr/lib/libglib-1.2.so.0 > Cannot access memory at address 0x2 > >>> > > What can I do to fix it?
Make sure everything is compiled with debug symbols and frame pointers, especially glib? It looks like gdb gets confused because the stack layout is different than what it expects. If you compiled the application from source (I assume you did, not much point trying to debug it otherwise), the path of least resistance is to debug only the application code and treat its library calls as black boxes. That means figuring out what appliation code calls the functions above (or what gets called by them) and setting a break point there explicitly. > I use gdb 5.2.1 on a Mandrake Linux 8.2. (it happened with gdb > 5.1.x, too) I doubt it has anything to do with gdb versions. -- calm down, it's *only* ones and zeros. http://syscalltrack.sf.net/ http://vipe.technion.ac.il/~mulix/
msg21265/pgp00000.pgp
Description: PGP signature
