Re: Help getting backtrace in gdb

[Noam Postavsky]

On Tue, Jun 27, 2017 at 6:01 PM, Kaushal Modi <address@hidden> wrote:
>
> My assumption was that Fsignal would get called before the seg fault.

I would not expect it to be called, if you're strictly following the
recipe for Bug#27504.

>>
>> You can try evaluating (signal 'wrong-number-of-arguments '(x y)) to
>> see if your Fsignal breakpoint is working.
>
>
> Nope, it does not work..
> I get the backtrace in the gdb-launched emacs but no breakpoint in the gdb.
>
> The gdb shows just this:

Hmm, it didn't stop at all? Can you put a breakpoint in 'main'?

> Should I be concerned about this part:
>
> =====
> SIGINT is used by the debugger.
> Are you sure you want to change it? (y or n) [answered Y; input not from
> terminal]
> =====

No that's normal, it's from this thing in emacs/src/.gdbinit:

# Don't enter GDB when user types C-g to quit.
# This has one unfortunate effect: you can't type C-c
# at the GDB to stop Emacs, when using X.
# However, C-z works just as well in that case.
handle 2 noprint pass