Closed Bug 919564 Opened 11 years ago Closed 11 years ago

shell/js-gdb.gdb catch handler has symbol error for __GI___sigaction

Categories

(Core :: JavaScript Engine, defect)

All
Linux
defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla27

People

(Reporter: luke, Assigned: luke)

Details

Attachments

(1 file)

I don't know if this is a per-gcc/gdb version problem, but I get an error when the current signal handler is executed:
  No symbol "__GI___sigaction" in current context.
However, the symbol __sigaction works fine.  Does this symbol work for you also?
(In reply to Luke Wagner [:luke] from comment #0)
> I don't know if this is a per-gcc/gdb version problem, but I get an error
> when the current signal handler is executed:
>   No symbol "__GI___sigaction" in current context.
> However, the symbol __sigaction works fine.  Does this symbol work for you
> also?
I remember that the problem was you can't just use "sigaction" as it aliases the struct sigaction and gdb didn't know how to handle the difference.

I had sometimes errors that the symbol wasn't found, but not every time (maybe only when compiling with clang++). Using __sigaction works fine for me.
Attached patch fix-js-gdb.gdbSplinter Review
Great, then let's try this.  This patch also fixes some sort of merge error introduced by http://hg.mozilla.org/mozilla-central/rev/2d2709188afa#l16.1
Assignee: general → luke
Status: NEW → ASSIGNED
Attachment #808802 - Flags: review?(bbouvier)
Attachment #808802 - Flags: review?(bbouvier) → review+
https://hg.mozilla.org/mozilla-central/rev/64ed8a633254
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla27
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: