Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: David Lecomber <david@streamline-computing.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Daniel Jacobowitz <drow@false.org>,
	patches <gdb-patches@sources.redhat.com>
Subject: Re: [PATCH] Seg fault whilst stepping when watch set [ping!] [in  breakpoint.c]
Date: Sun, 21 Nov 2004 00:24:00 -0000	[thread overview]
Message-ID: <1100996751.22991.39.camel@cpc2-oxfd5-5-0-cust91.oxfd.cable.ntl.com> (raw)
In-Reply-To: <01c4cef8$Blat.v2.2.2$3fd12960@zahav.net.il>

> Also, last time we talked, I asked whether this could be due to the
> Fedora exec-shield feature, but didn't see any response to that.
> Could you please check that?

I'm not sure how to verify that one - the seg fault happens running as
either root or normal user, if that's related..

Thanks for looking at this bug, here's the latest stack trace and
session log for current CVS:

Program received signal SIGSEGV, Segmentation fault.
evaluate_subexp (expect_type=0x0, exp=0x0, pos=0xbfffed14,
noside=EVAL_NORMAL) at eval.c:71
71        return (*exp->language_defn->la_exp_desc->evaluate_exp)
(gdb) bt
#0  evaluate_subexp (expect_type=0x0, exp=0x0, pos=0xbfffed14,
noside=EVAL_NORMAL) at eval.c:71
#1  0x080f120d in evaluate_expression (exp=0x0) at eval.c:161
#2  0x080e159d in insert_bp_location (bpt=0x85208d0,
tmp_error_stream=0x8493008, disabled_breaks=0xbfffedb0,
    process_warning=0xbfffedb4, hw_breakpoint_error=0xbfffedb8) at
breakpoint.c:949
#3  0x080e1817 in insert_breakpoints () at breakpoint.c:1149
#4  0x081118f9 in keep_going (ecs=0xbfffeeb0) at infrun.c:2848
#5  0x0810ff76 in handle_inferior_event (ecs=0xbfffeeb0) at
infrun.c:2672
#6  0x0810f617 in wait_for_inferior () at infrun.c:996
#7  0x0810f3e5 in proceed (addr=1, siggnal=TARGET_SIGNAL_HUP, step=1) at
infrun.c:816
#8  0x0810c9c3 in step_1 (skip_subroutines=1, single_inst=0,
count_string=0x0) at infcmd.c:688
#9  0x0810c77e in next_command (count_string=0x0, from_tty=1) at
infcmd.c:585
#10 0x080c1b7e in do_cfunc (c=0xbfffed14, args=0x0, from_tty=1) at
cli/cli-decode.c:57
#11 0x080c356e in cmd_func (cmd=0x83f8c30, args=0x0, from_tty=1) at
cli/cli-decode.c:1627
#12 0x080989ef in execute_command (p=0x83e08e9 "", from_tty=1) at
top.c:733


the session log,

(gdb) b f90demo.f90 : 41
During symbol reading, unsupported tag: 'DW_TAG_module'.
During symbol reading, Attribute value is not a constant
(DW_FORM_block1).
Breakpoint 1 at 0x804b007: file f90demo.f90, line 41.
(gdb) r
Starting program: /home/david/f90demo

Breakpoint 1, sample () at f90demo.f90:86
warning: Source file is more recent than executable.

86      CALL MPI_INIT(ierr)
Current language:  auto; currently fortran
(gdb) watch i
During symbol reading, incomplete CFI data; unspecified registers (e.g.,
eax) at 0x804bc35.
Hardware watchpoint 2: i
(gdb) n
Error in re-setting breakpoint 2:
No symbol "i" in current context.
During symbol reading, incomplete CFI data; unspecified registers (e.g.,
eax) at 0xb7f3b612.
#

I know the patch I originally suggested could be a cure of the symptom,
rather than the cause - but as it's harmless, if we can't figure out why
it happens, it could be worth just committing anyway: all the patch does
is check a value is non-null, and if so takes action - without the patch
such a scenario will always segfault!

Cheers
David


       reply	other threads:[~2004-11-21  0:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <01c4cef8$Blat.v2.2.2$3fd12960@zahav.net.il>
2004-11-21  0:24 ` David Lecomber [this message]
2004-11-21  0:42   ` Daniel Jacobowitz
2004-11-21  5:29     ` Eli Zaretskii
2004-11-21  6:48       ` Daniel Jacobowitz
2004-11-21  5:19   ` Eli Zaretskii
2004-11-21  6:49     ` Daniel Jacobowitz
2004-11-21 10:36       ` David Lecomber
2004-11-21 19:40       ` Eli Zaretskii
2004-10-17  0:09 [PATCH] Seg fault whilst stepping when watch set David Lecomber
2004-10-25 16:10 ` [PATCH] Seg fault whilst stepping when watch set [ping!] David Lecomber
2004-11-01 22:05   ` [PATCH] Seg fault whilst stepping when watch set [ping!] [in breakpoint.c] David Lecomber
2004-11-02  4:38   ` Eli Zaretskii
     [not found]     ` <1099385491.31287.19.camel@cpc1-oxfd5-5-0-cust86.oxfd.cable.ntl.com>
2004-11-02 21:40       ` Eli Zaretskii
2004-11-03 12:08         ` David Lecomber
2004-11-17 21:38           ` David Lecomber
2004-11-03 18:09         ` Eli Zaretskii

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=1100996751.22991.39.camel@cpc2-oxfd5-5-0-cust91.oxfd.cable.ntl.com \
    --to=david@streamline-computing.com \
    --cc=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    /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