>Description:
Mysqldump seg faults if compiled with openssl support.
gdb output:
Starting program: /usr/local/bin/mysqldump -cf anydb
Program received signal SIGSEGV, Segmentation fault.
0xff24db6c in mysql_options () from /usr/local/lib/mysql/libmysqlclient.so.15
(gdb) bt
#0 0xff24db6c
%eax)
> 0x81fa94a :
> jne0x81fa942
> 0x81fa94c : mov %ebp,%esp
> 0x81fa94e : pop%ebp
> 0x81fa94f : ret
> End of assembler dump.
> (gdb)
>
>
> List:MySQL General Discussion« Previous MessageNext Message »
> From:Michael BacarellaDat
94e : pop%ebp
0x81fa94f : ret
End of assembler dump.
(gdb)
List:MySQL General Discussion« Previous MessageNext Message »
From:Michael BacarellaDate:January 26 2004 6:21pm
Subject:Re: MySQL 3.23.58 seg faults occasionally
> > the crashes below happen in independent are
> > the crashes below happen in independent areas of code. The 2 first are
> > inside InnoDB, and the third inside MySQL. This looks like random thread
> > crashes, or random memory corruption.
>
> My colleague tells me that the third stack trace (the one inside MySQL)
> is from a RESET MASTER. T
> the crashes below happen in independent areas of code. The 2 first are
> inside InnoDB, and the third inside MySQL. This looks like random thread
> crashes, or random memory corruption.
My colleague tells me that the third stack trace (the one inside MySQL)
is from a RESET MASTER. This server u
support from http://www.mysql.com/support/index.html
.
List:MySQL General Discussion« Previous MessageNext Message »
From:Michael BacarellaDate:January 16 2004 12:32am
Subject:MySQL 3.23.58 seg faults occasionally
First we cut to the chase with a resolved stack trace from
First we cut to the chase with a resolved stack trace from
the most recent crash:
0x80c23d5 handle_segfault__Fi + 425
0x40022f54 _end + 935506260
0x822cdef btr_search_build_page_hash_index + 4771
0x82281c3 btr_search_info_update_slow + 919
0x8213f9e btr_cur_search_to_nth_level + 3154
0x81e9dce row
Jochen Wiedman asked that I post this stack trace.
Please cc me on any replies, as I'm not subscribed to the list.
The original problem description is at the end.
Cheers, Dave
Original Message
Subject: Re: MySQL segmentation faults...
Date: Thu, 18 Sep 2003 20:59:57 +0200
Jochen Wiedman asked that I post this stack trace.
Please cc me on any replies, as I'm not subscribed to the list.
The original problem description is at the end.
Cheers, Dave
Original Message
Subject: Re: MySQL segmentation faults...
Date: Thu, 18 Sep 2003 20:59:57 +0200
Hi,
I'm trying to get a version of MySQL 4.1.0 installed on my (Gentoo Linux)
machine. I have a copy of MySQL 4.0.13 already installed, using Gentoo's
ebuilds, but am trying to install 4.1.0 in a side-by-side configuration.
(Into /usr/local/mysql_alpha, talking to port 3300) - So I can run 4.0
Chris,
Monday, November 04, 2002, 11:33:22 PM, you wrote:
CW> Same thing here. Local sockets are working find. Remote connections
CW> segfault. Getting ready to try the *workaround*. I am using mysql from
CW> the stock install of RH8.0
Take a look at this:
https://bugzilla.redhat.com/bu
Whats the workaround?? How should I start with mysql with defualt
setting in a command line???
Thanks guys
On Monday, November 4, 2002, at 01:33 PM, Chris West wrote:
[EMAIL PROTECTED]
-
Before posting, please check:
http:/
Same thing here. Local sockets are working find. Remote connections
segfault. Getting ready to try the *workaround*. I am using mysql from
the stock install of RH8.0
Chris
-
Before posting, please check:
http://www.mysql
daemon
actually seg faults. #1 - The segfault message (below) is not logged by the
safe_mysqld script so that may want to be looked at. After a while of
testing I discovered that if the --skip-name-resolve is specified in the
my.cnf file then the server accepts remote connections. From the output of
Hi!
> "Sinisa" == Sinisa Milivojevic <[EMAIL PROTECTED]> writes:
Sinisa> Van writes:
>>
>> Sinisa:
>>
>> As in possibly the binutils problem? I've had to use:
>> gcc version 2.95.4 20011006 (Debian prerelease)
>> to do any builds of things that need glibc2.3.2, but had to revert to the p
Van writes:
>
> Sinisa:
>
> As in possibly the binutils problem? I've had to use:
> gcc version 2.95.4 20011006 (Debian prerelease)
> to do any builds of things that need glibc2.3.2, but had to revert to the potato
> compiler to compile the kernel.
>
> What's the recommended compiler/glibc for
Sinisa Milivojevic wrote:
>
> Van writes:
> > Running a Debian kernel 2.4.9 and MySQL 4.0 compiled and appears to be running.
> >
> > vanboers@tempe:~$ strace ./mysqlscan 1 2
> > execve("./mysqlscan", ["./mysqlscan", "1", "2"], [/* 17 vars */]) = 0
...
> > brk(0x1200ba000)
Van writes:
> Greetings:
>
> Running a Debian kernel 2.4.9 and MySQL 4.0 compiled and appears to be running.
> Selects against the local database appear to work fine.
>
> I've got a couple userland applications that update data in remote 3.23.x
> servers that no longer work. I haven't seen any
Greetings:
Running a Debian kernel 2.4.9 and MySQL 4.0 compiled and appears to be running.
Selects against the local database appear to work fine.
I've got a couple userland applications that update data in remote 3.23.x
servers that no longer work. I haven't seen anything related to this in t
On Friday 26 October 2001 11:12, [EMAIL PROTECTED] wrote:
> Hello,
>
> I am experiencing seg faults in seemingly innocent code with MySQL version
4.0.0
> and the embedded library, libmysqld.
> The fault only happens when calling particular functions, specifically
> mysql_ping
Hi!
On Oct 26, [EMAIL PROTECTED] wrote:
> Hello,
>
> I am experiencing seg faults in seemingly innocent code with MySQL version 4.0.0
> and the embedded library, libmysqld.
> The fault only happens when calling particular functions, specifically
> mysql_ping() and mysql_query(
Hello,
I am experiencing seg faults in seemingly innocent code with MySQL version 4.0.0
and the embedded library, libmysqld.
The fault only happens when calling particular functions, specifically
mysql_ping() and mysql_query(). There might be others, but these are the only
ones I've fou
Werner Stuerenburg wrote:
>> The main aspect I'm interested in is avoiding data loss. So I want that any
>> change to database must immediatly (or at least on regular intervals) be
>> made persistent. Is there any configurable parameter to do this?
>
>
>
> You may want to read about transact
> The main aspect I'm interested in is avoiding data loss. So I want that any
> change to database must immediatly (or at least on regular intervals) be
> made persistent. Is there any configurable parameter to do this?
You may want to read about transaction services.
--
Herzlich
Werner Stuer
Hi all!
I'm thinking about using MySql in an application over an unstable system.
Database will probably be subject to system crashes and unexpected lack of
power supply.
So I need the database has a strong Persistence policy and, if possible,
that it allows the user
to set some "parameters" to in
is a heap I had to take over when I got the job. I'm not sure if
there are lib conflicts, but... I'll take a closer look.
>Submitter-Id:
>Originator:Seer Snively
>Organization:
-- Seer Snively
-- Lead Slacker
-- Nethelp International
>
>MySQL support:
26 matches
Mail list logo
