Le 04.06.2014 15:48, Christoph Berg a écrit :
Control: tag -1 moreinfo
Re: bmorel 2014-06-04
<20140604132642.9797.58545.reportbug@D2SI-P07-2.D2SI>
Package: pgadmin3
Version: 1.18.1-3
Severity: important
File: pgadmin
Tags: upstream
Dear Maintainer,
*** Reporter, please consider answering these questions, where
appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
Can you provide any details on this? What did you do? What's the
output? Can you provide a backtrace?
Christoph
Hello.
Honestly, the crash is quite random.
One thing which *might* be a cause could be that I am using a ssh
connection: I first go on a distant server ( which does not have the
database installed on it, but which is allowed to access the db ) so
that pgadmin can then access the real DB server.
I do not remember having that crash when working with my local database
or with a database in a VM on my computer.
About providing a backtrace... I have started pgadmin3 through my
terminal, and the only thing it showed was "memory corruption or double
free". If you have some idea about how to have more informations about
this crash, I would be happy to investigate further.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
