[perl #17683] [PATCH] Fixes segfault in pdb

[JüRgen BöMmels]

# New Ticket Created by Jürgen Bömmels
# Please include the string: [perl #17683]
# in the subject line of all future correspondence about this issue.
# <URL: http://rt.perl.org/rt2/Ticket/Display.html?id=17683 >

Hi,

When you use pdb and hit just <ENTER> you get a segfault. Thats quite
anoying especially if you are used to gdbs behaviour.

The attached patch fixes this by just ignoring empty lines.

bye
b.

-- attachment 1 ------------------------------------------------------
url: http://rt.perl.org/rt2/attach/38900/31614/ec6c32/debug.diff

[Aldo Calpini]

Jürgen Bömmels wrote:
> Hi,
>
> When you use pdb and hit just <ENTER> you get a segfault. Thats
> quite anoying especially if you are used to gdbs behaviour.
>
> The attached patch fixes this by just ignoring empty lines.

this doesn't seem to me how pdb is supposed to work.
docs/debugger.pod says:

A blank line always repeat the last command entered.

and that's also perl -d behaviour.
either fix it differently, or patch the documentation too :-)

cheers,
Aldo

__END__
$_=q,just perl,,s, , another ,,s,$, hacker,,print;

[Juergen Boemmels]

Aldo Calpini <dada...@alos.it> writes:

> Jürgen Bömmels wrote:
> > Hi,
> >
> > When you use pdb and hit just <ENTER> you get a segfault. Thats
> > quite anoying especially if you are used to gdbs behaviour.
> >
> > The attached patch fixes this by just ignoring empty lines.
>
> this doesn't seem to me how pdb is supposed to work.
> docs/debugger.pod says:
>
> A blank line always repeat the last command entered.
>
> and that's also perl -d behaviour.
> either fix it differently, or patch the documentation too :-)

Everything you want.
But I don't think the previous segfault was intended behaviour.

A blank line always gets a segfault.

Ok, after some more debugging of the debugger i got it working like
documented.

bye
b.