From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: mludvig@suse.cz
Cc: gdb@sources.redhat.com
Subject: Re: Strange segfaults of gdb
Date: Fri, 12 Apr 2002 02:13:00 -0000 [thread overview]
Message-ID: <9743-Fri12Apr2002120839+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <3CB5B5F1.7010809@suse.cz> (message from Michal Ludvig on Thu, 11 Apr 2002 18:12:33 +0200)
> 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.
next prev parent reply other threads:[~2002-04-12 9:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-11 9:12 Michal Ludvig
2002-04-11 14:43 ` Michael Snyder
2002-04-12 2:13 ` Eli Zaretskii [this message]
2002-04-12 4:27 ` Michal Ludvig
2002-04-12 5:05 ` Eli Zaretskii
2002-04-16 11:16 ` Michael Snyder
2002-04-17 3:12 ` Michal Ludvig
2002-12-12 16:36 Terje Eggestad
2002-12-13 9:59 ` Michal Ludvig
[not found] ` <1039817373.10496.19.camel@eggis1>
2002-12-14 6:09 ` Michal Ludvig
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=9743-Fri12Apr2002120839+0300-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=gdb@sources.redhat.com \
--cc=mludvig@suse.cz \
/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