Mario wrote:
I'd like to help :-) I wanted to avoid a core dumped but you told
me that's a normal thing for a SIGQUIT signal.
Did you try running `ulimit -c 0` first? That should do what you want -
prevent generation of the dump file.
Regards, Philip.
--
Philip Yarra
Senior Software Eng
On 19/12/06, Andrew Dunstan <[EMAIL PROTECTED]> wrote:
This normally a SIGQUIT, and on my machine at least the default action for
that is a core dump. Perhaps you need to say what you are trying to do and
why.
I'd like to help :-) I wanted to avoid a core dumped but you told
me that's a no
On 19/12/06, Alvaro Herrera <[EMAIL PROTECTED]> wrote:
I think the problem Mario is really trying to solve is quitting at
psql's "Password: " prompt. Ctrl-C is ignored at that point apparently.
SIGQUIT (thus Ctrl-\ in most people's setup) does it but it also dumps
core.
yes, that is true an
Jeremy Drake wrote:
> On Wed, 20 Dec 2006, Philip Yarra wrote:
>
> > Mario wrote:
> > > Even if you get a core dumped every time you press CTRL+\ ? why?
> >
> > Try ulimit -c 0, then run it (you should get no core dump)
> > Then ulimit -c 50, then run it (you should get a core dump)
> >
>
On Wed, 20 Dec 2006, Philip Yarra wrote:
> Mario wrote:
> > Even if you get a core dumped every time you press CTRL+\ ? why?
>
> Try ulimit -c 0, then run it (you should get no core dump)
> Then ulimit -c 50, then run it (you should get a core dump)
>
> SIGQUIT is supposed to dump core. Ul
"Mario" <[EMAIL PROTECTED]> writes:
> On 20/12/06, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
> >
> > This isn't a bug. It's working as designed.
>
> Even if you get a core dumped every time you press CTRL+\ ? why?
That's what C-\ does. Try it with any other program:
$ sleep 1
Quit (core d
Mario wrote:
Even if you get a core dumped every time you press CTRL+\ ? why?
Try ulimit -c 0, then run it (you should get no core dump)
Then ulimit -c 50, then run it (you should get a core dump)
SIGQUIT is supposed to dump core. Ulimit settings can suppress
generation of core files.
Mario wrote:
> On 20/12/06, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
>> Mario wrote:
>> > When psql is running and CRTL + \ is pressed, a core dumped show up.
>> > In first place I ran psql into gdb, saw the backtrace and I believed
>> > it was a libc6 bug and I reported to my distro security t
On 20/12/06, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
Mario wrote:
> When psql is running and CRTL + \ is pressed, a core dumped show up.
> In first place I ran psql into gdb, saw the backtrace and I believed
> it was a libc6 bug and I reported to my distro security team
> https://launchpad.n
Mario wrote:
> When psql is running and CRTL + \ is pressed, a core dumped show up.
> In first place I ran psql into gdb, saw the backtrace and I believed
> it was a libc6 bug and I reported to my distro security team
> https://launchpad.net/distros/ubuntu/+source/glibc/+bug/76437
This isn't a bu
When psql is running and CRTL + \ is pressed, a core dumped show up.
In first place I ran psql into gdb, saw the backtrace and I believed
it was a libc6 bug and I reported to my distro security team
https://launchpad.net/distros/ubuntu/+source/glibc/+bug/76437
Ubuntu edgy has got libc-2.4, a fri
11 matches
Mail list logo
