Segmentation fault

[Daniel]

Binary package hint: dpkg

This is what I was doing:
Trying to install KDevelop package, then I accidentall moved the package to another filesystem, but dpkg had already started "Reading the database ... Leyendo la base de datos), then it crashed.

daniel@HannaPC:~/Desktop/2007-09-10/Otros/Otros$ sudo dpkg -i kdevelop_3.4.0-0ubuntu3_amd64.deb
Password:
Seleccionando el paquete kdevelop previamente no seleccionado.
(Leyendo la base de datos ...
********************************************** THIS IS WHEN I ERASED THE FILE ****************************************************
189357 ficheros y directorios instalados actualmente.)
Desempaquetando kdevelop (de kdevelop_3.4.0-0ubuntu3_amd64.deb) ...
dpkg-deb: fallo al leer el archivo `kdevelop_3.4.0-0ubuntu3_amd64.deb': No existe el fichero ó directorio

Fallo de segmentación (core dumped)

[Erik Andrén (erik-andren)]

In what way is this a bug?
Are you experiencing system stability issues afterwards?

[dwilches (dwilches)]

The program should not crash in that after realizing that the file doesn't
exist anymore:

dpkg-deb: fallo al leer el archivo `kdevelop_3.4.0-0ubuntu3_amd64.deb': No
existe el fichero ó directorio
Fallo de segmentación (core dumped)

On 9/11/07, Erik Andrén <email address hidden> wrote:
>
> In what way is this a bug?
> Are you experiencing system stability issues afterwards?
>
> --
> Segmentation fault
> https://bugs.launchpad.net/bugs/138887
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Daniel Wilches Maradei
<email address hidden>
<email address hidden>

[Ian Jackson (ijackson)]

Erik Andrén writes ("[Bug 138887] Re: Segmentation fault"):
> In what way is this a bug?

That's a ridiculous question. dpkg obviously shouldn't crash.

I will look into this.

Ian.

[Colin Watson (cjwatson)]

Ian fixed this a while back, but the bug never got closed for some reason.

dpkg (1.14.5ubuntu15) gutsy; urgency=low

  * Bugfixes to fd cleanup handling:
    - avoid closing fsys tarfile pipe twice even in normal
      operation - normally EBADF but might sometimes close some other
      desired fd and cause hideous doom. (LP: #137191.)
    - avoid duplicate attempts to [f]close in obscure error
      situations which might conceiveably close wrong fds
    - cast &fd to void* when passing to push_cleanup cu_closefd
    - fix parse.c:parsedb to use ehflag_normaltidy in a sane way
    - when passing &fd to push_cleanup cu_closefd, make fd always static
  * Bugfix in trigger deferred file processing: reset lexer start state
    when calling yyrestart (has no effect except after parsing/reading
    errors in the deferred file).
  * Fix some error handling bugs in tarfn.c:
    - Avoid freeing uninitialised h.[Link]Name (can cause crash if .deb
      becomes unreadable while we start up). (LP: #138887.)
    - Use m_malloc instead of malloc (and ditch ad-hoc error handling).

 -- Ian Jackson <email address hidden> Thu, 20 Sep 2007 18:12:20 +0100