[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Segfault in current bzr
From: |
Eli Zaretskii |
Subject: |
Re: Segfault in current bzr |
Date: |
Mon, 27 Sep 2010 22:14:10 +0200 |
> From: Lars Magne Ingebrigtsen <address@hidden>
> Date: Mon, 27 Sep 2010 21:59:11 +0200
>
> Lars Magne Ingebrigtsen <address@hidden> writes:
>
> > #2 0x00000000005a5dd9 in wait_reading_process_output (
> > time_limit=<value optimized out>, microsecs=<value optimized out>,
> > read_kbd=-1, do_display=<value optimized out>,
> > wait_for_cell=<value optimized out>, wait_proc=0x0, just_wait_proc=0)
> > at process.c:5072
>
> Which must be this code:
>
> FD_CLR (channel, &connect_wait_mask);
> if (--num_pending_connects < 0)
> abort ();
You can't really know, in an optimized build. GCC is very good in
collapsing multiple calls to th same function into a single call.
I suggest to build with -O0, and then trying to crash. At least then
the backtrace and the line numbers won't lie. And you get to actually
see the values of the variables as a bonus, instead of all those
<value optimized out> thingies.
- Segfault in current bzr, Lars Magne Ingebrigtsen, 2010/09/27
- Re: Segfault in current bzr, Lars Magne Ingebrigtsen, 2010/09/27
- Re: Segfault in current bzr, Lars Magne Ingebrigtsen, 2010/09/27
- Re: Segfault in current bzr,
Eli Zaretskii <=
- Re: Segfault in current bzr, Lars Magne Ingebrigtsen, 2010/09/27
- Re: Segfault in current bzr, Lars Magne Ingebrigtsen, 2010/09/27
- Re: Segfault in current bzr, Lars Magne Ingebrigtsen, 2010/09/27
- Re: Segfault in current bzr, Jan Djärv, 2010/09/27
- Re: Segfault in current bzr, Lars Magne Ingebrigtsen, 2010/09/27
- Re: Segfault in current bzr, David Kastrup, 2010/09/27
- Re: Segfault in current bzr, Eli Zaretskii, 2010/09/27