This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Strange segfaults of gdb


> Date: Thu, 11 Apr 2002 18:12:33 +0200
> From: Michal Ludvig <mludvig@suse.cz>
> 
> Breakpoint 1, main () at xmmtest.c:10
> 10              printf("v1=%f, v2=%f, v3=%e\n", v1, v2, v3);
> (gdb) p 1
> $1 = 1
> (gdb) c
> Continuing.
> Segmentation fault (core dumped)
> 
> It doesn't matter which program I run, what I want to print and if I 
> then want invoke 'run', 'continue' or even 'si'. It segfaults. Core file 
> doesn't give any reasonable informations.

You mean, you cannot even tell from the core file where (inside what
function) GDB crashes?  That'd be very strange indeed--what could
prevent you from getting att his information?  Is the core file
corrupt or something?

What if you run GDB under another GDB--can you see where does the
subordinate GDB crash then?

> Does anybody have an idea how print, set and step can be related?

It's very hard to tell without knowing where's the crash happening.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]